Re: transcoders bad ( LC-2017)

 Dear Terren Suydam ,

The Mobile Web Best Practices Working Group has reviewed the comments you
sent [1] on the Last Call Working Draft [2] of the Content Transformation
Guidelines 1.0 published on 1 Aug 2008. Thank you for having taken the time
to review the document and to send us comments!

The Working Group's response to your comment is included below, and has
been implemented in the new version of the document available at:
http://www.w3.org/TR/2009/WD-ct-guidelines-20091006/.

Please review it carefully and let us know by email at
public-bpwg-comments@w3.org if you agree with it or not before 6 November
2009. In case of disagreement, you are requested to provide a specific
solution for or a path to a consensus with the Working Group. If such a
consensus cannot be achieved, you will be given the opportunity to raise a
formal objection which will then be reviewed by the Director during the
transition of this document to the next stage in the W3C Recommendation
Track.

Thanks,

For the Mobile Web Best Practices Working Group,
Dominique Hazaël-Massieux
François Daoust
W3C Staff Contacts

 1. http://www.w3.org/mid/48978078.8060908@singleclicksystems.com
 2. http://www.w3.org/TR/2008/WD-ct-guidelines-20080801/


=====

Your comment on 4.1.5 Alteration of HTTP Header Values:
> Hello,
> 
> As the technical lead for SingleClick Systems mobile development, I'm 
> writing to protest the W3C's failure to provide a clear rule against
> the 
> modification of the User-Agent header.
> 
> As mobile developers, my team spends a lot of time creating the mobile
> 
> experience *we* want our users to see. If our users are subjected to
> the 
> confusing experience of transcoding, we lose money.
> 
> I urge the W3C to adopt the standards set forth by Luca Passani's 
> Manifesto, of which I'm sure you're aware.
> 
> Sincerely,
> Terren Suydam


Working Group Resolution (LC-2017):
Section 4.1.5 on alteration of HTTP Header Field Values remains
substantially as in the previous version of the document, but has been
reinforced by saying that proxies must not delete headers and that is must
be possible for the server to reconstruct the original User Agent
originated headers by using the X-Device-* HTTP header fields:
http://www.w3.org/TR/2009/WD-ct-guidelines-20091006/Overview.html#sec-altering-header-values

We have strengthened section 4.2.6 Receipt of Vary HTTP Header Field:
http://www.w3.org/TR/2009/WD-ct-guidelines-20091006/Overview.html#sec-receipt-of-vary-header

We have also introduce new guidelines in section 4.2.2 User Preferences to
force proxies to provide a means for users to express their preferences for
inhibiting content transformation:
http://www.w3.org/TR/2009/WD-ct-guidelines-20091006/Overview.html#sec-administrative-arrangements

In addition, we have updated the conformance section to state that
Transformation Deployments that choose to claim conformance with these
guidelines need to spell out the circumstances in which they deviate from
"should" clauses by providing a conformance statement that comes as a
separate document referenced by the guidelines:
http://www.w3.org/TR/2009/WD-ct-guidelines-20091006/Overview.html#sec-transformation-deployment-conformance

----

Received on Tuesday, 6 October 2009 15:49:37 UTC