Link to home
Start Free TrialLog in
Avatar of kalyangkm
kalyangkmFlag for United States of America

asked on

How to handle reserved words in XSD

I have a scenario where in the the XSD looks like the following after converting the XML to XSD. When I remove xml part from xmlDocument, the XSD works but if I keep it as xmlDocument it has issues. Please let me how to handle this.

Avatar of Gertone (Geert Bormans)
Gertone (Geert Bormans)
Flag of Belgium image

the XML recommendation states that names for elements schould not start with "xml" (or uppercase variants) for "future standardisation" reasons

By now it is fairly clear there will not be an XML 2.0 or the acceptance of XML 1.1, so most tools are very lax with this requirement
Some tools however will not allow you to do so.
So, this is likely a limitation by your tool being too strict (or actually adhering strict to the recommendation)

I consider element names that start with "xml" as poor design and I strongly recommend not to do that. Simply because by XML 1.0 recommendation you should not and you might hit a tool that prevents you (as you just seem to have experienced)

So, change the name of your element. If you can't do that, tell us which tool is breaking on it, we might find a workaround or suggest alternative tooling
Avatar of kalyangkm


We are using SAP PO middleware and looks like its not xml 1.1 + capable from what you are saying. Please let me know if there is any alternative.
Avatar of Gertone (Geert Bormans)
Gertone (Geert Bormans)
Flag of Belgium image

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial