Re: Surnames and indexing white pages

David Herron <david@twg.com> Tue, 17 August 1993 18:09 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa11264; 17 Aug 93 14:09 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa11260; 17 Aug 93 14:09 EDT
Received: from haig.cs.ucl.ac.uk by CNRI.Reston.VA.US id aa16555; 17 Aug 93 14:09 EDT
Received: from bells.cs.ucl.ac.uk by haig.cs.ucl.ac.uk with local SMTP id <g.05017-0@haig.cs.ucl.ac.uk>; Tue, 17 Aug 1993 18:13:41 +0100
Received: from eco.twg.com by bells.cs.ucl.ac.uk with Internet SMTP id <g.16880-0@bells.cs.ucl.ac.uk>; Tue, 17 Aug 1993 18:13:25 +0100
Received: from LOCAL.eco.twg.com by eco.twg.com (5.67/ECO.m-$Revision: 2.16 $) id AA05031; Tue, 17 Aug 93 13:12:33 -0400
Message-Id: <9308171712.AA05031@eco.twg.com>
Received: from apache.twg.com by apache.twg.com id <29860-0@apache.twg.com>; Tue, 17 Aug 1993 10:13:02 -0700
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: David Herron <david@twg.com>
Subject: Re: Surnames and indexing white pages
To: IPM Return Requested <osi-ds@cs.ucl.ac.uk>
Date: Tue, 17 Aug 93 10:13:01 PDT
In-Reply-To: Your message of Tue, 17 Aug 93 12:05:17 EST.<8362.9308170205@lemon>
Sensitivity: Personal
Conversion: Prohibited
Conversion-With-Loss: Prohibited
Encoding: 63 TEXT , 4 TEXT

It is good to run across someone else who's been angered over the eurocentricism
apparent in the X.400/X.500 spec's .. the same comments about the name
structure which you said for X.500 is also true for X.400.

One of my hobbies is Medieval Recreation.  That is, I study (free time allowing)

how people lived in the Middle Ages and attempt recreation of these things.
If you wander over to rec.org.sca you'll find some friends of mine ;-).  One
of the things I study is naming practices, what sort of names did people use
in the middle ages, and the structure and grammar thereof.  This hardly makes
me any kind of Linguist, but more of an extremely interested hobbyist.

I'm not about to suggest restructuring of the personal name attributes to
support medieval names.  Everything which John Gottschalk just mentioned
is very true.

There are a number of name styles which I'm aware of.  The `surname' system
familiar to us is just one and was imposed on us at some point in history
(to make some legal/genealogical things easier).

The `patronymic' or `matronymic' systems are what John was talking about
with either `bin' or `bintu' (those are middle eastern).  It's just like
he says, in a patronymic society you take your fathers name and make it
into the `son of' form (genitive) (and matronymic societies do this with
mothers name).  I understand this is still done in Iceland besides the middle
eastern examples which John mentioned.

In some cultures (medieval Wales for instance) the patronymics can go back
for multiple generations (John ap George ap Lloyd ap Llewellyn .. for instance).

I haven't studied many non european systems.  I recently took a class on
medieval Japanese names, however.  Those had five components which I don't
clearly remember right now, most especially the order.  However one was
from the `clan' you were a member of.  Another was for the branch of government
(society?) you worked in.  Another for your ranking.  Another for something
which served as `given name' but translated as "son #1", "daughter #2".  etc.

Then there are `occupational' (John the Smith became John Smith when
organized surnames were imposed on us).  And from descriptive bynames
(John Goodheart).  And from locations (Jack London for instance).  But these
all fit the model which X.500 uses, especially since those were what was
imposed as surnames.

Now..  is any of this actually a problem?  Do the perceived needs for X.500
require that the children of one person be listed in the directory
in a way allowing easy finding of them?  Or is the real need in lookups
and so you want to specify a useful presentation order of the components?
Or will there be legal/genealogical reasons why it will be requested
that parent/child relationships be shown in X.500?



To my understanding a good generalization of personal names is

	to allow for `n' components (n is pretty small but varies
	from culture to culture.. the largest value I know of is 5)

	specification of presentation order and which component(s) is/are
	used for sorting.

I suspect this isn't the place to raise these issues.  Since the Person
class is defined in X.500 it is *that* committee to which these issues
are brought.

<- David Herron <david@twg.com> (work) <david@davids.mmdf.com> (home)
<-
<- All hard work brings a profit, but mere talk leads only to poverty.
<-               Proverbs 14:23