w3c
Is DID Resolution a layer defined on top of the DID layers?
...or is the DID Resolution specification a "sub-specification" of the DID specification?
I believe it more useful over the next 100 years for DID Resolution to be a layer on top of the DID layers. For example...
Being discussed/answered here: https://github.com/w3c-ccg/did-resolution/issues/18#issuecomment-461663993
The way I would put it is that the DID Resolution spec has a dependency on the main DID spec. I guess you could also call it a "layer on top". The term "sub-specification" doesn't make much sense to me.
See my answer in the other issue https://github.com/w3c/did-resolution/issues/18#issuecomment-2332184349. I think we could indeed describe a bit better how DID Resolution related to DID Core and other specs.
Does "Ready for PR" imply someone is to write something? What is the current status?
Does "Ready for PR" imply someone is to write something? What is the current status?
Yes exactly, that's the intention of the "Ready for PR" label. Currently @mccown is assigned to this. I imagine that this issue here and #18 could probably be addressed in a single PR.
This was discussed during the did meeting on 14 November 2024.
View the transcript
w3c/did-resolution#17
markus_sabadello: How DID resolution relates to DID Core.
… how a DID gets to the related DID Doc.
Wip: currently assigned to Steve McCown -- issue 17 and 18. Plans to look at those before the next meeting.
This was discussed during the #did meeting on 15 May 2025.
View the transcript
w3c/did-resolution#18
<Wip> w3c/
Clarify the role of the DID Resolution spec relative to other DID specs #18
and
Is DID Resolution a layer defined on top of the DID layers? #17
smcown: not sure about the issues or request that Mike is making...
markus_sabadello: Yes I think it may be just a couple of small changes in the intro sections...
smcown: ok let me take a look for the next meeting....
manu: yes we should probably address this...
smcown: ok
wip: can probably close it one PR for both issues...
I think this has been addressed by https://github.com/w3c/did-resolution/pull/151