Re: Accept- & Content-Resolution headers proposal

Where did the "/style/default" URI come from to begin with?
If from a document of some sort, could that document describe the
choices right there with distinct URI for each supported resolution?
Adding that description of resolution specific resources only requires
updating the definition of those document formats, rather than
updating a protocol that is device and document format independent.



>
> The client (a laptop, say) requests -
>
> GET /style/default HTTP/1.2
> Host: example.com
> Accept-Content: text/css, text/dsssl, text/xsl
> Accept-Resolution: 116.66 dpi
>