The specs are using JSON-LD keywords for type and id directly: @id and @type. Using aliases id and type instead should be considered. Aliases would make the DTS more open to serve domain-specific or project-specific datasets (see discussion of #280).
context snippet for aliasing:
"id": {"@type": "@id", "@id": "@id"},
"type": {"@type": "@id", "@id": "@type"},
When #300 is considered positively, the type alias may need revision.
An example for a popular ontology using aliases for @type and @id is the Web Annotation Data Model, see https://www.w3.org/ns/anno.jsonld .
The specs are using JSON-LD keywords for type and id directly:
@idand@type. Using aliasesidandtypeinstead should be considered. Aliases would make the DTS more open to serve domain-specific or project-specific datasets (see discussion of #280).context snippet for aliasing:
When #300 is considered positively, the
typealias may need revision.An example for a popular ontology using aliases for
@typeand@idis the Web Annotation Data Model, see https://www.w3.org/ns/anno.jsonld .