Fwd: [tei-council] regularizing names

[John A. Walsh]

Here's my previous reply to Julia.  I meant to send it to the list,  
but it only went to Julia.

John
| John A. Walsh, Associate Director for Projects and Services
| Digital Library Program / Indiana University Libraries
| Indiana University, 1320 East Tenth Street, Bloomington, IN 47405
| Voice:812-855-8758 Fax:812-856-2062 <mailto:jawalsh at indiana.edu>

Begin forwarded message:

> From: "John A. Walsh" <jawalsh at indiana.edu>
> Date: July 8, 2005 7:47:58 PM EST
> To: Julia Flanders <Julia_Flanders at Brown.edu>
> Subject: Re: [tei-council] regularizing names
>
>
> Julia and Perry,
>
> This seems to me to be a very elegant solution.
>
> I'm wondering where in the header these <regName> elements should  
> live.  It
> seems that <profileDesc> is the logical place, since it groups  
> together lots of
> other non-bibliographic metadata.  <profileDesc> could include a
> <regularization> (or <regularisation>) element that groups together  
> the many
> <regName> elements.
>
> And perhaps the guidelines should also discuss the option of  
> pointing to an
> external file dedicated to name regularizations.  For instance, if  
> my project
> consists of hundreds of commentaries on Romantic poetry, I don't  
> need to repeat
> <regName authority="LCNAF" id="byron" >Byron, George Gordon Byron,
> Baron</regName> in every document.  Rather, I could do something  
> like this:
> "...the dastardly and poisonous malignity of <persName
> reg="myRegNames.xml#byron">Byron's</persName> most foul and  
> treacherous
> libel...," pointing to a master myRegNames.xml file.  Of course,  
> this latter
> approach has some potential overlap with the functionality of @key,  
> if one
> accepts that the key can be an id in an XML file as well as it  
> could be a id in
> a database.  But then the TEI is all about choices :-), so I don't  
> see this as a
> problem.
>
> John
> -- 
> | John A. Walsh, Associate Director for Projects and Services
> | Digital Library Program / Indiana University Libraries
> | Indiana University, 1320 East Tenth Street, Bloomington, IN 47405
> | Voice:812-855-8758 Fax:812-856-2062 <mailto:jawalsh at indiana.edu>
>
>
> Quoting Julia Flanders <Julia_Flanders at Brown.edu>:
>
>
>> Here's what Perry and I have come up with concerning the
>> regularization of names.
>>
>> We propose, tentatively, that in P5 we handle the regularization of
>> names as follows:
>>
>> Name elements (<name> and the other "primary" name elements including
>> <persName>, <placeName>, <orgName>, <geogName>) may carry a reg=
>> attribute, which points to a <regName> element which contains
>> information on regularization. This element might live in the TEI
>> header or in some other convenient place. The datatype for reg= would
>> be tei.data.code. The element name (<regName> as against <reg>) is
>> chosen to help distinguish the function of this regularization
>> structure from other kinds of regularization in the document.
>>
>> The nested naming elements such as <foreName>, <surname>, etc.--i.e.
>> those which cannot occur on their own but must be nested inside a
>> primary naming element--would not carry the reg= attribute and cannot
>> be regularized independently. We considered a mechanism for doing
>> this and if any Council members think it would be a good idea we can
>> add this bit.
>>
>> The <regName> element may either contain a regularized version of the
>> name as its content, or it may carry a pointer to an external
>> resource (either locally maintained or an authority file external to
>> the project, such as Library of Congress Name Authority files). It
>> could also do both, and we don't see a need to police this choice
>> (e.g. by making these options exclusive).
>>
>> The <regName> element would carry three attributes:
>> --authority=  indicates what authority, if any, is being used as the
>> source of the regularization, with values such as "NACO", other
>> possibilities
>> --url= (or target=) points to an external resource
>> --xml:id= allows the element to be pointed to from the naming element
>> in the text.
>>
>> Example:
>>
>> <regName authority="NACO" xml:id="rn17">Clinton, William J.</regName>
>> <regName authority="NACO" xml:id="rn18">Aldrin, Edwin Eugene, Jr.</ 
>> regName>
>>
>> <!-- above <regName> elements may be somewhere in <teiHeader> or  
>> <hyperDiv>,
>>             and may be part of a new prosopographic element -->
>> <!-- ... -->
>> <name reg="#rn17">Bill Clinton</name>
>> <persName reg="#rn18">Buzz Aldrin</persName>
>>
>> We are still concerned about how this use of reg= and <regName> will
>> fit in with other forms of regularization (e.g. spelling). However,
>> since all other uses of reg= will probably now be addressed as child
>> elements, the possibility of confusion is diminished.
>>
>> Comments welcome--
>>
>> Julia
>> _______________________________________________
>> tei-council mailing list
>> tei-council at lists.village.Virginia.EDU
>> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
>>
>