Skip to main content

GEDRM Change Log

GEDRM 0.1​

Status: Normative Draft Baseline
Release type: Initial semantic-lock baseline

Consolidated semantic-lock baseline​

GEDRM 0.1 has been consolidated after completion of the semantic-lock review.

Added / formalized​

  • Normative formal concept-kind taxonomy.
  • Clear distinction between concept family and concept kind.
  • Data Object as a generic governed data-bearing concept.
  • Business/semantic classifications:
    • Master Data;
    • Reference Data;
    • Transactional Data;
    • Market Data.
  • Derived Data as a provenance classification rather than a peer business data type.
  • Source Data explicitly excluded as a permanent first-class intrinsic category; source-ness is relational/contextual.
  • Mastered formalized as a Processing / Governance State rather than a peer data type.
  • Golden Record formalized as a Data Representation.
  • Faceted, overlapping classification semantics across business, provenance, state, and legal/sensitivity dimensions.
  • Privacy-law Data Controller and Data Processor as first-class Legal / Privacy Roles contextual to Processing Activity.
  • Personal Data as an orthogonal Legal / Sensitivity Classification.
  • Processing Activity, Derivation Activity, Mastering Activity, and Control Execution as Activity / Process concepts.
  • Control Evidence as a first-class Assurance Evidence concept.
  • Requirement Reference as external traceability while keeping Data Requirement outside the core GEDRM 0.1 ontology.
  • Sparse, semantics-driven normative cardinalities.
  • Machine-readable representation policy covering JSON-LD, RDF/OWL, SHACL, role assignment, scope, namespace stability, and profile constraints.
  • Semantic-lock register and future-refinement appendix.

Refined​

  • Data Transformer terminology retained to avoid collision with privacy-law Data Processor.
  • Provider / Publisher / Distributor / Broker boundaries.
  • System of Record / Authoritative Source / Source of Authority three-way distinction.
  • Authoritative vs authorized semantics.
  • Master Data / Mastered / Golden Record boundaries.
  • Governed-construct taxonomy:
    • Data Policy = Normative Artefact;
    • Policy as Code = Executable Governance Representation;
    • Data Contract = Interaction Artefact;
    • Data Quality Rule = Evaluation Artefact;
    • Data Control = Assurance Mechanism;
    • Control Evidence = Assurance Evidence.
  • HDIP PDEP Data Product bundle semantics.
  • Conformance rules and non-equivalence rules.
  • Payment-domain examples covering Transactional, Reference, Market, Derived, Control Evidence, and privacy-role semantics.

HDIP mappings​

  • Data Originator -> candidate ADO — Authorized Data Originator.
  • Authoritative Source -> ADS — Authorized Data Source.
  • Data Distributor -> ADD — Authorized Data Distributor.
  • Data Asset -> HDIP governed Data Asset.
  • Data Product -> HDIP Data Product.
  • Data Product Owner -> HDIP Data Product Owner.
  • Data Policy / Policy as Code / Data Contract / Data Quality Rule / Data Control / Control Evidence -> HDIP governed runtime and assurance mappings.

Notes​

GEDRM 0.1 intentionally does not represent ADO, ADS, or ADD as universal industry-standard acronyms.

The human-readable gedrm-specification.md remains the normative semantic authority. Planned JSON-LD, RDF/OWL, SHACL, and concept-registry artefacts are companion formalizations and MUST remain consistent with it.