Property Pack ontology

    The Property Pack is the standardised bundle of information needed to support a property transaction. This ontology candidate models that bundle as a defined part of SPDTF, spanning several semantic contexts rather than pretending it is one universal business domain.

    Accelerated determination

    The Technical Working Group must determine this candidate by the end of September 2026. The current 0.1.0-draft model remains machine-proposed. Later domain, scheme and Interoperability working-group review may propose controlled changes; none of those reviews or an external authority decision has yet occurred.

    What a Property Pack is

    It is an exchange and delivery profile: a governed set of information that travels with a property transaction and draws on conveyancing, estate agency, finance, property-data services, property technology, surveying and shared identifiers. The 451 required source items define the current coverage boundary; they do not prescribe 451 RDF properties or reproduce the structure of a JSON document.

    Candidate at a glance

    451required source data points, each traced to the candidate
    159OWL resources: 53 classes and 106 properties
    14controlled-vocabulary schemes with 85 curated concepts
    45SHACL node shapes carrying 100 property constraints
    8semantic homes: six bounded contexts, one common boundary and one scheme context
    413source-topic concepts for consolidated Property Pack questions

    Contextual boundaries

    Every ontology resource has one semantic home. The dashed arrows point from the Common boundary because it supplies a small set of shared elements; they do not mean that every context interoperates through it, and they do not assert mapping, control or inheritance. Cross-domain mappings are a separate Category 8 review concern and remain awaiting working-group evidence.

    Common boundary Bounded context Scheme context Shared elements supplied by the Common boundary
    100%

    Loading diagram…

    Declared context architecture: six bounded contexts, the DBT Smart Data scheme context, and the deliberately small Common boundary. Click a node to open its context page.

    Explore the reference

    451 items

    Definition and scope

    Inspect every required source item, constraint, semantic home, candidate disposition and evidence trace.

    Lineage

    PDTF schema lineage

    Separate proven schema coverage from the incomplete semantic crosswalk to the ontology extracted from PDTF schema.

    Atlas

    Complete model

    A class-relationship diagram in the PDTF schema convention, with synchronized structured references for all 159 candidate resources.

    OWL

    Ontology resources

    Human definitions, technical identifiers, semantic homes, domains, ranges, constraints and evidence traces.

    451 items

    Data dictionary

    The exact Property Pack source scope, source constraints and candidate-model disposition for every item.

    SKOS

    Controlled vocabularies

    Fourteen curated value schemes plus the distinct source-topic concept layer.

    SHACL

    Validation shapes

    Forty-five target-class shapes and every emitted datatype, class, count and pattern constraint.

    Traceable

    Source coverage

    How all 451 source items reach candidate constructs without importing the legacy ontology.

    Exact claims

    Standards profile

    RDF 1.2 Basic, SPARQL 1.2 and SHACL 1.2 targets, with explicit non-claims.

    Evidence

    Technical validation

    Parser, SHACL probe, competency-query and deterministic-regeneration results.

    Pending

    Technical determination

    Review remit, deadline, evidence, questions and the decision record that must be completed before any determination is claimed.

    Later

    Review and releases

    How later domain review, controlled change and immutable versions follow the accelerated technical determination.

    Scope and authority

    Closed business-data scope

    Exactly the 451 workbook rows marked Required. Supporting ontology constructs make the data meaningful but do not enlarge that business-data scope.

    Greenfield semantics

    The PDTF schema contains the Property Pack source definition. The separate schema-derived ontology is expected to express corresponding meaning, but that coverage is not yet proven. This candidate imports neither topology; the item-level semantic crosswalk remains incomplete.

    Human authority

    AI drafted the candidate. The Technical Working Group makes the accelerated initial determination; later working groups may review and propose versioned changes. Government use does not itself grant OPDA external authority.

    Comments

    Loading comments…