-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DID Resolution Result for DID URL Dereferencing #69
Comments
@clehner yes definitely. You correctly identified a gap where the DID Resolution spec is lagging behind DID Core a bit. This spec needs to better describe the output structures of DID URL dereferencing. I wrote the part of the DID test suite that deals with resolving and dereferencing, and I agree this should also be reflected here. I'll try to work on this as soon as there's a bit of time. |
DID Resolution Result says:
The result of § 4. Dereferencing a DID URL might not be a DID document but could be something else, e.g. a verification method (Example 8), or a output service endpoint URL (Example 10). DID Core (in § 7.2 DID URL Dereferencing.) says that
contentStream
, the resource part of the return value of DID URL dereferencing, "MAY be a resource such as a DID document that is serializable in one of the conformant representations, a Verification Method, a service, or any other resource format that can be identified via a Media Type and obtained through the resolution process".Should the DID Resolution Result section, and the JSON-LD context file, be updated to support DID URL dereferencing results other than DID documents?
In DID Test Suite there are examples of outputs of DID URL dereferencing, similar to the outputs for DID resolution, which perhaps could be useful here. In these, the
contentStream
property is a string (even if the content is a DID Document or JSON/JSON-LD object),dereferencingMetadata
is an object, likedidResolutionMetadata
; andcontentMetadata
is an object, likedidDocumentMetadata
. e.g.:versionTime
The text was updated successfully, but these errors were encountered: