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

    Validation and examples

    This category connects the ontology’s constraint layer to concrete diagnostic data. It explains what SHACL checks, how form-specific profiles constrain one shared class model, which source leaves remain recorded as gaps, and how exemplar graphs demonstrate expected conformance and failure behaviour.

    schema-derived draft

    Passing the documented checks shows conformance to tested rules in the draft corpus. It does not approve the semantic model, prove source data true, or establish an SPDTF standard. Known limits and validator requirements remain part of the result.

    How the validation evidence fits together

    1. Base shapes express graph constraints separately from OWL class semantics.
    2. Overlay profiles select form-specific constraints and record uncovered source leaves in the gap register.
    3. Diagnostic exemplars pair instance graphs with expected reports for hard cases and negative tests.
    4. Validation reports summarise generated-page and corpus checks without turning technical success into semantic approval.

    Inspect constraints and evidence

    Constraint reference

    SHACL shapes

    Browse all 408 base node shapes, severity levels and SHACL-AF rules in the committed validation graph—the source of the historical rule that a form is its SHACL overlay.

    Open page     Form-specific constraints

    Overlay profiles and gaps

    Inspect all 31 per-form profiles, most intentionally thin: they bind Category-G leaves and record the rest in the explicit gap register.

    Open page     Worked data

    Diagnostic exemplars

    Review all 17 worked instance graphs, each paired with an expected SHACL report, including conformant, non-conformant and hard-case examples.

    Open page     Generated assurance

    Model validation report

    See coverage and validation results for the generated model presentation and its underlying ontology corpus.

    Open page

    Interpret results carefully

    A green check can show…It cannot show…
    The input parsed and satisfied the tested SHACL configuration.That every relevant business rule has been encoded.
    A generated page agrees with the committed source used by its drift gate.That the source definition has been approved by SPDTF participants.
    An exemplar produced its recorded expected report.That arbitrary real-world data or untested inference regimes behave identically.

    Before relying on a result, review the known issues and validator caveats and use the exact validation recipe on Consume the ontology.

    Comments

    Loading comments…