[thelist] Re: Why code for standards

[Peter-Paul Koch]

> >Ideally, to represent the point of view of web developers in creating
> >standards and to prevent strange, unimportant or unrealistic details from
>cropping up in new standard documents so that standards created for the WWW
>will address common concerns of the web developers actually using the
>standards.
>
>Don't forget to do a little marketing, too. Explain why this group will
>better answer those needs than WinWriters, or The HTML Writers Guild, or
>the IEEE or any of the other groups which are doing much the same thing
>(you'll have some overlap with the STC and the Webmasters Guild, but not as
>much, I think; HWG is probably the main "competition"). Probably shouldn't
>be in the mission statement, but it should be able to be clearly derived
>from it.

Yes, a very valid concern. At the moment I don't have a good answer, except
that I'm sure Evolt will handle this much better than HWG. I remember when
the HWG-W3C list was founded, they were all so immensely excited at being in
W3C that they decided only a select few could get on the list and no
information would be given to other HWG members.

Assuming Evolt does better and has more people to help I assume we get
better ideas. These ideas will have to speak for us.

Not a particularly strong argument, but the best I have at the moment.
<tip type="w3c dom documentation" author="ppk">
Everything you always wanted to know about the W3C DOM methods and
properties but couldn't find in simple language:
http://www.xs4all.nl/~ppk/js/index.html?version5.html
Remember: you *must* use the W3C DOM for your DHTML to work in Netscape 6,
Opera and Konqueror. Besides it has many, many more fascinating
possibilities.
</tip>
ppk

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp.