Object Description

<objectDesc> contains all the information about the object as such. Within the @form you should specify one of the available values. The object is further described in <supportDesc>.


Into <support> a series of information about the material support are given.

<support> <watermark></watermark> <material key="Parchment"></material> </support>

In <material> with @key enter the a value from the Writing Material taxonomy proposed from the schema. oXygen should prompt the values from the schema.


<extent> contains information about the global dimensions of the object. The value outer for @type in <dimensions> indicates the external dimensions, including the board, the cover, and the spine. The value leaf for @type in <dimensions> indicates the size of the leaf. The leaf from which the measurements have been taken can be added in a <note> linked with @corresp to the <dimensions> element. In this way, measurements of several leaves can be added. Other values for @type are possible.

<extent> <measure unit="leaf">183</measure> <measure unit="leaf" type="blank">3</measure> <measure unit="quire">25</measure> <dimensions type="outer" unit="mm"> <height>370</height> <width>270</width> <depth>115</depth> </dimensions> <dimensions type="leaf" unit="mm" xml:id="leafdim"> <height>365</height> <width>265</width> </dimensions> <note corresp="#leafdim"> Data on leaves dimensions taken from <locus target="#6r"></locus>. </note> </extent>

Measurements in <dimensions> should always be given in millimiters, unless the source catalogues provides them otherwise.

You can also specify which leaves are blank, adding a <locus> immediately after the relative measure.


<collation> can be used to give textual information about how the leaves are arranged using a <list> of <item> elements.

<collation> <list> <item xml:id="q1"> <dim unit="leaf">8</dim> <locus from="1r" to="8v"></locus> 3, stub after 6 6, stub after 3 </item> <item xml:id="q2"> <dim unit="leaf">10</dim> <locus from="11r" to="20v"></locus> </item> … </list> </collation>

Give a @xml:id to each item in the list to be able to refer to this unit, using "q" and a consecutive number.

If only general information on the collation is provided and no quire structure is given, this information can be stated in a <note> inside <collation>:

<collation> <note> The textual sequence of the manuscript is disturbed, see <ref target="#ms_i1.1"></ref>. </note> </collation>

Quires with an uneven @unit for <dim> will ALWAYS need clarification of the phenomenon occurring as below. No item view will be loaded if only the following is given:

WRONG ENCODING EXAMPLE <item xml:id="q2"> <dim unit="leaf">9</dim> </item>

you need at least the following:

<item xml:id="q2"> <dim unit="leaf">9</dim> 1 added </item>

To notate singletons and stubs, please use the following pattern as in Ethio-Spare

6, stub after 3

Added leaves, where no stub is visible might be recorded as

1, no stub

where the number before the comma is the folio number of the singleton.

Also, you can use with care for consistency the following values

3 replaced, 4 missing, 5 missing, 6 replaced, 9 added

This information will be analyzed to produce diagrams of each quire and formula notations. Added leaves are shown with hyphens, stubs are not shown, replaced leaves are dot-hyphen lines.

Sometimes you might need to describe the position of a quire using <locus> elements. Please, do this in a <note>, as the <locus> element is here reserved for the quire extent.

Different numerations of quires are encoded as follows:

<item xml:id="q26" n="25"> <num value="20">፳</num> <dim unit="leaf">8</dim> <locus from="195r" to="202v"></locus> </item>
  • In <item> with @n we encode the progressive number of quires, assigning "a" as value for initial guard leafs and "b" for final guard leafs. This information was given in Roman Numerals in DomLib, but needs to be in arabic numerals here.

  • The numeration given by the scribe is copied and annotated with a simple <num> with @value element.

  • The number of leafs in the quire is given in <dim>

  • <locus> provides as usual the extremes.

Inside <collation> you can use <signatures> for quire marks and decoration of quiremarks.

<collation> <signatures> Decorated <note>Simply decorated quire marks are written in the middle of the upper margin of fols. 3r, <locus target="#11r"></locus>, 19r, 27r.</note> </signatures> <list> ... </list> </collation>


You might also use <foliation> with a list of items in it to describe different numbering systems used.

<foliation> <list> <item xml:id="fol1"> <locus from="1r" to="98v"></locus> arabic numbers on the top right corner </item> <item xml:id="fol2"> <locus from="1r" to="45v"></locus> ethiopic numbers on the left right corner </item> <item xml:id="fol3"> <locus from="1r" to="102v"></locus> quire numbers on the bottom right </item> </list> </foliation>


You can also add a <condition> element containing a fully marked up description of the condition of the manuscript. Do indicate a general value from the State of Preservation Taxonomy proposed from the schema for indexing purposes.

<condition key="deficient"></condition>

If no information on the condition of the manuscript is available, the element should be simply not added to the record.

Layout Description

<layoutDesc> contains the description of how the text is laid out on the page.

Each layout information is given in a <layout> element therein.

For example for measurement a series of specific purpose attributes and elements can be used:

<layout columns="1" writtenLines="18"> <dimensions unit="mm" rend="pricked ruled"> <height>245</height> <width>210</width> <dim type="intercolumn">15</dim> </dimensions> <dimensions type="margin"> <dim type="top">35</dim> <dim type="bottom">65</dim> <dim type="right">40</dim> <dim type="left">15</dim> </dimensions> </layout>

If the layout measurement refer to a specific part of the manuscript a <locus> element can be used within <layout> to provide the range or a @corresp with the ID of the <msPart>, <msItem> or quire in the collation, whichever might be relevant.

<layout corresp="#p.1.1_i1" columns="1" writtenLines="18"> … </layout>


<layout columns="1" writtenLines="18"> <locus from="1r" to="20v"></locus> … </layout>

The leaf from which the measurements have been taken can be indicated in a <note> inside <layout>:

<layout columns="2" writtenLines="26"> <locus from="119ra" to="132ra"></locus> <note corresp="#textarea #margin">Data on text area and margin dimensions taken from <locus target="#119r"></locus>.</note> <dimensions unit="mm" xml:id="textarea"> <height>145</height> <width>100</width> </dimensions> <dimensions type="margin" unit="mm" xml:id="margin"> <dim type="top">15</dim> <dim type="bottom">30</dim> <dim type="right">20</dim> <dim type="left">5</dim> <dim type="intercolumn">10</dim> </dimensions> </layout>
  • @columns contains the number of columns on a page. One column should be encoded as <layout columns='1'>, when no information is available, this element should not be added.

  • @writtenLines contains the number of lines on a page.

The first <dimensions> contains the information about the text area. A @rend can be used to list separated by spaces other visible characteristics.

The second <dimension type=‘margin’> contains the measures of the margins.

Within a <layout> you can also use <ab> as in the following examples:

<ab type="ruling" subtype="pattern">Ruling pattern: 1A-1A/0-0/0-0/A.</ab> <ab type="pricking" subtype="pattern">Primary pricks are partly visible (s., e.g., fol. 37v).</ab>

<ab> can contain <locus> if you need to state precisely where an event occours.

<ab type="punctuation" subtype="dividers"> <list> <item xml:id="div1" corresp="#p.1">Colon</item> <item xml:id="div2" corresp="#p.2"> Five red and black dot vertical colon. <locus from="30v" n="3"></locus> <locus from="30v" n="11"></locus> <locus from="31r" n="14"></locus> <locus from="31v" n="10"></locus> </item> </list> </ab>

This page is referred to in the following pages

Revisions of this page

  • Pietro Maria Liuzzo on 2018-04-30: first version of guidelines from Wiki
  • Pietro Maria Liuzzo on 2018-04-24: stub of page