EDC - Bi-directional transfers for Metadata (i.e. Feedback Channel)

eclipse-tractusx / sig-release

https://eclipse-tractusx.github.io/sig-release

Apache License 2.0

8 stars 8 forks source link

EDC - Bi-directional transfers for Metadata (i.e. Feedback Channel) #624

Open stefan-ettl opened 4 months ago

stefan-ettl commented 4 months ago

As a Dataspace Participant consuming data from a data provider, I want to have a possibility to give feedback about the received data using the negotiated contract and its metadata.

Upstream EDC Some data sharing scenarios require both the provider and consumer to supply transfer metadata. Support the ability to exchange transfer metadata in a full-duplex fashion.

[ ] Concept/Idea for "a Back Channel" has been created.

Initial creator: @jimmarino

stephanbcbauer commented 4 months ago

Was presented in open planning ⇾ contributors and committer are involved.

stephanbcbauer commented 2 months ago

Hello @stefan-ettl , @jimmarino , @lgblaumeiser

Since the feature is a 24.08 feature and the development phase is coming to an end, we need a status on the feature.

[ ] Currently you are assigned (Responsible) → Is this correct? If not, please assign the correct contact person
[ ] Please check whether the status (backlog, work in progress ...) is set correctly
[ ] Please check whether there is an assignment to a committee or expert group (supported-by) to be found on the board
[ ] Please comment on the current status of the feature
[ ] Are all SubTasks (issues from other repositories that deal with the feature) linked? → The easiest way is to mention the feature here in the issue (via the ID) so we can see which teams/repositories are involved.

If you need any clarification, please get in touch, thank you very much. Stephan

lgblaumeiser commented 2 months ago

@stephanbcbauer , this issue is not on the supported-by board mentioned above, I have not found any reason, why not, can you please have a check?

lgblaumeiser commented 2 months ago

2024-06-11

[x] Currently you are assigned (Responsible) → Is this correct? If not, please assign the correct contact person
[x] Please check whether the status (backlog, work in progress ...) is set correctly
[x] Please check whether there is an assignment to a committee or expert group (supported-by) to be found on the board
[x] Please comment on the current status of the feature: About to be started, as it is a concept, providing the result is not test relevant for the release
[x] Are all SubTasks (issues from other repositories that deal with the feature) linked? → The easiest way is to mention the feature here in the issue (via the ID) so we can see which teams/repositories are involved.

lgblaumeiser commented 2 months ago

Concept document will be ready with the Catena-X release

stephanbcbauer commented 1 month ago

Hello @lgblaumeiser

In a few weeks, we want to publish Tractus-X Release 24.08. For this, we need a clear status about the features (which will be included in the release and which will be cancelled or postponed to the next release).

Currently, the feature is still in status Work in progress. Please update the status by 09.07.24 eob.

If the feature is not ready for release 24.08, or it is possibly not planned at all, please set the status to Not in release. Please remember that in this case, any dependent components must be informed.

Thank you and best regards.

jimmarino commented 1 month ago

I have the concept document written. I'll make a PR against the TX-EDC. This should satisfy the requirement.