Re: A simpler approach to DID services and content-addressing

Daniel, that is available for the developer to use as the DID URL. However,
it is to be processed by the client - post resolution.  The matrix syntax
parameters enables information to be passed to the resolver, so that it can
handled at resolution time.  So it is good for interacting with the ledger.
In the Indy case - getting non-pure-DID-type data off the ledger (schema,
creddef, rev reg) by the resolver with DID syntax.  Query params can be
used after the data is back to the client.



On Thu, Apr 4, 2019 at 8:39 AM Daniel Hardman <daniel.hardman@evernym.com>
wrote:

> Please forgive me if this question triggers remedial tutoring.
>
> Is there some important reason why we can't repurpose an existing
> convention? For example, could we just adopt the familiar syntax for query
> strings?
>
> did:example:1234abcd?a=b&c=d&e=f
>
> This has the advantage that every software stack on the planet probably
> already has code that can parse it, and every developer already knows it.
>
>
>

-- 

Stephen Curran
Principal, Cloud Compass Computing, Inc. (C3I)
Technical Governance Board Member - Sovrin Foundation (sovrin.org)

*Schedule a Meeting: **https://calendly.com/swcurran
<https://calendly.com/swcurran>*