Do we need to include iterating over extensions in the DID resolution algorithm?

[wip-abramson]

"Iterate over all services, verification methods, and verification relationships" <- Does this need to also iterate over any extensions in the document?

This is related to step 4 of the DID resolution algorithm that handles expanding relative URLs.

From https://github.com/w3ctag/design-reviews/issues/1157#issuecomment-3439062470

[w3cbot]

This was discussed during the #did meeting on 11 November 2025.

View the transcript

w3c/did-resolution#238

Wip: number 238 - currently there is no clear way to handle did resolution in the spec

markus_sabadello: yes I can take this on

JoeAndrieu: I don't know what they mean - properties defined in extensions registry. Nothing in did document called .. we should add did method specific properties.

manu: can we say iterate over all properties in the DID document

manu: then we don't have to talk about extensions - then just going through everything in DID Document.

JoeAndrieu: where in the spec is that you have to process all these things. Seems weird that did document resolution have to do things.

manu: this is part of the expand URLs algorithm you want to go into every object in the did document and expand the URLs

---

[peacekeeper]

I think the answer is simply "no". This step in the DID Resolution Algorithm is specifically about expanding relative URIs, not about extensions.

In other parts of the algorithm, we have statements like the following that mention extensions:

• An extension specification MAY specify how to dereference the DID path of the input DID URL.
• An extension specification MAY specify how to dereference the DID query of the input DID URL.

So personally I don't think anything needs to be done here, but maybe someone else has thoughts on addressing this comment of the review.