One of the ideas of matrix parameters in DID URL syntax has been that a resource hash can be included in a path, e.g.: did:ex:1234;hl=zQmWvQxTqbG2Z9HPJgG57jjwR154cKhbtJenbyYTWkjgF3e This could also be combined with query-based hashlinks, e.g.: did:ex:1234;hl=zQmWvQxTqbG2Z9HPJgG57jjwR154cKhbtJenbyYTWkjgF3e/mypath1/path2?hl=zQmWvQxTqbG2Z9HPJgG57jjwR154cKhbtJenbyYTWkjgF3e (The first "hl" would be for the DID document, the second "hl" would be for the resource identified by the DID URL). RFC3986 says this: https://tools.ietf.org/html/rfc3986#section-3.3 /"..., the semicolon (";") and equals ("=") reserved characters are often used to delimit parameters and parameter values applicable to that segment"/ Markus On 4/22/20 7:19 AM, alex thompson wrote: > Regarding parameterized URLs > https://tools.ietf.org/html/draft-sporny-hashlink-04#section-3.2 > > Can we generalize that for URL segments instead of just query string similar to > https://tools.ietf.org/html/rfc6920#section-5 > > Examples: > ../hl;zQmWvQxTqbG2Z9HPJgG57jjwR154cKhbtJenbyYTWkjgF3e > ../hw.txt#hl;zQmWvQxTqbG2Z9HPJgG57jjwR154cKhbtJenbyYTWkjgF3e > > I think there are clear use cases for having it in the path (avoiding conflicts with windows filesystems not allowing "?") > and fragment (doing client side only validation) > > Alex Thompson >Received on Wednesday, 29 April 2020 08:07:44 UTC
This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:24:58 UTC