XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
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] Six Reasons Not to use XML Attributes

>> 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


[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