RE: complexity (was: Re: XHTML and RDF)

> > >Anyways, it seems we agree that W3C folks tend to create solutions
> > >that evidently go into the wrong direction :-(
> >
> > Just a reminder. W3C folks are the companies members... not necessary
> > academics or researchers, but software developers.
>
>Actually, looking at most W3C standards, I get exactly the opposite
>impression -- that they are created by academics that have never written
>any serious software, or even tried to consider the implications of
>writing an efficient implementation.
>
>Did you realize that even the most advanced browsers, with an enormous
>manpower behind them, do implement only a little fraction of the
>standards? And that's not because they are too lazy; that's because many
>of these standards are just absurdly complex.

I think a friend of mine hit this on the head. It doesn't really matter who 
is coming up with these specs, the people coming up with the specs don't 
have to implement them or use them with the possible exception of the XML 
and HTML working groups. It may not occur to them how complex or unruely 
their specs are since they don't really have to interact with them. I know I 
wouldn't. I've tried to accomplish the same thing here and it's not until I 
start to implement them that I see the problem.

Now given the overall structure of the W3C, I don't see a lot that they can 
do about that. Perhaps what the W3C should concentrate on is culling back 
existing standards and simplifying them. Sometimes less is better than more. 
Perhaps it would be best if the W3C suspended activities on new specs to 
work on simplifying the specs they've already written.

Orion Adrian

_________________________________________________________________
Get rid of annoying pop-up ads with the new MSN Toolbar – FREE! 
http://toolbar.msn.com/go/onm00200414ave/direct/01/

Received on Wednesday, 7 April 2004 10:33:59 UTC