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

New Draft of CT Document 1q

From: Jo Rabin <jrabin@mtld.mobi>
Date: Fri, 13 Mar 2009 15:46:16 -0000
Message-ID: <C8FFD98530207F40BD8D2CAD608B50B401C5D5F2@mtldsvr01.DotMobi.local>
To: "Mobile Web Best Practices Working Group WG" <public-bpwg@w3.org>
Hello everyone, another Friday 13th Publication. Here is the latest
draft with a change list and the change marked version is accessible
from within the document, under previous revisions.

I will review the dangling threads over the next day or two and present
a list of undecided resolutions some time over the weekend.



Changes in this Revision

1) Minutes of 11 November 2008


     RESOLUTION: On the subject of character encoding, we have revisited
     it and we still can't think of anything useful other than "avoid
     bugs" when transforming between character encoding (which we don't
     intend to say) but add it to the list in so that character
     encoding is specifically referred to

Done - but then removed that section accordance with the resolution

2) Minutes of 25 November 2008


RESOLUTION: Add some text in 4.1.5 to state that inferring that a
desktop User-Agent is needed in the absence of any indication (e.g. URI
patterns) is contrary to the guidelines

Done - Added a note to that effect

RESOLUTION: Strike first paragraph in section on transformations
carried out by CT proxies as it refers to what CT-proxies do (stated in
the introduction) and does not have any normative meaning.

Done - Removed : A proxy should strive for the best possible user
experience that the user agent supports. It should  only alter the
format, layout, dimensions etc. to match the specific capabilities of
the user agent. For example, when resizing images, they should only be
reduced so that they are suitable for the specific user agent, and this
should not be done on a generic basis.

RESOLUTION: Reword "the user agent has linearization or zoom
capabilities or other features which allow it to present the content
unaltered" as "the user agent has features (such as linearization or
zoom) that allow it to present the content unaltered"


RESOLUTION: Move the note under to the start of the section


3) Minutes of 2 December 2008


RESOLUTION: Ref-2097 resolve yes and add a section under 1.3 scope
noting that OPES RFC 3238 is relevant to this work and has been

Done - but CF also subsequent discussion of OPES points [ACTION-902] **

ACTION-889 - Take the editorial comments in
into account for next version of the draft [on Jo Rabin - due


a) HTTP Header => HTTP Header Field

b) 4.1.5 and 4.1.6 Not consistent

change header fields => modify the values of header fields

(the point being I think that adding headers is changing header fields, 
hopefully this makes it clear, Eduardo?)

c) Reference to "CT-Proxy" in 4.2.7

the CT-Proxy => a proxy

d) Server Origination

WAP/WML proxies => WAP Gateways
consider include => consider including

e) Use of Vary - D.1.3.1

Language Tidied Up

f) Alteration of Response

per subsequent discussion not altered

g) HTTPS link rewriting

Further discussion ongoing on this section 

h) Examples

mobile delivery => delivery to mobile devices

Further discussion ongoing on mandatory heuristics

i) Via Header Field

deleted "compliance to"

ability to transform vs. intention to transform - this is something that

has been discussed before ... the proxy doesn't know at this stage 
whether it intends to transform, or not, only that in the right 
circumstances it might ...

... I'm actually not sure why we still have this clause here (past 
reasons have I think now gone away), as I don't know whether it actually

does anything of any use that the Server can act on.

"should not alter them in any way" => should not alter them by removing 
comments from them

