Like Jason, I'm not sure I agree w/ the default namespace changing by default... but that's something we can work out easy enough.

We don't even have to work it out. That is just a native feature of XML. You can choose whatever default namespace you want. Most people just happen to choose HTML when creating HTML output. I was just demonstrating that there is nothing special about the HTML tags in a Facelets document.

One area I am still not clear on is what changes a page (or component) author will need to do to accommodate CDATA sections in their page. Issue 697 (https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=697) states:

> There should also be control on how comments and CDATA are handled. There shouldn't be an assumption that what is in the template should be passed directly to the browser, but rather have more control over what gets passed and what doesn't.

So in what cases are CDATA currently required? And how would the page/component author need to change their document to be non-ambiguous on how to handle these?

I think the point here is that when CDATA is used into the template, the parent component should decide whether that CDATA gets rendered, and if so, whether it is rendered w/ or w/o the CDATA wrapper. The point is that CDATA in a template does not necessarily mean CDATA in the output. If a parent component doesn't have anything to say about the content (perhaps it just passes through children) then there needs to be a global setting as to whether CDATA gets rewrapped when being rendered.

-Dan