-
Notifications
You must be signed in to change notification settings - Fork 115
[Mode of Operation] Is it necessary to specify only the *final* holder ... #363
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
editorial
Purely editorial changes to the specification.
Comments
On 03/01/2019 15:55, Michael Herman (Toronto) wrote:
In https://w3c.github.io/vc-data-model/#mode-of-operation, it states
The final holder presents its verifiable credentials to the verifier
in a verifiable presentation, requesting a supported action.
Is it necessary to specify that only the /final/ holder a present its
VCs to the verifier? Why can't any holder in the chain present the VCs
to a verifier vs. just the final holder?
Of course any holder MAY present the VC, but in this case only the final
holder DID present the VC. So how to differentiate between the holder
that did and the holder that didnt?
David
…
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#363>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADe4_04KPH7VOxvs5Q6IzPzMeN5dyqpmks5u_ifugaJpZM4ZoVLW>.
|
I believe @David-Chadwick has answered your question @mwherman2000 and I don't expect we need to add more text to the spec to make that distinction. Closing, please re-open if you disagree (and suggest concrete spec text so we have something to consider/refine). |
TallTed
added a commit
that referenced
this issue
Apr 24, 2019
revisiting #363 - I think this deserves changing. "Final holder" suggests that the VC cannot be passed to another holder after this one -- but that's not so. As any step in the lifecycle can recur, and the order of those steps may vary, "final" has no place in it. (I also think this is editorial, but others may have differing opinion.)
I believe this has been addressed via the solution for issue #577 and should be closed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In https://w3c.github.io/vc-data-model/#mode-of-operation, it states
Is it necessary to specify that only the final holder a present its VCs to the verifier? Why can't any holder in the chain present the VCs to a verifier vs. just the final holder?
The text was updated successfully, but these errors were encountered: