W3C home > Mailing lists > Public > public-credentials@w3.org > August 2019

RE: What’s after DIDs?

From: Michael Herman (Parallelspace) <mwherman@parallelspace.net>
Date: Thu, 15 Aug 2019 14:37:06 +0000
To: Markus Sabadello <markus@danubetech.com>, Daniel Thompson-Yvetot <drthompsonsmagickindustries@gmail.com>, Manu Sporny <msporny@digitalbazaar.com>
CC: Dave Longley <dlongley@digitalbazaar.com>, Henry Story <henry.story@gmail.com>, Credentials Community Group <public-credentials@w3.org>
Message-ID: <MN2PR13MB2608850C6E99506714AC9939C3AC0@MN2PR13MB2608.namprd13.prod.outlook.com>
The DNS-based Universal DID Server data platform transparently supports:

  *   did:example:123456 and
  *   123456.example.did

…with complete interoperability.

Universal DID Resolution is based on existing, common, every day DNS (port 53) protocols that have been powering the Internet for decades …as well as any of the newer JSON-over-HTTP-over-DNS protocols.

I’m approaching a minimally viable state of code completeness and will be posting a webcast on YouTube “soon”.

Best regards,

From: Markus Sabadello <markus@danubetech.com>
Sent: August 13, 2019 2:47 PM
To: Daniel Thompson-Yvetot <drthompsonsmagickindustries@gmail.com>; Manu Sporny <msporny@digitalbazaar.com>
Cc: Dave Longley <dlongley@digitalbazaar.com>; Henry Story <henry.story@gmail.com>; Credentials Community Group <public-credentials@w3.org>
Subject: Re: What’s after DIDs?

Hi Daniel,

The DID itself can't be did/example/123456, because that's not a valid URI (DIDs being valid URIs is one of their central features).

In theory it would be possible to define a DID Resolution binding<https://w3c-ccg.github.io/did-resolution/#bindings-https> that would resolve a DID like did:example:123456 by making an HTTP GET call to https://api.service.com/v1/did/example/123456.

But then again, what's wrong with just concatenating the DID with colons, i.e. https://api.service.com/v1/did:example:123456 ?

On 7/31/19 3:46 AM, Daniel Thompson-Yvetot wrote:
> Which colon are you referring to?

My question is better phrased as a proposal:

If this was the id:


and this the resolver:


with a mere concat this would be simple.


On Tue, Jul 30, 2019 at 7:35 PM Manu Sporny <msporny@digitalbazaar.com<mailto:msporny@digitalbazaar.com>> wrote:
> On 7/30/19 12:39 PM, Daniel Thompson-Yvetot wrote:
> > Is there a real reason why it has to be : delimited instead of /
> > delimited?
> Which colon are you referring to?
> -- manu
> --
> Manu Sporny (skype: msporny, twitter: manusporny)
> Founder/CEO - Digital Bazaar, Inc.
> blog: Veres One Decentralized Identifier Blockchain Launches
> https://tinyurl.com/veres-one-launches

Received on Thursday, 15 August 2019 14:37:33 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:24:55 UTC