Markus Sabadello

Closing, since this has been moved to DID Extensions.

I generally agree with the direction of simplifying the specification by removing the abstract data model and replacing it with a concrete one (which can then be converted to different...

During the 29 Aug 2024 DID WG call, it has been mentioned that perhaps the terms "primary resource" and "secondary resource" could be confusing to readers, and that we should...

Marking as pending-close, since this has been discussed on a high level. For now, two concrete new issues have been identified related to this topic: - https://github.com/w3c/did-resolution/issues/94 - https://github.com/w3c/did-extensions/issues/582

Marking as pending-close, since this has been discussed on a high level. For now, one concrete issue has been identified related to this topic: - https://github.com/w3c/did-resolution/issues/93

Right.. For [Multibase](https://github.com/multiformats/multibase), I think aligning with [Multikey in the CID-1.0 spec](https://www.w3.org/TR/cid-1.0/#multibase-0) makes most sense, which uses `base64url` and `base58btc`. For [Multicodec](https://github.com/multiformats/multicodec/blob/master/table.csv), we may want to support some more options...

Makes sense to align with VC specs.

I had a RWoT paper with DID Resolution topics, caching is one of them: https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/did-resolution-topics.md#caching Quoting from that: _Caching behavior could be controlled by configuration of the DID Resolver, by...

There's a paper with some proposals for caching in DID Resolution, submitted to Rebooting-the-Web-of-Trust 11: https://github.com/WebOfTrustInfo/rwot11-the-hague/blob/master/advance-readings/caching-in-did-resolution.md

This issue is about the "representation" terminology entry, which currently says this: > **representation** As defined for HTTP by [[RFC7231](https://w3c.github.io/did-resolution/#bib-rfc7231)]: "information that is intended to reflect a past, current, or...