Comments (4)
Based on our conversations last meeting, https://www.w3.org/2017/06/20-vcwg-minutes.html, I think it's clear we don't have a consistent term that we use for what is presented to the inspector.
We do have the terms credentials and entity profiles.
However, we do not describe the workflow as
- Issuers issue credentials
- Claimants create entity profiles combining one or more claims from one or more credentials
- Claimants present entity profiles to Verifiers
- Verifiers verify the claims are statements made by the issuer
And I think we should. The current equivalent language is
- An Issuer issues Claims about Subjects using Identifiers.
- Claimant presents claims (either directly or indirectly) to an Verifier.
- A Verifier verifies that the Claims represent statements made by the original Issuer.
Even if the terms I use above aren't quite ideal, I think we need to shift our language to use language similar to this to highlight that the lifecycle of a claim is far more flexible than traditional, static credentials where you do have to give your entire driver's license to the bouncer to get into the bar.
from vc-data-model.
The poll terminology may be fine as long as we clarify in the FPWD that this is in the simplest case of a single claim. To address issues of minimal and selective disclosure we should then also expand that flow to clarify the terms credential and entity profile.
I think our conversations often stumble because we conflate credentials, claims, and entity-profiles.
I'd prefer to just have the one inclusive flow from credentials through to profiles and for us to gradually learn to be more rigorous in how we talk about it.
For instance, I think it makes far more sense that issuers issue credentials, and that claimants present profiles. Period. The claims themselves are the individually verifiable statements within those credentials and profiles, but even when a credential has a single claim, it is clearer to discuss the issuer issuing the credential. Similarly, when a profile has a single claim, calling it a profile makes it clear the place it has in the process, who controls it, and who receives it.
I believe that clarity would improve the dialog.
from vc-data-model.
Hi Joe. Do you think this issue has now been resolved in the latest data model document? If so can we close this issue.
If not, can you propose some text changes below that would resolve the issue for you.
Thanks
from vc-data-model.
Yes. We can close this issue.
from vc-data-model.
Related Issues (20)
- Does the specification need a normative "Credential Type Specifications" section? HOT 5
- (editorial) "bitstring" vs "bit string" HOT 1
- `Type-Specific Credential Processing` is better phrasing than `Credential Type-Specific Processing` HOT 2
- Backtick characters in Internationalization / Language examples HOT 2
- typo in Terms of Use HOT 2
- Support of SHACL Schema in Version 2.0 HOT 4
- "…" as a term name in the context file? HOT 2
- Unnecessary direction attribute? HOT 12
- EnvelopedVerifiablePresentation missing in data model HOT 5
- first example contains an http url identifying a credential HOT 5
- Remove at risk issue markers for property extension points. HOT 1
- What does the hash values in §B.2 mean? HOT 4
- Proposal: remove ambiguity and asymmetry as it relates to subject identifiers HOT 7
- Do we need sha3-512 in the vocabulary tables? HOT 6
- Should we use `Ed25519Signature2020` in the Examples? HOT 3
- Unmatched HTML Tag HOT 3
- Revisit Verifiable Credential media types HOT 19
- consider merging 3.4 and 5.1 as both sections are about the credential lifecycle. HOT 1
- Add issuee definition HOT 17
- Truth (or falsity) is not part of VCDM ecosystem HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from vc-data-model.