/rec/multilinguality/content-language-paths

[michellutz]

Requirement /rec/multilinguality/content-language-paths says:

The Web API SHOULD take the language specified in the Accept-Language HTTP header of a request to all paths into account. The Web API SHOULD include the Content-Language HTTP header in the response for a request to all paths.

Would the proposed approach based on HTTP standards be easily implementable by existing solutions?

[cportele]

ldproxy supports the headers and takes the accept header "into account" in content negotiation, but this has limits. See #13.

[heidivanparys]

Proposed approach: document for each of the tested implementation whether or not they support these headers. For providers of software solutions: explain whether support could be added and how difficult/useful/... that would be.

In general: document for each of the tested implementations how good they support each requirement and recommendation. If we would agree on that way forward, then this issue could be closed.