Content negotiation process using ‘Accept-Profile:’ header

[jyucsiro]

See https://www.w3.org/TR/dx-prof-conneg/#getresourcebyprofile

Flagged by @dr-shorthair

[dr-shorthair]

My suggestion is that we quietly implement Content-Profile: in the response first, and add Accept-Profile: as an option in the request later.

And let @nicholascar as soon as we have managed so he can add it to the list of implementations for W3C.

[nicholascar]

Hi all, please see same section in the ED as it contains an update on the PWD.

The IETF requested that we change to using a Link header to achieve what we originally intended Content-Profile to achieve. The requirement for Accept-Profile is unchanged.

[nicholascar]

...and pyLDAPI is up-to-date with this ED's recommendations, if you want to see a tool doing this.

[dr-shorthair]

Ah - OK. So Link: is a kind of soft-typed thing, where the value of rel tells you what it is doing.
Not convinced, but those IETF types are pretty stubborn.