Altova Mailing List Archives


Re: [xml-dev] Valid element name

From: Melvin Chin <mc@----------.--->
To: "Fraser Goffin" <goffinf@----------.--->, "XML Developers List" <xml-dev@-----.---.--->
Date: 11/15/2006 5:42:00 PM
At 02:52 PM 2006-11-15 +0000, Fraser Goffin wrote:
><PremisesRatingData(NU)_FloodRate>
>
>Are there any reasonable approaches to encode invalid characters into
>something else that would be legal within an element name ??

A couple of ways actually.  A quick and simple way to manage small scale
"invalid" names is to do you own table-mapping of invalid characters to valid
ones, escaped by a reserved string.   Eg.
         Reserve String = "___" (3 underscore characters)
         Table Map:  '(' --> A, ')' --> B
         Then: <PremisesRatingData(NU)_FloodRate>
         Becomes: <PremisesRatingData___ANU___B_FloodRate>

Another way to handle situation if you have majority "invalid" name most of
the time, just perform MD5(invalid_name) and use that as your name in the
XML instance and keeping a table of "MD5(invalid_name) --> invalid_name"
to reverse-map back to original name.



cheers.

Disclaimer

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.