W3C home > Mailing lists > Public > public-bpwg-ct@w3.org > September 2007

Re: ACTION-550: Draft some initial material for Section 2.3 of the Guidelines

From: Aaron and Valérie Irvine <irvdel@googlemail.com>
Date: Thu, 27 Sep 2007 20:35:24 +0100
Message-ID: <70201e050709271235s6f535223s503d0e41a70cc2bd@mail.gmail.com>
To: "public-bpwg-ct@w3.org" <public-bpwg-ct@w3.org>

Sean Patterson skribis:

__ 2.3.2.4	Determining whether or not a web page should be transformed __

>The Cache-Control: no-transform header can be added by content
>transformation servers but it should not be modified by content
>transformation servers.

to be clear, I'd suggest:

The Cache-Control: no-transform header can be added by origin servers
or by content
transformation servers but it must not be modified, nor removed, by content
transformation servers.



__ 2.3.2.3	Identifying the mobile browser __

While advanced mobile content applications will analyse the User-Agent
(or maybe the suggested X-Device-User-Agent if enough authors would
update there detection scripts??), I feel authors of simpler mobile
content should also be allowed the one-liner of grepping the accept
for profile="http://www.wapforum.org/xhtml" or
application/vnd.wap.xhtml+xml.  Essentially, accept header for "is
this a mobile", and [original] UA for "what kind of mobile".



__ 2.3.2.6	Identification of mobile content __

>*	The Content-Type header of the response is one of the following values:
>o	application/vnd.wap.xhtml+xml
>o	text/vnd.wap.wml

and there's also
application/xhtml+xml;profile="http://www.wapforum.org/xhtml" (which
works well for both mobile and current vanilla desktop browsers so is
great for authoring simplest mobile friendly sites):

*	The Content-Type header of the response is one of the following
values:
o	application/vnd.wap.xhtml+xml
o	application/xhtml+xml;profile="http://www.wapforum.org/xhtml"
o	text/vnd.wap.wml



>*	There is a link element in the response document with a media
>attribute that has a value of "handheld" that points to a mobile
>document.  Here is an example:
>		<link rel="alternate" media="handheld" href="www.mobileversion.com/" />
> ... (The mobile browser would need to have the capability of presenting the choice to the user for this to work.)

expand to:

*	There is a link element in the response document with a media
attribute that has a value of "handheld" that points to an *alternate* mobile
document.  Here is an example:
	<link rel="alternate" media="handheld"
type="application/vnd.wap.xhtml+xml" href="/mobileversion.php" />

And there is a link element with a media
attribute that has a value of "handheld" that indicates that the
*current* document has been designed with mobile friendliness in mind:
      <link rel="stylesheet" type="text/css" href="/small_screen.css"
media="handheld" />

And the special case of this which simply states that the page is
mobile friendly, for example:
      <style type="text/css" media="handheld"></style>

....
(The mobile browser or adapting proxy would need to have the
capability of presenting the choice to the user for this to work.)


bondezire,
Aaron IRVINE
http://lingvo.org/
(opinions expressed are my own and may or may not reflect those of my employers)
Received on Friday, 28 September 2007 00:54:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:10:36 GMT