OK, thank you all. There seems to be consensus that the [text in the IETF draft](https://profilenegotiation.github.io/I-D-Profile-Negotiation/I-D-Profile-Negotiation.html#rfc.section.6) covers this: > When used in a Link header field, the "profile" attribute is a hint indicating which profile the resource representation retrieved by dereferencing the link conforms to. Note that this is only a hint; for example it does not override the "Content-Profile" header field of a HTTP response obtained by actually following the link. Multiple "profile" attributes on a single link value indicate that the resource representation conforms to multiple profiles. Now we only have to resolve #290 and we're ready to close. -- GitHub Notification of comment by larsgsvensson Please view or discuss this issue at https://github.com/w3c/dxwg/issues/501#issuecomment-525641306 using your GitHub accountReceived on Wednesday, 28 August 2019 08:32:05 UTC
This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:28:32 UTC