JSON-LD has an official vocabulary at https://www.w3.org/ns/json-ld that describes its keywords and processing concepts as RDF terms (classes like json-ld:Context, json-ld:TermDefinition, individuals like json-ld:set, json-ld:list, etc.).
YAML-LD introduces its own concepts — YAML tags, anchors, aliases, multi-document streams, and YAML-specific processing rules — that are not captured by the JSON-LD vocabulary.
We should define a YAML-LD namespace (e.g. https://www.w3.org/ns/yaml-ld or similar) with an ontology that:
- Describes YAML-LD-specific terms (tags, anchors, aliases, etc.)
- Extends the JSON-LD vocabulary where appropriate
- Supports content negotiation (HTML for humans, Turtle/JSON-LD for RDF clients)
This would allow tooling and documentation to refer to YAML-LD concepts using stable, dereferenceable URIs.
JSON-LD has an official vocabulary at https://www.w3.org/ns/json-ld that describes its keywords and processing concepts as RDF terms (classes like
json-ld:Context,json-ld:TermDefinition, individuals likejson-ld:set,json-ld:list, etc.).YAML-LD introduces its own concepts — YAML tags, anchors, aliases, multi-document streams, and YAML-specific processing rules — that are not captured by the JSON-LD vocabulary.
We should define a YAML-LD namespace (e.g.
https://www.w3.org/ns/yaml-ldor similar) with an ontology that:This would allow tooling and documentation to refer to YAML-LD concepts using stable, dereferenceable URIs.