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,
Born digital.
Most MoEML documents, or significant fragments with 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
Links to page-images in the
The mdt (MoEML Document Type) prefix used on
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 _subcategories
, meaning all subcategories of the category.
The molgls (MoEML gloss) prefix used on
This molvariant prefix is used on
This molajax prefix is used on
The molstow prefix is used on
The molshows prefix is used on
The sb prefix is used on
Our editorial and encoding practices are documented in detail in the Praxis section of our website.
When creating a new file or entity, encoders need to conform to MoEML’s naming conventions. Files are either XML documents or binary documents. Files in MoEML need unique IDs that are of the words_with_underscore
type (see below for details). Entities are referents to items of various types (locations, people, etc.), generated in files including but not limited to: PERS1, ORGS1, GLOSS1, and BIBL1. Entities can also have files of their own, in corresponding project folders, such as
a_lord_mayor
folder. These entities require unique IDs that are of the XXXX1type (see below for details). Note that files that refer to entities will have a combination of both ID types: words_with_underscore_XXXX1 (see Stow example below). The project’s schema will prevent you from adding names which do not conform.
The first thing you need to do when creating an ID is to check MoEML’s A-Z Index and make sure that you are not duplicating an entity ID. An easy way to do this is to try and find the ID you are about to create: ctrl+F (for Windows) or command+F (for iOS) then type in your new ID. If you cannot find it, the ID does not already exist and can be added. If it already exists, use the next numeral available. For example, if you are about to add TEST1 and you find it in the index, change the ID you are creating to TEST2.
The A-Z index can take a long time to load. For a simple list of all xml:ids, see the .txt version of the A-Z Index. This page can be found by simply changing
An entity can refer to a location, person, work of literature, and others. For example, the historical person George Abbot has an entity ID of ABBO1.
When creating a new entity ID, you must follow MoEML’s entity ID structure, which consists of 4 capital letters, followed by the next available integer (i.e., a sequence of one or more digits).
In MoEML, you can either create born digital files or encoded primary sources:
how_to
and info
, use lower-case letters and underscores to separate between words (e.g., draw_on_agas
, encode_library_text
).library
, use four letters and a number (e.g., MAGN3
, CHRU1
).stow
, use stow
, followed by an underscore, followed by the edition year (four digits), followed by an underscore, followed by either a word (in lower-case letters) or entity ID (if one already exists). For example, stow_1598_bridges
is the file name of stow_1598_ALDE2
is the file name of
Binary documents are non XML files/documents; this includes PDFs, Word documents, images, and videos. When naming such documents/files, follow the naming conventions for files in how_to
and info
: use all lower-case letters, and only underscores to separate between words.
If you are not sure if a file name or entity ID fits MoEML’s naming conventions, or if you have any questions, please consult with the