Re: [dxwg] Registration of target attribute "profile" for the Link-Header (#501)

The discussion over in #290 (unfortunately) has implications for this issue, too.
The preferred way of publishing URI/token mappings discussed there is to use the `Link` header and the target attribute `profile` discussed here. That way a host could declare that for the resource `` the URI `urn:example:foo` is mapped to the token `bar` by adding the following `Link` header to the http response:
Link: <>
    profile="urn:example:foo token=bar"
Currently, the I-D defines the value of the `profile` parameter as `absolute-URI`. That means that **if** we want to support tokens, we need to extend the syntax of the `profile` attribute to something like
`absolute-URI[<delimiting-character>"token"=token]` (where the first "token" is the string "token" and the second "token" is a `token` defined as in [RFC 7230 §3.2.6]( which would allow
My personal feeling is that defining an extension to the `profile` attribute only to map tokens to URIs is a Bad Idea (TM), particularly since we might not need it (depending on #290). In order to future-proof the syntax, however, it could make sense to define a generic extension syntax, à la
`absolute-URI[<delimiting-character>token=token]` which would also allow

As `<delimiting-character>` we need something not allowed in `absolute-URI`. Blank (U+0020) or pipe (U+007C) come to mind. If we use blank, we also must mandate the use of quotation marks on the right hand side of `profile="bla"`.
See also and
@nicholascar, @rob-metalinkage, @RubenVerborgh: What do you think?
And ACTION-290

GitHub Notification of comment by larsgsvensson
Please view or discuss this issue at using your GitHub account

Received on Friday, 30 August 2019 07:43:37 UTC