- From: Francois Daoust <fd@w3.org>
- Date: Mon, 10 Mar 2008 15:38:35 +0100
- To: public-bpwg-ct <public-bpwg-ct@w3.org>
Hi guys,
Note to US residents: the call is one hour later than it was two weeks
ago... Note to the others: the call is at the same local hour as before!
Some participants of the F2F agreed to be actioned on a few questions
(silly you, you shouldn't have come... gosh I was actioned too! ;)). I'm
not forgetting any of those but propose to skip them this week to give
them (and me) some time to address the actions.
-----
Chair: François
Staff Contact: François
Known regrets: none
Date: 2008-03-11T1500Z 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/080227
Agenda:
1. Editors meeting
------------------
- No problem to host the meeting in Sophia (south-east of France)
- We need to agree on dates. Possibilities are 18-21 March, or 25-28
March (two days within each of these possibilities, that is).
- Who would be there?
2. Control of the Behavior of the Proxy (§2.5)
----------------------------------------------
- Review/Inclusion of Aaron's contribution (ACTION-666):
http://lists.w3.org/Archives/Public/public-bpwg-ct/2008Mar/0000.html
3. Jo's shopping list on CT (ISSUE-223)
---------------------------------------
http://www.w3.org/2005/MWI/BPWG/Group/track/issues/223
- Summary of Seoul F2F discussions up to point 6 included
- Review points 7. and above
4. HTTPS rewrite
----------------
- Review of Andrew's contribution (ACTION-633):
http://lists.w3.org/Archives/Public/public-bpwg-ct/2008Feb/0026.html
5. Cache-control: no-transform and WAP gateways
-----------------------------------------------
- Review of fd contribution (ACTION-634)
http://lists.w3.org/Archives/Public/public-bpwg-ct/2008Feb/0011.html
(and replies)
6. Server Response to Proxy (§3.2)
----------------------------------
http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/CT/editors-drafts/Guidelines/080227#sec-ServerResponse
- 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
7. Proxy Receipt and Forwarding of Response from Server (§3.3)
--------------------------------------------------------------
http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/CT/editors-drafts/Guidelines/080227#d0e508
- how does that fit with the content tasting approach?
8. Proxy Response to Client (§3.4)
----------------------------------
http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/CT/editors-drafts/Guidelines/080227#d0e521
- 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?)
- resolution on dangerous content.
9. Further discussions / open questions if time allows
------------------------------------------------------
- Impact on sites that use redirections from the home page rather than
adaptation?
- CT and redirections: use cases
- Requirements: things we can't address with existing technologies.
Received on Monday, 10 March 2008 14:38:45 UTC