LEMDO: Chapter 19. Editions and Licensing

Chapter 19. Editions and Licensing

Introduction to Editions and Licensing

This chapter is designed for both editors and anthology leads to learn about how editions are licensed for inclusion in anthologies. Anthology leads can find more information written specifically for them in Chapter 20. Anthology Customization.

Learning Outcomes

By the time you have worked through every section of this chapter, you will:

Understand how editions are included in anthologies using LEMDO’s handshake model of inclusion.

Know how to license the files in your edition for publication.

Become familiar with the standard structure and organization of edition directories.

Be able to encode your edition page (emdABBR_edition.xml).

LEMDO Editions

LEMDO supports both individual editions and anthologies. For the most part, however, editions are commissioned for anthology projects. Anthologies have their own editorial boards and peer-review processes. LEMDO works with the anthology leads, and the anthology leads work with the editors they have convened for the anthology. Think of UVic as the publisher, LEMDO as the platform used to prepare and publish editions, the anthology leads as series editors, and the individual play editors as contributors to the series of editions embodied in an anthology.

LEMDO will allow editors to use the repository and tools without the editor being affiliated with an anthology if the editors are graduate students preparing projects or theses, or if the editors are a pedagogical partner and their students. LEMDO might liaise with the anthology leads to see if the prospective student edition might have a logical home in one of the anthologies eventually. At this point (2025), LEMDO has no plan to support multiple editions of any one play. Our key outcome is to expand the canon of teachable and performable early modern plays. One of LEMDO’s objectives, then, is to ensure that new editors work on plays that are not already under contract for one of the LEMDO anthologies.

Section	Description
The Handshake Model of Inclusion	Learn about how your edition will be included in an anthology
License Your Edition for Publication	Learn how to license your edition for publication
Edition Directories	Learn about the structure and organization of edition directories in the LEMDO repository
Encode Your Edition Page	Learn how to encode your edition page

The Handshake Model of Inclusion

Prior Reading

Introduction to Editions and Licensing

Introduction to the Handshake Model

Editions are not automatically included in anthologies. Two things have to happen for an edition to be included in an anthology:

The edition page and all of the component files of the edition must be licensed by the author/editor for inclusion in the anthology. The license is included in the


                                                <teiHeader>

of each file.

The anthology must explicitly include the edition using the lemdo-include instruction in the home page of the anthology (e.g., in qme.xml for a QME edition).

The purpose of this handshake model is to replicate in digital form the process of signing a contract. Both parties have to sign the contract for a publication to proceed. (Note that this digital handshake is usually in addition to a conventional publishing contract.)

Similarly, files are not automatically included in an edition. Three things have to happen for a file to be included in an edition:

The file must be licensed by the author/editor for inclusion in the sponsoring anthology.

The file must have a value of published on the


                                             @status

attribute of their


                                                <revisionDesc>

element.

The file must be listed in the edition page (e.g., emdMV_edition.xml).

Given that anthologies are published via the release model, whereby the anthology and its new content are periodically released to the public-facing website, this model makes the following publication strategies possible:

An anthology can have a web presence listing its personnel and editorial guidelines before any of the editions are commissioned or published.

An anthology can publish each edition as it is completed, rather than waiting for all editions to be complete before it publishes anything.

An individual edition can be published incrementally. By not licensing unfinished components of an edition and not including them in the edition page, the editor can hold back components of the edition that are not finished or not yet peer-reviewed. Even if the anthology includes the edition, only the finished parts of the edition will be pulled into the anthology.

Multi-Anthology Publication

Editions may be included in more than one anthology, with the consent of the editor. For example, the same edition of Macbeth might be included in the New Internet Shakespeare Editions, a King’s Men anthology (should someone decide to create one), and a Middleton anthology. One objective of the LEMDO project is to enable new combinations of already-edited plays; once we have a critical mass of editions, it becomes feasible to create new anthologies that regroup and reframe plays according to various selection principles (by author, by playing company, by theatre, or even by year).

Prior Reading

