There can be other roles in which a person contributes to the creation of a play. In DraCor we currently do not support providing explicit information on the "role" of an individual creator, but add them as plain authors.
See the example of the Shakespeare Drama Corpus below:
translator [trl]: A person or organization who renders a text from one language into another, or from an older form of a language into the modern form.
I am not sure which attribute to use best:
We could attach this information via an attribute, candidates are:
@ana from att.global.analytic (as always good for everything; role:trl)
maybe, but probably not * @role att.naming
What's IMHO not desireable: use a <respStmt>, we would want an attribute to be less invasive.
From the Guidelines:
Note, however, that the role a person has in a given context (such as witness, defendant, etc. in a legal document) should not be encoded using the roleName element, since this is intended to mark roles which function as part of a person's name, not the role of the person bearing the name in general. Information about roles, occupations, etc. of a person are encoded within the person element discussed below in 14.3 Biographical and Prosopographical Data.
There can be other roles in which a person contributes to the creation of a play. In DraCor we currently do not support providing explicit information on the "role" of an individual creator, but add them as plain authors.
See the example of the Shakespeare Drama Corpus below:
As a vocabulary we could re-use the MARC Relator Codes.
In the case of translator:
I am not sure which attribute to use best:
We could attach this information via an attribute, candidates are:
@ana
from att.global.analytic (as always good for everything;role:trl
)@role
att.namingWhat's IMHO not desireable: use a
<respStmt>
, we would want an attribute to be less invasive.From the Guidelines:
I quickly skimmed through the examples of
<author>
but could not find a single example that would use any attributes on the element (apart from xml:id): https://www.tei-c.org/release/doc/tei-p5-doc/en/html/examples-author.html@role
is documented as such:Using
@ana
:An option: We would have to define the prefix
role
somewhere... As in the example above: there is a RDF version of the mark relators at https://id.loc.gov/vocabulary/relators.html, e.g. URI of trl = https://id.loc.gov/vocabulary/relators/trl We can define our prefix rolehttp://id.loc.gov/vocabulary/relators/
-->