- From: Francois Daoust <fd@w3.org>
- Date: Mon, 08 Dec 2008 09:59:01 +0100
- To: public-bpwg-ct <public-bpwg-ct@w3.org>
-----
Chair: François
Staff Contact: François
Known regrets: none
Date: 2008-12-08T1500Z 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.
Latest draft:
http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/CT/editors-drafts/Guidelines/081107
1. Validation against formal published grammar (4.2.8.1)
-----
Thread:
http://lists.w3.org/Archives/Public/public-bpwg-ct/2008Nov/0037.html
Doc:
http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/CT/editors-drafts/Guidelines/081107#sec-alteration-of-response
Conclusion?
2. Pagination definition
-----
Thread:
http://lists.w3.org/Archives/Public/public-bpwg-ct/2008Dec/0028.html
PROPOSED RESOLUTION: ref. definition of pagination, adopt Eduardo's
proposed text in
http://lists.w3.org/Archives/Public/public-bpwg-ct/2008Dec/0028.html
... and close ACTION-890 on Eduardo
3. Alteration of header fields (4.1.5)
-----
Thread:
http://lists.w3.org/Archives/Public/public-bpwg-ct/2008Nov/0019.html
Doc:
http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/CT/editors-drafts/Guidelines/081107#sec-altering-header-values
- "Proxies SHOULD NOT change headers other than User-Agent and
Accept(-*) headers[...]"
... inconsistent with 4.1.6 since the CT proxy is already asked to add
X-Forwarded-For and Via headers and to *change* them (more specifically,
to complete their values) if they are already defined.
- Several other headers could have to be changed by the CT-proxy
(Content-Length for instance)
- What are trying to say here?
... and close ACTION-843 on Jo
4. HTTPS links rewriting
-----
Threads:
http://lists.w3.org/Archives/Public/public-bpwg-ct/2008Nov/0063.html
http://lists.w3.org/Archives/Public/public-bpwg-ct/2008Nov/0065.html
http://lists.w3.org/Archives/Public/public-bpwg-ct/2008Dec/0007.html
http://lists.w3.org/Archives/Public/public-bpwg-comments/2008OctDec/0007.html
- Security problems arise with links rewriting, whether links are in
HTTP or HTTPS, because of a change of origin that enables cross-site
scripting attacks.
- Add a "Security considerations" section?
- Specific HTTPS guidelines?
... and close ACTION-860, ACTION-864 on Jo
... and close ACTION-859 on Francois
5. LC-2040 - On properly defining the X-Device-* headers
-----
Thread:
http://lists.w3.org/Archives/Public/public-bpwg-ct/2008Nov/0062.html
Doc:
http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/CT/editors-drafts/Guidelines/081107#sec-original-headers
Last Call comment:
http://www.w3.org/2006/02/lc-comments-tracker/37584/WD-ct-guidelines-20080801/2040
- Stick to "existing practice" or define the header appropriately?
- I note we also reference the X-Forwarded-For header.
... and close ACTION-879 on Francois.
6. Mandating respect of some heuristics
-----
Thread:
http://lists.w3.org/Archives/Public/public-bpwg-ct/2008Nov/0080.html
- should a mobile CT proxy be allowed to transform content that was
developed with mobile in mind?
- forbid restructuring and recoding in the cases mentioned by Dom?
- allow exceptions to the rules as proposed by Eduardo?
- add an equivalent to section 4.1.5.4 on responses?
7. WML and the guidelines
-----
Threads:
http://lists.w3.org/Archives/Public/public-bpwg-ct/2008Nov/0068.html
http://lists.w3.org/Archives/Public/public-bpwg-ct/2008Nov/0071.html
- Mostly merged with previous topic
- Amend the text on http-equiv not to mention specifically *HTML* content?
8. AOB
-----
Received on Monday, 8 December 2008 08:59:38 UTC