RESOLUTION: ref. definitions of restructuring, recoding, optimizing,
leave things as they stand and get back to it in the end. If the
definitions are not used in the guidelines, then lessen the wording (not
need to use "definitions" if we don't make use of the term)

Just to note that reference is made in the appendices to these concepts
as "Scope for Future Work"

RESOLUTION: Add a short sentence on "pagination" first time it is
mentioned to clarify what we mean

Done - under the definition of "restructuring": "e.g. by linearization
or pagination." Replaced by [see resolution below] e.g. linearization
(i.e. reordering presentation elements, especially tables, so that they
fit on a narrow display and can be traversed without horizontal
scrolling) or pagination (i.e. splitting a document too large to be
stored in or transmitted to the terminal in one piece, so that it can be
nevertheless accessed by browsing through a succession of smaller
interlinked documents). 

RESOLUTION: replace SHOULD by MUST in "and [proxies] SHOULD provide a
simple means of retrieving a fresh copy"


francois: would like Jo to be here to experience the joy of "Validation
against formal published grammar ("
/me thanks francois for his kind consideration

4) Minutes of 9 December 2008


RESOLUTION: ref. definition of pagination, adopt Eduardo's proposed text
replacing "fragments" by "documents"


RESOLUTION: Adopt the wording validate ... and if XML MUST be well

Added the XML clause, but can't remember what the "Adopt the wording"
bit meant, so left "as is". Also added an xtermref to well-formed and a
bibl to XML 5th ed.

RESOLUTION: Modify the current text to say: It must be possible for the
origin server to reconstruct the original UA originated headers (see Original Headers) by copying directly from corresponding
X-Device header field values. 


RESOLUTION: Spell out the exact headers 4.1.5 (i.e. the exact accept-*)

Done: modified to say Accept, Accept-Charset and Accept-Format

[Also ednotes added to remind us that we need to look again at whether
Device- headers are actually needed, and also to look again at whether
modifying the User-Agent field does actually prevent 406 errors]

5) Minutes of 16 December 2008


No resolutions recorded

6) Minutes of 6th January 2009


RESOLUTION: WAP1 content WML, WBMP and so on is to be treated
transparently (but this doesn't affect the operation of WAP Gateways and
authorised transformations as specified in xxxx [ref to be supplied by
EdC in

Done-ish - what I did was to say that proxies should be transparent to
such content and then I added a note saying that this doesn't affect the
operation of proxies that are also WAP Gateways.

[at this point we waved a fond farewell to the CT Task Force]

7) Minutes of 8th January 2009


RESOLUTION: We will merge the CT taskforce back into the main BP group;
we will further merge the calls as well. The BP call will now take place
in the Tuesday slot previously allocated to CT and we will cease the
thursday calls. We will further move that CT slot a half-hour earlier on
Tuesdays at 14:30 UK. To be implemented next week as a trial pending
feedback from members not on the call.

RESOLUTION: Big thanks to Francois for his extremely capable Leadership
of CT Task Force

[bis from JR]

8) Minutes of 13 January 2009


A couple of things we decided NOT to do, so no action required.

9) Minutes of 20 January 2009


No decisions were made 

10) Minutes of 27 January


No decisions were made

[two weeks in a row! Come back Francois!]

11) Minutes of 3 February 2009


RESOLUTION: Ref CT Guidelines Section 5, Adopt EdC's Clarification at

[Note: do we need to say something about this being openly accessible?]

12) Minutes of 10 February


No decisions were made

13) Minutes of 3 March 2009


No decisions were made

14) Minutes of 10 March 2009-03-13


RESOLUTION: a CT proxy SHOULD NOT transform a page that matches
well-known mobile heuristics (to be defined) unless the user has
explicitly requested it

RESOLUTION: mobile doctypes (XHTML MP and Basic, WML, iMode) is a
recognized mobile heuraretic
RESOLUTION: <link rel="alternate" media="handheld" href=""/> is a
recognized mobile heuristic
RESOLUTION: MIME Types defined in
lines/081107#sec-Example-Content-Types  minus application/xhtml+xml are
mobile heuristics
RESOLUTION: a mobileOK claim is a mobile heuristic, but marked as a
"feature at risk"

Not done, an ednote refers

RESOLUTION: including an editor's note on calling for more
mobile-specific heuristics

Received on Friday, 13 March 2009 15:47:01 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:43:00 UTC