Short URL: http://html5.org/r/3949
| SVN | Bug | Comment | Time (UTC) |
|---|---|---|---|
| 3949 | 7487 | Clarify what the XML fragment serialization algorithm means by an internal general parsed entity being XML namespace-well-formed. | 2009-09-22 00:26 |
Index: source =================================================================== --- source (revision 3948) +++ source (revision 3949) @@ -30383,9 +30383,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> @@ -30439,7 +30439,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> @@ -84347,8 +84347,13 @@ 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>INVALID_STATE_ERR</code> exception instead of returning a string:</p>