- From: Markus Sabadello <markus@danubetech.com>
- Date: Mon, 19 Nov 2018 13:25:28 +0100
- To: public-credentials@w3.org
- Message-ID: <f25641d0-ec13-c181-525e-4e661c4d0191@danubetech.com>
Hello Mrinal, Thanks for your comments, the ABNF isn't fully up-to-date. There's currently some discussion about the exact syntax for service names: https://github.com/w3c-ccg/did-spec/issues/90 Also note that we're still missing did-query in the ABNF: https://github.com/w3c-ccg/did-spec/issues/85 A specific DID method can certainly NOT override the generic ABNF! Here's the ABNF we're currently using in the Universal Resolver <http://uniresolver.io/> implementation: https://github.com/decentralized-identity/did-common-java/blob/master/src/main/resources/did.abnf Markus On 11/17/18 2:43 AM, Mrinal Wadhwa wrote: > Hi everyone, > > The current published version of the DID spec (v0.11) includes > examples like this: did:example:123456789abcdefghi;photos > > However the grammar in v0..11 doesn't allow that semi-colon. > did-reference = did [ "/" did-path ] [ "#" did-fragment ] > did = "did:" method ":" specific-idstring > method = 1*methodchar > methodchar = %x61-7A / DIGIT > specific-idstring = idstring *( ":" idstring ) > idstring = 1*idchar > idchar = ALPHA / DIGIT / "." / "-" > > Is this an error or does this mean that specific schemes can override > the generic scheme? > > Our team has open sourced our Golang DID Parser > https://github.com/ockam-network/did > > Thank you all, > Mrinal > > CTO @ Ockam
Received on Monday, 19 November 2018 12:25:54 UTC