Lineage, provenance and verification

    Use this category to follow the schema-derived ontology back to its PDTF schema sources, understand the recorded modelling path, and inspect the separate checks that test the schema–ontology correspondence. These are related forms of traceability, but they are not interchangeable.

    schema-derived draft

    This category documents a draft semantic corpus derived from PDTF schema. It is not an approved SPDTF ontology. Each source, decision, historical record and verification artefact keeps the maturity and authority stated on its own page.

    Three different traces

    What each trace establishes and what it does not
    TraceQuestion answeredBoundary
    Source and decision provenance Where did a term come from, and which ODR, ADR or council record governed the modelling choice? A citation records lineage; it does not prove complete schema coverage.
    Historical modelling record Which standards, bounded contexts, taxonomy, OWL, SHACL and JSON-LD approaches were explored? The record contains mixed-maturity work and explicitly retained stubs.
    RML verification bridge Do cited schema locations and ontology terms resolve in both directions? RML is an independent bidirectional verification bridge, not a derivation step or runtime ETL pipeline.

    Follow the evidence

    A defensible reading order

    1. Start with provenance to identify the stated source and governing decision.
    2. Use the historical record to understand why a modelling approach was proposed or retained.
    3. Use the RML coverage and validation pages to test correspondence independently.
    4. Carry forward the page-level status; traceability does not promote a draft artefact.

    Comments

    Loading comments…