did-resolution
did-resolution copied to clipboard
w3c
Expand relative URLs to absolute URLs in "id" fields
This issue tracks an idea described here by @msporny: https://github.com/w3c-ccg/did-spec/issues/97#issuecomment-512518247
DID Resolvers could always modify the "just fragment identifiers" in a DID Document to be the entire DID plus fragment.
Related to https://github.com/w3c-ccg/did-resolution/issues/9
This was discussed during the did meeting on 23 January 2025.
View the transcript
w3c/did-resolution#40
markus_sabadello: This is an extension. Makes them easier to consume but could be an extension.
<Zakim> JoeAndrieu, you wanted to ask about expansion
<Zakim> manu, you wanted to support expansion in core spec.
JoeAndrieu: Not sure of the idea of extension -- DID Method specific. Can't verify the DIDDoc if there are extensions.
manu: Feature is only for a DID URLs -- fragments. "#key-1" -- should use automatically mean that the DID is prepended.
manu: Should be in the core, so there is no need to repeat the DID everywhere and creates opportunity for errors.
markus_sabadello: Not DID Method specific. You get the DIDDoc as is, and then could do transformations.
<Zakim> JoeAndrieu, you wanted to say it still doesn't apply to did:btc1
JoeAndrieu: You lose independent verification if the resolver gives something back other than the DIDDoc.
manu: Presumed it to be a flag so not needed.
This was discussed during the did meeting on 23 January 2025.
I do not think we reached consensus on what to do with this issue.
@msporny advocated for it to be introduced into the core spec, as a flag that could be passed to the resolver.
@jandrieu had concerns about it effecting the independent verifiability of resolution results if the DID document is transformed by the resolver.
Lets continue the discussion here. Anyone else feel strongly about this issue?
Closing, since https://github.com/w3c/did-resolution/pull/126 has been merged.