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

Re: Six Reasons Not to use XML Attributes

• From: Andrew Welch <andrew.j.welch@gmail.com>
• To: John Cowan <cowan@mercury.ccil.org>
• Date: Fri, 2 Mar 2012 18:44:10 +0000

>> I think that if you have a straight-up name field, you either end up
>> being culturally obtuse or also needing a bunch of parallel fields for
>> various collation scenarios.
>
> That's what I meant by the field needing to be repeatable.  Chris
> Maden devised the system that $EMPLOYER is using, which involves
> personNameProfile elements which are themselves repeatable, and which have
> children for purpose, pattern (what order to put the textual elements in),
> the (meta-)name of this profile, full name, and five elements for name
> parts: givenName (repeatable), familyName (repeatable), prefix, suffix,
> nickname, and full name, all of which are optional.  There is continual
> pressure to add middleName, but so far we have effectively resisted it:
> canonical U.S. middle names are additional given names.

Straying off topic - why not use the foaf markup?


-- 
Andrew Welch
http://andrewjwelch.com

• Follow-Ups:
  • Re: Six Reasons Not to use XML Attributes
    • From: "Christopher R. Maden" <crism@maden.org>

• References:
  • Six Reasons Not to use XML Attributes
    • From: "Costello, Roger L." <costello@mitre.org>
  • Re: Six Reasons Not to use XML Attributes
    • From: John Cowan <cowan@mercury.ccil.org>
  • Re: Six Reasons Not to use XML Attributes
    • From: Uche Ogbuji <uche@ogbuji.net>
  • Re: Six Reasons Not to use XML Attributes
    • From: John Cowan <cowan@mercury.ccil.org>
  • Re: Six Reasons Not to use XML Attributes
    • From: Uche Ogbuji <uche@ogbuji.net>
  • Re: Six Reasons Not to use XML Attributes
    • From: John Cowan <cowan@mercury.ccil.org>