Logical tier governance

    DPV Mapping Record

    https://opda.org.uk/pdtf/DPVMappingRecord

    Mapping record from an OPDA Kind class to its DPV baseline personal-data category and optional variant-conditional refinements. UFO Information Particular. Per ODR-0018 §Rule 4 + ODR-0012 §Evidence co-annotation, ODR-0012 is the authoring authority — this module emits the mapping records; ADR-0012 emits the resulting DPV co-annotation triples into opda-annotations.ttl (three-graph separation).

    Classification

    UFO: Information Particular (Guizzardi 2005 Ch. 4 §4.7). Mapping-record-as-resource pattern per ODR-0018 §3a.

    Relationships

    Predicate Target Cardinality Inverse Description
    baselineCategory 0..* — Reference to a DPV-PD category that all instances of the target Kind bear by default. Per ODR-0018 §Rule 1, every PII-bearing Kind declares its baseline. Per ODR-0012 §Reference-not-import + ODR-0018 §Rule 4, the DPV URI is cited but DPV is NOT imported.
    targetsKind Class 1..1 — DPV mapping record → OPDA Kind class. The Kind is the class whose instances bear the personal-data category named by opda:baselineCategory (with optional variant refinements).

    Constraints

    DPVMappingRecordIdentityKeyShape sh:Violation

    DPVMappingRecord MUST target exactly one Kind class via opda:targetsKind. ODR-0012 Phase 1 governance discipline (reference-not-import for DPV).

    Sources

    • harness/odr/ODR-0018/section-Rule4

    Comments

    Loading comments…