Simon Fell > Its just code > xmlns strikes again

I've been thinking about Sam's suggestion for how to provide unencoded content in my atom feed, in looking at his example, I spotted one problem, the second content entry, which is an unencoded text/html part has the html tags in the atom namespace.

<feed xmlns="http://example.com/newformat#" xmlns:ent="http://www.purl.org/NET/ENT/1.0/" version="1.0">
...
<content type="text/html" xml:lang="en-us">
      <p>Hello, <em>weblog</em> world! 2 &lt; 4!</p>
</content>

The <p> being in the default namespace of http://example.com/newformat#. Another validation on my stance that default namespaces are evil.