W3C home > Mailing lists > Public > public-html-xml@w3.org > January 2011

Re: The interpretation of script

From: John Cowan <cowan@mercury.ccil.org>
Date: Mon, 17 Jan 2011 18:12:24 -0500
To: David Carlisle <davidc@nag.co.uk>
Cc: public-html-xml@w3.org
Message-ID: <20110117231224.GM2461@mercury.ccil.org>
David Carlisle scripsit:

> the other way of course to get consistent parsing would be to have an  
> element that parsed the inline script in "foreign-content" xml-like  
> mode, but I'm not sure if it would be possible to get this enough like  
> xml to be worth it (you'd need at least a way of setting the initial  
> default namespace cf math and svg setting their respective namespaces)
> but namespace processing is so deeply ingrained into xslt, I'm not sure  
> an xslt with restricted namespace processing wouldn't just be confusing  
> (and I don't suggest adding unrestricted namespace processing to 
> text/html)

So if you want XSLT, put it in a script element and let the JavaScript shim
parse it.

John Cowan      cowan@ccil.org
        "Not to know The Smiths is not to know K.X.U."  --K.X.U.
Received on Monday, 17 January 2011 23:12:51 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:58:27 UTC