W3C home > Mailing lists > Public > public-bpwg-ct@w3.org > January 2009

RE: [agenda] CT Call 6 January 2009

From: Jo Rabin <jrabin@mtld.mobi>
Date: Mon, 5 Jan 2009 16:53:57 -0000
Message-ID: <C8FFD98530207F40BD8D2CAD608B50B4018E367A@mtldsvr01.DotMobi.local>
To: "public-bpwg-ct" <public-bpwg-ct@w3.org>

Happy new year everyone. A quick update on the status of an updated editor's draft - I'm afraid I haven't made as much progress as this as I wanted to over the break but will try to have something this week.


-----Original Message-----
From: public-bpwg-ct-request@w3.org [mailto:public-bpwg-ct-request@w3.org] On Behalf Of Francois Daoust
Sent: 05 January 2009 10:50
To: public-bpwg-ct
Subject: [agenda] CT Call 6 January 2009

Hi guys and happy new year!

Here is the agenda for tomorrow's CT call.
This could be the last CT-only call, see Topic 4. below.

Chair: François
Staff Contact: François
Known regrets: none

Date: 2008-01-06T1500Z for 60mn
Phone: +1.617.761.6200, +, +44.117.370.6152
Conference code: 2283 ("BCTF") followed by # key
IRC channel: #bpwg on irc.w3.org, port 6665.

Latest draft:

1. Mandating respect of some heuristics

- 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 on responses?

2. WML and the guidelines

- Mostly merged with previous topic
- Amend the text on http-equiv not to mention *HTML* content specifically?

3. LC-2040 - On properly defining the X-Device-* headers
Last Call comment:

- Last discussion showed support for not defining blank new HTTP 
headers, not to add to the already existing mess.

PROPOSED RESOLUTION: stick to X-Device-* header fields names on the 
ground that there is already a number of "existing" X- HTTP header 
fields for the same purpose, and that adding yet other "cleaner" ones 
would only create confusion.

4. Merging with the main body of the Working Group
Announcement (member-only link):

- idea is to have only one call for CT and the main body of BPWG.
- date/time of the merged conference is up to vote.
- merged call could start next week.

5. On the guidelines
Long thread starting at:

- summary?

6. Cache-Control extension mechanisms

- a long time ago, we resolved not to go down that path.
- any reason to reconsider our decision?

7. AOB

Received on Monday, 5 January 2009 16:54:35 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:06:30 UTC