- From: Lars G. Svensson via GitHub <sysbot+gh@w3.org>
- Date: Sun, 17 Mar 2019 15:30:25 +0000
- To: public-dxwg-wg@w3.org
@azaroth42 scripsit: > That would mean that we would register a new rel type, similar (abstractly) to the timemap rel type registered by Memento. (RFC7089) Or we use the 'profile' target attribute as proposed in #501. We could also consider to extend the [`text/uri-list`](https://www.iana.org/assignments/media-types/text/uri-list) media type by adding the possibility to convey profile (and token?) information, à la ``` <http response> HTTP/1.1 300 Multiple Choices Content-Type: text/extended-uri-list https://example.com/some/resource/profile-1 profile="urn:example:profile-1^profile-1-token" https://example.com/some/resoucre/profile-2 profile="urn:example:profile-2^profile-2-token" ``` The syntax for profiles is __only meant as an example__ . The basic idea is to to extend `text/uri-list` to ``` *line line = URI [WSP "profile=" URI [^profile-token]] \r\n WSP = SP / HTAB # from RFC 5234 ``` so that we can specify which profile the resource representation conforms to and (optionally) which token can be used instead of the profile URI. -- GitHub Notification of comment by larsgsvensson Please view or discuss this issue at https://github.com/w3c/dxwg/issues/549#issuecomment-473676501 using your GitHub account
Received on Sunday, 17 March 2019 15:30:30 UTC