Describe in more detail about the Data Space Participant Registry and the relationship to iSHARE

[ssteinbuss]

• Update the section 2.10 and explain in more detail the relationship of IDS and iSHARE
• Update section 3.1.3 with the an explanation how a data space autorhity manages the Data Space Registry like in the iSHARE satellites.

[ssteinbuss]

in section 2.10 we should change the scope from to be further investigated to something more clear:

• [ ] What are the contributions of iSHARE, and what is the practical role of the iSHARE satellites?
• [ ] Admission, Withdrawl, and exclusion are already explained in section 3.1
• [ ] Signed terms and conditions are currently not managed by IDSA
• [ ] A tooling for Data Space Authorities is available with the iSHARE satellite.
• [ ] Validation of specific roles or agreements via iSHARE Satellite
• [ ] Reference to the specific policies of a data space instance

Regarding section 3.1, the role model needs to e reconsidered and the term data space authority needs to be defined, also following the discussion and outline in the IDSA Rulebook V2. This includes the Data space registry and the data space policies and self-description.

• [ ] How does the iSHARE Satellite support the Data Space Authority, Registry, and Self-Description?
• [ ] Distinguish in section 3.1.3 between certification flow in IDS and the Management of Participants by a data space authority, reference to section 4 where digital identities and claims are managed during data exchange.
• [ ] The Data Space authority needs to be added to sections 3.1.1 and 3.1.2 as a role in a data space, derived from the IDSA Rulebook.

[ssteinbuss]

The Data Holder issue needs to be addressed separately but is connected to this discussion, We might want to add this to the context of the RAM.