[All Lists] [By Thread] [By Date] [Previous] [Next]

From: Devorah
Subject: Vocabulary file
Date: 6 Av 5782

Following the registry format discussion, I have drafted the vocabulary file.

The @context in registries references https://dep-specs.org/schema/registry. This URL should return a JSON-LD context document. I have written one.

{
  "@context": {
    "@vocab": "https://dep-specs.org/schema/registry#",
    "xsd": "http://www.w3.org/2001/XMLSchema#",
    "registry": { "@type": "xsd:string" },
    "publisher": { "@type": "xsd:string" },
    "version": { "@type": "xsd:string" },
    "contexts": { "@container": "@index" },
    "label": { "@type": "xsd:string" },
    "label_he": { "@type": "xsd:string" },
    "description": { "@type": "xsd:string" },
    "type": { "@type": "xsd:string" },
    "uri": { "@type": "@id" },
    "see_also": { "@type": "@id", "@container": "@set" },
    "equivalent_to": { "@container": "@set" },
    "deprecated": { "@type": "xsd:boolean" },
    "replaced_by": { "@type": "xsd:string" }
  }
}

This is 18 lines. It maps our terms to XSD datatypes. JSON-LD processors can expand it. Regular JSON parsers ignore the @context.

I believe this addresses the requirements.

Thread:

• Vocabulary file, Devorah (6 Av 5782)
• Re: Vocabulary file, R. Nachmani (6 Av 5782)
• Re: Vocabulary file, Dr. Lobel (6 Av 5782)
• Re: Vocabulary file, R. Halevi (11 Av 5782)

[Previous] [Next]