Encode Responsibility Statements
Rationale
We give credit to the contributors of each file using a series of responsibility statements.
This documentation gives information on the critical practice of giving credit where
it is due with the
<respStmt>
element in the metadata of each file.Practice: Who to Give Credit To
You will encode a series of
In addition to these four
<respStmt>
elements in the
<titleStmt>
at the top of each of your files. Each file will contain at least four
<respStmt>
elements:
One giving credit to yourself as editor
One giving yourself credit as copyright holder over editorial content
One giving the University of Victoria credit as copyright holder over the XML and
interface
One giving credit to the LEMDO Team for their collective work either encoding or converting
and remediating your files
<respStmt>
elements, you may wish to give credit to other contributors such as research assistants.In your edition page only, you will also add a
<respStmt>
for each of your anthology leads. If your edition was peer-reviewed by someone that
has agreed to be credited publicly, you will also give them a
<respStmt>
in your edition page.In your edition page, your modernized text, and your semi-diplomatic transcription,
you will also add a
<respStmt>
for the author of your text.Practice
Each
<respStmt>
has two child elements:
<resp>
and one of either
<persName>
or
<orgName>
. Note that we do not use the
<name>
element.The
<resp>
element is for stating what each contributor’s role is. LEMDO generally uses the
standard vocabulary from the Library of Congress’s MARC Code List for Relatorsto define each contributor’s role. For a full list of the roles that we allow in our
<resp>
elements, see Responsibilities Taxonomy.To encode the
<resp>
element:
Add a
@ref attribute to the
<resp>
element.For the value of the
@ref attribute, add a "resp:" prefix followed by the appropriate value from the
@xml:id column in the Responsibility Valuestable.
In the text node of the
<resp>
element, add the contributor’s role. In most cases, this will be the name that corresponds
with the responsibility value that you used.Use the
<persName>
element when giving credit to an individual contributor. To encode the
<persName>
element:
Add a
@ref attribute to the
<persName>
element.For the value of the
@ref attribute, add a "pers:" prefix if the person is an editorial, encoding, or technical contributor (i.e., editors,
anthology leads, RAs, programmers, etc.) or a "pros:" if the person is a historical figure (i.e., authors, booksellers, publishers, printers,
etc.).After the prefix in the value of the
@ref attribute, put the contributor’s xml:id. If you are uncertain of their xml:id, check
our Personography (for current contributors) or Prosopography (for historical people).In the text node of the
<persName>
element, add the contributor’s full name.Use the
<orgName>
element when giving credit to a group or organization. To encode the
<orgName>
element:
Add a
@ref attribute to the
<orgName>
element.For the value of the
@ref attribute, add an "org:" prefix followed by the group or organization’s xml:id. If you are uncertain of its
xml:id, check our Orgography.Special Case: Encode Responsibility Statements for Copyright Holders
LEMDO adds two separate
<respStmt>
elements for copyright holders. The first states the person who retains intellectual
rights (licensed under a CC BY-SA NC license) over the text. The second states that
the University of Victoria retains intellectual rights over the markup used in the
file.Both
<respStmt>
elements for copyright holders are encoded by putting the
@ref attribute and "resp:cph" value on the
<resp>
element. The distinction between the two is made in the text node of the
<resp>
element: for textual copyright holders, add (Content)at the end of the text node; for markup copyright holders, add
(XML and interface)at the end of the text node.
Special Case: Give Credit to the LEMDO Team
LEMDO credits the LEMDO team as a whole for their work encoding, converting, and remediating
files. Because the LEMDO team works on every file that is published, they are credited
in each file. To give credit to the LEMDO team:
Add a
<respStmt>
element at the end of your list of responsibility statements.Give a value of
"resp:edt_mrk" on the
@ref attribute on the
<resp>
element.If your file was converted from IML, put
Conversion and Remediationin the text node of the
<resp>
element.If your file was encoded for the first time in TEI (i.e., it was not converted from
IML), put
Encoderin the text node of the
<resp>
element.Put an
<orgName>
element after the
<resp>
element.Give a value of
"org:LEMD1" on the
@ref attribute on the
<orgName>
element.In the text node of the
<orgName>
element, put LEMDO Team.
Examples
The following is an example of a series of responsibility statements in a critical
paratext:
<titleStmt>
<title type="main">Title</title>
<respStmt>
<resp ref="resp:aut">Author</resp>
<persName ref="pers:PEEE1">Author of Critical Paratext</persName>
</respStmt>
<respStmt>
<resp ref="resp:cph">Copyright Holder (Content)</resp>
<persName ref="pers:PEEE1">Editor Name</persName>
</respStmt>
<respStmt>
<resp ref="resp:cph">Copyright Holder (XML and interface)</resp>
<orgName ref="org:UVIC1">University of Victoria</orgName>
</respStmt>
<respStmt>
<resp ref="resp:edt_mrk">Encoder</resp>
<orgName ref="org:LEMD1">LEMDO Team</orgName>
</respStmt>
</titleStmt>
<title type="main">Title</title>
<respStmt>
<resp ref="resp:aut">Author</resp>
<persName ref="pers:PEEE1">Author of Critical Paratext</persName>
</respStmt>
<respStmt>
<resp ref="resp:cph">Copyright Holder (Content)</resp>
<persName ref="pers:PEEE1">Editor Name</persName>
</respStmt>
<respStmt>
<resp ref="resp:cph">Copyright Holder (XML and interface)</resp>
<orgName ref="org:UVIC1">University of Victoria</orgName>
</respStmt>
<respStmt>
<resp ref="resp:edt_mrk">Encoder</resp>
<orgName ref="org:LEMD1">LEMDO Team</orgName>
</respStmt>
</titleStmt>
The following is an example of a series of responsibility statements in a modernized
text:
<titleStmt>
<title type="main">Title</title>
<respStmt>
<resp ref="resp:aut">Author</resp>
<persName ref="pros:PRRR1">Author Name</persName>
</respStmt>
<respStmt>
<resp ref="resp:edt">Editor</resp>
<persName ref="pers:PEEE1">Editor Name</persName>
</respStmt>
<respStmt>
<resp ref="resp:cph">Copyright Holder (Content)</resp>
<persName ref="pers:PEEE1">Editor Name</persName>
</respStmt>
<respStmt>
<resp ref="resp:cph">Copyright Holder (XML and interface)</resp>
<orgName ref="org:UVIC1">University of Victoria</orgName>
</respStmt>
<respStmt>
<resp ref="resp:edt_mrk">Encoder</resp>
<orgName ref="org:LEMD1">LEMDO Team</orgName>
</respStmt>
</titleStmt>
<title type="main">Title</title>
<respStmt>
<resp ref="resp:aut">Author</resp>
<persName ref="pros:PRRR1">Author Name</persName>
</respStmt>
<respStmt>
<resp ref="resp:edt">Editor</resp>
<persName ref="pers:PEEE1">Editor Name</persName>
</respStmt>
<respStmt>
<resp ref="resp:cph">Copyright Holder (Content)</resp>
<persName ref="pers:PEEE1">Editor Name</persName>
</respStmt>
<respStmt>
<resp ref="resp:cph">Copyright Holder (XML and interface)</resp>
<orgName ref="org:UVIC1">University of Victoria</orgName>
</respStmt>
<respStmt>
<resp ref="resp:edt_mrk">Encoder</resp>
<orgName ref="org:LEMD1">LEMDO Team</orgName>
</respStmt>
</titleStmt>
The following is an example of a series of responsibility statements in an edition
page:
<titleStmt>
<title type="main">Title</title>
<respStmt>
<resp ref="resp:edt">Editor</resp>
<persName ref="pers:PEEE1">Editor Name</persName>
</respStmt>
<respStmt>
<resp ref="resp:edt_coord">Co-Coordinating Editor</resp>
<!-- MICA1: should this just be Coordinating Editor? -->
<persName ref="pers:PEEE1">Anthology Lead Name</persName>
</respStmt>
<respStmt>
<resp ref="resp:cph">Copyright Holder (Editorial content)</resp>
<persName ref="pers:PEEE1">Editor Name</persName>
</respStmt>
<respStmt>
<resp ref="resp:cph">Copyright Holder (XML and interface)</resp>
<orgName ref="org:UVIC1">University of Victoria</orgName>
</respStmt>
<respStmt>
<resp ref="resp:vet">Peer Reviewer</resp>
<persName ref="pers:PEEE1">Peer Reviewer Name</persName>
</respStmt>
<respStmt>
<resp ref="resp:edt_mrk">Encoder</resp>
<orgName ref="org:LEMD1">LEMDO Team</orgName>
</respStmt>
</titleStmt>
<title type="main">Title</title>
<respStmt>
<resp ref="resp:edt">Editor</resp>
<persName ref="pers:PEEE1">Editor Name</persName>
</respStmt>
<respStmt>
<resp ref="resp:edt_coord">Co-Coordinating Editor</resp>
<!-- MICA1: should this just be Coordinating Editor? -->
<persName ref="pers:PEEE1">Anthology Lead Name</persName>
</respStmt>
<respStmt>
<resp ref="resp:cph">Copyright Holder (Editorial content)</resp>
<persName ref="pers:PEEE1">Editor Name</persName>
</respStmt>
<respStmt>
<resp ref="resp:cph">Copyright Holder (XML and interface)</resp>
<orgName ref="org:UVIC1">University of Victoria</orgName>
</respStmt>
<respStmt>
<resp ref="resp:vet">Peer Reviewer</resp>
<persName ref="pers:PEEE1">Peer Reviewer Name</persName>
</respStmt>
<respStmt>
<resp ref="resp:edt_mrk">Encoder</resp>
<orgName ref="org:LEMD1">LEMDO Team</orgName>
</respStmt>
</titleStmt>
Prosopography
Janelle Jenstad
Janelle Jenstad is a Professor of English at the University of Victoria, Director
of The Map of Early Modern London, and Director of Linked Early Modern Drama Online. With Jennifer Roberts-Smith and Mark Kaethler, she co-edited Shakespeare’s Language in Digital Media: Old Words, New Tools (Routledge). She has edited John Stow’s A Survey of London (1598 text) for MoEML and is currently editing The Merchant of Venice (with Stephen Wittek) and Heywood’s 2 If You Know Not Me You Know Nobody for DRE. Her articles have appeared in Digital Humanities Quarterly, Elizabethan Theatre, Early Modern Literary Studies, Shakespeare Bulletin, Renaissance and Reformation, and The Journal of Medieval and Early Modern Studies. She contributed chapters to Approaches to Teaching Othello (MLA); Teaching Early Modern Literature from the Archives (MLA); Institutional Culture in Early Modern England (Brill); Shakespeare, Language, and the Stage (Arden); Performing Maternity in Early Modern England (Ashgate); New Directions in the Geohumanities (Routledge); Early Modern Studies and the Digital Turn (Iter); Placing Names: Enriching and Integrating Gazetteers (Indiana); Making Things and Drawing Boundaries (Minnesota); Rethinking Shakespeare Source Study: Audiences, Authors, and Digital Technologies (Routledge); and Civic Performance: Pageantry and Entertainments in Early Modern London (Routledge). For more details, see janellejenstad.com.
Joey Takeda
Joey Takeda is LEMDO’s Consulting Programmer and Designer, a role he assumed in 2020
after three years as the Lead Developer on LEMDO.
Mahayla Galliford
Project manager, 2025-present; research assistant, 2021-present. Mahayla Galliford
(she/her) graduated with a BA (Hons with distinction) from the University of Victoria
in 2024. Mahayla’s undergraduate research explored early modern stage directions and
civic water pageantry. Mahayla continues her studies through UVic’s English MA program
and her SSHRC-funded thesis project focuses on editing and encoding girls’ manuscripts,
specifically Lady Rachel Fane’s dramatic entertainments, in collaboration with LEMDO.
Martin Holmes
Martin Holmes has worked as a developer in the UVic’s Humanities Computing and Media
Centre for over two decades, and has been involved with dozens of Digital Humanities
projects. He has served on the TEI Technical Council and as Managing Editor of the
Journal of the TEI. He took over from Joey Takeda as lead developer on LEMDO in 2020.
He is a collaborator on the SSHRC Partnership Grant led by Janelle Jenstad.
Navarra Houldin
Training and Documentation Lead 2025–present. LEMDO project manager 2022–2025. Textual
remediator 2021–present. Navarra Houldin (they/them) completed their BA with a major
in history and minor in Spanish at the University of Victoria in 2022. Their primary
research was on gender and sexuality in early modern Europe and Latin America. They
are continuing their education through an MA program in Gender and Social Justice
Studies at the University of Alberta where they will specialize in Digital Humanities.
PLACEHOLDER HISTORICAL PERSON
PLACEHOLDER PERSON
Si Micari-Lawless
Si Micari-Lawless is a research assistant with LEMDO and MoEML, and an incoming fourth-year
English major at the University of Victoria.
Tracey El Hajj
Junior Programmer 2019–2020. Research Associate 2020–2021. Tracey received her PhD
from the Department of English at the University of Victoria in the field of Science
and Technology Studies. Her research focuses on the algorhythmics of networked communications. She was a 2019–2020 President’s Fellow in Research-Enriched
Teaching at UVic, where she taught an advanced course on
Artificial Intelligence and Everyday Life.Tracey was also a member of the Map of Early Modern London team, between 2018 and 2021. Between 2020 and 2021, she was a fellow in residence at the Praxis Studio for Comparative Media Studies, where she investigated the relationships between artificial intelligence, creativity, health, and justice. As of July 2021, Tracey has moved into the alt-ac world for a term position, while also teaching in the English Department at the University of Victoria.
Orgography
LEMDO Team (LEMD1)
The LEMDO Team is based at the University of Victoria and normally comprises the project
director, the lead developer, project manager, junior developers(s), remediators,
encoders, and remediating editors.
University of Victoria (UVIC1)
https://www.uvic.ca/Metadata
| Authority title | Encode Responsibility Statements |
| Type of text | Documentation |
| Publisher | University of Victoria on the Linked Early Modern Drama Online Platform |
| Series | Linked Early Modern Drama Online |
| Source |
TEI Customization created by Martin Holmes, Joey Takeda, and Janelle Jenstad; documentation written by members of the LEMDO Team
|
| Editorial declaration | n/a |
| Edition | Released with Linked Early Modern Drama Online 1.0 |
| Encoding description | Encoded in TEI P5 according to the LEMDO Customization and Encoding Guidelines |
| Document status | prgGenerated |
| Funder(s) | Social Sciences and Humanities Research Council of Canada |
| License/availability |
This file is licensed under a CC BY-NC_ND 4.0 license, which means that it is freely downloadable without permission under the following
conditions: (1) credit must be given to the author and LEMDO in any subsequent use
of the files and/or data; (2) the content cannot be adapted or repurposed (except
in quotations for the purposes of academic review and citation); and (3) commercial
uses are not permitted without the knowledge and consent of the editor and LEMDO.
This license allows for pedagogical use of the documentation in the classroom.
|