Copyright held by
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,
Provider: University of Victoria
Database: The Map of Early Modern London
Content: text/plain; charset="utf-8"
TY - ELEC
A1 - LeBere, Kate
ED - Jenstad, Janelle
T1 - Quickstart: Introduction to Markup
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/quickstart_markup.htm
UR - https://mapoflondon.uvic.ca/edition/7.0/xml/standalone/quickstart_markup.xml
ER -
Research Assistant, 2020-2021. Managing Encoder, 2020-2021. Jamie Zabel was an MA student at the University of Victoria in the Department of English. She completed her BA in English at the University of British Columbia in 2017. She published a paper in University College London’s graduate publication
Project Manager, 2020-2021. Assistant Project Manager, 2019-2020. Research Assistant, 2018-2020. Kate LeBere completed her BA (Hons.) in History and English at the University of Victoria in 2020. She published papers in
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.
Janelle Jenstad is Associate Professor of English at the University of Victoria, Director of
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.
Our editorial and encoding practices are documented in detail in the Praxis section of our website.
Unlike past generations of editors, we are producing texts that must be
readable by machines before they are rendered and made readable by humans.
Therefore, virtually every editorial choice must be tagged in such a way
that a computer can both interpret it and display it
(
Markup has the additional advantage of allowing us to process a marked-up text in
many different ways:
The effort you put into markup makes your text extraordinarily valuable for
a wide variety users because it can be used for many diverse purposes.
Markup is information added
The information added to a text is
When we add
You will also see
MoEML uses a markup language known as TEI-XML. It is a dialect of XML devised by the Text Encoding Initiative (thus, the acronym TEI), a consortium of people who came together to devise a markup language specifically for text-bearing objects (manuscripts, books, documents). XML stands for eXtensible Markup Language. It is not a single language, but a set of standards for writing XML languages. The standard was published in 1996 by the World Wide Web Consortium. It was designed to replace SGML.
What does markup look like? Let’s start with an example using italics.
Italics can indicate many different things:
A human reader can read ambiguous markup. When a human sees italics, they can
infer their meaning through contextual clues. A computer, however, can not.
As encoders, we must specify what italics mean in each given scenario:
These are all examples of
An
But what if you want to specify what
and it’s a monograph!
To refresh:
As you can see, in Oxygen, elements, attributes, and values are different
colours. Note that attributes and values are only added to the opening
tag—the closing tag does not repeat them. It is also important to note that
elements can have more than one attribute:
While particular elements, attributes, and values can vary depending on the XML language, the structure of an XML element is always the same.
Now that you have an idea how elements, attribute, and values can be used to mark up a text, it is time to open Oxygen and try some encoding. If you have not downloaded Oxygen, go here.
Once in Oxygen, follow these steps:
Now you should have an empty XML document. The first thing you will need to do is create an element that all of your text will be nested within. Our documents at MoEML all use the element element type
.
Once the closing
</name>
has been restored, type your full name within the
Now let’s try adding attributes and values. Write a sentence and tag the parts of the sentence with different elements of your choosing: