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

    Model views by audience

    Five linked presentations of the schema-derived ontology model. Each view targets a distinct audience and presents the same underlying data model at a different level of abstraction. The tiers are linked by stable per-entity URIs so a reader can traverse from business narrative to deployed Turtle without losing the thread.

    This manual is generated from the 24 emitted TTL files at source/03-standards/ontology/ per the information-architecture blueprint.

    Tier index

    Tier Audience What it answers
    Concept Property-industry SMEs — surveyors, conveyancers, lenders, government data leads "What does an OPDA Property mean, and why does Identity Criterion matter?" — business-language narrative, hard cases, IC. No jargon.
    Logical Data engineers, solution architects, integration architects "What typed attributes does Property have, and how does it relate to Address, LegalEstate, Transaction?" — ER diagrams, typed attribute tables, cardinalities. Platform-independent.
    Physical — ontology Ontology engineers, SHACL implementers, regulators "Which Turtle file emits opda:Property, what SHACL shapes constrain it?" — OWL / SHACL / SKOS / Turtle verbatim.
    Physical — deployment Triplestore operators, SPARQL consumers, devops "Which named graph holds opda:Property, and how do I fetch it from opda.org.uk/pdtf/Property?" — deployment topology, named-graph layout, content-negotiation, CI gates.
    Physical — relational Database engineers, analytics teams and SQL integration developers "How could the same entities and relationships be projected into relational tables?" — a technology-specific relational projection, kept subordinate to the ontology meaning.

    How to navigate

    • Start by audience. Pick the tier that matches your role from the table above. Each tier's overview page lists every entity, scheme, and exemplar in that tier.
    • Follow an entity across tiers. Every entity has a stable file path that mirrors across Concept, Logical, and Physical-Ontology tiers. Cross-tier links at the bottom of each entity page take you to its presentation in the other tiers.
    • Trace from URI back to docs. Every opda:<EntityName> URI in the source TTLs carries a dct:source URI that resolves into the Concept tier.

    See also: Validation report · Information architecture

    Comments

    Loading comments…