On 18 Jun 2010, at 5:13 AM, Karl Dubost wrote:
Le 18 juin 2010 à 06:03, Anne van Kesteren a écrit :
If you don't play with the latest why would you be interested in
specifications that are still in development? And why the
assumption that the snapshot would reflect reality more than the
latest draft? Often changes to the latest draft are made based on
finding out that implementations implemented something different
from the snapshot.
what would you recommend to solve the needs for the two communities?
* Some people who want a JIT snapshot.
* Some people who want a slow moving version for reading,
translating, working and trying.
* Some people who need a stable milestone
Open to hear.
On my side I will ask people at work.
Hi all,
First, thanks for having the conversation.
People who are following work closely want the freshest information
possible. That includes mailing list discussions, specs, and so forth.
Those who are leading the way expect people following close behind to
keep up. ("What? You didn't read my proposal from last Thursday in
time for Monday's call??")
Other people can't keep up or that's just not their priority. I think
it would be useful for the group (as the TAG used to do) to publish a
monthly summary of key decisions, changes, milestone updates, and so
on. That summary would be very helpful to some, even if it were only a
rough approximation of the truth.
For specs, I love Editor's drafts. I also think that snapshots are
very useful, especially during review periods, since managing
expectations with a moving target during a review is a challenge. So
snapshots at LC, CR, PR are all helpful.
I have not yet investigated why CSS 2.1 has not been updated lately.
Anne and Henri, would you be available for a phone chat to talk about
this task force we're running? Karl, you can come too if you want ;)
_ Ian
--
Ian Jacobs (i...@w3.org) http://www.w3.org/People/Jacobs/
Tel: +1 718 260 9447
