Format matrix
Format matrix
Per-resource format availability against the OPDA namespace https://opda.org.uk/pdtf/*. These IRIs are identifiers; resolution is optional and aspirational (see content negotiation). When served, opda.org.uk is the origin directly — no W3C PICG redirect (ADR-0006 dropped it when the base moved to opda’s own domain). The matrix below shows what that origin would return per Accept header.
Headline matrix
| Resource path | text/turtle | application/ld+json | application/rdf+xml | text/html | Notes |
|---|---|---|---|---|---|
https://opda.org.uk/pdtf/ | yes | yes | yes | redirect to docs | Foundation namespace; serves foundation.ttl (15 triples) |
https://opda.org.uk/pdtf/harness/release/1.0.0/ | yes | yes | yes | yes | Version-IRI; immutable per release |
https://opda.org.uk/pdtf/scheme/ | yes | yes | yes | redirect to docs | SKOS scheme aggregate (873 triples; 23 schemes) |
https://opda.org.uk/pdtf/graph/<module> | yes | yes | yes | yes | Module class graph where <module> ∈ {property, agent, transaction, claim, governance, descriptive} (the modules contribute to the one …/pdtf/ ontology; no separate per-module ontology IRI) |
https://opda.org.uk/pdtf/graph/<module>-shapes | yes | yes | yes | redirect to docs | Per-module SHACL shapes graph |
https://opda.org.uk/pdtf/graph/<module>-annotations | yes | yes | yes | redirect to docs | Per-module DPV annotations graph |
https://opda.org.uk/pdtf/graph/shapes | yes | yes | yes | redirect to docs | Foundation meta-shapes |
https://opda.org.uk/pdtf/graph/annotations | yes | yes | yes | redirect to docs | Foundation meta-annotations |
https://opda.org.uk/pdtf/shape/profiles/baspi5 | yes | yes | yes | docs page | BASPI5 overlay profile (488 triples) |
https://opda.org.uk/pdtf/harness/release/profiles/baspi5/0.1.0/ | yes | yes | yes | yes | BASPI5 profile release snapshot (owl:versionIRI target) |
https://opda.org.uk/pdtf/<EntityLocalName> | yes | yes | yes | Concept-tier page | Per-entity dereference (e.g. …/Property, …/LegalEstate, …/Buyer) |
https://opda.org.uk/pdtf/derived/opda-validation.ttl | yes | yes | yes | redirect to docs | Pending composer activation |
https://opda.org.uk/pdtf/derived/opda-ui.ttl | yes | yes | yes | redirect to docs | Pending composer activation |
https://opda.org.uk/pdtf/derived/opda-inference.ttl | yes | yes | yes | redirect to docs | Pending composer activation |
https://opda.org.uk/pdtf/context.jsonld | no (JSON-only) | yes | no | no | Canonical JSON-LD @context (see jsonld-context.md) |
Per-entity dereference behaviour
A request like GET https://opda.org.uk/pdtf/Property with Accept: text/turtle returns the fragment of opda-property.ttl containing opda:Property plus the foundation-level context triples needed for the entity to make sense in isolation:
- The
opda:Propertyowl:Classdeclaration rdfs:subClassOfchain to the nearestowl:Classin the foundation graph (transitive)rdfs:label,rdfs:comment,skos:scopeNote,dct:sourceonopda:Property- The
opda:andxsd:prefix declarations - The
https://opda.org.uk/pdtf/owl:Ontologyheader (so the consumer knows which release the fragment came from)
This is the “concise bounded description” pattern: enough context to validate the fragment in isolation, but not the whole module. Consumers needing the full module fetch https://opda.org.uk/pdtf/graph/property instead.
Conditional requests
Origin server honours If-None-Match (ETag-based) and If-Modified-Since (Last-Modified-based). Version-IRI URIs (/1.0.0/, /0.1.0/) are immutable, so consumers can cache aggressively (Cache-Control: public, max-age=31536000, immutable). Non-version-IRI URIs revalidate per cycle.
Source ADR
- ADR-0006 — w3id.org/opda ontology namespace — namespace scheme + opda-direct (optional) resolution.
- ADR-0013 — Overlay profile emission — BASPI5 + derived-profile URLs.
Comments