Understand MoEML’s Website and Document StructureLucas SimpsonAuthorTye LandelsAuthorJanelle JenstadAuthorKim McLean-FianderAuthorAuthorMartin HolmesCameron ButtAuthorTye LandelsEncoderJanelle JenstadEncoderMartin HolmesEncoderKim McLean-FianderEncoderCameron ButtCopy EditorSarah MilliganCopy EditorCameron ButtMarkup EditorData ManagerTye LandelsJunior ProgrammerJoey TakedaProgrammerMartin HolmesAssociate Project DirectorKim McLean-FianderProject DirectorJanelle JenstadThe Map of Early Modern Londonhttp://mapoflondon.uvic.ca/includes.xmlVictoria, BC, CanadaDepartment of EnglishP.O.Box 3070 STNC CSCUniversity of VictoriaVictoria, BCCanadaV8W 3W12016University of Victoria978-1-55058-519-3Janelle Jenstadlondon@uvic.ca
Copyright held by
The Map of Early Modern London on behalf of the contributors.
This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.
Further details of licences are available from our
Licences page. For more
information, contact the project director, Janelle Jenstad, for
specific information on the availability and licensing of content
found in files on this site.
Provider: University of Victoria
Database: The Map of Early Modern London
Content: text/plain; charset="utf-8"
TY - ELEC
A1 - Simpson, Lucas
A1 - Landels-Gruenewald, Tye
A1 - Jenstad, Janelle
A1 - McLean-Fiander, Kim
A1 - Holmes, Martin
A1 - Butt, Cameron
ED - Jenstad, Janelle
T1 - Understand MoEML’s Website and Document Structure
T2 - The Map of Early Modern London
ET - 7.0
PY - 2022
DA - 2022/05/05
CY - Victoria
PB - University of Victoria
LA - English
UR - https://mapoflondon.uvic.ca/edition/7.0/website_structure.htm
UR - https://mapoflondon.uvic.ca/edition/7.0/xml/standalone/website_structure.xml
ER - Simpson, Lucas, TyeLandels-Gruenewald, JanelleJenstad, KimMcLean-Fiander, MartinD.Holmes, and CameronButt. Understand MoEML’s Website and Document Structure. The Map of Early Modern London, Edition 7.0, edited by JanelleJenstad, U of Victoria, 05 May 2022, mapoflondon.uvic.ca/edition/7.0/website_structure.htm.Simpson, Lucas, TyeLandels-Gruenewald, JanelleJenstad, KimMcLean-Fiander, MartinD.Holmes, and CameronButt. Understand MoEML’s Website and Document Structure. The Map of Early Modern London, Edition 7.0. Ed. JanelleJenstad. Victoria: University of Victoria. Accessed May 05, 2022. mapoflondon.uvic.ca/edition/7.0/website_structure.htm.Simpson, L., Landels-Gruenewald, T., Jenstad, J., McLean-Fiander, K., Holmes, M.D., & Butt, C.2022. Understand MoEML’s Website and Document Structure. In J.Jenstad (Ed), The Map of Early Modern London (Edition 7.0). Victoria: University of Victoria. Retrieved from https://mapoflondon.uvic.ca/editions/7.0/website_structure.htm.Born digital.Jenstad, Janelle. Building a Gazetteer for Early Modern London, 1550-1650. Placing Names. Ed. Merrick Lex Berman, Ruth
Mostern, and Humphrey Southall. Bloomington and
Indianapolis: Indiana UP, 2016. 129-145. Primary or Secondary Sources. U of Victoria
Libraries. U of Victoria. https://www.uvic.ca/library/research/tips/primvsec/index.php.London
The city of London, not to be confused with the allegorical character (London).
(LOND5.xml)
The Julian calendar, in use in the British Empire until September 1752. This calendar is used for
dates where the date of the beginning of the year is ambigious.
The Julian calendar with the calendar year regularized to beginning on 1 January.
The Julian calendar with the calendar year beginning on 25 March. This was the
calendar used in the British Empire until September 1752.
The Gregorian calendar, used in the British Empire from September 1752. Sometimes
referred to as New Style (NS). Years run from January 1 through December 31.
The Anno Mundi (year of the world) calendar is based on the supposed date of the
creation of the world, which is calculated from Biblical sources. At least two different
creation dates are in common use. See Anno Mundi (Wikipedia).
Regnal dates are given as the number of years into the reign of a particular monarch.
Our practice is to tag such dates with calendar=regnal, and provide an
equivalent date using a more systematic calendar (usually Julian) in a custom dating
attribute.
Lucas SimpsonLucasSimpson
LS
Research Assistant, 2018-2021. Lucas Simpson was a student at the University of
Victoria.
Joey TakedaJoeyTakeda
JT
Programmer, 2018-present. Junior Programmer, 2015-2017. Research Assistant, 2014-2017.
Joey Takeda was a graduate student at the University of British Columbia in the Department
of English (Science and Technology research stream). He completed his BA honours in English
(with a minor in Women’s Studies) at the University of Victoria in 2016. His primary
research interests included diasporic and indigenous Canadian and American literature,
critical theory, cultural studies, and the digital humanities.
Tye Landels-GruenewaldTyeLandels-Gruenewald
TLG
Data Manager, 2015-2016. Research Assistant, 2013-2015. Tye completed his undergraduate
honours degree in English at the University of Victoria in 2015.
Cameron ButtCameronButt
CB
Research Assistant, 2012–2013. Cameron Butt completed his undergraduate honours degree in
English at the University of Victoria in 2013. He minored in French and has a keen interest
in Shakespeare, film, media studies, popular culture, and the geohumanities.
Sarah MilliganSarahMilligan
SM
Research Assistant, 2012-2014. MoEML Research Affiliate. Sarah Milligan completed her MA
at the University of Victoria in 2012 on the invalid persona in Elizabeth Barrett Browning’s
Sonnets from the Portuguese. She has also worked with the Internet Shakespeare
Editions and with Dr.
Alison Chapman on the Victorian Poetry Network, compiling an index of Victorian periodical
poetry.
Kim McLean-FianderKimMcLean-Fiander
KMF
Director of Pedagogy and Outreach, 2015–2020. Associate Project Director, 2015.
Assistant Project Director, 2013-2014. MoEML Research Fellow, 2013. Kim McLean-Fiander comes
to
The Map of Early Modern London from the Cultures of Knowledge
digital humanities project at the University of
Oxford, where she was the editor of Early Modern Letters Online, an open-access union
catalogue and editorial interface for correspondence from the sixteenth to eighteenth
centuries. She is currently Co-Director of a sister project to EMLO called Women’s Early Modern Letters Online (WEMLO). In the past, she held an internship with the
curator of manuscripts at the Folger Shakespeare
Library, completed a doctorate at Oxford on
paratext and early modern women writers, and worked a number of years for the Bodleian Libraries and as a freelance editor.
She has a passion for rare books and manuscripts as social and material artifacts, and is
interested in the development of digital resources that will improve access to these
materials while ensuring their ongoing preservation and conservation. An avid traveler, Kim
has always loved both London and maps, and so is particularly delighted to be able to bring
her early modern scholarly expertise to bear on the MoEML project.
Janelle JenstadJanelleJenstad
JJ
Janelle Jenstad is Associate Professor of English at the University of Victoria, Director
of
The Map of Early Modern London, and PI of Linked Early Modern Drama Online. She has taught at Queen’s University, the Summer
Academy at the Stratford Festival, the University of Windsor, and the University of
Victoria. With Jennifer Roberts-Smith and Mark Kaethler, she co-edited Shakespeare’s Language in Digital Media (Routledge). She has prepared a documentary edition of 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, Renaissance and
Reformation,Journal of Medieval and Early Modern Studies,
Early Modern Literary Studies, Elizabethan
Theatre, Shakespeare Bulletin: A Journal of Performance
Criticism, and The Silver Society Journal. Her book
chapters have appeared (or will appear) in Institutional Culture in Early
Modern Society (Brill, 2004), Shakespeare, Language and the Stage,
The Fifth Wall: Approaches to Shakespeare from Criticism, Performance and Theatre
Studies (Arden/Thomson Learning, 2005), Approaches to Teaching
Othello (Modern Language Association, 2005), Performing Maternity
in Early Modern England (Ashgate, 2007), New Directions in the
Geohumanities: Art, Text, and History at the Edge of Place (Routledge, 2011), Early
Modern Studies and the Digital Turn (Iter, 2016), Teaching Early Modern
English Literature from the Archives (MLA, 2015), Placing Names:
Enriching and Integrating Gazetteers (Indiana, 2016), Making
Things and Drawing Boundaries (Minnesota, 2017), and Rethinking
Shakespeare’s Source Study: Audiences, Authors, and Digital Technologies
(Routledge, 2018).
Martin D. HolmesMartinD.Holmes
MDH
Programmer at the University of Victoria Humanities Computing and Media Centre (HCMC).
Martin ported the MOL project from its original PHP incarnation to a pure eXist database
implementation in the fall of 2011. Since then, he has been lead programmer on the project
and has also been responsible for maintaining the project schemas. He was a co-applicant on
MoEML’s 2012 SSHRC Insight Grant.
Parish Clerks’ Company
The Parish Clerks’ Company was a
company in early modern London. While it never
technically applied for livery status, it largely acted as a livery company. The
Parish Clerks’ Company is still active and
maintains a website at http://www.londonparishclerks.com/ that includes a history of the
company.
Most MoEML documents, or significant fragments with xml:id attributes, can
be addressed using the mol: prefix and accessed through the web application
with their id + .xml.
The molagas prefix points to the shape representation of a location on
MoEML’s OpenLayers3-based
rendering of the Agas Map.
Links to page-images in the Chadwyck-Healey
Early English Books Online (EEBO)
repository. Note that this is a subscription service, and may not be accessible to those
accessing it from locations outside member institutions.
Links to page-images in the
English Broadside Ballad Archive (EBBA).
The mdt (MoEML Document Type) prefix used on catRef/target points
to a central taxonomy in the includes file.
The mdtlist (MoEML Document Type listing) prefix used in linking attributes points to a listings page constructed from a category in the central MDT taxonomy in the includes file. There are two variants, one with the plain xml:id of the category, meaning all documents in the specified category, and one with the suffix _subcategories, meaning all subcategories of the category.
The molgls (MoEML gloss) prefix used on term/corresp points
to a a glossary entry in the GLOSS1.xml file.
This molvariant prefix is used on ref/target attributes during automated
generation of gazetteer index files. It points to an element in the generated variant spellings
listing file which lists all documents which contain a particular spelling variant for a
location.
This molajax prefix is used on ref/target attributes during the static build
process, to specify links which point to MoEML resources which should not be loaded into the source
page during standalone processing; instead, these should be turned into links to the XML source
documents, and at HTML page load time, these should be turned into AJAX calls. This is to handle
the scenario in which a page such as an A-Z index of the whole site would end up containing
virtually the whole site inside itself.
The molstow prefix is used on facs attributes to link to the HCMC verison of the Stow facsimiles.
Usually the first group is the year (1633) and then last is the image number (0001).
The molshows prefix is used on facs attributes to link to the copies of page-images
from mayoral shows stored in the london account on the HCMC server.
The first group is the year (1633), the second is the source repository, and then last is the image
file name.
The sb prefix is used on ref/target attributes to link to
Stow’s Books URLs at UToronto.
Our editorial and encoding practices are documented in detail in the Praxis section of our website.
AuthorA person or
organization chiefly responsible for the intellectual or artistic content of a work, usually
printed text. This term may also be used when more than one person or body bears such
responsibility. MoEML uses the term author to designate a
contributor who is wholly or partly responsible for the original content of either a
born-digital document, such as an encyclopedia entry, or a primary source document, such as
a MoEML Library text.Data managerA person or organization responsible for managing databases or
other data sources.MoEML uses the term data manager to designate
contributors who maintain and manage our databases. They add and update the data sent to us
by external contributors or found by MoEML team members. They also monitor journals and
sources regularly to ensure that our databases are current.Markup editorA person or organization performing the coding of SGML, HTML, or
XML markup of metadata, text, etc.MoEML uses the code mrk both for the primary
encoder(s) and for the person who edits the encoding. MoEML’s normal workflow includes a
step whereby encoders check each other’s work. We use the term
encoder to designate the principal encoder, and markup
editor to designate the person who checks the encoding.Project directorA person or organization with primary responsibility for all
essential aspects of a project, or that manages a very large project that demands senior
level responsibility, or that has overall responsibility for managing projects, or provides
overall direction to a project manager.MoEML’s Project Director directs the intellectual and scholarly aspects of
the project, consults with the Advisory and Editorial Boards, and ensures the ongoing
funding of the project.ProgrammerA person or organization responsible for the creation and/or
maintenance of computer program design documents, source code, and machine-executable
digital files and supporting documentation.MoEML uses the term programmer to designate a person
or organization responsible for the creation and/or maintenance of computer program design
documents, source code, and machine-executable digital files and supporting
documentation.Research team headA person who directed or managed a research project.MoEML uses the terms research term head and
assistant project manager interchangeably.Copy editorMoEML uses the term copy editor to designate the
person who brings the document into conformity with MoEML stylistic and citational practice.
Acceptable names for this role are copy editor, principal copy editor, secondary copy
editor, or copy editor of a particular section of text.Removed info/links for CodeSharing, not supported from version 6.4 onwards.Commented out instructions for encoding an entry in PERS1.xml. These instructions have been superceded by the more detailed instructions in encode_person.xml/Standardized respStmts for JENS1, MCFI1,
and HOLM3 and added TAKE1 as Junior Programmer.Added index terms.Corrected documentation on modern contributors in
PERS1.Updated documentation on facsimile elements
in location documents.Corrected documentation on encoding
sex.Added XInclude for listPrefixDef in the
header.Rewrote and updated content on location document
structure.Imported and edited content on encoding reference
entries in BIBL1.xml (now located in website_structure_biblio).Added section on LINKS1.xml database
document.Added xml:ids for div elements in
"PERS1.xml" section.Revised documentation re: adding contribuotrs to
PERS1.xml.Added global publicationStmt through
XInclude.Updated section ORGS1.xml database structure to
include info for adding modern organizations.Added section on ORGS1.xml database
structure.Added @xml:ids to div elements.Put change elements inside
revisionDesc into the correct (latest first) order.Added profileDesc containing document type
information expressed in catRef elements.Added section for revision descriptions.Converted @rend to @style, through XSLT
transformation. Created file and added content from
xml_encoding.Understand MoEML’s Website and Document
Structure
This manual provides instructions for encoders, editors, and contributors working on
MoEML’s XML documents. It includes information about the
website structure and document types. Please do not hesitate to contact the MoEML team for additional
assistance.
Because MoEML’s practices are always being updated, please refer
back to this manual frequently.
Beginning with version 6, MoEML’s publication process moved
to a static build model. What this means is that all of the encoded
documents, which are kept in the Subversion repository, are processed into HTML documents
that all sit together in the same folder. Subfolders contain various other resources
such as images, JavaScript and CSS files, and the various XML versions of our files
that we provide for others to download and use.
When the build runs (either locally if you run it on your own machine, or more
commonly when our Jenkins Continuous Integration server runs it automatically),
a folder called site is created inside the static folder.
site contains, as you might expect, the entire MoEML website.
It is fully functional; you can open any of its pages in a web browser and it will work. This fully-functional site is the development version
we access and use every day from the Jenkins server. Beginning with version 6.4, this static version now includes a static search engine built using the Project EndingsstaticSearch codebase developed by Martin Holmes and Joey Takeda, so we have no further need for the eXist XML database which was previously used to power the search.
When we are ready to publish a new version, we simply set the new version number in the VERSION file (in the root folder of the repository), let Jenkins do run its build process, and after final checks, we archive the old version of the site and push the new content up to the HCMC web server.
MoEML’s document collection (i.e. the data folder in
the Subversion repository) consists of several types of
documents. With the exception of files that are
themselves database-like (such as the personography, PERS1.xml, or the bibliography,
BIBL1.xml), these documents fall into two main categories: born-digital
documents and transcriptions of primary sources. These different types of scholarly
endeavour have different encoding needs.
In the case of born-digital documents, we are creating the resource for the first time;
that means we are generating both the content and the representational features as a
single creative act, and we encode following our project style guide with the intention that the rendered result conforms with the rest of
the born-digital content on our site. In this sense, we tend to encode with one eye on the
rendered result.
The case of primary-source transcriptions is very different. We strive to represent the
original source document as faithfully as possible. In other words, we classify different
components of the document (front matter, body, back matter, title page, chapter, etc.)
and describe how things appear (small-caps, italic, centre-aligned, and so on). The
overriding concern here is to tell the truth. We transcribe the source text,
tag it to represent its structure and components, and describe how it appears using CSS
properties and values in the style attribute.
All of MoEML’s data is in TEI P5 XML document form. This
structure is made public through the See XML link in the sidebar on
every page. These documents should all validate against a standard P5 schema, and they
fall into three distinct categories: simple documents, location documents, and complex
(multi-text) documents. Each of these document types has a template that editors can use.
These files are saved in the subversion repository
under templates.
Most of the XML files in the MoEML database, whether they are
born-digital contributions or primary sources that we have transcribed, share a common
file structure. They consist of a teiHeader and a single text element.
The basic structure of a simple document looks something like this:
About MoEMLCameron ButtEncoderJanelle JenstadProject Director
[Information about the source document, if applicable]
Our editorial and encoding practices are documented in detail in the Praxis section of our website.
Added global publicationStmt through
XInclude.About MoEML
Topic the first
[Paragraph content]
[Paragraph content]
Some points to note:
The xml:id attribute on the root TEI element should be the
same as the name of the file, but without its extension (.xml). So when the file is
called about.xml, the xml:id attribute should be
about.Some of the content in the header is pulled in to the file
automatically through the use of XInclude. This enables us to maintain a single central copy of blocks of
content which are going to be the same for many different files. Every document is characterized by several catRef elements which refer to
categories in our document type taxonomy.There is only one text element.The title of the document (which will appear at the head of the page in the
rendered web output) is contained in a titlePart element inside
front/docTitle.The main content is contained in one or more div element(s), containing
heads.
Tags and attributes used to mark up the content itself are covered in more detail
below.
Some simple documents will have subsections and even sub-subsections. This is achieved
by using nested div elements. Nesting can be as deep as required, but should be
kept as simple as possible. For instance, this is a page which has an introduction and
two subsections:
Location documents are similar to simple documents insofar as they contain only one
text element and usually have a straightforward structure. The two defining aspects of
location documents are the facsimile element, which specifies the location’s
position on the Agas map, and the div element with a type value of
placeInfo, which contains the location’s geo-coordinates. ABCH1.xml
exemplifies is the basic outline of a location document:
Abchurch Lane runs north-south from Lombard Street to Candlewick (Cannon) Street. The Agas Map labels it Abchurche lane. It lies mainly in Candlewick Street Ward, but part of it serves as
the boundary between Langbourne Ward and Candlewick Street Ward.
Abchurch Lane
Abchurch Lane
Abchurch Lane51.5123897,-0.0875297
Abchurch Lane runs north-south from Lombard Street to Candlewick (Cannon)
Street.
The abstract Element
encoding instructionsborn-digital documentsdocument structurelocation documentslocationsmapabstracts
Use the abstract element to tag a 150 word abstract that provides a
summative and interesting overview of the location. Preferably, the abstract should be
equal to (or at least a portion of) the first paragraph. This description appears in
the pop-up generated when users click on the hyperlinked name of the location in a
library and encyclopedia document. As noted in the example above, the
abstract element is nested within the profileDesc element in the
teiHeader. Note that the description itself should be tagged with a
p element within the abstract element.
The title element determines the authority name of the location, the name that we determine to be most commonly used in London around
1598-1603.
From all the place’s name variants, the authority name is the definitive name by which we refer to the place.
Often the authority name is the one used by the institution occupying the place itself, if such a self-referential document is available.
For example, the Bills of Mortality serve as a good source of authority names for parish churches
because the Parish Clerks’ Company compiles the bill, which is full of place names of churches and
parishes (Jenstad 138).
The facsimile Element
encoding instructionsborn-digital documentsdocument structurelocation documentslocationsmapfacsimilesagas mapgeocoding locations
The facsimile element specifies that there is one surface
(surface) on which this location is depicted. In all location documents, the
graphic for that surface is agas_full.jpg, our facsimile of the Agas map; we encode
this graphic using a simple TEI graphic tag with a url attribute.
On that graphic, the location is depicted as a series of pixel points, which,
together, constitute a zone (zone) of the graphic. Each pixel point consists
of an x and y coordinate separated by a comma without a space. A space ( ) separates
each pair of coordinates. We assign the zone element an xml:id
value, which enables us to point to it later in the file. The xml:id value,
ABCH1_agas in the example above, is constructed from the
xml:id of the location document, an underscore, and agas.
For more information about the facsimile element, see documentation on adding MoEML locations to the
Agas map.
Note that some older location documents may include an additional surface
element nested within the facsimile element. The contents of this additional
surface element point to the location’s position on MoEML’s former, now-deprecated version of the Agas map, which was divided
into tiles. This content may be removed in the future, but should be ignored for the
time being.
Note also that, sometimes, a place will be located outside of the area depicted in
the Agas map. In such instances, omit the graphic element and encode only
a self-closing zone element without an xml:id. For example,
The div type="placeInfo" Element
encoding instructionsborn-digital documentsdocument structurelocation documentslocationsmap
The div type="placeInfo" element nests a
head element, which designates the location page’s title, and the
listPlace element, which contains geographical information about the
location. In the example above, listPlace contains only one place
element, but in some cases there will be several. For example, if the same street
appears on multiple map tiles, it may be split into separate sections. In such cases,
different sections may require different names, so each place has contains a
placeName element. place elements must also have a
corresp value that points to the zone element nested inside the
facsimile element, thereby specifying that the place element is
located at the position specified by the corresponding zone element. The
value of the corresp attribute should be the xml:id of the
corresponding zone element.
For information about encoding geo-coordinates inside the place element
using the location and geo elements, see documentation on geocoding locations.
Some special files—the bibliography (BIBL1.xml), the personography
(PERS1.xml), the glossary of terms (GLOSS1.xml), the
orgography (ORGS1.xml), and the linksography (LINKS.xml)—are
centralized databases, containing information related to bibliographical
material, events, terms, organizations, and people that are mentioned on the site.
BIBL1.xml is a works cited and consulted
list for MoEML. Each individual bibl entry corresponds
to a source referenced in our document structure. The content of a
bibl tag should reflect MoEML’s standards for
citation, which are outlined
fully in the MoEML Guide to Editorial
Style. Each bibl element should be assigned a
unique xml:id and a type value of prim, sec,
or both: Entries for primary sources should have a
type value of prim. Primary sources are materials that
provide first-hand information or original data on a topic
(Primary or Secondary Sources). The Agas map and Thomas Dekker’s The
Shoemaker’s Holiday are both primary sources in BIBL1.xml.Entries that are secondary sources should have a
type value of sec. Secondary sources are works that are
one step removed from the original source, usually describing, summarizing,
analyzing, evaluating, derived from, or based on primary source materials
(Primary or Secondary Sources). David
Bevington’s Tudor Drama and Politics and Janelle Jenstad’s
The City Cannot Hold You: Social Conversion in the
Goldsmith’s Shop are both secondary sources in BIBL1.xml.Entries that function both as primary sources and secondary sources should have
a type value of both. For example, John Stow’s Survey of London uses both unmediated, primary source
methodologies and mediated, secondary source methodologies; we therefore assign this
source a type value of both.
Inside the bibl tag, the following citation components, when present, should
be tagged as follows:
Component Relevant Tag Example Author’s name Tag each author’s name with the author
tag. Barber, Bruno and Christopher Thomas Title of an article in a periodical Tag the title of an article with the
title tag with a level value of a. Middleton’s Civic Employments Title of a chapter in a monograph Tag the title of a chapter with the
title tag with a level value of a. The Significance of the Metropolis Title of a webpage Tag the title of a webpage with the
title tag with a level value of a. Catalogue Title of a periodical Tag the title of a periodical with the
title tag with a level value of j. Early Theatre Title of a monograph Tag the title of a monogrpah with the
title tag with a level value of m. Literature and Architecture in Early Modern England Title of a website Tag the title of a website with the
title tag with a level value of m. Shakespearean London Theatres Editor, translator, or compiler’s name Tag each editor, translator, or compiler’s name with the
editor tag. Ed. Ian Gadd and Alexandra GillespieTrans. David GerardIdentification NumbersTag identification codes such as, DOI, STC, and ESTC numbers with the
idno tag with a type attribute whose value corresponds to the identifier type.
doi:10.1111/j.1475-6757.2000.tb01171.x.
or
STC 25264.
Stable URLsTag stable URLs with the
ref element with a target attribute whose value is the URL itself.https://www.museumoflondon.org.uk/collections/other-collection-databases-and-libraries/museum-london-archaeological-archive.
DatesTag dates with the
date element. See documentation on
encoding dates.1912
or 1583
At this moment, all other components of a citation do not need to be tagged. In the
long term, MoEML plans to elaborate the markup of
bibliographical entries so that dates, publishers, and publication places will also be
tagged.
The following table oultines how to structure BIBL1.xml entries for common source
types.
Source TypeTemplateExample CodePrinted monographAuthor Surname, Author Forename. Title of
Monograph. Place of Publication: Publisher, Year of Publication.
Medium designation (Print).Bevington, David. Tudor Drama and Politics: A Critical Approach to Topical Meaning. Cambridge: Harvard UP, 1968. Print.Article or chapter in a printed volumeAuthor Surname, Author Forename. Title of Article/Chapter. Title of Volume. Ed. Editor Forename Editor Surename Place of Publication: Publisher, Year of Publication. Page range of article/chapter. Medium designation (Print).Adelman, Janet. Making Defect Perfection: Shakespeare and the One-Sex Model. Enacting Gender on the English Renaissance Stage. Ed. Viviana Comensoli and Anne Russell. Chicago: U of Illinois P, 1999. 23–52. Print.Entire websiteTitle of Website.
Website Sponsor or Publisher (if available and different from website title). Homepage URL.London Book Trades Database. Oxford Bibliographical Society. http://lbt.bodleian.ox.ac.uk/mediawiki/index.php/Main_Page.Page within a websiteAuthor Surname, Author Forename (if available). Title of
Page on Website. Title of Website.
Ed. Editor Forename Editor Surname (if available). Website Sponsor or Publisher (if available and different from website title). Page URL.Bevington, David. Henry IV, Part 1. Enyclopedia Britannica. https://www.britannica.com/EBchecked/topic/261756/Henry-IV-Part-1.Blaisdell, Theodore A. Mapping Significance: Geographical Musings on the Three hoe plays. Lehigh Preserve. Lehigh University. https://preserve.lehigh.edu/etd/488/.Journal article accessed onlineAuthor Surname, Author Forename. Title of
Article. Title of Periodical Volume.Issue
(YYYY): Page range of article. doi:doi_number (if available).Lilley, Keith D.Urban Planning After the Black Death: Townscape Transformation in Later Medieval England (1350–1530). Urban History 42.1 (2015): 22–42. doi:10.1017/S0963926814000492.
If there is no DOI, leave an XML comment.
Bland, Mark. The Appearance of the Text in Early Modern England. Text 11 (1998): 91–154.
More Information
encoding instructionsborn-digital documentsdatabasesdocument structureographiesBIBL1.xmlbibliographyreferencesprimary sourcessecondary sourcesfurther readingmore informationrelated resourcesdata entry
One thing to note is that BIBL1.xml entries must be added in alphabetical order based on their xml:ids. For more information about MoEML’s bibliogrpahy practices,
see documentation on styling works cited.
For information about how to encode in-text citations, see documentation on linking to reference material in
BIBL1.xml..
The file contains information about historical and literary persons, as well as modern
contributors. An individual entry looks like this:
William BaronsWilliamBaronsBishop of London
Bishop of London1504–1505.
ODNBWikipedia
For a thorough explanation of how to encode a personography entry, see Encode Persons.
Linking Names to the Personography
encoding instructionsborn-digital documentsdatabasesdocument structureographiesPERS1.xmlpersonographypersonspeoplelink to personsdata entry
For instructions on how to tag and link to personography entries within a document,
refer to MoEML’s instructions for linking to people in PERS1.xml.
The Glossary of Early Modern Terms database (GLOSS1.xml)
is arranged in much the same way as PERS1.xml and BIBL1.xml.
However, instead of listing the entries in a listPerson or listBibl, a
simple list element is used, with a type value of
glossary. Each term is then listed as an item with its
xml:id declared in an attribute. Each item contains a
term with its regularized spelling and a note element with a
p element containing a description of the term. For example, Term
Definition of term.
Term
Definition of term.
For instructions on how to tag and link to glossary entries within a document, refer to
MoEML’s instructions for linking to glossary entries in
GLOSS1.xml.
The orgography database (ORGS1.xml) consists of six listOrg elements in which related org elements are nested:
Complete Orgography
Greater Livery Companies
[Organization entry][Organization entry]
Lesser Livery Companies
[Organization entry][Organization entry]
Playing Companies
[Organization entry][Organization entry]
Other EM Organizations
[Organization entry][Organization entry]
Modern Organizations
[Organization entry][Organization entry]
Pedagogical Partnership Project
[Organization entry][Organization entry]
Each org element represents an individual database entry for an organization. Databse entries (i.e., org elements) must be assigned a unique xml:id as well as a type attribute with a value of either greater, lesser, playingCo, other, modern, or ppp. Database entries must also contain the following elements:
An orgName element, which is used to tag the full name of the organizationA note element
A p element, which is nested inside of the note element and is used to tag a short text string describing the organization
Depending on the type of organization, databse entries (i.e., org elements) may be assigned a subtype element and may contain one or more of the follwoing elements:
A reg element, which is nested inside of the orgName element and is used to tag a regularized spelling of the name of the organizationA figure element, which is nested inside of the note element and encodes a graphic associated with the organization. For instructions on encoding graphics, see Graphics.A listPerson element, which is used to reference one or more person(s) associated with the organization
A head element, which is nested inside of the listPerson element and is used to tag a label for the listPeople associated with the organization are represented by a self-closing person element. At least one person element must be nested inside of the listPerson element. Each person element must have a corresp attribute that points to the xml:id of a person in the personography database (PERS1.xml).A listOrg element in which database entries for subsidiary organizations (i.e., org elements) are nested.
The following subsection, Types of Organizations, outlines when to use the optional elements and attribute isted above.
encoding instructionsborn-digital documentsdocument structureographiesORGS1.xmlorgographyorganizationsorganization typesdata entry
Types of Organizations
Six categories of organizations are included in the orgography database (ORGS1.xml):
greater livery companieslesser livery companiesplaying companiesother early modern organizationsmodern organizationspedagogical partnership project groups
Each category corresponds with an individual listOrg parent element.
Depending on how an organization is classified, you must use different elements,
attributes, and values when encoding a database entry.
Each of the twelve great livery companies of London have already been added to the
ORGS1.xml database. In these entries, the org element has a type
value of greater as well as a subtype value of one one of
R1, R2, R3R12. The latter value
indicates the ranking of the greater livery company, as established in 1515. Consider
the following example of a database entry for a greater livery company: The Worshipful Company of Drapers
The Drapers’ Company was one of
the twelve great companies of London. The
Drapers were third in the order of precedence established in 1515. The Worshipful Company of
Drapers is still active and maintains a website at https://www.thedrapers.co.uk/,
with a history and short
bibliography.
When adding an entry for one of the lesser livery companies of London, add only a
type value of lesser to the org element. No
subtype attribute is required. Consider the following example of a
database entry for a lesser livery company: The Worshipful Company of Carpenters
The Carpenters’ Company was one
of the lesser livery companies of London.
Playing Companies
encoding instructionsborn-digital documentsdatabasesdocument structureographiesORGS1.xmlorgographyorganizationsplaying companiesdata entry
When adding an entry for an early modern playing company, add only a type
value of playingCo to the org element. No subtype
attribute is required. Consider the following example of a database entry for a
playing company: Lady Elizabeth’s MenLady Elizabeth’s Men
Lady Elizabeth’s Men was a
playing company in early modern London. The group was formed in 1611 and was
named after Princess Elizabeth, daughter of King James
I. After she married in 1618, the company changed its name to The
Queen of Bohemia’s Men.
Other Organizations
encoding instructionsborn-digital documentsdatabasesdocument structureographiesORGS1.xmlorgographyorganizationsother early modern organizationsdata entry
When adding an entry for an early modern organization that is not a
livery company, add only a type value of other to the
org element. No subtype value is required. Consider the
following example of a database entry for an organization other than a livery company:
The Corporation of London
The Corporation of London was the municipal government for the City of London, made up of the Mayor of London, the Court of Aldermen, and the Court of Common Council. It exists today in largely the same form.
Modern Organizations
encoding instructionsborn-digital documentsdatabasesdocument structureographiesORGS1.xmlorgographyorganizationsmodern organizationsdata entry
When adding an entry for a modern organization, add only a type value of
modern to the org element. No subtype value is
required. Consider the following example of a database entry for a modern organization:
EEBO-TCPEarly English Books Online–Text Creation
Partnership
EEBO-TCP is a partnership with ProQuest and with more than 150
libraries to generate highly accurate, fully-searchable,
SGML/XML-encoded texts corresponding to books from the Early
English Books Online Database. EEBO-TCP maintains a website at http://www.textcreationpartnership.org/tcp-eebo/.
Teams
encoding instructionsborn-digital documentsdatabasesdocument structureographiesORGS1.xmlorgographyorganizationsmodern organizationsteamsdata entry
Teams (e.g., the Editorial Board, the Advisory Board, the MoEML Team) are also considered modern organizations. When adding an entry for a team, add a type value of modern to the org element. No subtype value is required. Unlike other modern organizations, entries for teams require a list of team members. To encode a list of team members, insert a listPerson element after the orgName element but before the note element. Inside the listPerson element nest self-closing person elements with corresp values pointing to each team member’s xml:id in the personography database (PERS1.xml).
Teams can be divided into subunits. For example, the MoEML Team is divided into Project Leaders, Student Research Assistants, Alumni, etc. If a team includes subunits, insert a listOrg element inside the database entry (i.e., org element) for the team. Nest additional database entries (i.e., org elements) for each subunit inside the listOrg element. Entries for subunits should follow the data structure outlined here for teams and should be assigned an xml:id that is prefixed with the xml:id of their parent entry (e.g., XMPL20_1, XMPL20_2, etc.). Note that it is possible to encode database entries for subunits of subunits (and so on) using the listOrg element. Note also that, when a team includes subunits, team members should be listed in the specific subunit to which they belong (e.g., project leaders are listed in the database entry for the Project Leaders subunit, which is a child of the database entry for the MoEML team).
Consider the following examples of database entries for teams:
Editorial Board
Editorial board.
The University of Victoria Humanities Computing and Media Centre HCMCHCMC Programmers for MoEML
HCMC staff who have worked as programmers on the MoEML project.
HCMC Graphic editors for MoEML
HCMC staff who have worked as graphics editors on the MoEML project.
HCMC staff have collaborated in the project as programmers and graphics editors. The mandate of the HCMC is to further research, teaching and learning in the faculty of Humanities, in particular the fields of Humanities Computing and Language Learning. We host a research and development office and manage a room of bookable computer workstations for use by faculty, research assistants etc. participating in projects supported by the HCMC.
When adding an entry for a pedagogical partnership group, add a type value of ppp to the org element. No subtype value is required. Next, insert a listPerson element after the orgName element but before the note element. Inside the listPerson element nest self-closing person elements with corresp values pointing to each student’s xml:id in the personography database (PERS1.xml). Insert a header (tagged using the head element) that reads Student Contributors inside the listPerson element before the series of person tags.
Pedagogical partnership groups can be divided into student groups. For example, a set of student groups in a class will often work on a series of encyclopedia articles. If a pedagogical partnership group includes student groups, insert a listOrg element inside the database entry (i.e., org element) for the group. Nest additional database entries (i.e., org elements) for each student group inside the listOrg element. Entries for student groups should follow the data structure outlined here for pedagogical partnership groups and should be assigned an xml:id that is prefixed with the xml:id of their parent entry (e.g., XMPL28_1, XMPL28_2, etc.). Note that students should be listed in the specific student group to which they belong (e.g., members of the Student Group A are listed in the database entry for the Student Group A, which is a child of the database entry for the Class 101).
Consider the following examples of a database entries for pedagogical partnership groups:
Exeter University EAS 124 Fall 2014 Contributors
Student Contributors
Student contributors enrolled in EAS 124: Country, City and Court:
Renaissance Literature, 1558-1618 at University of Exeter in the Fall
2014 session, working under the guest editorship of Briony Frost.
Marylhurst University English 386 Fall 2014 StudentsMarylhurst University English 386 Fall 2014 Student Group 1
Student Contributors
Student contributors enrolled in English 386: The Eternal City: Rome in the Western Literary Imagination at Marylhurst University in the Summer 2014 session, working under the guest editorship of Meg Roland.
Marylhurst University English 386 Fall 2014 Student Group 2
Student Contributors
Student contributors enrolled in English 386: The Eternal City: Rome in the Western Literary Imagination at Marylhurst University in the Summer 2014 session, working under the guest editorship of Meg Roland.
Linking Organization Names to the Orgography
encoding instructionsborn-digital documentsdatabasesdocument structureographiesORGS1.xmlorgographyorganizationslinkslink to organizationsdata entry
For instructions on how to tag and link to orgography entries within a document,
refer to MoEML’s instructions for linking to organizations in
ORGS1.xml.
LINKS1.xml is MoEML’s database of links between documents that
are related to each other in some way. Each set of links is encoded within a
linkGrp (contained within a div in the body of LINKS1.xml).
Each linkGrp contains two (empty) elements: link with an target that references a set of documents that
are all related in each other in some way. In the value field associated with the
target, list a series of two or more pointers to documents using the
mol:uri scheme. For example: ptr with an target that points to the xml:id of a
note which contains a short explanation of how the documents are related.
The note is not contained within linkGrp; it exists
elsewhere in LINKS1.xml, referenced as the value of target. For example:
Thus, a complete and properly encoded linkGrp would look like this:
The n attribute is not an explanation of the relationship between
the document; instead it denotes a short caption of this link group.
The note contains a p that provides a short and clear explanation of
the relationship between documents. For example:
Thus the complete and proper encoding of a group of links looks something like this:
Early modern London
included three wharves that could easily be confused because of their names and
locations: Fish Wharf in Queenhithe Ward, Fish Wharf near London Bridge in the parish of St. Magnus in Bridge Within
Ward, and Fresh Wharf (also known as
Fresshffysshewharfe or
Frosshwharf), which was
also located near London Bridge but within the
parish of St. Botolph, Billingsgate in Billingsgate Ward.
A single document may be included in multiple target attributes. By linking
documents as such, we are able to display a list of related documents for
each public document that lists documents sharing a link with the current
document.
Paratextual pages such as About are XML files like any other. They are saved in the /data/info
subcollection. These files have a slightly different convention for file names and
xml:id attributes: they are named with lower-case filenames and
xml:ids. These names and IDs are typically longer and more descriptive, with
multiple-word names separated with underscores. For example,
credits.xmlwebsite_structure.xml
To create a new page on the site, simply create a new XML file in the
/data/info subcollection. For example, to create a page titled
Future Plans, create the following XML file: /data/info/future_plans.xml with xml:id=future_plans on its root element: The page would then be seen at the web address
mapoflondon.uvic.ca/future_plans.htm and would be linked as follows: Future Plans
Boilerplate Text on the Site
encoding instructionsborn-digital documentsprimary source documentswebsite structuredocument structureboilerplate textcaptionslabelstemplatestemplated textmenusformworks / formeworks / forme worksfootersheaders
Text that appears in captions and labels can be edited in
/data/boilerplate/boilerplate.xml. Most of the smaller captions appear in
segs with an xml:id=captions. For example: Click on a square to zoom in. Changing the seg content will change the text on the website. Do not
change the xml:id attribute, which determines the appropriate caption. To
create a new caption, collaborate with a MoEML
programmer.
Also in the /data/boilerplate folder is
/data/boilerplate/site_menus.xml, which controls what appears in the main
site menu and in the links in the footer of every page. Be cautious in making changes to
this content, because it will affect every page on the website.