Microsoft KB Archive/262585

= PRB: Do Not Use &quot;xml&quot; Keyword to Begin User-Defined Namespace Prefixes =

Article ID: 262585

Article Last Modified on 8/8/2003

-

APPLIES TO


 * Microsoft XML Parser 2.0
 * Microsoft XML Core Services 4.0
 * Microsoft XML Core Services 4.0

-



This article was previously published under Q262585



SYMPTOMS
If you use the &quot;xml&quot; keyword (in any combination of uppercase or lowercase letters) in user-defined namespace prefixes in an XML document, the Microsoft XML (MSXML) parser generates the following error message:

The namespace prefix is not allowed to start with the reserved string &quot;xml.&quot;



CAUSE
The xml keyword in any combination of uppercase or lowercase letters is a reserved word, and therefore cannot be specified as the first three characters of a user-defined namespace prefix.



RESOLUTION
Rename the namespace prefix so that it does not begin with the xml keyword.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.



Steps to Reproduce Behavior
 Open a new file in Microsoft Notepad.  Cut and paste the following XML code into Notepad:     </xmldt:ISBN> </Book> </Books> </li> Save the file as an XML file on your hard drive.</li> Open the saved XML file in Internet Explorer, and note that the MSXML parser generates the error message in the &quot;Symptoms&quot; section of this article.</li> Change the case of the xml keyword (uppercase and mixedcase) in the prefix name, and then save and open the XML file in Internet Explorer. Note that the same error message appears.</li> Rename the namespace prefix so that it does not begin with the xml keyword. Save and open the XML file in Internet Explorer, and note the MSXML parser successfully loads the document in Internet Explorer and displays it by applying the default Extensible Stylesheet Language (XSL) stylesheet.</li></ol>

Additional query words: IE

Keywords: kbprb KB262585

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.