Comments on: W3C Change: Your Turn!

By: John Hoare

John Hoare — Thu, 19 Oct 2006 15:50:50 +0000

I find it intriguing that this post especially hasn’t sparked off more talk.

Is it because people don’t have any more ideas? Or is it because people have already begun to see the W3C as a lost cause?

By: JackP

JackP — Sun, 08 Oct 2006 21:52:06 +0000

While I’ve never been involved in the W3C, and my my knowledge is really mostly in the accessibility area, I think your proposals are a jolly good idea. It would be good to have individuals without a big corporate wedge behind them being able to contribute: it would also reduce the perception that standards are being “bought”.
It’s a darn good idea, and I hope they are listening to you…

By: Isaac Lin

Isaac Lin — Thu, 05 Oct 2006 00:54:45 +0000

Along similar lines to David Baron's thoughts, I believe the W3C needs to refocus its objectives. I think your first suggestion of improving the W3C's connection to the web community is a very good idea; I believe it should extend to the larger software development, document management / workflow, and other communities that have been affected by the web. The W3C should not unnecessarily replicate work already being done by other reputable groups, and not seek to boil the ocean on its own. By choosing targetted areas to work on, particularly ones in which in has expertise or areas that no one is adequately covering, the W3C can be more productive, and thereby regain trust from the web community.

By: Mark Kawakami

Mark Kawakami — Tue, 03 Oct 2006 15:47:10 +0000

I think the W3C could regain some lost relevance by helping to petition/encourage/hound given browser makers (Mozilla, Apple, Microsoft, Opera) or other relevant parties (web server developers, for instance) to attempt an implementation of currently “paper-only” working drafts or at least specific parts of them. Ideally, this would be driven not by whatever member of the W3C thinks his/her pet project is most important and screams the loudest, but by a reasoned evaluation of what projects have the most potential for either fixing long-standing problems with the web-browsing/publishing experience or would help to move the web forward in a positive direction.

This would give us some sort of testbed to work with the item and iron out the kinks. But more importantly, for features that prove genuinely useful, hopefully having one implementation would spur the other relevant companies to adopt the standard more quickly.

I don’t want to give any concrete examples (for fear of my own “pet feature” prejudice), but