v1 namespace
Stable URIs for the Obligation-First v0.1 specification. Every artifact below dereferences to a real document — schema, crosswalk, or worked-example record. Adopters fetch the context at https://obligationfirst.org/v1/context.jsonld; terms expand under the permanent https://w3id.org/of/v1/ vocabulary.
JSON-LD context
/v1/context.jsonldCanonical context. Adopters reference this URL in their records.
JSON Schemas
/v1/schema/authority.schema.jsonof:Authority/v1/schema/instrument.schema.jsonof:Instrument/v1/schema/term.schema.jsonof:Term/v1/schema/obligation.schema.jsonof:Obligation (Requirement / Restriction / Permission / Reparation)/v1/schema/proceeding.schema.jsonof:Proceeding/v1/schema/allegation.schema.jsonof:Allegation/v1/schema/determination.schema.jsonof:Determination/v1/schema/executable-encoding.schema.jsonPolymorphic executable-encoding reference
Worked-example records
Three real record sets round-tripped through v0.1, served as JSON for direct fetch and validation. The @id values inside reference adopter-domain URLs (everyailaw.com, aiincidentlaw.org, publedge.org) are aspirational, illustrating what each adopter will mint when binding. The JSON bytes are served here.
/v1/examples/colorado-sb24-205/records/13 records — Colorado AI Act, three-layer reality/v1/examples/air-canada/records/5 records — Moffatt v. Air Canada, proceeding strand/v1/examples/publedge-jia-utah-72/records/5 records — Utah OAIP JIA, joint interpretation
Source-of-truth links
PROTOCOL.mdThe specificationreference/crosswalks/gist, LegalRuleML, Akoma Ntoso, ELI/ECLICHANGELOG.mdVersion history