This documentation assumes that you are familiar with the principles of LEMDO’s handshake model of inclusion and know how to link to LEMDO documents:

The Handshake Model of Inclusion

Hash Character

Encode Reference Links

Rationale

For your edition to be included in an anthology release, you must correctly license the files that you wish to publish, your edition page must link to each file that you wish to publish, and your Anthology Lead(s) must include your edition in the anthology’s [anth].xml file. This documentation explains what editors must do during each step of the licensing process. (For more information on how Anthology Leads include editions in anthologies, see Practice: Include Editions for Release.)

Practice: Include Files in Your Edition

To include files in your edition and have them appear on your edition’s landing page, you must add links to them in your emdABBR_edition.xml file. For detailed information on how to encode a list of files for inclusion, see Practice: Encode the Notes Statement.

If you are publishing a partial edition (e.g., if you are publishing your semi-diplomatic transcription, modernized text, collation, textual annotations, and bibliography in the Peer-Review anthology and plan to publish the remaining components of your edition later), do not include the files that you do not wish to publish in that partial release. You can add them in at a later date.

Practice: License Your Edition for Inclusion in an Anthology

In addition to including the files that you wish to publish in your edition page, you must license each file for inclusion in your publishing anthology (or anthologies) and for inclusion in LEMDO. You must also license your emdABBR_edition.xml file. To do so, follow these steps:

In the


                                                <teiHeader>

of each file, find the


                                                <publicationStmt>

element.

The


                                                <publicationStmt>

element should have a child


                                                <availability>

element. To the


                                                <availability>

element, add a child


                                                <licence>

element (note that the element name uses the Canadian and British spelling).

Add a


                                             @from

attribute to the


                                                <licence>

element.

Give the


                                             @from

attribute a value of the planned date for your anthology’s next release. If you are uncertain about the date, contact your Anthology Lead(s). LEMDO uses ISO format (yyyy-mm-dd) for dates.

Add a


                                             @resp

attribute to the


                                                <licence>

element.

Give the


                                             @resp

attribute a value of pers: followed by your xml:id. If you do not know your xml:id value, you can find it by searching for your name in the LEMDO Personography.

Add a


                                             @corresp

attribute to the


                                                <licence>

element.

Give the


                                             @corresp

attribute a value of anth: followed by your anthology’s identifier. A list of anthology identifiers is available in the table below.

Add a second


                                                <licence>

element. Give it the same values as before, though this one’s


                                             @corresp

value should be anth:lemdo. This licenses it for inclusion in LEMDO as a whole.

Correctly encoded


                                          <licence>

elements will look like this:

Anthology Identifiers for Licensing
Anthology Name	Identifier
Digital Renaissance Editions	DRE1
Douai Shakespeare Manuscript Project	DOUA1
MoEML Mayoral Shows	moms
New Internet Shakespeare Editions	NISE1
Queen’s Men Editions	QME1

Inclusion in an Anthology

Once you have correctly included and licensed the files for your edition, your Anthology Lead(s) can include your edition in the anthology using an import instruction in their [anth].xml file. You will work together to determine when your edition is ready to be included and published in a new release of the anthology.

Other Resources

LEMDO YouTube video: Putting It All Together (Editorial)

LEMDO YouTube video: Putting It All Together (Technical)

LEMDO YouTube video: Releasing Your Anthology (Editorial)

LEMDO YouTube video: Releasing Your Anthology (Technical)

Edition Directories

Rationale

Your edition directory contains all of the documents produced for your edition. Each edition directory is named after its DRE Play ID, the acronym we use for the play. By having a discrete directory for each edition, we can give each editor full permission to make changes to all files related to their edition. This documentation explains how to navigate the structure of your edition’s directory and where in that directory you will add specific types of files.

Edition Directory Structure

All edition directories contain the following four folders:

app: Your app folder houses your edition’s apparatus files (i.e., your annotation and collation files).

crit: Your crit folder houses your edition’s critical paratexts (e.g., your acknowledgements; general, textual, and optional critical introductions; bibliography; and stage history). You may add a role list file to your crit folder.

