[
Lists Home |
Date Index |
Thread Index
]
> Once again, we see that the W3C process is simply deaf to fundamental
> criticisms. W3C working groups are pretty good about accepting minor
> corrections and suggestions for improvements within the frameworks
> they've laid out. However, they absolutely cannot hear when a chorus
> of voices is screaming that the framework itself is bad, will not
> support the weight they're trying to lay on it, and should be torn
> down.
It's all a question of what stage you're at in the process. If you've
decided to build a railway, and you assemble a team of railway engineers
to design it, who then ask for feedback on the decision to use a
particular loading gauge, then comments that say you should have built a
canal instead are not going to get much attention. Those comments should
have come earlier, while the decision was being made.
It's an unfortunate fact that W3C Requirements documents get very little
feedback. People don't scream when the requirements are published, they
wait until they see the specs. They need to recognize that by then, it's
probably too late: the people who want a railway have won, and those who
want a canal have missed the boat... Of course, sometimes (as with XSLT
1.1), the project can still get derailed.
Michael Kay
|
