-
Notifications
You must be signed in to change notification settings - Fork 97
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 "service-type" DID URL matrix parameter. #62
Conversation
This adds one concrete DID URL matrix parameter. Description: Identifies a set of services from the DID Document by service type. Example: |
The purpose/use case for this parameter needs to be expressed. It's unclear why referencing a set via a URL would be more useful than simply passing a plain DID to an application and allowing it to make some kind of (more) informed selection of an appropriate service after dereferencing the DID Document. |
Same questions as in #60 (comment) ... and I'd expect that question to be true of any type-based matrix parameter. |
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 a potential |
@peacekeeper any update on this after the F2F? |
@peacekeeper is working with @jandrieu to create use cases for matrix parameters. The use cases for matrix parameters weren't clear (as in, not clearly articulated and there were a number of people that were arguing that the matrix parameter use cases could be solved via other means, like resolver parameters). Next step is to get use cases for matrix params, which have been renamed to "DID Parameters", and then see if we need special syntax for that or if we can just use query parameters. |
This PR is stale, has conflicts and is blocked pending discussion of DID Parameters. I'd prefer to close it for now, to focus the attention of the WG on PRs that are not blocked. @peacekeeper thoughts? |
Marked pending close after the resolution 1 on the 4/7/2020 call. |
I agree this should be closed, but the reason for closing is that there has been consensus that there is no need for having |
Let's take this up on the next special topic call since we're still discussing the general area of DID Parameters. |
Re-creating PR from CCG repo: w3c-ccg/did-spec#191. Please consider earlier discussions there.
Preview | Diff