RE: [agenda] CT Call Tuesday 23 September 2008

Regrets for Tuesday's CT call.  I won't be able to attend.

Sean

> -----Original Message-----
> From: public-bpwg-ct-request@w3.org [mailto:public-bpwg-ct-request@w3.org]
> On Behalf Of Francois Daoust
> Sent: Monday, September 22, 2008 1:57 AM
> To: public-bpwg-ct
> Subject: [agenda] CT Call Tuesday 23 September 2008
> 
> 
> Hi CT fans,
> 
> On to more Last Call comments resolutions...
> 
> Francois.
> 
> 
> -----
> Chair: François
> Staff Contact: François
> Known regrets: none
> 
> Date: 2008-09-23T1400Z 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.
> 
> 
> 1. New comments received
> -----
> - my "no-comment" comment:
> http://lists.w3.org/Archives/Public/public-bpwg-
> comments/2008JulSep/0154.html
> - review from the Internet Architecture Board:
> http://lists.w3.org/Archives/Public/public-bpwg-
> comments/2008JulSep/0152.html
> 
> 
> 2. LC-2018: on the title
> -----
> ACTION-831 on SeanP
> http://lists.w3.org/Archives/Public/public-bpwg-ct/2008Sep/0009.html and
> replies
> 
> Choice between:
> - Content Transformation Proxies: Guidelines
> - Guidelines for Mobile Web Content Transformation Proxies
> 
> 
> 3. LC-2025: On the quality and purpose of the doc
> -----
> ACTION-829 on Heiko
> http://lists.w3.org/Archives/Public/public-bpwg-ct/2008Sep/0004.html and
> reply
> 
> Stick to clear concise normative wording but complete with use cases and
> examples?
> 
> 
> 4. LC-2012: clarification of the introduction
> -----
> http://lists.w3.org/Archives/Public/public-bpwg-ct/2008Sep/0015.html
> 
> 
> 5. LC-2064: duplicated IDs in the document
> -----
> http://lists.w3.org/Archives/Public/public-bpwg-ct/2008Sep/0019.html
> PROPOSED RESOLUTION: LC-2064 is a mistake. There are no duplicated IDs
> in the document.
> 
> 
> 6. LC-2003: no mention of whitelists
> -----
> http://lists.w3.org/Archives/Public/public-bpwg-ct/2008Sep/0026.html
> PROPOSED RESOLUTION: re. LC-2003, stick to our position and use Jo's
> proposed response in public-bpwg-ct/2008Sep/0026.html
> 
> 
> 7. LC-2068: on requests that contain Cache-Control: no-transform
> directives
> -----
> http://lists.w3.org/Archives/Public/public-bpwg-ct/2008Sep/0029.html
> - any better idea to make it crystal clear that we're just trying to
> emphasize the fact that no-transform may occur in the request as well?
> 
> 
> 8. LC-2008: on use of Vary header
> -----
> http://lists.w3.org/Archives/Public/public-bpwg-ct/2008Sep/0030.html
> PROPOSED RESOLUTION: re. LC-2008, update the text according to Jo's
> proposal in public-bpwg-ct/2008Sep/0030.html
> 
> 
> 9. LC-2009, LC-2010, LC-2011: the Link element strikes back
> -----
> See Jo and fd's ping-pong starting at:
> http://lists.w3.org/Archives/Public/public-bpwg-ct/2008Sep/0027.html
> 
> 
> 10. HTTPS links re-writing
> -----
> http://lists.w3.org/Archives/Public/public-bpwg-ct/2008Sep/0013.html
> 
> The list of comments:
> LC-2026
> LC-2027
> LC-2085
> LC-2028
> LC-2029
> LC-2030
> LC-2015
> LC-2031
> LC-2016
> LC-2032
> LC-2001
> LC-2033
> LC-2004
> LC-2024
> 
> 
> 11. AOB
> ------
> 
>

Received on Tuesday, 23 September 2008 03:34:16 UTC