If you want to use the @reg attribute simply to identify the person (by
using a regularised form of the name) you'd be better off using the new
mechanism for pointing from name instances to their corresponding <person>
elements, as detailed in chapter 17 of the Guidelines.
So, instead of saying:
Bundeskanzler <persName reg="Helmut Schmidt">Schmidt</persName> hat gestern
gesagt, daß er sich nicht vorstellen könne....
Bundeskanzler <persName key="#HS1">Schmidt</persName> hat gestern gesagt,
daß er sich nicht vorstellen könne....
Where @key points to a <person> element in the header (or elsewhere) with
the id "HS1":
<persName>Helmut Heinrich Waldemar Schmidt</persName>
<!-- other info -->
This is much better for search and indexing purposes.
M. J. Driscoll
From: TEI (Text Encoding Initiative) public discussion list
[mailto:[log in to unmask]] On Behalf Of Daniel Röwenstrunk
Sent: Tuesday, May 15, 2007 11:21 AM
To: [log in to unmask]
Subject: Attribute reg in persName
we are working on a project digitizing German newspaper articles,
letters and diaries all from the 19th century. We decided to use the TEI
P5 structure for tagging our texts. Most of the stuff we need is
completely perfect in P5, we got just one little thing:
we would like to use the "reg" attribute in persName, which disappeared
during the switch from P4 to P5. We have searched the mailing list
archives for this topic and found some threads discussing the absence of
the attribute and the alternative use of the reg-tag within the
persName-tag. We understand that using <reg /> has some significant
advantages especially for tagging the content of the <reg />'s content.
As we don't want to add text via a reg-tag and we don't need to tag the
content of the register-value either, the "old" reg-attribute would
perfectly fit our needs.
Anyway, the question arises, why the reg-attribute was discarded from
persName but not from orgName?
Is it possible to allow the usage of the attribute reg in persName again?