|
|
Posted by Jukka K. Korpela on 06/14/05 16:22
"Simon" <spambucket@myoddweb.com> wrote:
> I know that a site that validates is a good site, because it
> follows the rules given by W3c.
If you think so, you do not know what validation is. For an
explanation, see http://www.cs.tut.fi/~jkorpela/html/validation.html
(Validation does not imply that W3C rules are followed. Neither does
it, or following the rules, imply that the site is a good one. As a
trivial proof of the latter non sequitur, consider a site that consists
of a single HTML document that fully conforms to HTML specification and
has an empty body, say <body><div></div></body>.)
> But I am about to employ a web designer/programmer should I
> automatically reject them if their site does not validate?
If you are about to hire a technical editor, would you reject any
application that contains a spelling error?
> what about css, should it validate?
CSS is not an SGML or XML application, so "validation" is an
incorrect/misleading word in that context.
Surely the crucial questions are: Do you intend to require that _your_
pages validate? As a different question, do you intend to require that
they conform to W3C recommendations? Which of them? (HTML? Which one?
CSS? Which one? WAI?) Do you understand the consequences?
(And what makes you think validation costs money, as you suggest in the
Subject line but fail to explain or even mention in the message body?)
--
Yucca, http://www.cs.tut.fi/~jkorpela/
Pages about Web authoring: http://www.cs.tut.fi/~jkorpela/www.html
Navigation:
[Reply to this message]
|