[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: RE: Best Practice for designing XML vocabularies containin

• From: Michael Sokolov <msokolov@safaribooksonline.com>
• To: David Lee <dlee@calldei.com>
• Date: Sat, 02 Feb 2013 14:30:25 -0500

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!

-Mike

• References:
  • Best Practice for designing XML vocabularies containing accentedcharacters -- allow both composed and decomposed forms
    • From: "Costello, Roger L." <costello@mitre.org>
  • RE: Best Practice for designing XML vocabularies containingaccented characters -- allow both composed and decomposed forms
    • From: David Lee <dlee@calldei.com>