Property — deployment view

The Property module is the Identity-Criterion crux of OPDA. Property, LegalEstate, RegisteredTitle, Address + variant-specific subclasses, Lease-Term, UPRNSuccessionEvent, LeaseExtensionEvent — the deployment graph for the Property module is the largest of the six business modules.

Source TTL(s)

File	Role	Physical-Ontology tier
`opda-property.ttl`	TBox: classes + properties + variants	property/classes.md
`opda-property-shapes.ttl`	Identity-key + IC-breach shapes + SHACL-AF quality rules	property/shapes.md
`opda-property-annotations.ttl`	DPV baseline + variant-conditional refinement maps	property/annotations.md

Named graph(s)

Named graph IRI	Source TTL	Triples	`owl:versionIRI`
`https://opda.org.uk/pdtf/graph/property`	`opda-property.ttl`	199	`https://opda.org.uk/pdtf/harness/release/property/1.0.0/`
`https://opda.org.uk/pdtf/graph/property-shapes`	`opda-property-shapes.ttl`	54	—
`https://opda.org.uk/pdtf/graph/property-annotations`	`opda-property-annotations.ttl`	31	—

Load order: the TBox graph imports the foundation + vocabularies substrate:

owl:imports <https://opda.org.uk/pdtf/harness/release/1.0.0/>, <https://opda.org.uk/pdtf/scheme/>

Consumers must load the foundation graphs first (transitively via owl:imports). Property shape + annotation graphs declare no owl:imports and load alongside the TBox graph.

See named-graphs.md §Module-TBox graphs for details.

Derived-profile membership

Profile	`opda-property.ttl`	`opda-property-shapes.ttl`	`opda-property-annotations.ttl`
opda-validation	included (classes + properties + subClassOf + labels)	included (all triples)	excluded (DPV is UI-time)
opda-ui	included (all triples)	included (all triples; DASH UI predicates)	included (all triples; DPV disclosures drive form affordances)
opda-inference	included (classical-logic axioms only)	excluded (shapes confuse reasoners)	excluded (no inference contribution)

Overlay bindings

BASPI5 binds three Property-module classes via sh:targetClass:

BASPI5 shape	Target class	Module-shape graph counterpart
`Baspi5_PropertyShape`	`opda:Property`	`opda:PropertyIdentityShape` (Cat 1)
`Baspi5_AddressShape`	`opda:Address`	`opda:AddressIdentityShape` (Cat 1)
`Baspi5_LegalEstateShape`	`opda:LegalEstate`	`opda:LegalEstateIdentityShape` (Cat 1)

The overlay cannot redefine foundation identity keys per the Cat 3 NoIdentityOverride meta-shape; it constrains BASPI5-specific per-form cardinality + enum subsets + DASH UI on top of the foundation shapes.

See overlay-deployment/baspi5.md §Source profile TTL for the full ValidationContext reification.

Content-negotiation entry points

Resource path	Resolves to
`https://opda.org.uk/pdtf/graph/property`	property module TBox (`opda-property.ttl`)
`https://opda.org.uk/pdtf/harness/release/property/1.0.0/`	property versionIRI snapshot
`https://opda.org.uk/pdtf/graph/property-shapes`	property shape graph (`opda-property-shapes.ttl`)
`https://opda.org.uk/pdtf/graph/property-annotations`	property annotation graph (`opda-property-annotations.ttl`)
`https://opda.org.uk/pdtf/Property`	per-entity dereference (TBox + matching shape fragment)
`https://opda.org.uk/pdtf/Address`	per-entity dereference
`https://opda.org.uk/pdtf/LegalEstate`	per-entity dereference
`https://opda.org.uk/pdtf/RegisteredTitle`	per-entity dereference
`https://opda.org.uk/pdtf/UPRNSuccessionEvent`	per-entity dereference
`https://opda.org.uk/pdtf/LeaseExtensionEvent`	per-entity dereference

Content-type routing per the Accept-header matrix.

Deployment graph

--- config: layout: elk elk: mergeEdges: false nodePlacementStrategy: BRANDES_KOEPF --- %%{init: {"theme": "base", "themeVariables": {"primaryColor": "#FFF8E1", "primaryTextColor": "#E65100", "primaryBorderColor": "#F57F17", "lineColor": "#37474F"}}}%% flowchart LR accTitle: Property module deployment graph accDescr: Shows how Property TTLs flow through named graphs, derived profiles, BASPI5 overlay bindings, and HTTP entry points. classDef data fill:#FFF8E1,stroke:#F57F17,stroke-width:2px,color:#E65100 classDef process fill:#E1F5FE,stroke:#0277BD,stroke-width:2px,color:#01579B classDef service fill:#E8F5E9,stroke:#2E7D32,stroke-width:2px,color:#1B5E20 classDef user fill:#F3E5F5,stroke:#7B1FA2,stroke-width:2px,color:#4A148C classDef infra fill:#E3F2FD,stroke:#1565C0,stroke-width:2px,color:#0D47A1 subgraph SRC["Source TTLs"] T["opda-property.ttl
199 triples"]:::data S["opda-property-shapes.ttl
54 triples"]:::data A["opda-property-annotations.ttl
31 triples"]:::data end subgraph NG["Named graphs"] NGT["opda.org.uk/pdtf/graph/property
versionIRI 1.0.0/"]:::infra NGS["opda.org.uk/pdtf/graph/property-shapes"]:::infra NGA["opda.org.uk/pdtf/graph/property-annotations"]:::infra end subgraph CMP["Composer"] C["opda-gen compose"]:::process end subgraph DRV["Derived profiles"] DV["opda-validation.ttl
classes + shapes"]:::data DU["opda-ui.ttl
classes + shapes + annotations"]:::data DI["opda-inference.ttl
classes only"]:::data end subgraph OVR["Overlay bindings — BASPI5"] OB1["Baspi5_PropertyShape
targets opda:Property"]:::data OB2["Baspi5_AddressShape
targets opda:Address"]:::data OB3["Baspi5_LegalEstateShape
targets opda:LegalEstate"]:::data end subgraph HTTP["HTTP entry points"] H1["opda.org.uk/pdtf/graph/property"]:::service H2["opda.org.uk/pdtf/Property"]:::service H3["opda.org.uk/pdtf/Address"]:::service H4["opda.org.uk/pdtf/LegalEstate"]:::service end subgraph CONS["Consumers"] U1["SHACL validators"]:::user U2["DASH UI"]:::user U3["OWL reasoners"]:::user U4["BASPI5 round-trip"]:::user end T --> NGT S --> NGS A --> NGA NGT --> C NGS --> C NGA --> C C --> DV C --> DU C --> DI NGT --> OB1 NGT --> OB2 NGT --> OB3 NGS --> OB1 NGS --> OB2 NGS --> OB3 NGT --> H1 NGT --> H2 NGT --> H3 NGT --> H4 DV --> U1 DU --> U2 DI --> U3 OB1 --> U4 OB2 --> U4 OB3 --> U4

Cross-tier links

Logical tier: docs/manual/logical/property/ — typed attributes + cardinalities + ER diagrams for Property classes.
Physical-Ontology tier: docs/manual/physical-ontology/property/ — Turtle source layout + per-class blocks + per-shape constraint bodies.
Overlay deployment: docs/manual/physical-database/overlay-deployment/baspi5.md — BASPI5 Property bindings.
Operations: byte-identity CI regenerates the three Property TTLs; round-trip CI validates Property exemplars (registered-freehold-house, flat-with-split-uprn, etc.).