Technical Glossary (GLOSS1)

Scope

The sitewide technical glossary in GLOSS1.xml contains technical terms and project-specific terms and definitions thereof. Exclusions: it does not contain definitions of bibliographical or editorial terms. Those terms will be defined in a separate glossary or in EMEE.
Only LEMDO Team members at UVic can edit GLOSS1.

Structure

The file is structured as a series of <div> elements, one for each letter of the alphabet. Each one contains a <list> element with the @type value of "glossary".
<div xml:id="GLOSS1_F">
  <head>F</head>
  <list type="glossary">
    <item xml:id="PATH1">
      <label>file path</label>
      <gloss>A list of nested directory names separated by slashes. It is a way of showing directories nested within other directories (e.g., lemdo/data/texts).</gloss>
    </item>
    <item xml:id="EXTE1">
      <label>file extension</label>
      <gloss>The letters that follow the period in a filename. These letters, known as a filename suffix, indicate the file type, for example, .xml is an eXtensible Markup Language document.</gloss>
    </item>
  </list>
</div>
Give the <div> the @xml:id value of "GLOSS1_X", where X is the letter of the alphabet contained in the <div> .
Each item needs a unique xml:id. Follow the ABCD1 pattern for LEMDO xml:ids.
The <label> element contains the term being glossed. As much as possible, this term is the one used in the documentation. There may, however, be cases where a synonym is used in the documentation, with a link on the synonym to the term. The content of <label> will be displayed in the pop-up.
The <gloss> element contains our definition. If you are writing the definition, keep in mind that the people who need these glosses are editors using the LEMDO Encoding Guidelines to encode their editions, and Research Assistants at UVic and elsewhere. Avoid using additional technical terms in your definition of a technical term. Give examples where appropriate. Make a link to another resource if it is helpful.
Note: We have a Schematron rule to prevent <list type="glossary"> from being used outside of GLOSS1, except in <egXML> .

Prosopography

Isabella Seales

Isabella Seales is a fourth year undergraduate completing her Bachelor of Arts in English at the University of Victoria. She has a special interest in Renaissance and Metaphysical Literature. She is assisting Dr. Jenstad with the MoEML Mayoral Shows anthology as part of the Undergraduate Student Research Award program.

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.

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

Project manager 2022–present. Textual remediator 2021–present. Navarra Houldin (they/them) completed their BA in History and Spanish at the University of Victoria in 2022. During their degree, they worked as a teaching assistant with the University of Victoriaʼs Department of Hispanic and Italian Studies. Their primary research was on gender and sexuality in early modern Europe and Latin America.

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.

Glossary

Schematron
“Schematron is an open-source language for ensuring that certain patterns are present in XML documents. For example, it can insist upon certain spellings, enforce curly apostrophes, and limit the use of elements to specific contexts. It is the feather duster of an XML project. See An Overview of Schematron.”

Metadata