OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] RE: Best Practice for designing XML vocabularies containingaccented characters -- allow both composed and decomposed forms

On 2/2/2013 2:08 PM, David Lee wrote:
>              <xs:choice>
>                  <xs:element name="résumé" type="xs:string" />
>                  <xs:element name="reěsumeě" type="xs:string" />
>              </xs:choice>
> --------------
> I personally shudder at this concept ...  frightening <ducks under  covers>
I agree, that's a terrible idea. Sadly the pragmatic recommendation must 
be just don't do that: ie don't use characters that can be represented 
differently in NFC and NFD in node names.  And if your vocabulary *must* 
include such names, then it is incumbent on you to normalize incoming 
data (to NFC I would think) when you process it. Stop the madness!


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS