Open Data Governance Standard (ODGS) — Reference Specification & Runtime Engine (v6.1.0)

Vendor-Neutral Runtime Semantic Policy Enforcement & Cryptographic Attestation (S-Cert) for Data Pipelines and Federated Dataspaces.

1. Overview & Architectural Scope

The Open Data Governance Standard (ODGS) (v6.1.0) resolves the Definition–Execution Gap (in-pipeline governance) and the Phase 6 Operationalisation Gap (post-transfer usage enforcement in federated dataspaces).

While dataspace control planes (Eclipse DSP/DCP, W3C ODRL 2.2, Eclipse DRP, and the Gaia-X Data Transfer Agent) govern pre-transfer negotiation and credential verification, ODGS governs in-pipeline runtime execution once data arrives at the processing boundary — deterministically evaluating payload constraints (HARD_STOP, SOFT_STOP, LOG_ONLY) and emitting a zero-knowledge Semantic Certificate (S-Cert) (RFC 8785 JCS + RFC 7515 JWS).

Normative Standards Alignment

2. Repository Structure

├── 1_NORMATIVE_SPECIFICATION/
│   ├── SPECIFICATION.md                        # Normative 5-Plane & Phase 6 Dataspace Specification
│   ├── conformance_rules.md                    # Level 1 Core & Level 2 Attested Conformance Rules
│   ├── ontology/
│   │   ├── ontology_graph.owl                  # W3C OWL 2 Ontology (ISO/IEC 38505 & 25012 grounded)
│   │   └── odgs_dataspace.linkml.yaml          # LinkML Dataspace Vocabulary (Eclipse CAP / W3C PROV-O mapped)
│   └── schemas/
│       ├── 01-metrics-schema.json              # Plane II: Metric Definitions Schema
│       ├── 02-rules-schema.json                # Plane III: Validation Rules Schema
│       ├── 03-ontology-schema.json             # Plane IV: Contextual Process Bindings Schema
│       ├── 04-s-cert-schema.json               # Plane V: Semantic Certificate (S-Cert) Schema
│       ├── odgs-dataspace.context.jsonld       # JSON-LD Context (odgs, odrl, cred, prov, cap, ovc)
│       ├── legislative/                        # 72 Metrics, 60 ISO/IEC 25012 DQ Dimensions, Ontology Graph
│       ├── judiciary/                          # 101 Validation Rules & Root Cause Taxonomy
│       └── executive/                          # Contextual Process Bindings & Physical Data Maps
├── 2_INFORMATIVE_REFERENCE/
│   ├── architecture/                           # Reference Architecture, Adapter, Ontology & Audit Guides
│   └── src/
│       ├── odgs/
│       │   ├── core/                           # Cryptographic hashing (RFC 8785 JCS) & Adapter ABC
│       │   ├── executive/                      # OdgsInterceptor (Python Runtime PEP)
│       │   ├── dataspace/                      # ODRL 2.2 Binder, Phase 6 PEP, CAP/PROV-O/OSCAL Exporters, DTA Verifier
│       │   └── system/                         # CLI (`odgs`), FastAPI Server, Schema Validators, dbt Adapter
│       └── interceptor.js                      # Cross-language Node.js Interceptor Reference Implementation
├── docs/                                       # MkDocs Technical Documentation (Eclipse EDWG, Gaia-X, IDSA, LinkML)
├── examples/
│   └── run_all_dataspace_scenarios.py          # End-to-end executable demonstration of Scenarios 1–5
└── tests/                                      # Python (pytest) & Node.js (vitest) Conformance & Parity Suites

3. Quick Start

Installation (Local Development / Reference Verification)

pip install -e ".[dev]"

1. Run the End-to-End Dataspace Scenarios (ODRL 2.2 → Phase 6 PEP → S-Cert → CAP v2.2.1 / PROV-O / OSCAL)

# Run all 5 normative dataspace scenarios (HARD_STOP, SOFT_STOP, LOG_ONLY, DTA Provenance, CAP/PROV-O/OSCAL)
python3 examples/run_all_dataspace_scenarios.py

# Or via the CLI:
odgs dataspace-demo --format cap-vc
odgs dataspace-demo --format s-cert
odgs dataspace-demo --format prov-o
odgs dataspace-demo --format oscal

2. In-Pipeline Enforcement in Python (OdgsInterceptor & DataspaceRuntimePEP)

from odgs.dataspace.odrl_binder import bind_odrl_policy
from odgs.dataspace.runtime_pep import DataspaceRuntimePEP, AdministrativeRecusalError
from odgs.dataspace.cap_exporter import export_cap_declaration_vc

odrl_agreement = {
    "@context": "http://www.w3.org/ns/odrl.jsonld",
    "@type": "Agreement",
    "uid": "urn:uuid:agreement-energy-grid-2026-091",
    "obligation": [{
        "uid": "urn:odrl:duty:k-anonymity-min-50",
        "action": "aggregate",
        "constraint": [{
            "leftOperand": "aggregation_household_count",
            "operator": "gteq",
            "rightOperand": 50
        }]
    }]
}

process_urn = "urn:odgs:process:energy-consumer:grid-load-forecasting"
rules, binding = bind_odrl_policy(odrl_agreement, process_urn=process_urn)
pep = DataspaceRuntimePEP(rules=rules, bindings=[binding])

# Evaluate runtime payload and emit Semantic Certificate (S-Cert)
s_cert = pep.evaluate(
    process_urn=process_urn,
    payload={"aggregation_household_count": 64, "region": "NL-ZH"},
)

# Project S-Cert into an Eclipse CAP v2.2.1 Declaration Verifiable Credential
cap_vc = export_cap_declaration_vc(
    s_cert,
    issuer_did="did:web:consumer.energy-dataspace.eu",
    subject_did="did:web:consumer.energy-dataspace.eu#pipeline-1",
)

4. The 5-Plane Architecture & Phase 6 Dataspace Handshake

flowchart LR
    subgraph ControlPlane ["Control Plane (Pre-Transfer)"]
        ODRL["W3C ODRL 2.2 / Eclipse DSP & DRP"]
        ISO["ISO/IEC 38505-1 & 25012 Definitions"]
    end

    subgraph DataPlane ["Data Plane (Phase 6 Runtime PEP)"]
        BIND["Contextual Process Binding (context_bindings.json)"]
        PEP["ODGS Interceptor / DataspaceRuntimePEP"]
        DECISION{"HARD_STOP | SOFT_STOP | LOG_ONLY"}
    end

    subgraph AttestationPlane ["Attestation & Conformity Plane"]
        SCERT["Semantic Certificate (S-Cert: JCS + JWS)"]
        CAP["Eclipse CAP v2.2.1 (cred:Evidence)"]
        PROVO["W3C PROV-O & NIST OSCAL"]
    end

    ODRL --> BIND
    ISO --> BIND
    BIND --> PEP
    PEP --> DECISION
    DECISION --> SCERT
    SCERT --> CAP
    SCERT --> PROVO

5. Verification & Test Suite

# Run Python test suite (core interceptor, ISO schema conformance, and dataspace bridge)
pytest

# Run cross-language Node.js parity tests
npm test

# Build technical documentation strictly
mkdocs build --strict

6. License

Released under the Apache License, Version 2.0. See LICENSE and GOVERNANCE.md.