- From: Orie Steele <orie@transmute.industries>
- Date: Tue, 30 Jul 2024 17:56:59 -0500
- To: "W3C Credentials CG (Public List)" <public-credentials@w3.org>
- Message-ID: <CAN8C-_LTiSe_TPJcu9+a=WEOpgiBXdtiGezypBtj17HHKEUipA@mail.gmail.com>
Hi, I noticed that the respec for did-method-web was misconfigured, and rendering errors. I merged several open pull requests from 2023, fixed the respec and removed myself as editor. I suggest CG Chairs appoint a new editor to replace me, and schedule some recurring calls to ensure the document progresses to FCGS (eventually). I hope the DID WG will define standard path and query behavior for DIDs. I suspect many people will eventually wish for IDNA compatible DID URLs like: did:web:نامهای.com/path/supported?query=supported#sub-resource-id <http://xn--mgb44a.com/path/supported?query=supported#sub-resource-id> See also: - https://url.spec.whatwg.org/#idna - https://www.unicode.org/reports/tr46/ - https://www.w3.org/TR/did-core/#did-syntax - https://bcgov.github.io/trustdidweb/#international-domain-names For those wanting to support controller documents with international domain names today (without waiting for the DID WG to finish defining path and query syntax), I recommend reviewing: https://www.w3.org/TR/controller-document/ Unlike the DID in the example above, these URLs are understood by browsers and supported in HTTP clients today: https://نامهای.com/path/supported?query=supported#sub-resource-id (404) https://i❤️.ws#page-top <https://xn--i-7iq.ws/#page-top> (works but does not resolve to a controller document) Regards, OS
Received on Tuesday, 30 July 2024 22:57:15 UTC