In MODS we considered that people might be using different rules for what
is considered a surname and would use the appropriate entry element for
their context. So that, as stated below, the "De" could be part of the
surname or included at the end of the given name ("de"). We did separate
termsOfAddress and date. One can indicate an authoritative source by using
the authority attribute on name (to specify an authority file). In version
3.3 we are adding an element to recordInfo to state the description
standard used (if that standard specifies formulating names it would be
relevant here). We tried to avoid very detailed parsing of the name, and
I'm not sure what benefit there would be to giving a separate element for
these kinds of parts of names.
In response to an earlier comment by Karen Coyle, we already have an
element under <name> for <displayForm>.
On Mon, 22 Oct 2007, joseph greene wrote:
> Hello Thomas,
> Perhaps this is more an issue of cataloguing rules than of data
> structure. (Of course, wouldn't it be nice if the data structure were as
> specific as the cataloguing rules!)
> For example, the AACR2 (I only have the old 1988 2nd edition on hand),
> section 22.5D1, 'Articles and prepositions' states that
> 'If a surname includes an article or preposition [...], enter under the
> element most commonly used as entry element [...] Dutch. If the surname
> is Dutch, enter under the part following the prefix unless the prefix is
> 'ver'. In that case, enter under the prefix.
> Beeck, Leo op de
> Brink, Jan ten
> Ver Boven, Daisy'
> (I have to admit, these rules being Anglo-American, they may not be the
> best; later on they say: 'Flemish. See Dutch.')
> The U.K.'s National Council on Archives concurs:
> 'In surnames with separable prefixes, use the last word as the entry
> element, with cross-references from the prefix plus name in direct order
> if the language of origin requires.'
> 2.3A.2.3 Surname with separable prefixes
> So, following your example,
> <namePart type="family">Konig</namePart>
> <namePart type="given">Jan de</namePart>
> Best regards,
> Joseph Greene
> Irish Virtual Research Library and Archive Project (HII),
> James Joyce Library,
> Dublin 4.
> (t) 01 716 7506
> (e) [log in to unmask]
> (w) www.ucd.ie/ivrla
> ----- Original Message -----
> From: Thomas Place <[log in to unmask]>
> Date: Monday, October 22, 2007 8:24 am
> Subject: Re: [MODS] request for a new value for type attribute of namePart
> To: [log in to unmask]
> > I think that what I am talking about is not about rules or the same
> > name
> > treated differently in different contexts. The case in hand is
> > about
> > different names that look very similar.
> > The name Jan de Koning (1) is not the same as Jan De Koning (2).
> > (1) consists of three parts: given name = Jan, infix = de, family
> > name Koning.
> > (2) consists of two parts: given name = Jan, family name = De Koning.
> > MODS has a facility to indicate the parts of a name, which is
> > great.
> > However it is only possible to include given name and family name.
> > My
> > request is to include infix as a proper name part.
> > Note that it is not the case that the person who is Jan De Koning
> > (2) in
> > Belgium becomes Jan de Koning (1) in the Netherlands (or vice
> > versa). Also
> > in the Netherlands Jan De Koning remains Jan De Koning and he has a
> > different name from Jan de Koning. The difference becomes apparent
> > in
> > alphabetic lists that order on family name. Jan De Koning (2) comes
> > under
> > the D as De Koning, Jan and Jan de Koning (1) under the K as
> > Koning, Jan
> > de. I don't know the historical background of this subtle difference.
> > Thomas Place
> > On 20-10-2007 17:02, Karen Coyle wrote:
> > > This brings up something that does come up occasionally, which is
> > that
> > > we made need a way to indicate which set of "rules" is being
> > applied to
> > > a name. As you say,the same name can be treated differently in
> > different
> > > contexts. So, although we have
> > >
> > > Smith, John
> > > Mao, Tse-tung
> > >
> > > if we were to display these in their "natural" (cultural?) order
> > they
> > > would be
> > >
> > > John Smith
> > > Mao Tse-tung
> > >
> > > I don't know whether it makes sense to develop rules, or to
> > include a
> > > display form, but something is needed if the names will be shared
> > across
> > > contexts.
> > >
> > > kc
> > >
> > > Thomas Place wrote:
> > >> To: the MODS standard agency.
> > >>
> > >> There is a problem to represent Dutch personal names in MODS.
> > >> A Dutchman who is called Jan de Koning has as family name
> > 'Koning' and
> > >> as given name 'Jan'. The infix 'de' is not part of the family
> > name.
> > >> The possible values of the type attribute of namePart are
> > limited to
> > >> an explicit enumeration of values in the schema. There is no
> > value to
> > >> represent infixes like 'de', 'van' and 'van de'. Is it possible
> > to add
> > >> 'infix' (or another string with the same semantics) to the
> > enumeration
> > >> of values in the schema?
> > >>
> > >> Note that in Flanders the name would be Jan De Koning; 'Jan' is
> > the
> > >> given name and 'De Koning' is the family name. So this is a
> > problem
> > >> not of Dutch names, but of the names of the Dutch.
> > >>
> > >> We discovered this problem when writing guidelines for using
> > MODS for
> > >> institutional repositories. Probably more questions and/or
> > requests
> > >> will come out of this project (e.g., adding author identifiers
> > is a
> > >> problem).
> > >>
> > >> Regards,
> > >> Thomas Place
> > >>
> > >
> > --
> > Thomas W. Place ([log in to unmask])
> > Tilburg University, PO Box 90153, 5000 LE Tilburg, the Netherlands
> > phone: +31 13 466 2474; fax: +31 13 466 3370