- From: Francois Daoust <fd@w3.org>
- Date: Mon, 25 Feb 2008 14:03:49 +0100
- To: public-bpwg-ct <public-bpwg-ct@w3.org>
Hi, Now that we're definitely (?) clear about the scope, time to move on! Tomorrow's call will be about parsing the draft, and selecting practical solutions (grounded on existing technologies as agreed) for each of our guidelines. The goal is to replace things like: "The proxy [...] must indicate its capabilities using the [@@transforming-proxy-capability] mechanism." ... by things like: "The proxy [...] must indicate its capabilities using comments in the VIA header. Comments format to use must be..." ... with a view to presenting the draft to the main body of the working group. (Note that I am NOT saying this is the path to go in that particular case!) ----- Chair: François Staff Contact: François Known regrets: none Date: 2008-02-26T1500Z for 60mn Phone: +1.617.761.6200, +33.4.89.06.34.99, +44.117.370.6152 Conference code: 2283 ("BCTF") followed by # key IRC channel: #bpwg on irc.w3.org, port 6665. Current draft: http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/CT/editors-drafts/Guidelines/080124 Agenda: 1. Client Origination of request (§3.1) --------------------------------------- http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/CT/editors-drafts/Guidelines/080124#d0e306 - replace HTTP control mechanisms with an options-oriented approach (should go with ACTION-661 on Jo) - keep the possibility for the client user agent to add a Cache-Control: no-transform header to switch off the CT-proxy directly. - anything else? 2. Proxy Receipt, Forwarding or Response to a Request (§3.2) ------------------------------------------------------------ http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/CT/editors-drafts/Guidelines/080124#d0e339 - remove all mentions to Cache-Control extensions (should go with ACTION-661 on Jo) - how to advertise the CT-proxy's capabilities? Suggestions: + using the VIA header [Jo8] + using the PRAGMA header [Jo10] + don't advertise - content tasting and/or headers modifications? Suggestions: + content tasting using modified headers and use of Vary header in the response [Jo21] [dotMobi] + content tasting using original headers [Jo5] + modify User-Agent but keep original one or a clear mention that it was modified at the end of it [Jo7] + allow headers modifications but somehow enclose original ones [Jo7] [fd: X-Modified-Headers] 3. Server Response to Proxy (§3.3) ---------------------------------- http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/CT/editors-drafts/Guidelines/080124#d0e501 - stick to Cache-Control: no-transform (should go with ACTION-661 on Jo) - recommend the use of the HTTP Vary header [Jo21] [dotMobi] - recommend the use of <link> elements? - HTTP-300 and/or give the user a choice of representations 6. Proxy Receipt and Forwarding of Response from Server (§3.4) -------------------------------------------------------------- http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/CT/editors-drafts/Guidelines/080124#d0e581 - anything else to say? 7. Proxy Response to Client (§3.5) ---------------------------------- http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/CT/editors-drafts/Guidelines/080124#d0e594 - how to advertise transformations done? Suggestions: + using the VIA header [Jo8] + using the PRAGMA header [Jo10] + don't advertise - heuristics: anything else? (detection of mobile-friendly patterns in the URI? More on link elements?) 8. Further discussions / open questions if time allows ------------------------------------------------------ - Testing: CT-proxy must provide an open channel for developers to be able to test? - Impact on sites that use redirections from the home page rather than adaptation? - CT and redirections: use cases - CT-proxy options set by the user: what they mean in practice (e.g. what does/can preferred-medium do?) - Getting back to dangerous content. - Requirements: things we can't address with existing technologies. References ---------- [Jo] The thread on Jo's good ol' list of suggestions (the list covers all the solutions I can think of, but feel free to add to the list!): http://lists.w3.org/Archives/Public/public-bpwg-ct/2007Oct/0023.html (referenced above by using [Jo18] for "Jo's item 18") [fd] My own ones that actually are included in the above list: http://lists.w3.org/Archives/Public/public-bpwg-ct/2008Feb/0041.html [dotMobi] dotMobi's note on CT: http://dev.mobi/files/ContentTransformation_consultative.html François.
Received on Monday, 25 February 2008 13:04:06 UTC