-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Contributor roles #71
Comments
OK, maybe I should have looked at the existing issue linked above instead of opening a new one, hm |
Why not |
regarding As I wrote, I couldn't find examples of
https://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONARS The example then would be:
|
Hi all, sorry for chiming in a bit late. I proposed to use |
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/trlWe can define our prefix role
http://id.loc.gov/vocabulary/relators/
-->The text was updated successfully, but these errors were encountered: