[R25.03] [Architecture] Propose a B2C tech solution to enable public access of cx-data maintaining Data Sovereignty

[matbmoser]

Overview

As we got to know by the VDA Verband der Automobilindustrie e. V. one of the requirements from the regulations is that a part of the "Battery Passports", "Digital Product Passports" and other products' data MUST be accessed not in B2B by any public consumer. It was noted during a meeting with the Digital Product Pass Expert group and the stutainability domain that Catena-X has currenltly no plan or solution to tackle that.

I have something in mind already, but I would like to propose it formally and discuss it with the architecture committee first

Motivation

• I want to find how big is the problem, and what are the actual requirements on this topic, talking with the expert groups and discussion possible solutions.
• I want that people do not need to use two dataspaces or not use catena-x at all because this feature is not clarified or available.
• I want that Catena-X can provide an answer to this topic so that companies choose Catena-X as a "complete" solution for complying with the regulations.

Explain the topic in 2 sentences

There MUST be a solution that allows end users to view data from OEMs. Currently, Catena-X supports only, B2B and not B2C because the EDC requires companies to be onboarded in Catena-X.

I want to propose and analyze the impact of enabling a tech solution for B2C interaction while still maintaining the Data Sovereighty, increasing the interoperability with other non-edc dataspaces.

What's the benefit?

Enables any users to use Catena-X Standards and Values (Data Sov, Decentrality, Interoperability, Secure) to retrieve data from B2C. Increasing also the interoperability with multiple networks which do not use the EDC connector.

What are the Risks/Dependencies ?

• Architecture Committee
• Digital Product Pass Expert Group -> Problem Description
• Sustainability Committee
• Data Sovereighty Expert Group
• Certification

Detailed explanation

I have drafted a proposal on how can Catena-X maintain their data sovereighty concept, and still be able to handover data throught the EDC to other non-edc dataspaces. Also providing a "public interface" for Customers to retrieve a limited set of data which lies behind the EDC in a Data Source.

This is mandated by regulation, so many organizations are implementing central solutions to enable this kind of behavior. So the idea here is to decentralize the public data provision and enable data sovereignty concepts using SSI.

In this way that the "complete" set of data would be shared via the "EDC" and the regulatory public data using another interface which needs to be proposed and discussed in this feature.

Current implementation

1. Eclipse Data Space Connectors (EDC) supports only B2B connections by design.
2. Catena-X is using just the EDC to retrieve and provide data for companies.
3. The EU regulations mandate that economic operator companies provide public data to customers.
4. Currently, Authorities and Customers are not allowed to retrieve data

Proposed improvements

1. Catena-X propose a standard for providing public data (B2C) with data sovereighty. Provides simple reference implementation.
2. Authorities and Consumers can retrieve a set of partial data using catena-x B2C interface and visualize the data.
3. Catena-X will help companies comply with the regulations and it will have success in the market
4. Companies that require more than just "public" data can use the "Connector" and the policies to retrieve the complete set of data.

Feature Team

Committer

• @matbmoser
• Any volunteers?

User Stories

• Issue 1: Document and Specify the problem
• Issue 2: Draft a technical concept which gives a solution to the B2C public data access problem
• Issue 3: Create a whitepaper with the Architecture Committe
• Issue 4: Present to the respective committees and expert groups, aligning the perspectives.

Acceptance Criteria

• [ ] The problem statement is cleary defined
• [ ] The technical solution is drafted and clear
• [ ] Consensus from the Architecture Committee is granted
• [ ] A white paper document in Github must be generated to document this proposal (create sig-architecture?)

Test Cases

None

Expected Result

• Catena-X has at least a draft solution for B2C at the Architecture Committee publishing whitepaper
• Feedback is gathered from all the interested expert groups
• Catena-X Expert Groups (DPP, PCF, ESG, etc..) can propose a standard for this use case

Examples

• https://thebatterypass.io/en/did:web:acme.battery.pass:0226151e-949c-d067-8ef3-162431e28976
• https://vera-staging.dpp.spherity.dev/?did=did:web:api-rcs.susi.spherity.dev:did-registry:acme-power-drive-x-1000-3985-cb-1739186-d-8-d

Architectural Relevance

It will enable Catena-X to do B2C data exchanges, maintaining data sovereignty and increasing interoperability.

The following items are ensured (answer: yes) after this issue is implemented:

• [ ] This feature aligns with our current architectural guidelines
  • Data Sovereignty: All data sharing activities across company boundaries follow the Catena-X Regulatory Framework, in particular the Data Exchange Governance, and the Dataspace Protocol via a compliant Connector (like the tractusx-edc or similar, see Connector KIT)
  • [ ] CX-0010 Business Partner Number
  • [ ] CX-0013 Identity of Member Companies
  • [ ] CX-0018 Data Space Connectivity (EDC)
  • [ ] CX-0049 DID Document Schema
  • [ ] CX-0050 Framework Agreement Credential
  • [ ] CX-0149 Verified Company Identity
  • Interoperability: Digital Twins are used (compliant to the Digital Twin KIT and the Industry Core KIT)
  • [ ] CX-0001 EDC Discovery API
  • [ ] CX-0002 Digital Twins in Catena-X
  • [ ] CX-0018 Data Space Connectivity (EDC)
  • Data Format:
  • [ ] The data model is based on a published Semantic Model
• [ ] The impact on the overall system architecture has been assessed. The Feature does not require changes to the architecture or any existing standard? Please have a look here on the overarching architecture
• [ ] Potential risks or conflicts with existing architecture has been assessed

Justification: This feature will be proposed in the Architecture Management committee

Additional information

• [ ] I am aware that my request may not be developed if no developer can be found for it. I'll try to contribute a developer (bring your own developer)

Possible Solutions

• Enable DID:WEB interface that is able to retrieve public data from an EDC connector.
  • 
  • Maybe the Web App in the consumer side is an "not authenticated connector?"
  • Maybe this connector can have a "self issued credential? by default?" so anyone can deploy it in their local and retrieve public data???
  • How would catena-x specify this public data agreement
• Create a new type of "operating"/"certified" company which is allowed to provide public data to the external world using an application without login.
  • 

[matbmoser]

@lgblaumeiser now that I am not inside yet of the Architecture Committee can you let them aware that there is this problem, I have found it yesterday in a meeting with @stanfaldin and the VDA.

I want to take this topic and discuss with them together once I join Catena-X.

[matbmoser]

I would like to create a "sig-architecture" so we can centralize and publish this topics. @stephanbcbauer what do you think about that?

[matbmoser]

Maybe place the dpp in Cofinity-X? And all then Cofinity-X would enable a public interface, retrieving data from the edcs from companies.

Maybe we could add a new operator company type, which are certified or allowed to provide public data from Catena-X.

Maybe like this: