- From: Markus Sabadello <markus@danubetech.com>
- Date: Tue, 29 Aug 2023 09:53:57 +0200
- To: public-credentials@w3.org
- Message-ID: <be4d9097-65fb-77bc-1038-d58781e32a2d@danubetech.com>
Hello Stefannie, From that documentation page I can't really tell what a "CordaX500Name" looks like when expressed as a single string, do you have an example? But basically a method-specific-id can be anything that matches this ABNF pattern: method-specific-id = *( *idchar ":" ) 1*idchar idchar = ALPHA / DIGIT / "." / "-" / "_" / pct-encoded So it can consist of letters, digits, and the . - _ characters as well as percent-encoding such as %20 You say the name is base encoded and then percent-encoded, but from a DID syntax perspective, this feels unnecessary. If the "CordaX500Name" can be expressed using only characters from the list above, then there may be no need to base- or percent-encode anything, and readability can be preserved. Markus On 8/29/23 09:33, ステファニー タン(SBIホールディングス) wrote: > Hi everyone, > > I am seeking community support/advice regarding DID method-specific-id > in the syntax. If the DID Name is a CordaX500Name > (https://docs.r3.com/en/api-ref/corda/4.8/open-source/javadoc/net/corda/core/identity/CordaX500Name.html > <https://docs.r3.com/en/api-ref/corda/4.8/open-source/javadoc/net/corda/core/identity/CordaX500Name.html>) > that has been base encoded, and then percent-encoded: > > 1. will there be any potential issues if we use the above method? > (technically speaking, is it possible?) > 2. is there a way to preserve readability? > > > Thank you! > > Stefannie > > >
Received on Tuesday, 29 August 2023 07:54:06 UTC