Vendor-Neutral Runtime Semantic Policy Enforcement & Cryptographic Attestation (
S-Cert) for Data Pipelines and Federated Dataspaces.
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, Data Plane Signaling, W3C ODRL 2.2, Eclipse DRP, and the Gaia-X Data Transfer Agent) govern pre-transfer negotiation, credential exchange, and transfer signaling, ODGS integrates at the consumer data-plane processing boundary — evaluating payload-observable constraints (HARD_STOP, SOFT_STOP, LOG_ONLY), signaling transfer suspension/termination on breach, and emitting a consumer-signed Semantic Certificate (S-Cert) (RFC 8785 JCS + RFC 7515 JWS) as a first-party audit record (cap:Declaration).
Dataspace Trust Model & Constraint Observability Boundary: In cross-organizational dataspace transfers,
S-Certreceipts are produced and signed by the consumer over payloads evaluated in the consumer's environment. Pre-processing payload checks can evaluate structural, value-range, and aggregation constraints (e.g., k-anonymity counts or field bounds), whereas behavioral usage obligations (such aspurpose,retention, oronward sharing) cannot be observed from a payload prior to processing (inspect_odrl_constraint_observability). Accordingly, anS-Cert(and its projectedcap:DeclarationVC) is a verifiable consumer self-attestation / audit record — not provider-verified proof of policy enforcement.
| Standard / Ecosystem | Normative Specification | Role in ODGS v6.1.0 |
|---|---|---|
| ISO/IEC JTC 1/SC 40 | ISO/IEC 38505-1:2026 & TR 38505-2:2018 |
Separates corporate governance of data (Evaluate, Direct, Monitor) from operational data management via contextual process bindings (context_bindings.json). |
| ISO/IEC JTC 1/SC 7 & TC 184 | ISO/IEC 25012:2008, ISO 8000-8, ETSI EN 304 311 |
Grounds all 60 data quality dimensions in standard_dq_dimensions.json (Inherent, System-Dependent, Inherent_and_System_Dependent). |
| W3C | W3C ODRL 2.2, W3C VC 2.0, W3C PROV-O, W3C OWL 2 |
Compiles payload-observable ODRL 2.2 constraints into executable rules (odrl_binder.py), flags unobservable usage constraints (signaling.py), and exports S-Cert lineage graphs (export_w3c_prov_o). |
| Eclipse Dataspace Working Group | Data Plane Signaling, Eclipse DSP (ISO/IEC DIS 26450), Eclipse DCP (ISO/IEC DIS 26451), Eclipse CAP v2.2.1 (LinkML) & Eclipse DRP |
Integrates as a consumer data-plane component (DataPlaneSignalingBridge + GET /transfers/:dataFlowId/agreement), emits dspace:TransferSuspensionMessage / dspace:TransferTerminationMessage on breach, issues DID-signed cap:Declaration VCs via Eclipse DCP (handle_dcp_presentation_query), and evaluates Eclipse DRP delegationEvidence. |
| Gaia-X & IDSA | Gaia-X Architecture 25.11 (§4.8.4.2) & IDSA Rulebook 2026-3 (§121) |
Verifies Phase 6 post-transfer obligations and upstream provenance hashes (dta_verifier.py) with decentralized correlation_id observability. |
| NIST | NIST OSCAL v1.1.2 |
Exports runtime evaluation outcomes as OSCAL Assessment Results finding and observation records (export_nist_oscal_finding). |
├── 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
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 dcp-vp
odgs dataspace-demo --format s-cert
odgs dataspace-demo --format prov-o
odgs dataspace-demo --format oscalfrom 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",
)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
# 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 --strictReleased under the Apache License, Version 2.0. See LICENSE and GOVERNANCE.md.