provin
← Back to top

Standards

Standards & Regulations

How provin aligns — by design — with the directions of major standards and regulations.

These are not certification claims. The properties each framework demands are treated as build-time constraints in the provin design.

regulation

EU AI Act

Aligned

Article 50 (transparency) 2026-08-02; high-risk obligations deferred by the Digital Omnibus (in force 2026-07) to Annex III 2027-12-02 / Annex I embedded 2028-08-02

eur-lex.europa.eu/eli/reg/2024/1689/oj ↗

Requires high-risk AI systems to document the origin and quality of training, validation, and test data. In effect, Article 10 demands timestamped, automated evidence of when a standard was applied to which data in which pipeline — an evidentiary obligation that self-declared governance cannot satisfy.

provin generates and inherits a VC signature chain at every pipeline boundary, providing the cryptographic traceability that this obligation structurally requires.

How to adapt

A ProcessObserver records a VC at each step; a Sink (Writer interface) is intended to emit the regulator-facing format.

framework

GAIA-X

Complementary

gaia-x.eu/ ↗

A European data sovereignty and interoperability framework that defines the trust specifications.

provin positions itself as the operational substrate aligned with GAIA-X’s direction — an OSS implementation surface for data flow that meets the GAIA-X trust specifications.

How to adapt

Register GAIA-X Self-Descriptions in the Schema Registry; reference them as input/output credentials in pipelines.

standard

Open Data Spaces / Dataspace Protocol (IDSA)

Complementary

ISO standardization in progress; Dataspace Protocol specification published

internationaldataspaces.org/ ↗

A protocol specification for inter-organizational data sharing developed by the International Data Spaces Association. It builds on Usage Control + Web technologies to guarantee interoperability across data spaces.

provin complements the Dataspace Protocol as the provenance layer. Where the Dataspace Protocol defines how parties connect and negotiate, provin defines what is guaranteed about the data that flows.

Eclipse Dataspace Components (EDC) integration is implementable against provin’s Source / Sink extension-point contracts; edc-source / edc-sink adapters are planned as a separate repository.

How to adapt

Let the Dataspace Connector handle policy negotiation; attach a provenance VC at a downstream provin Source extension point. edc-source / edc-sink adapters for EDC are planned as a separate repository.

framework

Ouranos Ecosystem / ODS-RAM

Complementary

ODS-RAM V2 published 2026-04-01; IPA technical specification due FY2026

www.meti.go.jp/policy/mono_info_service/digital_architecture/ouranos.html ↗

Japan’s national data interoperability initiative led by METI and IPA, spanning companies, industries, and borders. The Open Data Spaces Reference Architecture Model (ODS-RAM) V2 was published in April 2026, moving the program into its real-world implementation phase.

provin is positioned as an OSS substrate aligned with the ODS-RAM reference architecture, providing the provenance layer that connects to Japan’s data-space initiatives.

How to adapt

Place the provin Pipeline at the ODS-RAM connector layer; carry provenance VCs across data spaces.

standard

SCITT (IETF Working Group)

Complementary

datatracker.ietf.org/wg/scitt/about/ ↗

Supply Chain Integrity, Transparency, and Trust — a transparency-log-based provenance standard focused primarily on intra-organizational supply chain integrity.

provin complements SCITT by forming VC signature chains across organizational boundaries. Together, intra-org (SCITT) + inter-org (provin) provide complete coverage.

How to adapt

Anchor ProcessObserver notifications to the per-org transparency log (tlog); SCITT Transparency Log integration is intended.

standard

W3C Verifiable Credentials Data Model

Foundation

www.w3.org/TR/vc-data-model-2.0/ ↗

provin issues provenance proofs in formats compliant with the W3C VC Data Model. DID resolution and VC verification rely on standard cryptographic primitives (Ed25519 et al.), making provin interoperable with the broader VC ecosystem.

How to adapt

The vc package (W3C VC Data Integrity) issues VC Data Model–compliant credentials — verifiable with standard libraries.

regulation

Digital Product Passport / ESPR

Aligned

EU Battery Regulation full DPP mandatory 2027-02-18

commission.europa.eu/energy-climate-change-environment/standards-tools-and-labels/products-labelling-rules-and-requirements/ecodesign-sustainable-products-regulation_en ↗

A regulatory wave requiring per-product, electronic traceability across raw materials, manufacturing, and distribution. Starting with EU Battery Regulation and expanding to apparel, electronics, and construction materials.

The provin Pipeline Chain inherits provenance across “manufacturer → distributor → retailer” boundaries, forming a foundation for per-product DPP implementations.

How to adapt

Build a per-product Pipeline Chain; the final Sink emits the DPP format (JSON-LD).

regulation

DSCSA (Drug Supply Chain Security Act)

Aligned

Full electronic interoperability effectively in force (US)

www.fda.gov/drugs/drug-supply-chain-integrity/drug-supply-chain-security-act-dscsa ↗

US pharmaceutical supply chain regulation requiring traceability from manufacturer to pharmacy.

provin implements cross-organizational traceability as a VC signature chain, applicable as the data-coordination substrate among manufacturers, distributors, and dispensers.

How to adapt

Ingest EPCIS events via a Source process (ingest adapter planned as a separate repo); sign each org boundary with a VC so the custody chain stays cryptographically traceable.

regulation

GDPR Article 30

Aligned

eur-lex.europa.eu/eli/reg/2016/679/oj ↗

Record-of-processing-activities requirement. Combined with the EU AI Act, this forces organizations to explain the processing path of AI training data in real time.

The provin registry plus signature chain serves as that recording substrate.

How to adapt

A ProcessObserver builds the records-of-processing entries; a Sink is intended to emit the Article 30 format.

standard

OASIS Data Provenance Standards (DPS)

Complementary

DPS TC launched 2025-04; Data Provenance Metadata v1.0 CSD01 public review 2026-06 (pre-final)

www.oasis-open.org/tc-dps/ ↗

The Data & Trust Alliance’s data provenance metadata standards, now advancing toward a de jure standard at OASIS (sponsored by Cisco, IBM, Intel, Microsoft, and Red Hat). The vocabulary describes a dataset’s origin, rights, and privacy posture.

DPS defines what a provenance record says; provin defines who claims it and how it stays attributable — transport and signature. The spec is at committee-draft stage; adoption will take a profile / context extension on the provin side (a new subject schema), designed once the vocabulary settles.

How to adapt

Requires a profile extension: add the DPS metadata vocabulary as a subject schema, transported over the signature chain.

standard

C2PA / Content Credentials

Complementary

Specification 2.4 published; ISO/IEC JTC 1 standardization in progress

c2pa.org/ ↗

The standard for media content provenance (images, video, audio), carried as a signed manifest embedded in the file — driven by Adobe, Google, Microsoft, and others, with ISO standardization underway.

C2PA covers provenance inside the asset; provin covers provenance across the pipeline between organizations. As a C2PA asset flows through a pipeline, provin fills in the continuity — who received it, what was done, what was passed on — so the point and the line meet.

How to adapt

Requires a profile extension: define a Source profile that receives C2PA-manifested assets; provin connects the inter-organizational span.

standard

SLSA / in-toto

Complementary

SLSA v1.0 (OpenSSF) / in-toto attestation (CNCF)

slsa.dev/ ↗

The attestation standards of the software supply chain. Signing claims about “who built what, from what” is the same move provin makes — applied to builds.

Responsibilities split by artifact type: software (SLSA / in-toto) versus data (provin). Put side by side, all three lineages of an AI system — code, model, and data — get provenance.

How to adapt

Build provenance goes to SLSA / in-toto, data provenance to provin — cross-reference attestations via an Observer.

standard

W3C PROV

Complementary

PROV-DM / PROV-O W3C Recommendation (2013)

www.w3.org/TR/prov-overview/ ↗

The classic W3C standard for expressing provenance as an Entity / Activity / Agent graph, with implementations accumulated in academic and archival domains.

provin’s signature chain maps naturally onto the PROV model. It is the interop point with PROV-based tooling and research assets — and the reference point that places provin in the lineage of provenance representation.

How to adapt

Implement an Observer exporter that maps the chain onto PROV vocabulary (Entity / Activity / Agent).

ecosystem

Catena-X

Complementary

In production as the automotive dataspace (EDC-based)

catena-x.net/ ↗

The EU automotive industry dataspace, running in production on EDC — the EU-side counterpart of Japan’s Ouranos / ODS-RAM.

For data handed across the industry — parts traceability, CO2 accounting — provin functions as the provenance layer downstream of the EDC connection, and connects to Digital Product Passport requirements.

How to adapt

Place a provin pipeline behind the Catena-X EDC connector to chain provenance of parts and CO2 data.

regulation

EU Data Act

Aligned

Applicable from 2025-09-12

eur-lex.europa.eu/eli/reg/2023/2854/oj ↗

The EU regulation imposing access and sharing obligations on IoT product data — the turning point where sharing stops being goodwill and becomes duty.

The more sharing becomes an obligation, the more the provenance of what was handed over — and a tamper-evident record that it was handed over — is worth. provin contributes signed provenance and receipt evidence to that fulfillment trail — it does not claim to prove legal fulfillment itself.

How to adapt

Make the fulfillment of data-sharing obligations verifiable with provin's signature chain.

Code samples are planned and will be added incrementally.