Formalized the issue of XML serialization producing invalid XML in certain cases
authortravil
Wed, 26 Mar 2014 16:01:06 -0700
changeset 40 5fa98c6547a4
parent 39 1860a8d798cf
child 41 f9b5a818ef99
Formalized the issue of XML serialization producing invalid XML in certain cases
by adding an Issue and filing the related bug.

This can be prevented, but would be a design change for the feature.
index.html
--- a/index.html	Sat Mar 22 17:02:28 2014 -0700
+++ b/index.html	Wed Mar 26 16:01:06 2014 -0700
@@ -319,6 +319,13 @@
             definitions. The <a title="concept-serialize-xml">XML serialization</a> algorithm defined 
             in this document does not escape, encode, or fail to serialize such attribute names.
         
+        <p class="issue"><a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=25168">Bug: 25168</a>
+            Should an XML Serialization check for these potential issues and tweak element 
+            and attribute localNames that could cause problems? For example, replace "<code>:</code>" 
+            (U+003A COLON) with "<code>_</code>" (U+005F LOW LINE) in element localNames and drop/replace
+            "<code>xmlns</code>" and "<code>xmlns:</code>" prefixes in attribute localNames? Or should
+            the XML Serialization fail to serialize under these scenarios?
+        
         <p>To produce an <dfn title="concept-serialize-xml">XML serialization</dfn> of a
             <a title="node" data-spec="DOM4" class="externalDFN">Node</a> <var>node</var> given a
             <a title="concept-context-namespace">context namespace</a> <var>namespace</var>, a