- From: Larry Masinter <LMM@acm.org>
- Date: Thu, 7 Jun 2007 17:03:33 -0700
- To: "'Nicholas Shanks'" <contact@nickshanks.com>, "'Maciej Stachowiak'" <mjs@apple.com>
- Cc: "'WebKit Development'" <webkit-dev@lists.webkit.org>, <ietf-http-wg@w3.org>
Content negotiation for HTTP based on parameters beyond MIME types
was the focus of a significant amount of IETF work, including
RFC 2295 ("Transparent Content Negotiation in HTTP")
RFC 2296 ("HTTP Remote Variant Selection Algorithm -- RVSA/1.0")
and a set of 'media features' (including resolution, screen
size, pixel depth, etc.) in a Media Feature registry
(RFC 2506, BCP 31).
The protocol documents are experimental, but there are experimental
implementations.
In addition, the media feature tags originally targeted for use
in HTTP were used in Internet Fax (for negotiation of resolution
of scanned document images) and are being used in SIP and
IMAP extensions.
There are other ways of describing target device capabilities,
constraints and preferences (such as screen resolution) that have
been proposed in other organizations (W3C CCPP, for example),
but I think you'd be better off starting with something that's
already been worked on than trying to invent yet another namespace
of things like "resolution".
Larry
--
http://larry.masinter.net
Received on Friday, 8 June 2007 00:04:13 UTC