-
Notifications
You must be signed in to change notification settings - Fork 99
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
Add "content-type" and "content-id" DID URL matrix parameters. #61
Conversation
This adds two concrete DID URL matrix parameters. Description: At Rebooting-the-Web-of-Trust 8 in Barcelona, a use case was described by @talltree and @kenebert to use DID URL syntax for referencing objects in a DID target system that are not DID Documents. See https://github.com/WebOfTrustInfo/rwot8-barcelona/blob/master/topics-and-advance-readings/DID-Content-References.md. Example: |
It seems like a DID URL is the wrong tool for that -- or that those things should actually be given their own DIDs so they can be referenced directly. My understanding is that a minimal DID Document could just have an |
Right, why doesn't this solve the problem that these two matrix parameters are attempting to solve? This also raises the question, can DID Documents have alternate content-types, and if so, should that be retrieved via an HTTP API, or are we going to add the concept of content-types to DID Registries (the latter being a really scary expansion in scope). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe that we should not merge this until we've determined whether there is actually consensus to resurrect the matrix parameter syntax at all. Less is more.
Regarding these matrix parameters, the original idea was to be able to construct DID URLs that can identify arbitrary method-specific resources that are not part of or related to the DID document. I believe there are at least two better ways of accomplishing this:
Therefore, unless @ken-ebert or @talltree or @brentzundel see a use case for the |
I am fine with closing this PR |
Closing due to community consensus. |
Re-creating PR from CCG repo: w3c-ccg/did-spec#195. Please consider earlier discussions there.
Preview | Diff