Guiding Questions
Purpose: Capture regulatory and business needs for data lineage to support compliance and value-added services.
Requirements & Use Cases
Which legal, contractual, or sectoral requirements exist for provenance and traceability?
Are there AI Act or other regulatory triggers that mandate detailed data lineage or traceability?
Are there business cases for using provenance data to add value (e.g., sustainability claims, quality certification)?
Purpose: Adopt or extend existing provenance ontologies to flexibly represent traceability information.
Data Modelling
Will existing ontologies (e.g., W3C PROV-O, PAV) be adopted and extended for sector needs?
Should provenance be modelled as “events” (e.g., CloudEvents) for flexibility?
Purpose: Define storage, retention, encryption, and access policies for provenance data across participants.
Storage & Management
Will provenance/traceability data be stored locally by participants, by certified 3rd parties, or in a hybrid model?
What are the retention, encryption, and access control policies?
Purpose: Clarify which processes and telemetry data should be observable for governance and monitoring purposes.
Observability Scope
Which Control Plane activities (catalog publication, contract negotiation, transfer process) will be observable?
Will operational telemetry (uptime, performance) also be included under the same governance?
Purpose: Designate certified observability providers while avoiding centralization and systemic risks.
Trust & Third Parties
Which organisations could act as certified observability service providers?
How will centralization risks be mitigated?
Purpose: Integrate provenance and traceability rules into the rulebook under governance oversight. Governance Linkages
Governance Linkages
How will rules for provenance and traceability be reflected in the rulebook?
Which governance body will approve changes to provenance and traceability standards or processes?
Last updated