Clarify DID support in the SSI-CID authentication suite - #233
Open
acoburn wants to merge 1 commit into
Open
Conversation
Member
|
Would it be useful to reference in this suite And maybe add non-normative snippet from |
Member
|
LWS WG's DID expert could also double check terminology with: https://www.w3.org/TR/did-resolution/#conformance |
Member
|
FWIW: CID spec seems to have chosen |
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
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.
Resolves #231
As a follow-on to the retirement of the SSI-DID-Key Authentication suite (#229), this adjusts the SSI-CID Authentication suite to be more explicitly inclusive of DID methods.
The only normative change is a change from stating "the verifier MUST dereference the sub (subject) claim" to be "the verifier MUST resolve the sub (subject) claim"
All other changes are in non-normative sections, including the addition of an introductory note about compatibility with DID-1.1 (currently in CR status)