Request for comments: OO-LD v1.0.0-rc.1 (community review before v1.0)

[simontaurus]

OO-LD (Object-Oriented Linked Data) unifies JSON Schema and JSON-LD in a single document: one artefact that is at once a valid JSON Schema and a referenceable JSON-LD remote context. v1.0.0-rc.1 is a release candidate; we are requesting community review before tagging v1.0. Critique of any part is welcome.

What to read (about 20-30 min)

• Specification (v1.0.0-rc.1): https://oo-ld.org/1.0.0-rc.1/spec/
• Guide (introduction, get-started, use-cases, worked mappings, reference): https://oo-ld.org/1.0.0-rc.1/
• Playgrounds: JSON/YAML, Python
• Reference implementation: OpenSemanticLab (live demo)

Where we would most value your eyes

Linked data / JSON-LD

• The "a schema is consumed as a JSON-LD remote context, never as a JSON-LD document" asymmetry, and the composition rules that reflect each $ref into a scoped @context - correct and idiomatic?
• Term synonyms (x-oold-context) and their promotion into @context (one IRI selected per profile) - is this the right mechanism?
• Governance: which parts belong in the W3C JSON-LD CG versus IETF? (create specification draft #14)

JSON Schema / API / LLM tooling

• The tiered semantic delivery (native @context for JSON Schema 2020-12 / OpenAPI 3.1 / MCP; x-jsonld-context/x-jsonld-type for OpenAPI 3.0; folding into title/description for strict structured-output) - correct and lossless? (Normative semantic-delivery profiles + conformance (@context / x-jsonld-* / title+description) #77)
• x-oold-ref vs $ref for the possibly-cyclic reference graph.

How to give feedback

Comment here, or open focused issues and link them. We aim to respond within a few days and to fold accepted feedback into v1.0.

[LukasOro]

I would like to express a concern that surfaced when trying to port the EU Battery Passport model from SAMM to
OO-LD regarding the round trip safety of the @type alias "type". I have proposed a fix for the @context in issue #117

[simontaurus]

This request for comments has been announced in the following places, in case discussion starts there rather than here:

• W3C JSON-LD community: Polyglot Modeling w3c/yaml-ld#19 (the "Polyglot Modeling" thread)
• W3C JSON-LD Working Group: Best practice: a document that is both a JSON Schema and a JSON-LD remote context (OO-LD) w3c/json-ld-bp#92 - proposing the "a document that is both a JSON Schema and a JSON-LD remote context" pattern as a best practice
• JSON-LD Frame -> JSON Schema Mapping w3c/json-ld-framing#181 - related work on frame to JSON Schema mapping

Feedback from any of those threads will be consolidated here and folded into v1.0 (#25, #27).