You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MUST raise invalidDid if the multibaseValue does not begin with the letter z.
I have been assuming so far that the invalidDid error would be returned only if the DID doesn't conform to the generic DID Core syntax. So if you try to resolve did:key:12345, the error would actually be notFound, since the DID does conform to the generic DID Core syntax, but the method-specific ID "12345" doesn't exist within the did:key method.
But maybe my assumption was wrong. I also understand the rationale that invalidDid would cover not only the generic DID Core syntax, but also method-specific syntax requirements (starting with z, in this case). So, just opening this issue to talk about it. We could define this in more detail in the DID Resolution spec: https://w3c-ccg.github.io/did-resolution/#errors
The text was updated successfully, but these errors were encountered:
I actually agree with you here and think that invalidDid should only be used for dids that don't meet the requirements from did core. There is an issue on the spec itself about this: w3c-ccg/did-method-key#60
I see that one of the tests is:
I have been assuming so far that the
invalidDid
error would be returned only if the DID doesn't conform to the generic DID Core syntax. So if you try to resolvedid:key:12345
, the error would actually benotFound
, since the DID does conform to the generic DID Core syntax, but the method-specific ID "12345" doesn't exist within thedid:key
method.But maybe my assumption was wrong. I also understand the rationale that
invalidDid
would cover not only the generic DID Core syntax, but also method-specific syntax requirements (starting withz
, in this case). So, just opening this issue to talk about it. We could define this in more detail in the DID Resolution spec: https://w3c-ccg.github.io/did-resolution/#errorsThe text was updated successfully, but these errors were encountered: