Gaia-X Integration (ODRL-VC Profile & Data Transfer Agent)¶
1. Bridging Phase 5 (Transfer) and Phase 6 (In-Pipeline Usage)¶
Within the Gaia-X Architecture Document (25.11) and the Gaia-X Data Transfer Agent (DTA):
- Phase 5 (Transfer): The
DTAevaluates pre-transfer access prerequisites (odrl:read) and records negotiated post-transfer consumer obligations on theTransferRequestResult. - Phase 6 (Access & Usage): Because a transfer agent's involvement ends when bytes land at the consumer boundary, post-transfer payload-observable checks (such as k-anonymity aggregation counts or field bounds) execute inside the consumer's processing pipeline, emitting a consumer-signed
S-Certaudit record aligned with Gaia-X Architecture Document 25.11 (ยง4.8.4.2). (Note on Trust Model: becauseS-Certreceipts are generated and signed by the consumer over consumer-supplied payloads, they constitute a verifiable first-party consumer audit record rather than provider-verified proof of downstream usage such as purpose, retention, or onward sharing.)
2. Verification Workflow (dta_verifier.py)¶
- Bind Agreement (
bind_odrl_policy): The consumer binds the negotiated W3C ODRL 2.2 / Gaia-X ODRL-VC agreement (uid) to its targetprocess_urn, settingcorrelation_idto the DTAagreement_id/transfer_id. - Runtime Gate (
DataspaceRuntimePEP.evaluate): On every pipeline execution, the PEP evaluates the bound constraint against the payload and emits anS-Cert(payload_hash+semantic_hash+correlation_id). - Cryptographic Attestation (
sign_s_cert_ed25519): TheS-Certis signed using Ed25519 (RFC 7515 JWS /EdDSA). - Provider / DTA Verification (
verify_dta_post_transfer_obligation): The provider or DTACredentialVerificationplugin verifies thecorrelation_id,semantic_hash,verdict == PASS, and Ed25519 JWS signature without ever accessing the consumer's raw data.