search

w3c-ccg / did-spec

Please see README.md for latest version being developed by W3C DID WG.
https://w3c.github.io/did-core/
Other
124 stars 45 forks source link

What happens when you feed a did: URL to a URL resolver? #80

Closed msporny closed 5 years ago

msporny commented 6 years ago

@gklyne wrote:

  1. Hierarchical URI scheme? Is the scheme intended to operate in a hierarchical fashion? RFC 3986 defines a (hierarchical) reference resolution procedure that operates on any URI containing "/" characters (which are part of your "did-path" syntax. Conventionally, this works in conjunction with an "authority" component that is introduced by "//", but your scheme proposal does not use "authority" syntax. I'm not sure if there are any potential surprises in store if resolution is attempted with DID URIs.
msporny commented 6 years ago

Run experiments where we feed various DID URLs (basic, basic+service, basic+service+path, basic+path+fragment, etc.) to a URL resolver library and see what happens.

peacekeeper commented 6 years ago

I believe most URI parsers would be able to correctly extract query and fragment, but wouldn't be able to interpret the rest of the DID syntax (method, method-specific identifier, service, path). Of course specialized DID URI parsers could do that.

gklyne commented 6 years ago

My comment wasn't so much to do with parsing a did: URI - I agree most parsers should handle that OK.

I was more concerned with what surprises might be in store if relative URI references were used in connection with a did: base URI (cf. https://tools.ietf.org/html/rfc3986#section-5)

peacekeeper commented 5 years ago

Quick note that this issue is relevant to the Service Endpoint Construction algorithm in the DID Resolution spec. Perhaps we should create a new issue over there and close this one.

jandrieu commented 5 years ago

Closing as we have adopted this issue in the new DIDWG repo.