"Allow markup and insist that it be well-formed.

This is arguably the hardest thing to do, but it's not really that hard, is it?"

I agree that it isn't very hard. RSS is XML thus must be well-formed (and valid).

Thus people and tools creating RSS (and similiar formats) can be expected and required to and should be able to make sure that inlined XHTML is well-formed as well.

Tobi

... and it might be a good idea to put XHTML 1 in the XHTML 1 namespace.

Tobi

HTML is a meme. XHTML may someday replace it, but till then, I dont think you can get around it. I like the "leave them on the net somewhere and point to them" solution. That is, SSF.

What not use namespaces? This is what Jabber/XMPP use. For example:

<funkyxml xmlns="funky:xml">
  <item xmlns="http://www.w3.org/1999/xhtml">
    <h1>Woohoo!</h1>
    <p>This is in HTML.</p>
  </item>
</funkxml>

Here's a page on how to do this in XHTML. It should also be done with every other XML document too: http://www.w3.org/TR/xhtml1/#well-formed

- Nolan

Over two years later, and I'm sitting looking at a WS-I monitor log.xml file and it contains captured SOAP messages as escaped content .. Grr ..

You know what would help folks like me a lot is if we knew how to base64binary encode/decode in XSLT, but anyway, my version of a SOAP log file will embed captured XML documents as XML.

I'm getting 404 errors when clicking on the links to your example feeds and doc2.html.

Bah. I don't know when that happened. Sorry. Fixed now.

I've also been gently and not-so-gently pushing people away from CDATA and from escaped markup in the XML FAQ for a while as well, and I agree we simply haven't reached the mass market on this. We need to shout LOUDER!

It's a form of Tag Abuse, and as such I think it's time to resuscitate The Society for the Definitive Abolition of Tag Abuse (SDATA). All who grok the problem are welcome!