Open Property Data Association
Smart Property Data Trust Framework
Become a member Join a working group

    ADR Corpus

    The Architecture Decision Records (ADRs) capture the engineering decisions behind the OPDA programme — the site architecture, the ontology generator and CI gates, the modelling toolchain, and the hosting/deployment pipeline. Each record states the context, the options weighed, and the decision taken.

    88 records in total — every one is a live page rendered from its MADR markdown. ADRs are the counterpart to the Ontology Decision Records (ODRs): ADRs decide how we build; ODRs decide what the model means.

    No. Title Status Page
    0001 Selective adoption of DCAM v3 and DAMA-DMBOK2 elements accepted view
    0002 Folder hierarchy and slug taxonomy accepted view
    0003 Refactor to idiomatic Astro architecture accepted view
    0004 Accreditation Directory spec accepted view
    0005 Deferred work register from the 2026-05-18 implementation push accepted view
    0006 Ontology namespace at w3id.org/opda/ via W3C PICG redirect accepted view
    0007 Ontology generator — deterministic emission specification accepted view
    0008 Ontology generator — implementation infrastructure accepted view
    0009 Foundation TTL emission accepted view
    0010 SKOS vocabulary emission accepted view
    0011 Module TBox emission accepted view
    0012 SHACL shapes + DPV annotation emission accepted view
    0013 Overlay profile emission accepted view
    0014 BASPI5 round-trip MVP harness + diagnostic exemplar regression accepted view
    0015 Integrate 4-tier ontology manual into the Astro site accepted view
    0016 Manual content-collection wiring + site navigation accepted view
    0017 Manual component library (12 reusable components + accent tokens) accepted view
    0018 Manual build-time remark + rehype plugins accepted view
    0019 Modelling-section / manual handshake accepted view
    0020 Generator emission of manual content-collection frontmatter accepted view
    0021 Generate manual entity pages from the ontology via Fuseki + a GRLC SPARQL API at build time accepted view
    0022 Make manual diagram elements clickable (navigate to entity pages) accepted view
    0023 Build-time ODR pages: convert markdown to enriched HTML once, freeze, and commit superseded view
    0024 ODR enrichment lives in the markdown; HTML is generated from it every build accepted view
    0025 Keep the hand-authored design above Tailwind Preflight superseded view
    0026 Bounded-Context Scheme Emission accepted view
    0027 Council-Session Indexing in AgentDB accepted view
    0028 Descriptive-Layer Walk Emission and Generated Home-Pass accepted view
    0029 Overlay-Profile Emitter Generalisation and Full Rollout accepted view
    0030 Category-Based Descriptive Emission Pipeline & Import Gates (G1–G3) accepted view
    0031 Category-G Curated Walk — Execution Plan and G11 Reconciliation accepted view
    0032 Curated Category-G Walk — Emission, Coverage Gate, and ODR-0024 Remediation accepted view
    0033 Room-Dimension Value-Structure Emission accepted view
    0034 Gated gUFO `rdf:type` Property-Typing Pass accepted view
    0035 Load-Time OWL-RL-Safe Inference Materialisation in Jena/Fuseki accepted view
    0036 SHACL 1.2 Validation via Apache Jena accepted view
    0037 Apache Jena as opda's Sole RDF/SHACL/SPARQL 1.2 Toolchain accepted view
    0038 Hosting, auth, and comments architecture (AWS) accepted view
    0039 Linked-data model as the foundation and direction of SPDTF development accepted view
    0040 AWS hosting CI/CD pipeline accepted view
    0041 Ontology Reference Document — Generation Model and Section Structure accepted view
    0042 Rename the `/manual` Section to `/model` accepted view
    0043 Ontology graph-diagram tooling — interactive engine + authored + static-gated composition accepted view
    0044 Ontology as web pages — dereferenceable per-entity detail pages, SPARQL-driven SSG accepted view
    0045 `ufoCategory` quarantine restoration, gUFO-alignment scheme, and the sixth three-graph gate accepted view
    0046 OntoClean meta-property markup — conditional, gated on the canonical-check CI meta-shape accepted view
    0047 Ontology graph-engine in-situ bake-off — every scored finalist as a switchable tab accepted view
    0048 Relationship-emission walk + object-property coverage gate proposed view
    0049 OWL axioms as documentary AI-signal — domain/range and the R2-excluded set proposed view
    0050 Single canonical UFO typing axis proposed view
    0051 Site content realignment: DVSTF/SPDTF terminology, UK-initiative chart, standards alignment, and the MHCLG roadmap proposed view
    0052 Stakeholder-review remediation: member parity, propdata.org.uk provenance, Moverly, and accreditation-gap corrections proposed view
    0053 Cache the Apache Jena Fuseki dist in the AWS deploy superseded view
    0054 Publish the source/ archive to a public S3 bucket served via CloudFront proposed view
    0055 Cross-section class-diagram links + the `rdfs:subClassOf` render layer implemented view
    0056 Relationship-residue emission — declare `partOfTransaction`/`concerns`, register aboutness/chain, extend the coverage gate proposed view
    0057 RML Mapping Implementation accepted view
    0058 MetaHarness Darwin Mode for Ontology Authoring and RML Gap-Closing accepted view
    0059 RML Mapping Section — Positioned Between Ontology and Schema accepted view
    0060 TriplesMap Reference Page — Bidirectional JSON Schema ↔ Ontology Resource Browsing accepted view
    0061 Jena-Sole-Toolchain Enforcement and the rdflib Migration Register accepted view
    0062 DBT Smart Data implications for SPDTF and PDTF schema lineage accepted view
    0063 Domain-led bounded-context working groups for SPDTF development accepted view
    0064 Revamp the modelling website before publishing the new working-group approach accepted view
    0065 AI-assisted evidence-to-model workflow with human-governed review proposed view
    0066 The 451 required Property Pack data points are the closed seed scope for a greenfield ontology accepted view
    0067 Model the Property Pack from first principles with bounded-context ownership accepted view
    0068 Govern the OPDA standards lifecycle through human consensus and staged ratification proposed view
    0069 Recruit later bounded-context working groups through a public campaign and simple sign-up accepted view
    0070 Operate OPDA working groups through a uniform Microsoft 365 workspace pattern accepted view
    0071 Recruit later bounded-context groups through a coordinated public campaign accepted view
    0072 Operate a scheduled, harnessed working-group inbox agent accepted view
    0073 Adopt the OPDA brand and replace the website design system implemented view
    0074 Organise the site around SPDTF and the PDTF schema implemented view
    0075 Treat the Property Pack ontology as an accelerated SPDTF component accepted view
    0076 Consolidate PDTF schema documentation under hierarchy-reflecting routes superseded view
    0077 Place the PDTF schema beneath SPDTF as a third-party input accepted view
    0078 Create a standalone working-group recruitment campaign at `/join` accepted view
    0079 Make the site public and retire the edge authentication gate accepted view
    0080 Add purposeful graphics to the OPDA homepage accepted view
    0081 Organise OPDA evidence into purpose-specific NotebookLM portfolios accepted view
    0082 Add a progressively enhanced site-search dialog implemented view
    0083 Rebuild proportionate risk-based CI/CD accepted view
    0084 Integrate HubSpot with working-group signup and approved website access accepted view
    0085 Follow each domain approval with Microsoft access and its own Postmark invitation accepted view
    0086 Create a task-first Marketing toolkit with portable recruitment assets accepted view
    0087 Acknowledge every submission independently of the CRM accepted view
    0088 Approve working-group domains from a Teams card proposed view

    About ADRs

    An ADR records a single architecture decision in MADR format: a short context-and-problem statement, the options considered, the decision outcome, and its consequences. ADRs are immutable once accepted — a later decision supersedes an earlier one with a new record rather than editing it in place.

    The corpus spans application and infrastructure concerns (site build, AWS hosting and CI/CD, source-archive publishing) as well as the ontology engineering pipeline. The semantic-modelling rationale — what the ontology asserts and why — lives in the ODR corpus.

    Comments

    Loading comments…