main: Your main folder contains your modernized play text(s) and semi-diplomatic transcription(s).

supp: We have supp directories in many editions to accommodate the remediated legacy editions from DRE, ISE, and QME.

Some edition directories may also have one or both of these additional folders:

images

perf

In addition to the folders contained by edition directories, each edition has an edition file that resides inside the edition directory but outside of the child folders. Your edition landing page is generated from your edition file, and it lists all the files that belong to your edition and gives responsibility statements for everyone involved in the creation and oversight of your edition (including anthology leads) of the edition. For information on encoding your edition page, see Encode Your Edition Page.

Special Case: Images Folders

If your edition contains images, how you store them depends on the number of images that you are including. If you are adding three or fewer images to your edition, you must create an images folder in which to store them. Once you have created your images folder, add it to the LEMDO repository following the instructions in Practice: Add Files to the Repository.

If your edition contains four or more images, you must contact the LEMDO team to upload your images to our image server.

Regardless of where you store your images (in an images folder or on our images server), you must include all of the images that you use in your edition along with .txt files containing permissions to use those images. For more information on adding images to your edition, see Choose Image Types and Sizes.

Special Case: Paratexts

LEMDO is republishing Sonia Massai and Heidi Craig’s Early Modern Dramatic Paratexts project. The paratexts from this project are being added to the relevant edition directories. As we add these files to the repository, editors will begin to see para folders being added to their edition directories. Please leave this folder untouched.

Special Case: Performance As Research Folders

If your edition also contains production materials from performance-as-research (PAR) work, your edition directory will have a perf folder for global performance commentary (as opposed to performance annotations), production credits, and metadata for performance videos. (The videos themselves are stored elsewhere.)

Encode File Categories for Edition Files

Prior Reading

Introduction to LEMDO’s Taxonomies

Rationale

LEMDO processes different types of documents in different ways. The processor looks for the


                                          <catRef>

elements inside the


                                          <textClass>

element in the


                                          <teiHeader>

of your document and then applies the appropriate processing for the document types that are captured in the


                                          <catRef>

elements. If your document does not have


                                          <catRef>

elements, our processor will not know what type of file it is. If your document has the wrong values in the


                                       @target

attribute of the


                                          <catRef>

elements, our processor will apply the wrong processing to your file.

LEMDO has special processing for edition pages. Following this documentation will ensure that your main edition page is processed correctly.

Practice: Encode the Profile Description

The


                                          <textClass>

element identifies the type of file and will be the same for all edition landing pages, regardless of anthology or edition. An edition file will have one required


                                          <catRef>

element using the value ldtBornDigEdition.

Note that


                                          <catRef>

is an empty element.

Examples

Prior Reading

Introduction to Editions and Licensing

Edition Directories

Encode File Categories for Edition Files

Rationale

An edition is comprised of multiple XML files all contained in a single directory in the LEMDO repository. One of the XML files is an edition page. The edition page serves two functions:

It contains the metadata for your edition that LEMDO needs in order to publish your edition in the correct anthology (or anthologies), including credits and a list of completed edition components.

It contains the content of the edition landing page curated and organized according to your anthology’s preferred layout.

This documentation will explain how to encode both the metadata and the contents in your edition page.

Practice: Create an Edition Page

The LEMDO team will create an edition page for you from your anthology’s edition page template upon request. When you start work on your LEMDO edition, contact the LEMDO team to ensure that they have created an edition page for you.

Components of Metadata

Information about your edition belongs in the


                                          <teiHeader>

of your edition page. The main components of the metadata are:


                                                <fileDesc>


                                                <profileDesc>


                                                <encodingDesc>


                                                <revisionDesc>

The File Description

The


                                          <fileDesc>

element contains information about the text encoded in the file. This includes the text’s title, responsibility statements for the author and all of the people (or organizations) who contributed to the file, an edition statement, publication information, a series statement, a notes statement, and a description of the text’s source.

Practice: Encode the Title Statement

There are four key components of the


                                             <titleStmt>

element: one child


                                             <title>

element, at least five


                                             <respStmt>

elements, at least one


                                             <sponsor>

element, and at least one


                                             <funder>

element.

You will give your edition an authority title in the


                                             <title>

element. Give the


                                             <title>

element a


                                          @type

value of main. This is the title that will appear at the top of your edition page and on the front cover and half-title page of the printed edition of your play. You will want to think carefully about the title of your edition. Should it be Othello, the Moor of Venice, Othello, or The Tragedy of Othello? Each title constitutes a different critical statement about your edition. You will want to confer with your anthology lead as you finalize your edition title.

You will give credit to each person or group who worked on your edition in the


                                             <respStmt>

elements of your edition page. This includes research assistants, encoders, anthology leads, and peer reviewers (if your edition has undergone open peer review). All LEMDO edition pages are required to provide responsibility statements for at least the following five roles:

Editor

Anthology lead(s)

The LEMDO team (either for their work converting and remediating the edition, or for their encoding work)

Additionally, anyone who has contributed to, overseen, reviewed, or supervised your edition who has not been credited in any specific files must be given credit in the edition page. Those who have been credited in specific files also may be given credit again in the edition page. Your anthology leads can give you guidance for adding any additional responsibility statements. For more information on encoding the


                                             <respStmt>

element, see Encode Responsibility Statements.

For information on how to encode the


                                             <sponsor>

and


                                             <funder>

elements, see Encode Sponsors and Funders in Your Metadata.

Example Title Statement

<titleStmt>
 <title type="main">Authority Title</title>
 <respStmt>
 <resp ref="resp:edt">Editor</resp>
 <persName ref="pers:PEEE1">Your Name</persName>
 </respStmt>
 <respStmt>
 <resp ref="resp:edt_coord">Co-Coordinating Editor</resp>
 <persName ref="pers:PEEE1">Anthology Lead Name</persName>
 </respStmt>
 <respStmt>
 <resp ref="resp:cph">Copyright Holder (Editorial content)</resp>
 <persName ref="pers:PEEE1">Your 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>
 <sponsor ref="org:OOOO1"/>
 <funder>
 <ref target="https://www.sshrc-crsh.gc.ca/">Social Sciences and Humanities Research Council of Canada</ref>
 </funder>
</titleStmt>

Practice: Encode the Edition Statement

You will use the


                                             <editionStmt>

element to specify in which version of an anthology your edition was first published. For instructions on how to encode your edition page’s


                                             <editionStmt>

, see Practice: Write the Edition Statement.

Practice: Encode the Publication Statement

You will license your edition for publication in an anthology using the


                                             <publicationStmt>

element. For detailed instructions on how to encode your edition page’s


                                             <publicationStmt>

, see License Your Edition for Publication.

Practice: Encode the Notes Statement

You will include all completed¹ components of your edition in the


                                             <notesStmt>

element. The


                                             <notesStmt>

element contains a child


                                             <relatedItem>

element for each XML file that you wish to publish with your edition, including all of your apparatus files, critical paratexts, main texts, and supplementary texts (if any). If you have created video landing pages, each one must be listed, which may make your list of related items quite long. (Note that images and videos are not XML files; you do not need to list such media in the


                                             <notesStmt>

To encode your


                                             <notesStmt>

Add a


                                                   <relatedItem>

element for each XML file that you want to publish.

Add a


                                                @target

attribute on the


                                                   <relatedItem>

element.

Give the


                                                @target

attribute a value of doc: followed by the filename of the XML file that you wish to include.

For example:

If you list a file in the edition table of contents in the


                                             <text>

element of your edition page and do not also include it in the


                                             <notesStmt>

, you will get an error message reminding you that you must have a


                                             <relatedItem>

element for the file. Although every file mentioned in the


                                             <text>

must have a corresponding


                                             <relatedItem>

element, the converse is not true. You may have many more files in your


                                             <notesStmt>

than you choose to list in your table of contents. You might choose not to list a page in your edition table of contents if you want people to access it by clicking a link on another page (e.g., a list of resources that you want your user to access via a Resources landing page.

Note that if you are publishing your edition in stages (e.g., you are publishing a first version of your edition that includes only the semi-diplomatic transcription, modernized text, collation, and textual notes), you must not list in your


                                             <notesStmt>

files that you do not intend to publish .

Special Case: Include Generated Pages

Remember to include pages that are generated by a processing instruction in an otherwise empty file. Such files include the standalone character list (generated by a roleList instruction) and the standalone manuscript description (generated by a msDesc instruction). These generated pages are usually made by the LEMDO team for you, at your request. The onus is on you and your anthology lead to make sure that such pages are listed in your edition page


                                                <notesStmt>

and listed in your curated table of contents.

For information about LEMDO’s processing instructions, see Inline Processing Instructions in LEMDO.

Practice: Encode the Source Description

The


                                             <sourceDesc>

element has a child

<p>

element. Use this element to describe the source of the XML file for the edition landing page (i.e., the file described in this present document). For an edition landing page created by the LEMDO team on behalf of an editor, the


                                             <sourceDesc>

is as follows:

<sourceDesc>
Edition landing page created by the <orgName ref="org:LEMD1">LEMDO Team</orgName> and curated by <persName ref="pers:PEEE1">[Editor Name]</persName>

</sourceDesc>

The Encoding Description

The


                                          <encodingDesc>

element provides information about how you have encoded and edited your edition. All


                                          <encodingDesc>

elements have a child

<p>

element (which gives information about the encoding guidelines that govern the file, normally the LEMDO Customization and Encoding Guidelines) and a child


                                          <editorialDecl>

element (which, in turn, has a child

<p>

element describing the editorial guidelines that govern the editorial work). For information on how to encode and write your encoding description, see Encode the Encoding Description in Your Metadata. Note that your anthology will provide you with the required format for the text in your edition page’s editorial declaration.

Edition pages’ encoding descriptions also have an additional element not used elsewhere: the project description.

Practice: Encode the Project Description

The child

<p>

element of


                                             <projectDesc>

is an opportunity for the editor to describe the editorial project in narrative form. Anthology leads may prescribe particular wording if they wish. Project descriptions are especially useful for capturing division of labour.

Some examples are:

<projectDesc>
This edition was prepared by <persName ref="pers:MART1">Mathew Martin</persName> and <persName ref="pers:COCK1">Peter Cockett</persName> for the Queen’s Men Editions anthology on the LEMDO platform
</projectDesc>

<projectDesc>
This edition was prepared by <persName ref="pers:SLIG1">Jessica Slights</persName> for the Internet Shakespeare Editions and Broadview Press. It has been remediated by the <orgName ref="org:LEMD1">LEMDO Team</orgName> for republication in the New Internet Shakespeare Editions on the LEMDO platform.
</projectDesc>

<projectDesc>
This edition was prepared by <persName ref="pers:HOWA1">Ashley Howard</persName> for the LEMDO platform.
</projectDesc>

<projectDesc>
This edition of <title level="m">The Merchant of Venice</title> was newly prepared by <persName ref="pers:JENS1">Janelle Jenstad</persName> and <persName ref="pers:WITT1">Stephen Wittek</persName> for the New Internet Shakespeare Editions on the LEMDO platform. Jenstad transcribed and encoded the semi-diplomatic transcriptions. Wittek wrote the critical introductions. The editors prepared the modernized text and collations together.
</projectDesc>

Note that there is terminal punctuation in the


                                             <projectDesc>

The Revision Description

You will track changes in your file using the


                                          <revisionDesc>

element. See Encode the Revision Description for information about how to encode the


                                          <revisionDesc>

Practice: Encode the Content of Your Edition Page

The content of your edition page (everything in the


                                          <body>

element) appears on your edition landing page. It is designed to be maximally flexible so that anthologies have the power to organize their own edition landing pages. The content and order of the


                                          <byline>

elements are entirely at the discretion of the anthology leads. Anthologies are in control of the headers and the order of edition components (using the


                                          <list>


                                          <head>

, and


                                          <item>

elements). You may also add an image anywhere in this section of the file.

Because each anthology has a different format for the content of its edition pages, we cannot include a single example here. We do, however, have templates in our lemdo/data/templates folder for each anthology’s edition pages. You may look at these templates to see sample formats.

Notes

1.This same mechanism allows you to exclude unfinished items, if you and your anthology lead agree to release your edition in stages.↑

Prosopography

Ashley Howard

Ashley Howard took her MA in Medieval and Early Modern Studies at the University of Victoria (2017–2020). During that time, she was a Remediating Editor for LEMDO. For her MA thesis, she prepared the first born-LEMDO edition, a critical edition of Ralph Knevet’s Rhodon and Iris.

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.

Jessica Slights

Jessica Slights is Professor of English in the Department of English & Theatre at Acadia University in Nova Scotia. She writes about and lectures on various aspects of early modern literature and culture, and her work has appeared in Early Modern Literary Studies, English Studies in Canada, Studies in Philology, and Studies in English Literature. She is co-editor, with Paul Yachnin, of Shakespeare and Character: Theory, History, Performance, and Theatrical Persons (Palgrave 2009). Her print edition of Shakespeare’s Othello is available from Broadview Press.

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.

Mathew Martin

Dr. Mathew R. Martin is Full Professor at Brock University, Canada. He is the author of Between Theatre and Philosophy (2001), Tragedy and Trauma in the Plays of Christopher Marlowe (2015) and Psychoanalysis and Literary Theory (2023), and co-editor, with his colleague James Allard, of Staging Pain, 1500–1800: Violence and Trauma in British Theatre (2009). For Broadview Press he has edited Christopher Marlowe’s Edward the Second (2010), Jew of Malta (2012), Doctor Faustus: The B-Text (2013) and Tamburlaine the Great Part One and Part Two (2014), and Robert Greene’s Selimus (2022). For Revels Editions he has edited George Peele’s David and Bathsheba (2018) and Marlowe’s The Massacre at Paris (2021). For Queen’s Men Editions he has edited The Famous Victories of Henry V (2016). He has published two articles of textual criticism on the printed texts of Marlowe’s plays: Inferior Readings: The Transmigration of Material in Tamburlaine the Great (Early Theatre 17.2 [December 2014]), and (on the political inflections of the shifts in punctuation in the early editions of the play) Accidents Happen: Roger Barnes’s 1612 Edition of Marlowe’s Edward the Second (Early Theatre 16.1 [June 2013]). His latest editing projects are a double-play Revels edition of Robert Greene’s Friar Bacon and Friar Bungay and John of Bordeaux and a Digital Renaissance Editions edition of Dido, Queen of Carthage.

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.

Peter Cockett

Peter Cockett is an associate professor in the Theatre and Film Studies at McMaster University. He is the general editor (performance), and technical co-ordinating editor of Queen’s Men Editions. He was the stage director for the Shakespeare and the Queen’s Men project (SQM), directing King Leir, The Famous Victories of Henry V, and Friar Bacon and Friar Bungay (2006) and he is the performance editor for our editions of those plays. The process behind those productions is documented in depth on his website Performing the Queen’s Men. Also featured on this site are his PAR productions of Clyomon and Clamydes (2009) and Three Ladies of London (2014). For the PLS, the University of Toronto’s Medieval and Renaissance Players, he has directed the Digby Mary Magdalene (2003) and the double bill of George Peele’s The Old Wives Tale and the Chester Antichrist (2004). He also directed An Experiment in Elizabethan Comedy (2005) for the SQM project and Inside Out: The Persistence of Allegory (2008) in collaboration with Alan Dessen. Peter is a professional actor and director with numerous stage and screen credits. He can be contacted at cockett@mcmaster.ca.

PLACEHOLDER PERSON

Sofia Spiteri

Sofia Spiteri is currently completing her Bachelor of Arts in History at the University of Victoria. During the summer of 2023, she had the opportunity to work with LEMDO as a recipient of the Valerie Kuehne Undergraduate Research Award (VKURA). Her work with LEMDO primarily includes semi-diplomatic transcriptions for The Winter’s Tale and Mucedorus.

Stephen Wittek

Stephen Wittek is Assistant Professor of Literature at Carnegie Mellon University and co-editor with Janelle Jenstad for the ISE edition of The Merchant of Venice. He is the author of The Media Players: Shakespeare, Middleton, Jonson, and the Idea of News (University of Michigan Press, 2015), and has also written for journals including Studies in English Literature, Digital Humanities Quarterly, and Journal of Cognitive History. In 2014, the CBC Radio One program Ideas produced an hour-long episode showcasing Dr. Wittek’s research on the co-evolution of English theatre and news culture (available for streaming or download).

Dr. Wittek holds a PhD in literature from McGill University and a Master’s degree in Shakespeare Studies from the Shakespeare Institute in Stratford-Upon-Avon, England. From 2013 to 2017, he was a Postdoctoral Fellow for McGill’s Early Modern Conversions project, a five-year research endeavor that brought together an interdisciplinary team of humanities scholars to study the multiform proliferation of conversion and conversional representation in early modernity (see http://www.earlymodernconversions.com). His continuing work for the project includes the essay collection Performing Conversion: Urbanism, Theatre, and the Transformation of the Early Modern World, which he is co-editing with José R. Jouve-Martin for the Early Modern Conversions book series (University of Edinburgh Press).

On the digital humanities front, Dr. Wittek is co-developer with Stéfan Sinclair and Matthew Milner for DREaM (Distant Reading Early Modernity), a database that will index 44,000+ early modern texts, thus making long-neglected material more amenable for use with tools for large-scale textual analysis.

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.

PLACEHOLDER ORGANIZATION (OOOO1)

The purpose of this item is to allow encoders to link to an organization when they cannot add a new one to the ORGS1 file for some reason. When linking to this item, please include a comment explaining the details of the item the link should really point to.

University of Victoria (UVIC1)

https://www.uvic.ca/

Glossary

empty element

“Empty elements are also called milestone or self-closing elements, but LEMDO uses the term empty element. Empty elements do not have child text or element nodes.”

Metadata

Authority title	Chapter 19. Editions and Licensing
Type of text	Documentation
Publisher	Linked Early Modern Drama
Series
Source
Editorial declaration
Edition
Encoding description
Document status	prgGenerated
License/availability

Chapter 19. Editions and Licensing

Introduction to Editions and Licensing

Learning Outcomes

LEMDO Editions

Contents

The Handshake Model of Inclusion

Prior Reading

Introduction to the Handshake Model

Multi-Anthology Publication

Further Reading

License Your Edition for Publication

Prior Reading

Rationale

Practice: Include Files in Your Edition

Practice: License Your Edition for Inclusion in an Anthology

Anthology Identifiers for Licensing

Inclusion in an Anthology

Other Resources

Further Reading

Edition Directories

Rationale

Edition Directory Structure

Special Case: Images Folders

Special Case: Paratexts

Special Case: Performance As Research Folders

Further Reading

Encode File Categories for Edition Files

Prior Reading

Rationale

Practice: Encode the Profile Description

Examples

Further Reading

Encode Your Edition Page

Prior Reading

Rationale

Practice: Create an Edition Page

Components of Metadata

The File Description

Practice: Encode the Title Statement

Example Title Statement

Practice: Encode the Edition Statement

Practice: Encode the Publication Statement

Practice: Encode the Notes Statement

Special Case: Include Generated Pages

Practice: Encode the Source Description

The Encoding Description

Practice: Encode the Project Description

The Revision Description

Practice: Encode the Content of Your Edition Page

Notes

Prosopography

Ashley Howard

Janelle Jenstad

Jessica Slights

Joey Takeda

Mahayla Galliford

Martin Holmes

Mathew Martin

Navarra Houldin

Peter Cockett

PLACEHOLDER PERSON

Sofia Spiteri

Stephen Wittek

Tracey El Hajj

Orgography

LEMDO Team (LEMD1)

PLACEHOLDER ORGANIZATION (OOOO1)

University of Victoria (UVIC1)

Glossary

Metadata