Update dataspace section #13
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
"The rest of the community" is a bold statement, as the IDSA's definition is consistent with ISO 20151 and the EDWG's perspective. |
mspiekermann
requested changes
Jun 12, 2025
|
|
||
| Dataspaces are designed to enable software agents representing organizations to negotiate data sharing contracts and to execute on those. A data sharing contract might represent a one-time data transfer, a continuous stream of data, or a regularly recurring event (e.g. regulatory data sharing obligations). Many of these activities will need to be automated to a degree where thousands of those negotiations and/or contract validations can happen in seconds. Take for example the use case of Manufacturing-X mentioned above. If every single part of a car, plane, train, ship or sufficiently complex industrial goods needs to be accompanied by a Digital Product Passport, which needs to be shared throughout the supply chain it will be prohibitively expensive and slow to have each and every sharing contract agreed upon and approved by humans. Especially as the legal entities participating are companies and the human end user requesting the setup of a data sharing contract is at best metadata information to tie the contract negotiation to a legal representative of the organization. However, even in those cases the human end-user doesn’t need to be represented in the data sharing contract as a credentialed identity, as it’s always the organization that is the entity which needs identification and credentials. | ||
| To be noted that in many dataspace such as Health, Finance, Education&Skills, the policy, claims and evidences exchanged using verifiable credentials, can be bound to a human which is not necessarly a legal representative of a organisation. |
There was a problem hiding this comment.
#4 includes the discussion and explains how end users fit into the dataspace concept.
| Given that peculiar definition of a dataspace by IDSA, the additional features set provided by OID4VC protocol are superfluous compared to the DCP protocol natively designed for the centralised IDSA Reference Architecture Model. | ||
| As such, a dataspace gouvernance that does not require, rights delegation, consent management, mandate, nor any form of legally relevant claims and evidence traceability, can use DCP. | ||
|
|
||
| For other data space governances where end-to-end tracability of policy, claims and evidence are required, either due to policy compliance or regulatory compliance, the OID4VC protocol is better suited. | ||
|
|
There was a problem hiding this comment.
The used perspective on dataspaces within this IDSA's definition is consistent with ISO 20151 and the EDWG's perspective. This is not even contradicting the discussed concepts of Data Spaces Support Center, CEN/CENELEC Trusted Data Transaction, FIWARE, Gaia-X, it is just not mixing different perspectives and separates technology, business, and regulation layers.
I am not against highlighting the different perspectives (we again just have to refer #4 ) , but the statements made here in the PR are just wrong.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
in the context of #8
highlight the major different between the definition of a dataspace by IDSA and the rest of the community.