OPDA Knowledge base
Physical — relational Module: governance

Governance module — relational schema

A thin module. dpv_mapping_record maps an OPDA Kind (a class, not an instance) to a DPV personal-data category. SpecialCategoryScheme is a declaration-only skos:ConceptScheme subclass with no members yet, so it produces no table at this tier.

Tables

TableRealisesIdentity
dpv_mapping_recordDPVMappingRecord(targets_kind_uri, baseline_category_uri)

Entity-relationship diagram

erDiagram accTitle: Governance module — entity-relationship diagram accDescr: dpv_mapping_record is a single standalone table; targets_kind_uri and baseline_category_uri are cited IRI literals stored as text, with no foreign key, because DPV is referenced rather than imported. dpv_mapping_record { uuid dpv_mapping_record_id PK text uri UK text targets_kind_uri text baseline_category_uri }

Mapping notes

  • targets_kind is a class reference, not a foreign key. It cites an owl:Class IRI (Person / Organisation / Claim — the Kind, not a row), stored as a text IRI literal. The three concrete records are PersonDPVMapping, OrganisationDPVMapping, and ClaimDPVMapping.
  • DPV is cited, not imported (ODR-0012). baseline_category_uri holds the dpv-pd category IRI as a literal — no foreign key to an imported DPV table.
  • SpecialCategoryScheme is deliberately omitted. It is an empty scheme declaration with no members; a special_category lookup appears only once members are ratified and emitted.

Cross-tier

Logical tier: governance module.

Comments

Loading comments…