rmathew, not a problem with the validator's parser, its behaviour is quite correct. The FAQ it links to with the error explains why.

rmathew, on including: use an offline preprocessor such as gcc or Dolt.

On states of CSS/JS: you can make the toggler a link to another page with the same content on it (and return false if the JS runs so that the link isn't followed when the content is revealed on the same page). Another option is to forget about the toggler and let people use scrollbars (which is what they are used to anyway!).

rmathew, take Hixie's rant seriously, and throw in a dose of Appendix C being a complete joke. The guidelines aren't really compatible with HTML, they are compatible, with most, but not all, browsers and depends on a bug in their HTML parsers! (Since in HTML a slash can end a tag, so <br /> actually means a line break followed by a greater than sign!

Browser implementations of XHTML (being served with the correct content type) generally suck too, Firefox turns of incremental rendering for example.

That said, XHTML is a nice language to work in, so you might want to write XHTML and transform it to HTML before it gets to the user (my CMS does that before I upload to the server).

Free copies of Windows? Well, I don't think that's an easy one to arrange.

IIS is not necessary for MSFT/SOA development. To deploy on a public site, it might be. I think that's fair for a company like MSFT to ask for. They have to make money somewhere.

Well fair enough, I didn't really expect anything else. That is Microsoft's business model after all. It just makes the statement:

[DotNetNuke] runs on software that you can get for free from Microsoft

... wrong.

avriettea: So, DotNetNuke runs on "software I can get for free from Microsoft". Excellent, I might take a look at it. How do I get my free copy of Windows and IIS from Microsoft? The page you linked to seemed to assume that people would have those already.