Skip to content
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

Closed
wants to merge 2 commits into from

Conversation

peacekeeper
Copy link
Contributor

@peacekeeper peacekeeper commented Oct 5, 2019

Re-creating PR from CCG repo: w3c-ccg/did-spec#195. Please consider earlier discussions there.


Preview | Diff

@peacekeeper
Copy link
Contributor Author

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: did:example:1234;content-type=schema;content-id=z9y8x7w6

@dlongley
Copy link
Contributor

dlongley commented Oct 5, 2019

to use DID URL syntax for referencing objects in a DID target system that are not DID Documents.

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 id (that is a DID) -- which should allow for just about anything to be expressed.

@msporny
Copy link
Member

msporny commented Oct 10, 2019

My understanding is that a minimal DID Document could just have an id (that is a DID) -- which should allow for just about anything to be expressed.

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).

Copy link
Contributor

@selfissued selfissued left a 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.

@peacekeeper
Copy link
Contributor Author

peacekeeper commented Dec 9, 2019

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:

  • Use the path and/or query component in DID URLs for identifying such resources.
  • Assign separate, dedicated DIDs to such resources.

Therefore, unless @ken-ebert or @talltree or @brentzundel see a use case for the content-id and/or content-type matrix parameters, I propose to close this PR.

@brentzundel
Copy link
Member

I am fine with closing this PR

@peacekeeper
Copy link
Contributor Author

Closing due to community consensus.

@msporny msporny deleted the peacekeeper-matrix-parameter-content branch January 7, 2020 15:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants