Schematron and Validation Errors Technical Writer Navarra Houldin Proofreader Mahayla Galliford Project Director Janelle Jenstad Project Manager Mahayla Galliford Training and Documentation Lead Navarra Houldin Programmer Martin Holmes Programmer Joey Takeda Junior Programmer Tracey El Hajj Social Sciences and Humanities Research Council of Canada

Released with Linked Early Modern Drama Online 1.0

 University of Victoria on the Linked Early Modern Drama Online Platform

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.

Linked Early Modern Drama Online

TEI Customization created by Martin Holmes, Joey Takeda, and Janelle Jenstad; documentation written by members of the LEMDO Team

Encoded in TEI P5 according to the LEMDO Customization and Encoding Guidelines

n/a

 Document Types All documents in LEMDO are either born-digital documents or primary documents. Within those two general categories, LEMDO offers additional ways to categorize a file. Born-digital Born-digital documents are anything other than primary texts Documentation Encoding and editorial guidelines; programming, processing, and rendering instructions; how-to instructions; element descriptions; and records of remediation. Responsibilities Responsibilities Project Director A person or organization with primary responsibility for all essential aspects of a project, has overall responsibility for managing projects, or provides overall direction to a project manager. LEMDO uses the term project director for the person who directs the LEMDO project. For anthology leads, use pbd. Proofreader A person who corrects printed matter. LEMDO uses the term proofreader for the person who performs minor corrections to a finalized document, which usually include typographical or rendering fixes. For copy-editing, use resp:edt_cpy. Programmer A person, family, or organization responsible for creating a computer program. Gloss needed. Technical Writer Writer of Technical Material: A person responsible for writing or compiling documentation of the project’s editorial, encoding, and programming practices. Automatically generated this file by extracting its content from lemdo.lite.odd. Tracey El Hajj 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.

 Mahayla Galliford 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

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 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.

 Janelle Jenstad 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 Beatrice 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

Joey Takeda is LEMDO’s Consulting Programmer and Designer, a role he assumed in 2020 after three years as the Lead Developer on LEMDO.

 LEMDO Team 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. A schema is a set of rules governing the use of TEI elements in a particular project. XML languages are all governed by a small set of shared principles; any document that follows these principles, even if it makes up its own elements, is well-formed XML. TEI is a formal language that is designed to comply with the principles of XML. TEI offers many elements and attributes in its XML-compliant language. But most projects still need to customize the TEI for their own purposes, by prescribing how and where TEI elements and attributes are to be used, precluding some elements and attributes, making other elements and attributes optional, making child elements required or optional, and defining allowed and required values for attributes. The schema captures the project’s requirements, prohibitions, and standards. We use a RelaxiNG schema at LEMDO. The main schema for LEMDO is lemdo-all.rng (where the .rng file extension indicates the schema type). The schema is responsible for generating the error messages in Oxygen when encoders break one or more of the rules associated with it. (Read more about schemas in the TEI Guidelines.) 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.
Prior Reading <ref target="learn_repoIntro.xml">The LEMDO Platform and Repository</ref> <ref target="learn_validate.xml">Validate Files</ref>
Introduction

Schematron is the language that LEMDO uses to write rules specific to LEMDO’s encoding. Schematron, alongside our schema, ensures that encoding is consistent and correct throughout the LEMDO project. If your encoding does not follow one of the Schematron rules that we have written, then you will get a validation error. This will prompt you to go back and correct your encoding. It is important that you fix validation errors as soon as you get them.

If you commit an invalid file, it will break the build. This means that our Jenkins Continuous Integration Server is unable to finish serving up a new version of the LEMDO-dev website. When the build is broken, nobody can see the work that they have recently committed rendered in HTML. If you inadvertently break the build, a member of the LEMDO team will contact you so that you can fix the error causing the build break.

If there is an error that is frequently occurring that is not currently prevented by Schematron, we will write a new Schematron rule in the ODD file (lemdo.odd). You must svn up regularly to ensure that you get any new Schematron rules that we add.

Step-by-Step: Check Validity Click the validation button at the top of your Oxygen window (it resembles a piece of paper with a checkmark on it). Check for the validation message at the bottom of your Oxygen window. It will say either Validation successful or Document contains errors. If your validation is successful, you can either continue working or save and commit your file. If your validation is not successful, you must fix the error. Never commit an invalid file.

For more detailed instructions for validating a file, see <ref target="learn_validate.xml">Validate Files</ref>.

Practice: Fix Validation Errors

To fix a validation error, look at the error message at the bottom of your Oxygen window. In most cases, we have written instructions for how to fix Schematron errors. For example, if you have a straight apostrophe in your file, you will get an error message that says: ERROR: Straight apostrophes are not allowed in text. Use curly apostrophes instead. The shortcut to add a curly apostrophe is ctrl+shift+’ (on PC or Unix) and command+shift+’ (on iOS).

If you are unable to see the entire message because it is cut off, you can pull up a window with the full message by double clicking on the message text.

If you are unable to fix the error yourself, contact the LEMDO team for help. Do not commit your file while it is invalid.