Skip to content

[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

Closed
mwherman2000 opened this issue Jan 3, 2019 · 3 comments
Assignees
Labels
editorial Purely editorial changes to the specification.

Comments

@mwherman2000
Copy link

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?

@David-Chadwick
Copy link
Contributor

David-Chadwick commented Jan 3, 2019 via email

@msporny msporny added the editorial Purely editorial changes to the specification. label Jan 22, 2019
@msporny msporny self-assigned this Jan 22, 2019
@msporny
Copy link
Member

msporny commented Feb 2, 2019

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).

@msporny msporny closed this as completed Feb 2, 2019
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.)
@TallTed TallTed reopened this Apr 24, 2019
@brentzundel
Copy link
Member

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
Labels
editorial Purely editorial changes to the specification.
Projects
None yet
Development

No branches or pull requests

5 participants