Issue 113 (language tag matching (Accept-Language) vs RFC4647), was: [Ltru] Proposed resolution for Issue 13 (language tags)

Phillips, Addison wrote:
> ...
> One additional issue related to language tags (you don't appear to be tracking it separately). I don't think that the current incarnation of section 5.4 (Accept-Language) is quite right. In particular, the Basic Filtering algorithm is made normative as the language negotiation strategy. I tend to find the Lookup algorithm a better/more common choice, personally, and others might make different choices, depending on the application. I think this text should be made more dependent on the text in 4647, rather than trying to recreate it in a shorter form. If HTTP-WG feels that an algorithm must be made normative, then my personal opinion is that it should be Lookup, not Filtering.
> ...

Hi Addison,

actually we *do* track this separately; the issue is 
<>, and we thought 
we were done with it almost a year ago. See discussion around 

The intention was to normatively refer to that matching algorithm that 
actually is equivalent to what RFC2616 used to define (remember, we're 
not changing the protocol here). Did we pick the wrong one?

BR, Julian

Received on Saturday, 18 July 2009 16:19:01 UTC