Markus Sabadello

@mwherman2000 Yes I have also been thinking about these as orthogonal questions, I would just note that for the second "axis": * Not every DID method involves a "ledger". *...

Maybe an analogy from the HTTP URL world would be things like `http://localhost/` or `http://192.168.1.1/profile.html`. The returned resource depends on who dereferences it. From [RFC3986](https://tools.ietf.org/html/rfc3986#page-6): > URIs have a global...

This has been addressed by https://github.com/w3c/did-resolution/pull/179, marking as pending-close.

I think we're overcomplicating this discussion about paths. I actually think that everything is basically fine the way it works now, including the algorithm in https://www.w3.org/TR/did-resolution/#dereferencing-algorithm-resource. @jandrieu wrote: > a...

Maybe change > where each item is a map that contains a to > where each item is a map that represents a

Coming back to this topic, there has been an extension DID parameter called "transformKeys" for a while that can convert verification methods in DID documents to JWK, or an entire...

I think this can be closed, since the extension registry also lists the DID parameter transformKeys: https://w3c.github.io/did-extensions/resolution/#transformKeys-param Which is defined here: https://github.com/decentralized-identity/did-spec-extensions/blob/main/parameters/transform-keys.md It includes support for JWKS, which is what...

Closing, since this feature is possible with an extension parameter.

Unassigning myself from this for now. Maybe @aphillips or someone else could propose a PR to address this?

> I think it would be better to have a single term I strongly disagree with removing or blurring the differentiation between resolving a DID and dereferencing a DID URL....