The point of "discussion" has now drifted from why code for standards to who should make the standards and why should we let group Foo make them.

Just an aside, I'm the content developer for a group of people that are currently developing a tech site, and I was handed the task of making the site compliant with the W3C standards. The closer it gets to being "valid" code, the worse it looks in the majority of browsers.

The 141 errors originally on the page have now been reduced to 16, and all of those are proprietary html attributes that I hope can be fixed using CSS. The point of this, is that someone actually taking the time to make their site comply with the "standards" everyone seems to agree are needed, would be quite dismayed to find that the browsers aren't rendering that newly compliant code in the manner expected. They are indeed likely to ask, "Why code for standards?"

DigitalGhost

_____________________________________________________________
Sign up for a FREE email account with SpectreNet.org at http://www.spectrenet.org
All accounts are permanent, spam, and pop-up free. Absolutely NO advertisements. Get the name you want from the site that delivers technology.

