Common boundary
A deliberately small exchange boundary for stable identity and meaning genuinely shared by several property domains.
Deliberately small
The Common boundary supports exchange; it does not control each domain’s internal meaning.
Context summary
Complete context diagram
This follows the schema-derived ontology's class-diagram convention: classes are nodes and class-to-class object properties are labelled relationships. One-hop neighbouring classes from another semantic home are muted and connected with dotted lines. Datatype properties can be revealed inside their class nodes; coded-value properties remain in the structured reference below. The three layer controls independently show or hide datatype fields, object-property relationships and inheritance links. These are asserted OWL relationships, not reviewed cross-domain mappings. The Category 8 mapping method explains how a separate, human-reviewed correspondence would be recorded.
Owned resources
Classs (1)
| Label | Definition | Domain | Range | Evidence traces |
|---|---|---|---|---|
Propertycommon:Property | An identifiable unit of land, buildings or both that persists independently of any particular address, transaction or domain view. | Not specified | — | 202 |
Datatype propertys (1)
| Label | Definition | Domain | Range | Evidence traces |
|---|---|---|---|---|
Unique Property Reference Numbercommon:uprn | The reference assigned to a property in the national address gazetteer and used as a non-arithmetic identifier. | Property | xsd:string | 1 |
Structured relationship view
This text table covers the same one-hop relationships as the context diagram, including properties that enter or leave this semantic home. Domainless properties are reported as unresolved; no domain is guessed.
Comments
Loading comments…
Sign in to post a comment