- From: Francois Daoust <fd@w3.org>
- Date: Mon, 16 Nov 2009 13:43:56 +0100
- To: Heiko Gerlach <heiko.gerlach@vodafone.com>
- CC: public-bpwg-comments@w3.org
Dear Heiko, The Last Call review period for the Guidelines for Web Content Transformation Proxies is over and we have not yet heard from you. We were wondering whether you had time to review the response to your comments below and the updated document, and whether you could let us know if you agree with it or not via email. The header of the previous email was generated from a template that did not give us the opportunity to apologize for the time it took us to get back to you. Comments received during the first Last Call review period generated a lot of discussions within the group. Resolutions of the issues took more time than expected. The group thinks the document has quite improved as a consequence, apologizes for the delay and would like to thank you again for your contribution! Thanks, For the Mobile Web Best Practices Working Group, Francois Daoust, W3C Staff Contact. fd@w3.org wrote: > Dear Heiko Gerlach , > > 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. (reference not available) > 2. http://www.w3.org/TR/2008/WD-ct-guidelines-20080801/ > > > ===== > > Your comment on : >> Old text >> Request resource with original headers >> >> If the response is a 406 response: >> >> If the response contains Cache-Control: no-transform, forward it >> >> Otherwise re-request with altered headers >> >> If the response is a 200 response: >> >> If the response contains Vary: User-Agent, an appropriate link element >> or header, or Cache-Control: no-transform, forward it >> >> Otherwise assess whether the 200 response is a form of "Request >> Unacceptable" >> >> If it is not, forward it >> >> If it is, re-request with altered headers >> >> BUT WHERE IS THE TRANSCODING? >> New Text: >> >> Request resource with original headers >> >> If the response is a 406 response: >> >> If the response contains Cache-Control: no-transform, forward it >> >> Otherwise re-request with altered headers >> >> If the response is a 200 response: >> >> If the response contains Vary: User-Agent, an appropriate link element >> or header, or Cache-Control: no-transform, forward it >> >> Otherwise assess whether the 200 response is a form of "Request >> Unacceptable" >> >> If it is not, TRANSCODE it >> >> If it is, re-request with altered headers > > > Working Group Resolution (LC-2089): > We don't specify that Transcoding must take place so we have not adopted > this amendment. > > ---- > > > >
Received on Monday, 16 November 2009 12:44:33 UTC