Re: Accept headers and media parameters

> The current semantics of Accept are going to lead to some awfully long
> requests. Suppose that a browser can accept application/foobar version 1.0,
> 1.1, 1.2, 2.0, 2.1, 2.2, 2.3, 2.4, and 2.5, but not any later versions, and
> prefers 2.x to 1.x.  Your accept header now looks like this:

> Accept: application/foobar;version=1.0;q=0.5,
>         application/foobar;version=1.1;q=0.5,
>         application/foobar;version=2.0;q=1.0,
>         application/foobar;version=2.1;q=1.0,
>         application/foobar;version=2.2;q=1.0,
>         application/foobar;version=2.3;q=1.0,
>         application/foobar;version=2.4;q=1.0,
>         application/foobar;version=2.5;q=1.0

Suppose that the definition of application/foobar is such that both
client and server recognize that anything that is
application/foobar;version=2.x is also application/foobar;version=2.y
for y<x. Then you can just accept 2.5 and leave the others implied.