Markus Sabadello
Markus Sabadello
During the [25th July 2024 DID WG call](https://lists.w3.org/Archives/Public/public-did-wg/2024Jul/0033.html), I mentioned "Interface Bindings (HTTPS)" as one of four major topics for this spec. See here: - https://w3c.github.io/did-resolution/#bindings The idea of this...
During the [25th July 2024 DID WG call](https://lists.w3.org/Archives/Public/public-did-wg/2024Jul/0033.html), I mentioned "Serializations of DID Resolution Result and DID URL Dereferencing Result" as one of four major topics for this spec. See...
During the [25th July 2024 DID WG call](https://lists.w3.org/Archives/Public/public-did-wg/2024Jul/0033.html), I mentioned "DID Resolution and DID URL Dereferencing Algorithms" as one of four major topics for this spec. See here: - https://w3c.github.io/did-resolution/#resolving...
@awoie made a good suggestion that JSON-LD context files must not be retrieved from a remote location in a production environment. The DID Resolution spec could state this explicitly. See...
This removes language about how to dereference a fragment in the case of a `application/did+ld+json` DID document, and instead states that this is defined by the media type.
See this thread: https://lists.w3.org/Archives/Public/public-credentials/2018Jun/0078.html Should DID resolution distinguish between a "DID that does not exist because it has never been created" and a "DID that has been revoked"? What results...
In the HTTP Binding, should reserved characters in DID URLs be percent-encoded? E.g. probably `https://uniresolver.io/1.0/identifiers/did:sov:WRfXPg8dantKVubE3HX8pw;service=agent` should really be `https://uniresolver.io/1.0/identifiers/did%3Asov%3AWRfXPg8dantKVubE3HX8pw%3Bservice%3Dagent` See also https://github.com/decentralized-identity/papers/issues/23
One of DID Resolution's main purposes is to discover a `serviceEndpoint` URL for a DID, e.g.: ``` { "id": "did:example:123456789abcdefghi;hub1", "type": "HubService", "serviceEndpoint": "https://hub.myhost.com/1234" } ``` We could also support...
DIDs can potentially be discovered from other identifiers such as HTTP URIs, domain names, or email addresses, using e.g.: - DNS entries in a domain name's zone file (see [here](https://www.ietf.org/id/draft-mayrhofer-did-dns-00.txt)...
At the moment, the specification defines various errors that can be returned by the DID Resolution and DID URL Dereferencing functions: https://w3c.github.io/did-resolution/#errors During the 29 Aug 2024 DID WG meeting,...