- From: Manu Sporny <msporny@digitalbazaar.com>
- Date: Tue, 3 Feb 2026 09:58:24 -0500
- To: W3C Credentials CG <public-credentials@w3.org>
- Cc: Amir Hameed <amsaalegal@gmail.com>
On Tue, Feb 3, 2026 at 4:59 AM Amir Hameed <amsaalegal@gmail.com> wrote: > Instead of https://server.com/resource, UDNA uses udna://did:entity.example/resource. Amir, on this point specifically, have you been following the DID Resolution PathService discussion? https://github.com/w3c/did-resolution/issues/181 ... which resulted in this PR: https://github.com/w3c/did-resolution/pull/260 Easier to read section here: https://pr-preview.s3.amazonaws.com/swcurran/did-resolution/pull/260.html#pathservice-service-type Ultimately, it enables any DID Method to do this: did:example:123456/resource and map that resource to any URL, for example: https://2001:db8:85a3::8a2e:370:7334/resource How much of an overlap with UDNA is there with the PathService feature in DID Resolution? -- manu -- Manu Sporny - https://www.linkedin.com/in/manusporny/ Founder/CEO - Digital Bazaar, Inc. https://www.digitalbazaar.com/
Received on Tuesday, 3 February 2026 14:59:06 UTC