RE: DIDs and httpRange-14

My interpretation of RFC 3986 is that as long as the URI describes a “what” in terms of what resource to be returned (e.g. a DID Document, a DID Document Fragment, collection of DID Documents, or another URI or URL, etc.) and not “how the processing” is to occur, the URI is a URI.

Checkout the original did-uri-spec webcast starting at these timecodes:

Overview: https://www.youtube.com/watch?v=e3V5oRB5lYA&list=PLU-rWqHm5p45c9jFftlYcr4XIWcZb0yCv&index=2&t=30s


Details: https://www.youtube.com/watch?v=e3V5oRB5lYA&list=PLU-rWqHm5p45c9jFftlYcr4XIWcZb0yCv&index=2&t=2360s


Best regards,
Michael Herman (Toronto/Calgary/Seattle)
Independent Blockchain Developer
Hyperonomy Business Blockchain / Parallelspace Corporation

W: http://hyperonomy.com<http://hyperonomy.com/>
C:  +1 416 524-7702


From: Markus Sabadello <markus@danubetech.com>
Sent: April 10, 2019 8:33 AM
To: W3C Credentials CG <public-credentials@w3.org>
Subject: DIDs and httpRange-14


I wouldn't call this a high priority issue, but there have been recurring questions on whether a DID is a URL or "only" a URI, what a DID identifies (Alice? Or Alice's DID Document?), and what it means exactly to resolve/dereference a DID (URL).

Maybe this isn't an actual problem, but for some reason it keeps bothering me.

So I thought I'd write up<https://docs.google.com/document/d/1gSUP9DEp7IO8jyNDsVnC-7Ed6PjbMRxl89nGYUoWoeI/> my current understanding of those questions.

Markus