- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 22 Sep 2009 00:19:53 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec In directory hutz:/tmp/cvs-serv8678 Modified Files: Overview.html Log Message: Clarify what the XML fragment serialization algorithm means by an internal general parsed entity being XML namespace-well-formed. (whatwg r3949) Index: Overview.html =================================================================== RCS file: /sources/public/html5/spec/Overview.html,v retrieving revision 1.3110 retrieving revision 1.3111 diff -u -d -r1.3110 -r1.3111 --- Overview.html 22 Sep 2009 00:05:22 -0000 1.3110 +++ Overview.html 22 Sep 2009 00:19:49 -0000 1.3111 @@ -24500,9 +24500,9 @@ appropriate error message.</p> <p>To enable authors to use MathML tools that only accept MathML in - its XML form, interactive HTML user agents are encouraged to - provide a way to export any MathML fragment as a - namespace-well-formed XML fragment.</p> + its XML form, interactive HTML user agents are encouraged to provide + a way to export any MathML fragment as an XML namespace-well-formed + XML fragment.</p> </div><div class="example"> @@ -24546,7 +24546,7 @@ <p>To enable authors to use SVG tools that only accept SVG in its XML form, interactive HTML user agents are encouraged to provide a - way to export any SVG fragment as a namespace-well-formed XML + way to export any SVG fragment as an XML namespace-well-formed XML fragment.</p> </div><p>When the SVG <code>foreignObject</code> element contains elements @@ -64684,8 +64684,13 @@ pick up the surrounding default ns when setting --> (This doesn't apply in the <code>Document</code> case.) <a href="#refsXML">[XML]</a> <a href="#refsXMLNS">[XMLNS]</a></p> + <p>For the purposes of this section, an internal general parsed + entity is considered XML namespace-well-formed if a document + consisting of an element whose contents are the internal general + parsed entity would itself be XML namespace-well-formed.</p> + <p>If any of the following error cases are found in the DOM subtree - being serialized, then the algorithm raises an + being serialized, then the algorithm must raise an <code><a href="#invalid_state_err">INVALID_STATE_ERR</a></code> exception instead of returning a string:</p>
Received on Tuesday, 22 September 2009 00:20:08 UTC