W3C home > Mailing lists > Public > public-bpwg@w3.org > August 2009

RE: MWABP: Reworked text for Handling Variations in Delivery Context.

From: Eduardo Casais <casays@yahoo.com>
Date: Fri, 14 Aug 2009 01:24:45 -0700 (PDT)
Message-ID: <122507.34208.qm@web45003.mail.sp1.yahoo.com>
To: public-bpwg@w3.org
Mainly editorial comments.

a) stylistic

3.6
"...content, navigation and/or page flow,..."
=>
"content, navigation or page flow,..."

3.6.1.2
"...in these repositories will vary from..."
=>
"...in these repositories varies from..."

3.6.2.2
"...will need to be refreshed during the session."
=>
"...must be refreshed during the session."


b) formal definitions

replace "header" with "header field". This is the
official IETF terminology as per RFC2616.


c) HTTP header

In practice, most of the fields mentioned are 
relied upon to select or adapt content on servers, 
so I do not think it really meaningful to separate 
the field "Accept" from the others. I suggest the 
following text for 3.6.1.2:

"In its basic form, the evidence from the client 
device is the HTTP header.

Typically, the following fields provide evidence of 
device capabilities:

- *Accept*: this list of MIME types can aid in the 
   selection or creation of alternative content 
   representations to suit the requesting device. 
   This field is not always reliable however, and
   its value often includes “*/*”, suggesting that
   clients can accept every MIME type. 
   [note the change regarding the */* indication]
- *User-Agent*: [...existing text...]
- *X-Wap-Profile*: [...existing text...] so the value 
   of this field is sometimes used with a DDR where 
   corrections to profiles are stored. Some devices 
   may send an additional field *X-Wap-Profile-Diff*
   advertising temporary or permanent variations of
   a specific terminal with respect to its standard
   profile."


d) Media queries

"...apply specific style rules based on the device 
characteristics (e.g. screen width, orientation, or 
resolution)."

Accurately, this should be "based on the display 
characteristics" -- these are the only ones that 
CSS media queries deal with.

A sentence to warn developers about the fact that 
browsers interpret CSS media types in idiosynchratic 
ways is in order.


E.Casais


      
Received on Friday, 14 August 2009 08:25:27 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:09:54 UTC