XHTML 1.1 validation and Atlas

Hello all,

Previously, I tried Atlas but abandoned it when it failed to produce valid XHTML 1.1 according to the W3C validator. The problem was that it did not recognize the tags inside the <script type="text/xml-script"> blocks, or the xmlns:script attribute.

Now, after surveying many other frameworks and finding them either lacking for my purposes or unable to run in a partial-trust environment, I'm turning back to see if Atlas can be made to work. Two questions:

Has anyone come up with a workaround for the invalid XHTML?Is the XHTML really invalid, or is the W3C validator lying? (Please substantiate your claim if it's the latter.)

No ideas?
I need to know about this aswell if anyone can help?

XML namespaces and XHTML are a bit tricky. There are other Ajax toolkits wrangling with the same issue. It has to do with a lot of things, but is not unique to Atlas.

If you are interested, you can read some interesting information on XHTML and other namespaces athttp://www.w3.org/TR/xhtml1/normative.html.

http://www-128.ibm.com/developerworks/xml/library/x-namcar.html

And, for this topic in particular, see item 3 here

http://codinginparadise.org/weblog/2005/08/xhtml-considered-harmful.html

And, a possible solution, referenced via the previous (albeit circuitiously), create a custom DTD!http://www.alistapart.com/articles/customdtd/

How quaint. I thought DTD was deprecated by XML Schema... And, so we are to use a deprecated syntax to make XHTML (the future of HTML) work. Not only that, how is using a custom DTD compliant with XHTML anyway? Ah, well. I don't have any answers.

Sorry for the messy response. It's a messy problem.

Thanks very much for the info.

XHTML Validation

Pages that previously validated as XHTML no longer do after adding the DropShadowExtender. The validator is complaining about undeclared elements such as "behaviors" in the output from the Atlas controls.

Any solution to this?

Mike Hanson

Is it just the DropShadow extender, or is it the addition of any extender? I suspect it's the latter and that it's due to the XML Script that Atlas adds. If so, this question may be better posed in one of the Atlas forums?

Thanks for the response David.

I have had a look at the source that was validated and you are correct, all of the errors point to the xml-script section appended to the end of the document, so I will go look through the Atlas forums to see if anyone else has raised the issue, if not I will post my original question there.

Thanks again
Mike Hanson