Roadmap#148 Enable Portal for Multi-Identity Clearing House for Regional Identity Verification

[MaximilianHauer]

Overview

Explain the topic in 2 sentences

Issue is a blocker for the efforts resulting out of the roadmap item

• https://github.com/catenax-eV/sig-roadmap/issues/148

What's the benefit?

What are the Risks/Dependencies ?

Detailed explanation

Current implementation

Proposed improvements

Feature Team

Contributor

• Contributor 1
• Contributor 2

Committer

• @oyo
• @ntruchsess
• @Phil91
• @evegufy
• @matbmoser

User Stories

• Issue 1, linked to specific repository
• Issue 2, linked to another specific repository

Acceptance Criteria

• Criteria 1
• Criteria 2
• Criteria 3

Test Cases

Test Case 1

Steps

1. Do something
2. Click something
3. Add something

Expected Result

1. Expectation
2. Expectation
3. Expectation

Architectural Relevance

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: (Fill this out, if at least one of the checkboxes above cannot be ticked. Contact the Architecture Management Committee to get an approval for the justification)

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)

[MaximilianHauer]

@ma3u wer von cofinity ist hier im lead für das Thema ? derjenige sollte das Thema auch für das sig-release einsteuern. Ich habe hier damals nur einen "puffer" angelegt damit das Thema nicht durch rutscht.

[ma3u]

Erik Wiegert and Dorka Bajazak

[stephanbcbauer]

Some hints from Release Management (@ther3sa) and Tractus-X Project Lead (@stephanbcbauer)

• Status currently in Inbox. ⇾ Only features with status backlog are considered in open planning
• Please add missing sections from the feature template, or fill them out
• Please add contributor and committer
• Please add assignee (overall responsible person who drives the feature)

[evegufy]

Committers:
@oyo
@ntruchsess
@Phil91
@evegufy

[evegufy]

@ybidois as discussed yesterday, the description should be updated by you. If you don't want to create new issue, I have the permission to update the existing description (and title), if you provide that information as comment, I can paste it accordingly

[stephanbcbauer]

@ybidois mentioned ⇾ still in discussion ⇾ high priority issue

[ma3u]

In Catena-X Board we already create a Roadmap item with further informations:

• https://github.com/catenax-eV/sig-roadmap/issues/148

The Catena-X components in steps 6 and 7 use the mandatory notarization and compliance services of Gaia-X Targus Release:

Step 6 Portal Registration: connect to Compliance Service

Step 7 SD Factory: connect to Notarization Service => temporary suspended

Step 8 store the Legal participant Credential => NOT in Jupiter standard anymore

The team needs to implement a List of Clearing Houses with the mapping to countries

@HFocken: Decision by Catena-X association required: If there is an overlapping country coverage of two or more Clearinghouse exists. What is the rule for a correct clearing of the onboarded company.

Related task (CAICT will implement the clearing house with the actually Tagus Release):

• Integrate the Gaia-X Clearinghouse Interface - Compliance GX Tagus Release V2 Api #993

Motivation, Goals, and Acceptance Criteria need to be delivered by the Internationalization committee:

• https://github.com/catenax-eV/sig-roadmap/issues/221

[matbmoser]

I am interested to keep informed on this part and participate in the design discussions

[ma3u]

Contributors: @dhiren-singh-007, @tfjanjua

[ma3u]

Follow-up the coordination in Catena-X Internationalization Commiitee:

• https://github.com/catenax-eV/sig-roadmap/issues/221