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

    Use and tooling

    This is the practical route for consuming the extracted corpus. It brings together the namespace contract, queries, validation recipe, content-negotiation guidance, downloadable Turtle and the documentation-tool comparison used to assemble the human-readable reference.

    schema-derived draft

    Stable routes and downloadable artefacts support inspection and testing; they do not make this an approved SPDTF ontology. Pin the corpus version you tested, follow the documented validator settings, and carry the draft status into downstream use.

    Consumer workflow

    1. Resolve namespaces. Bind the kind-split term, scheme, shape, graph and harness namespaces without collapsing their resource kinds.
    2. Choose an artefact. Download the class, shape or merged Turtle appropriate to the task and record the version used.
    3. Query or dereference. Use the sample SPARQL and stable resource IRIs to inspect the committed model.
    4. Validate deliberately. Use the documented SHACL configuration, including advanced rules where required, and compare results with known caveats.
    5. Treat tool output as a view. Generated renderings help inspect layers; none independently defines the ontology’s authority.

    Choose a practical route

    Queries and downloads

    Consume the ontology

    Get the prefix map, runnable SPARQL, content-negotiation guidance, the pyshacl advanced=True recipe and links to the downloadable Turtle bundles.

    Open page     IRI contract

    Namespaces and prefixes

    Inspect the kind-split namespace scheme, external vocabulary bindings, collision-avoidance rationale and example IRIs.

    Open page     Documentation tooling

    Tool bake-off and scorecard

    Compare every documentation tool against the full corpus, its per-layer strengths and omissions, and the M6 rubric used to score and select the woven reference’s presentation methods.

    Open page

    Source, representation and tool are different things

    LayerRoleUse it for
    Committed Turtle corpusMachine-readable source for this extracted draftLoading, querying, validation and reproducible generation.
    Native ontology pagesTask-oriented and dereferenceable documentationInterpretation, discovery, relationships, constraints and provenance.
    Third-party tool renderingsSupplementary views of selected layersComparison and specialist inspection, subject to each tool’s omissions.

    Check limitations and known issues before operational use, and use Terms and model resources when you need to resolve a particular class, property, shape, concept or scheme.

    Comments

    Loading comments…