Define how DID Methods can specify paths and their dereferencing rules

[wip-abramson]

Created based on Discussion in https://www.w3.org/2025/05/29-did-minutes.html

We would need to point to the DID Extensions and state how different DID methods can define the path and processing rules they are using.

There is also an ongoing discussion in #150 around whether paths should be processed consistently across DID methods.

[msporny]

Also related: https://github.com/w3c/did-resolution/issues/181

[w3cbot]

This was discussed during the #did meeting on 21 August 2025.

View the transcript

Define how DID Methods can specify paths and their dereferencing rules #156

<ottomorac> w3c/did-resolution#156

<ottomorac> Issue created by Will based on a discussion from 29-May. We would need to point to the DID Extensions and state how different DID methods can define the path and processing rules they are using. This is also connected to issue #150 related to whether paths should be processed consistently across DID methods.

Wip: Raised after discussion with Joe. Do we as a DID spec require a consistent experience across DID Methods, or is it a DID Method responsibility?

<manu> w3c/did-resolution#181

<manu> about a unified way to do path resolution

manu: I think we should. Three similar issues about this. Doesn't prevent DID Methods from having their own approaches, but we should try to get a consistent approach. Could be a long discussion, but without that we will get interop issues.

JoeAndrieu: I think we need to do it. Markus had doubts, happy Manu is for it. Should try to figure out, because there are lots of ways to do it, some in production. Differences in the DID Linked Resources, where is the data about the resource -- DIDDoc or Metadata or path?

manu: Hope is that 181 proposal is not in conflict. Special topic call to explore this as Joe suggested is a good idea.

ottomorac: Chairs to discuss and set a deep-dive session time.

---

[w3cbot]

This was discussed during the #did meeting on 04 September 2025.

View the transcript

Define how DID Methods can specify paths and their dereferencing rules w3c/did-resolution#156

<ottomorac> w3c/did-resolution#156

<ottomorac> We discussed scheduling a Special topic call for issue #156:Define how DID Methods can specify paths and their dereferencing rules. Potential options includeL 24-Sept or 3-Oct. Thoughts from Joe and Manu?

ottomorac: I wanted to mainly get thoughts from JoeAndrieu and manu

manu: either of those dates works just fine

JoeAndrieu: <finds problems with day/date alignment>

JoeAndrieu: any of these can be made to work

ottomorac: let's go with September 24th then
… sooner is better

---