This repository was archived by the owner on Jun 13, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 19
Create Communication Guide V2 #74
Copy link
Copy link
Open
Labels
Topic: DocumentationImprovements or additions to documentationImprovements or additions to documentationenhancementNew feature or requestNew feature or requeststatus:in-progressissue has been assigned and is currently being worked onissue has been assigned and is currently being worked on
Milestone
Description
name: Epic
about: Create a new Version of the IDS Communication Guide that is more specific and unamigious
title: 'Create Communication Guide V2'
labels: 'documentation; enhancement'
assignees: @ssteinbuss
Rationale
There is a need for further clarification on IDS Specification:
- The current Specifications are not unambiguous and lack important details
- A workshop series will work with a small and targeted group on an updated version of the IDS meta protocol specification
- This will have a clear impact on other IDSA artifacts, i.e., connectors and IDS-testbed
Owner
@ssteinbuss ; IDSA TSC.
Stakeholder Point of Contact
@ssteinbuss and the Communication Guide Workshop series on Thursdays.
Stakeholders are the developers and creators of IDS Core Components.
Dependencies
Description
To achieve this, IDSA will -
- evolve to support high-performance modern commercial-grade customer use cases (Kubernetes-ready, Gaia-X-ready, leveraging cloud-native compute foundation CNCF).
- simplify complexity for easy implementation of existing data products. (brownfield integration)
- find a good balance between standards and user flexibility (80/20 rule?). - find a good balance between architecture and specs.
The Outcome Outcome will be:
- a specification of the interaction of the IDS components with the data products [and the data models/data-products(to be specified) in use, the metadata in use (e.g., data usage policies, data offerings(what is the same as data products) ].
- This includes a tiered approach including/emphasizing mandatory and optional aspects.
Context
The IDS-G Communication specifications shall be precise and unambiguous so that they can be implemented interoperably.
Issues
- New Structure for Communication (Guide) #55
- Common entities in a data space #57
- Update Catalog section in communication Guide #60
- Update Contract negotiation part in Communication Guide #61
- Update Data Transfer part in Communication Guide #62
- Update identities section in Communication Guide #63
- Updata Trust Framework in Communication Guide #64
- Update Policies section in Communication Guide #65
- Update Registration section in Communication Guide #66
- Collect Foundational standards #67
Acceptance criteria
To be defined
Proof
To be defined
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Topic: DocumentationImprovements or additions to documentationImprovements or additions to documentationenhancementNew feature or requestNew feature or requeststatus:in-progressissue has been assigned and is currently being worked onissue has been assigned and is currently being worked on