Add "service-type" DID URL matrix parameter. #191
Conversation
| @@ -825,6 +825,15 @@ <h2> | |||
| </thead> | |||
|
|
|||
| <tbody> | |||
| <tr> | |||
| <td> | |||
| <code>service-type</code> | |||
There was a problem hiding this comment.
I don't understand the use case here. Why can't you dereference the DID Document, search for the service type you're looking for, and use that?
There was a problem hiding this comment.
I agree we could just leave it at that. However I think I remember conversations with @dmitrizagidulin that he may see a need for including a service type in the DID URL; some of his examples and considerations are in #90.
Whatever we decide here would probably also apply to #193.
There was a problem hiding this comment.
The specific request for service-type came from Daniel Buchner who has said for some months now that the folks working on identity hubs want to be able to request an array of all the services of that type (and that it will be typical for a DID controller to have more than one).
So while clearly the calling application could just request the DID document and then parse it itself, this matrix parameter would enable a DID URL to specify that specific service type, and thus for a resolver to follow the same algorithm for constructing a concrete URL as it would for a service parameter, only it would return an array of concrete URLs, not just one.
| <code>service-type</code> | ||
| </td> | ||
| <td> | ||
| Identifies a set of services from the DID Document by service type. |
There was a problem hiding this comment.
How do you use the list of services you get back when this is paired w/ a path?
There was a problem hiding this comment.
The path/query/fragment of the DID URL would be applied to ALL service endpoints in the resulting set.
peacekeeper
force-pushed
the
peacekeeper-matrix-parameter-service-type
branch
from
674ad61 to
4a792ab
Compare
peacekeeper
changed the base branch from
peacekeeper-matrix-parameters-new
to
gh-pages
|
Quick note that in the 2019-05-30 DID Spec and DID Resolution Spec meeting we discussed this PR, and specifically the question whether we need matrix parameters for service selection, versioning, etc., or whether such functionality should be supported in a different layer (i.e. DID Resolution protocol). In the meeting, there was support for this matrix parameter, but we'll continue to discuss a bit more before merging. |
rhiaro
added
the
discuss
|
This repo is scheduled to be archived. The work has moved to the DID WG. |
|
Closing. This PR has been re-created in the DIDWG repo: w3c/did-core#62 |
This adds one concrete DID URL matrix parameter. See #189.
Description: Identifies a set of services from the DID Document by service type.
Example:
did:example:1234;service-type=agentPreview | Diff