Decisions ODR Corpus
The Ontology Decision Records (ODRs) are the Linked Data
Council's historical deliberations and OPDA's current local modelling decisions —
the why behind the approach. Each record identifies its own scope and
authority, with the options considered, chosen outcome and consequences.
66 records in total — every one is a live page rendered from its markdown.
Records marked ✓ diagrams have been enriched with illustrative Mermaid
diagrams per ADR-0024 ; the rest render as text until
their enrichment wave lands.
No. Title Kind Status Page 0001 Linked Data Council: Review Methodology methodology accepted view · ✓ diagrams 0002 Ontology Languages and Vocabularies Adopted architecture accepted view · ✓ diagrams 0003 PDTF to Ontology: Programme and Work Breakdown programme accepted view · ✓ diagrams 0004 PDTF Ontology Foundation architecture accepted view · ✓ diagrams 0005 Property & Land: The Identity Crux pattern accepted view · ✓ diagrams 0006 Agents & Roles pattern accepted view · ✓ diagrams 0007 Transactions & Lifecycle pattern accepted view · ✓ diagrams 0008 Property Descriptive Attributes pattern accepted view · ✓ diagrams 0008d Authority-Retrieved Artefacts pattern accepted view 0009 Claims, Evidence & Provenance pattern accepted view · ✓ diagrams 0010 Overlay Profile Mechanism architecture accepted view · ✓ diagrams 0011 Enumeration Vocabularies pattern accepted view · ✓ diagrams 0012 Data-Governance Layer architecture accepted view · ✓ diagrams 0013 SHACL Validation & Severity architecture accepted view · ✓ diagrams 0014 Vocabulary Catalogue Amendments pattern superseded view · ✓ diagrams 0015 Address & Geography pattern accepted view · ✓ diagrams 0016 W3C Verifiable Credentials / DID Compatibility Layer mapping proposed view · ✓ diagrams 0017 SHACL-AF Non-Blocking Data-Quality Rules pattern accepted view · ✓ diagrams 0018 DPV Class-Level Co-Annotation Pattern pattern accepted view · ✓ diagrams 0019 Bounded-Context Representation pattern accepted view · ✓ diagrams 0020 Bounded-Context Scheme and Term→Context Mapping pattern accepted view · ✓ diagrams 0021 Deferred Form/Profile-Layer Enhancements architecture accepted view 0022 Descriptive-Layer Import Strategy & Property Categorisation architecture accepted view 0023 Descriptive-Layer Follow-On Council Roadmap programme accepted view 0024 Curated Category-G Walk — Leaf Dispositions and Modelling Rules pattern accepted view 0025 Entailment Regime and Inference Semantics architecture accepted view 0026 OWL-RL-Safe Ruleset Adoption and Unevaluated Modelling Axioms architecture accepted view 0027 Classification, Roles, Inheritance, and SKOS — opda Modelling Doctrine architecture accepted view 0028 Descriptive-Layer Conversion — Completeness Reconciliation programme accepted view 0029 Inference/Validation Boundary and the Entailment-Regime Disposition architecture accepted view 0030 Foundational-Ontology Choice: UFO-as-Lens, Scoped to the Relator Spine architecture accepted view 0031 opda:ufoCategory and the Upper-Ontology Layer architecture accepted view 0032 Relationship Layer — Reify Inter-Entity Associations as OWL Object Properties pattern proposed view 0033 OWL/RDFS Axioms as Documentary AI-Signal — the Consolidated Doctrine architecture proposed view 0034 Relationship-Residue Completion — Events, Information Objects, and the Aboutness/Provenance Boundary pattern proposed view 0035 RML as OPDA's Bidirectional Schema-Provenance Verification Mechanism architecture accepted view 0036 Independent classification facets methodology accepted view 0037 Property applicability and standard RDFS semantics methodology accepted view 0038 Independent contexts with explicit semantic bridges methodology accepted view 0039 SKOS enumerations with SHACL closure methodology accepted view 0040 Closed enumerations and open reference populations methodology accepted view 0041 Kinds, roles and phases methodology accepted view 0042 Place properties at the level that introduces their meaning methodology accepted view 0043 A bounded OWL surface with explicit validation methodology accepted view 0044 Selective materialisation and SHACL rules methodology accepted view 0045 Boundaries follow accountable language methodology accepted view 0046 Eight selected modelling concerns methodology accepted view 0047 Domain structure uses one modelling standard methodology accepted view 0048 Vocabulary and taxonomy from evidence methodology accepted view 0049 Govern classification metadata independently methodology accepted view 0050 One validation framework for authored and generated models methodology accepted view 0051 Human-reviewed mappings between contexts methodology accepted view 0052 Provenance, attribution and extraction quality methodology accepted view 0053 Temporal state, validity and recorded history methodology accepted view 0054 Sensitivity classification and bounded policy modelling methodology accepted view 0055 Dublin Core annotations alongside classification metadata methodology accepted view 0056 SSSOM provenance for cross-context mappings methodology accepted view 0057 Conditional ODRL policy use through the DPV profile methodology accepted view 0058 Named RDF 1.2 reifiers for mapping provenance methodology accepted view 0059 Criterion-based identity across contexts: map before merging methodology accepted view 0060 Distinguish data domains, subject areas and bounded contexts methodology accepted view 0061 Check identity, rigidity, dependence and unity with explicit OntoClean constraints methodology accepted view 0062 Organise by concern while preserving independent classification and model authority methodology accepted view 0063 Foundational analysis without external upper-ontology subsumption methodology accepted view 0064 Queryable strategic context maps linked to exact term mappings methodology accepted view 0065 OPDA namespace topology and stable identifiers methodology accepted view
About ODRs
An ODR is one of two kinds of decision:
An ontological commitment (kind: pattern or mapping) —
a declaration about what kinds of entities the domain contains, what their identity
criteria are, what Roles or Phases they pass through.
An artefact-engineering decision (kind: architecture,
methodology, or programme) — a decision about how to structure,
name, govern, sequence, or process the artefacts that encode the ontology.
Current ODRs follow the project's decision-record conventions: explicit status,
context, alternatives, consequences and confirmation. Authorised corrections are
recorded with an updated date and amendment history. Historical records retain
their original context and policy; new records make their scope and relationships explicit.
Methodology
All ODRs are ratified by the Linked Data Council — a simulated panel
of 9 named linked-data and ontology authorities whose published positions are used
to evaluate modelling decisions from multiple perspectives. See
ODR-0001 for the full methodology.
Comments
Loading comments…
Sign in to post a comment