[tei-council] on regularizing names

Sebastian Rahtz sebastian.rahtz at oucs.ox.ac.uk
Fri Sep 22 07:21:32 EDT 2006

Now that I have got my head around the issue,
it all looks murkier and murkier. Syd's main example
(in whatever markup) is:
> a) <reg> on a par w/ the PCDATA inside name:
>      <persName>Syd
>        <reg>Bauman, Sydney D.</reg>
>      </persName>
but this isn't name regularization,  it's linking "Syd" to the person
called "Sydney D. Bauman". Name regularization would just link
"Syd" to "Sydney", and (separately), "D." to "David" (or whatever it is).

Similarly, the pointer example
>       <p>In the 1940s he was known as
>       <persName reg="#reg25">Ritchie</persName>, but most of us
>       know him as <persName reg="#reg26">Ringo</persName>.</p>
>       <!-- meanwhile, in header or elsewhere: -->
>       <regName key="url:http://www.imdb.com/name/nm0823592/"
>                xml:id="reg25">Starkey, Richard</regName>
>       <regName key="url:http://www.imdb.com/name/nm0823592/"
>                xml:id="reg26">Starr, Ringo</regName>

is simply taking us to a real person again.

If my text is follows:

   My father <name>Jim</name> was thus named
   because the of the recent access to the throne
   of a king called <name>James</name>

the suggestion is that the first <name> should
change to (shorthand, bad idea) <name reg="James">Jim</name>,
so that someone can find all the uses of the name "James".

In this case we want <name key="#JAMES"> pointing to

 <aName xml:id="JAMES">

which talks about the abstract notion of the name "James",
as a forename, not the <regName> proposed above which
looks like a synonym for <person> in the example given.

Sebastian Rahtz      

Information Manager, Oxford University Computing Services
13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431

OSS Watch: JISC Open Source Advisory Service

More information about the tei-council mailing list