update glossary #7
Conversation
|
Hi @ticapix , thanks for activly engaging in this work. Your contribution will be reviewed and discussed here and during our meetings. Please keep in mind that we do have our contributing guidelines which ask for an issue first, before creating a PR. If you could provide a justification for your proposed changes, that would make it a lot easier to assess your contribution. |
|
I agree that definitions should come from established specifications and standards. I'll check the ISO and EDWG associated specs for the terms as those have the the closest reference and come up with a proposal. We might wait for the successful PAS submission. Again, feel free to comment on the terminology in the corresponding specification projects. |
| ## Introduction to Decentralized Claims in Dataspaces | ||
| The issuance, presentation and verification of decentralized claims requires a protocol for securely sharing decentralized identities and credentials. It helps ensure that data access is secure by verifying identities and credentials without relying on a central authority. | ||
| ## Introduction to Verifiable Credentials in Dataspaces | ||
| The issuance, presentation and verification of verifiable credentials requires a protocol for securely sharing policies, claims and evidence. |
There was a problem hiding this comment.
Please justify evidence. This is about the protocol and not about a Trust Framework. Otherwise remove.
There was a problem hiding this comment.
The protocol are for exchanging verifiable credentials (not claims)
The claims are inside the exchanged verifiable credentials. So are evidence.
What Trust Framework ?
| ## Introduction to Verifiable Credentials in Dataspaces | ||
| The issuance, presentation and verification of verifiable credentials requires a protocol for securely sharing policies, claims and evidence. | ||
| It helps ensure that information is traceable and tamper-proof. | ||
| The additional use of decentralised identifiers to identify verifiable credentials, policies, claims and evidence helps ensure that data access is secure by verifying identities and credentials without relying on a central authority. |
There was a problem hiding this comment.
Again, evidence, see comment before.
This document is not limited to access control, but about the reconciliation of policies and claims. Your reference here is a data plane activity.
| - __Verifier:__ An entity that checks the validity of the credentials presented by participants. | ||
| - __Self-Issued ID Tokens:__ Tokens created and signed by participants themselves to prove their identity. | ||
| - __Wallet:__ a store for Verifiable Credentials | ||
| - __Dataspace:__ Interoperable framework, based on common governance principles, standards, practices and enabling services, that enables trusted data transactions between participants. (DSSC v2) |
There was a problem hiding this comment.
Rejected. We base our work on ISO/IEC DIS 20151.
| - __Self-Issued ID Tokens:__ Tokens created and signed by participants themselves to prove their identity. | ||
| - __Wallet:__ a store for Verifiable Credentials | ||
| - __Dataspace:__ Interoperable framework, based on common governance principles, standards, practices and enabling services, that enables trusted data transactions between participants. (DSSC v2) | ||
| - __Participant:__ A natural person or a legal person committed to the governance framework of a particular data space and having a set of rights and obligations stemming from this framework. (DSSC v2) |
There was a problem hiding this comment.
Rejected. We base our work on ISO/IEC DIS 20151
| - __Wallet:__ a store for Verifiable Credentials | ||
| - __Dataspace:__ Interoperable framework, based on common governance principles, standards, practices and enabling services, that enables trusted data transactions between participants. (DSSC v2) | ||
| - __Participant:__ A natural person or a legal person committed to the governance framework of a particular data space and having a set of rights and obligations stemming from this framework. (DSSC v2) | ||
| - __Credential Issuer:__ A role an entity can perform by asserting claims about one or more subjects, creating a verifiable credential from these claims, and transmitting the verifiable credential to a holder. (W3C VC) |
There was a problem hiding this comment.
| - __Dataspace:__ Interoperable framework, based on common governance principles, standards, practices and enabling services, that enables trusted data transactions between participants. (DSSC v2) | ||
| - __Participant:__ A natural person or a legal person committed to the governance framework of a particular data space and having a set of rights and obligations stemming from this framework. (DSSC v2) | ||
| - __Credential Issuer:__ A role an entity can perform by asserting claims about one or more subjects, creating a verifiable credential from these claims, and transmitting the verifiable credential to a holder. (W3C VC) | ||
| - __Verifier:__ A role an entity performs by receiving one or more verifiable credentials, optionally inside a verifiable presentation for processing. (W3C VC) |
| - __Participant:__ A natural person or a legal person committed to the governance framework of a particular data space and having a set of rights and obligations stemming from this framework. (DSSC v2) | ||
| - __Credential Issuer:__ A role an entity can perform by asserting claims about one or more subjects, creating a verifiable credential from these claims, and transmitting the verifiable credential to a holder. (W3C VC) | ||
| - __Verifier:__ A role an entity performs by receiving one or more verifiable credentials, optionally inside a verifiable presentation for processing. (W3C VC) | ||
| - __Self-Issued ID Tokens:__ A verifiable credential where the issuer is also the subject. |
There was a problem hiding this comment.
Not sure to understand what is unclear to you in self-issued ID Token
| - __Credential Issuer:__ A role an entity can perform by asserting claims about one or more subjects, creating a verifiable credential from these claims, and transmitting the verifiable credential to a holder. (W3C VC) | ||
| - __Verifier:__ A role an entity performs by receiving one or more verifiable credentials, optionally inside a verifiable presentation for processing. (W3C VC) | ||
| - __Self-Issued ID Tokens:__ A verifiable credential where the issuer is also the subject. | ||
| - __Wallet:__ a type of [credential repository](https://www.w3.org/TR/vc-data-model-2.0/#dfn-credential-repositories) to store Verifiable Credentials. |
| ### Fundamentals | ||
| 1. Issuing Credentials: A Credential Issuer provides verifiable credentials to an organization. These credentials can be used to prove the organization's identity and access rights. | ||
| 2. Presenting Credentials: The organization presents these credentials to a Verifier when providing claims to another party. The Verifier checks the credentials' validity using a decentralized registry. | ||
| 1. Issuing Credentials: A Credential Issuer provides verifiable credentials to a participant. These credentials can be used to prove the participant's identity and access rights. |
There was a problem hiding this comment.
line 70 is the line 66, updated to be use the term participant defined above.
Are you missing context from the original document ?
| 1. Issuing Credentials: A Credential Issuer provides verifiable credentials to an organization. These credentials can be used to prove the organization's identity and access rights. | ||
| 2. Presenting Credentials: The organization presents these credentials to a Verifier when providing claims to another party. The Verifier checks the credentials' validity using a decentralized registry. | ||
| 1. Issuing Credentials: A Credential Issuer provides verifiable credentials to a participant. These credentials can be used to prove the participant's identity and access rights. | ||
| 2. Presenting Credentials: The participant presents these credentials to a Verifier when providing claims to another participant. The Verifier checks the credentials' validity using a [verifiable data registry](https://www.w3.org/TR/vc-data-model-2.0/#dfn-verifiable-data-registries). |
ssteinbuss
left a comment
ssteinbuss
left a comment
There was a problem hiding this comment.
All requested changes are not justified or out of context. Please provide additional details
I agree. Isn't IDSA a member of the DSSC Technical Architecture Board and the DSSC an European project of 28 international established organisations ? DSSC definitions are available online. |
3 participants
In the context of #8 :
Update glossary with definitions from existing specifications (W3C) or documents build by consensus (DSSC)