I think this depends on whether Scott's XML is claiming that the person
Fabius Honoratius's role in life is as tribune and relict, or whether
the role of this occurrence of his name in this text is to identify both
the tribune and the relict in the context of this inscription. If the
latter, then @role on `<persName>` is exactly what the wants, isn't it?
More to the point, shouldn't @role on `<person>` and @role in
`att.naming` be normalized, especially as the definition suggests
they're intended to be used in the same way?
(Re @nymRef: I'm often guilty of this myself. In fact, I think everyone
I know uses @nymref in their working XML as a substitute for the much
lamented P4 @reg [and the absense of @lemma on `<*name>`], with every
intention, of course, of then auto-generating a `<listNym>`, and adding
"../alists/names.xml#" to the beginning of all values, at the end of the
On 2014-02-12 21:20, Sebastian Rahtz wrote:
> On 11 Feb 2014, at 20:15, Scott Vanderbilt (TEI-L) <[log in to unmask]> wrote:
>> I am endeavoring to encode prosopographical attributes concerning persons named in some epigraphic texts. I am (perhaps inadvisedly) using @role in <persName> for this purpose. My problem is that these named persons often have multiple roles that I wish to encode. For instance, in one typical case, I have a named survivor in a funerary inscription who also happens to be the tribune of an auxiliary cohort.
>> So, I am encoding as follows:
>> <persName type="roman" role="tribune relict">
>> <name nymRef="Fabius" type="gentilicium">Fabius</name>
>> <name nymRef="Honoratus" type="cognomen">Honoratus</name
> I really wouldn’t do it like this myself. I’d keep persName for marking up inline occurrences or names,
> with a @ref pointing to a <person> element in a prosopographical context which expounds
> on what we know about the person, including their roles. Unless I mistake, of course, and your
> <persName> is inside a <person> already.
> However, I can see why you might want to have multiple values in @role, and I can’t see
> much reason not to allow it. I’d suggest you put in a feature request to change it from
> “one value” to “one or more values”. The use of @role on <person> _does_ permit
> multiple values, just to madden you.
> do you want me to remind you in that @nymRef is a pointer? i.e., it should be #Fabius, not Fabius,
> where “Fabius” is the ID of a <nym> element? Your markup actually implies that a local
> file called “Fabius” contains just a <nym>.
> Sebastian Rahtz
> Director (Research) of Academic IT
> University of Oxford IT Services
> 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
> Não sou nada.
> Nunca serei nada.
> Não posso querer ser nada.
> À parte isso, tenho em mim todos os sonhos do mundo.
Dr Gabriel BODARD
Researcher in Digital Epigraphy
King's College London
Boris Karloff Building
26-29 Drury Lane
London WC2B 5RL
T: +44 (0)20 7848 1388
E: [log in to unmask]