News for hackers. Stuff that matters.
Re:Adobe blocking publication of latest HTML5 draft? by telemachos on Friday February 12, 2010 @11:26AM (#1120917)
Mark Pilgrim makes a good point that I wonder about (http://twitter.com/diveintomark/status/9013587732): why are there member-only lists at all? That is, HTML is an open standard. I had no idea there were secret holds. Was this a known part of the process? Is it done often? Are there any precedents?
Re:Adobe blocking publication of latest HTML5 draft? by seldo on Friday February 12, 2010 @12:53PM (#1121181)
It has been a long time since I was involved in the W3C, but I can tell you that the public lists are plagued with clueless people who jump onto, e.g., the XHTML 2.0 standards definition list and ask for help with converting their BMPs into GIFs for their homepage. Even without those, there are legions of self-important blowhards who will spend weeks arguing whether "<section>" is the semantically best name for a tag.

W3C is not terribly quick at getting things done at the best of times, but the public lists are even more so.

All that said, I've never heard of a "hold" before, but then I was only ever on the public lists.

Re:Adobe blocking publication of latest HTML5 draft? by mrduncan on Friday February 12, 2010 @12:56PM (#1121188)
I agree that allowing users to post to the lists might be harmful in some cases, but I can't think of a good reason why these lists aren't readable by the public.
Re:Adobe blocking publication of latest HTML5 draft? by carson on Friday February 12, 2010 @12:56PM (#1121187)
It is probably there to allow the members to talk freely about internal projects that they don't want to have exposed externally before they are ready.
Re:Adobe blocking publication of latest HTML5 draft? by imd on Friday February 12, 2010 @06:23PM (#1122118)
Re:Adobe blocking publication of latest HTML5 draft? by telemachos on Friday February 12, 2010 @06:48PM (#1122176)
Yup, thanks. Someone quickly responded that he had wished to be formal earlier (http://lists.w3.org/Archives/Public/www-archive/2010Feb/0002...):

So I object to the chairs' decision that these documents are in scope.

I suppose a formal objection is decided by the domain lead, or appealed to the Director, and the team contact can help with this process? it's not in the special HTML-WG-only process document how this group goes about appealing decisions which the chairs seem to have made.

If I need to use the word "formally" in there somewhere, or if there's some "Formal Appeal Change Proposal" form I'm supposed to fill in, recapitulating all of the email arguments made to date, suggesting the documents "change" by disappearing, and written in iambic hexameter, please let me know.

That quickly devolves into some discussion of possible uses of the word 'formal', the minutes of a phone conference, other emails, typos, and also some serious conversation about whether or not the private lists should be used this way. Tab Atkins Jr. wrote this:

I would like to register my strong disapproval of this entire affair. This was an abuse of the member-only lists. Any Objection, potential or not, should _always_ take place on the public list. I am disappointed in the author of the private emails for their actions.

It really all is surprisingly like the senate, which to my mind is a shame. Having said that, maybe there's some inevitable thing that happens when this many people, much money, etc. are involved.

Re:Adobe blocking publication of latest HTML5 draft? by ZeroGravitas on Friday February 12, 2010 @12:56PM (#1121190)
I'm fairly certain that Apple communicated that it wouldn't implement Theora in private.
Re:Adobe blocking publication of latest HTML5 draft? by othermaciej on Friday February 12, 2010 @07:19PM (#1122224)
Re:Adobe blocking publication of latest HTML5 draft? by Hixie on Saturday February 13, 2010 @04:50AM (#1122834)
All of Apple's objections were public. (Also, Mozilla's objections to H.264, Google's opinion, Opera's position, Nokia's position, etc. They were all public.)

There _have_ been some private discussions between various people interested in solving the codec problem, but they have yet to bear useful fruit and the spec was unaffected by them. All the objections that affected the spec were public from the get-go.