Page 1 of 1

W3C Validation

Posted: Wed Dec 15, 2010 3:54 pm
by danst0
Hi,

how important is the validation of my s9y blog with the W3C Validator (http://validator.w3.org)?

I have a multitude of similar errors (and warnings) there, like the following
36 52 …a id="rss" href="/rss.php?version=2.0&fullFeed=1" title="Subscribe to this Blo… general entity "fullFeed" not defined and no default entity a
36 60 …s" href="/rss.php?version=2.0&fullFeed=1" title="Subscribe to this Blog (RSS)"… reference to entity "fullFeed" for which no system identifier could be generated a
46 58 … <ul><li><a href="http://scrmblog.com"" title="Frontpage">Frontpage</a></li><l… an attribute specification must start with a name or name token a
294 352 …<a href="/rss.php?version=2.0&fullFeed=1" title="scrmblog.com">subscribe to th… reference to entity "fullFeed" for which no system identifier could be generated a
Or have a look here: http://validator.w3.org/unicorn/check?u ... onformance

If it's important, what should I do about those errors related to the url parameters?

Daniel

Re: W3C Validation

Posted: Wed Dec 15, 2010 4:32 pm
by yellowled
danst0 wrote:how important is the validation of my s9y blog with the W3C Validator (http://validator.w3.org)?
"Important" is the wrong term here. Validation is the proper means to make sure your site is displayed correctly which is something you most definitely want. For further info, please see http://validator.w3.org/docs/why.html.
danst0 wrote:I have a multitude of similar errors (and warnings)
First of all, you're using the rather new Unicorn validator, which also checks CSS and stuff. Validating CSS is pointless, it also demonstrates why a validator is never an "absolute" means of control. For example, the Unicorn CSS validator is not aware of CSS Level 3 stuff yet. However, it is perfectly okay to use CSS3 now, since some browsers already support it and it won't hurt the other browsers to use it. This is due to technical limitations of the validator.

Second, eliminating validation errors can be an pain in the ass. However, most of the error messages usually refer to the very same error, so you usually can get rid of some of them in bulk by solving just one actual error in the page, which means you should really tackle one error at a time. Then revalidate, then continue.
danst0 wrote:If it's important, what should I do about those errors related to the url parameters?
I'm assuming you added the feed links, navigation and quicksearch to this template, so these are the ones you should check first. I guess the easiest way to check is to post your code for these here and let us have a look at it.

YL