Schema View Ontology View

Manuscript Contents

The contents of each manuscript part should be given into the smallest possible unit (<msPart>↗) to which they refer to, into a <msContent>↗, but they can be added at any level in a hierarchy of parts.


        <msContents>
                <summary></summary>

                <msItem xml:id="p2_i1">
                    <locus from="371a" to="422"></locus>
                    <title type="complete" ref="LIT2509Weddas"></title>
                    <textLang mainLang="gez" otherLangs="am"></textLang>
                    <note>Each sentence is translated continuously to Amharic.</note>

                    <msItem xml:id="p2_i1.1">
                        <locus from="371" to="278a"></locus>
                        <title type="complete" ref="LIT2509Weddas#Monday"></title>
                        <textLang mainLang="gez"></textLang>
                    </msItem>

                    <msItem xml:id="p2_i1.2">
                        <locus from="378b" to="383a"></locus>
                        <title type="complete" ref="LIT2509Weddas#Tuesday"></title>
                        <textLang mainLang="gez"></textLang>
                    </msItem>
                </msItem>
        </msContents>

Example 1

<title>↗ should point with a @ref to the identifier of the Work in the Clavis. In the Work file alternative titles in different languages should be given, here the title should be reported if relevant, e.g. if non-standard.

Summary

<msContents>↗ can contain a <summary>↗ of the contents, but these can be structurally described with nested <msItem>↗s.

You do not have to give this summary, because a summary will be built from the app starting from <msItem>↗s.

msItem

<msItem>↗ will hold information about contents of the manuscript.


            <msItem xml:id="ms_i2">
                <locus from="40r" to="48r"></locus>
                <title type="complete" ref="LIT3064RepCh344"></title>
                <textLang mainLang="gez"></textLang>
                <incipit xml:lang="gez">እሴብሕ፡ ጸጋኪ፡ ኦምልዕተ፡ ጸጋ፡ ወእትጋነይ፡ ለኪ፨ ኦምልዕተ፡ ውዳሴ፡ ተዘከርኩ፡ በልሌሊት፡ ንጽሐ፡ ድንግልናኪ፡</incipit>
                <explicit type="supplication">
                    <hi rend="rubric"> ኦእግዚእየ፡ ኢየሱስ። ክርስቶስ፨ ዕቀበኒ፡</hi> እመክረ፨ ሥጋ፨ ወነፍስ፡ ለገብርከ፨ ገብርከ፡
                    <persName ref="PRS11944GabraM">ረ፨ ማርያም፨</persName> <hi rend="rubric">አሜን፡ ስብሀት፡ ለኪ፡ ማርም፡ በኁ</hi>
                </explicit>
            </msItem>

Example 2

One <msItem>↗ can have more than one <locus>↗ (see specific page on the use of locus), for instance in composite mss:


            <msItem xml:id="p1_i8">
                <locus from="94v" to="105"></locus>
                <locus from="107"></locus>
            </msItem>

Example 3

If the text of an incipit, explicit, or addition which is quoted in the catalogue record contains text in verse, do use <lb>↗ with a progressive number in @n for each line.


            <incipit xml:lang="gez">
                <lb n="1"></lb>ኦእግዚአብሔር፡ ጥበበ፡ ጠቢባን፡ ከሃሊ።
                <lb n="2"></lb> እስከ፡ ለዓለም፡ እምጥንት፡ እንተ፡ ኢትበሊ።
                <lb n="3"></lb> ድኩመ፡ ሕሊና፡ ገብርከ፡ ወፈራሃ፡ ልብ፡ ኢተሃባሊ።
                <lb n="4"></lb> እስመ፡ ኀቤከ፡ እግዚኦ፡ ጸሎተ፡ አድኅኖ፡ እጼሊ።
                <lb n="5"></lb>  አድኅነኒ፡ አድኅነኒ፡ እምኵሉ፡ ቀታሊ።
            </incipit>

Example 4

Title

<title>↗ will point to a univocally identified work, for <msItem>↗s which correspond to an identifiable work or can be identified as a work. The ID of the work will be given in a @ref and it can be looked up in the list or search pages of the app, by ID, if that is known, or by title. 


                <title type="complete" ref="LIT1468GadlaK"></title>

Example 5

you can use @type to give information about the completeness of the text.

Rubric

<rubric>↗ contains the text of any rubric (heading or subheading) attached to a particular manuscript item. This should not be confused with rubrication, see Text Encoding and Hand Description.

Incipit and Explicit

<incipit>↗ and <explicit>↗ will contain a <locus>↗ and the original text directly within the element. Their language should always be specified, even if identical to the one given in <textLang>↗. Translations of the text will have to be into a <foreign>↗ specifying the language of the translation. More than one translation can be added.

The following example comes from Saint Petersburg, Rossijskaja Nacionalnaja Biblioteka, RNB Ef. n.s. 12.


                  <incipit xml:lang="gez">
                  <locus target="#1r"></locus>
                  በስመ᎓ ሥሉስ᎓ ቅዱስ᎓ ንወጥን᎓ በረኤተ᎓ እግዚአብሔር᎓ ወበሥነ᎓ ሀብቱ። በጸሒፈ᎓ ሰብዐቱ᎓ ጸሎታተ᎓ ሰዐታት᎓ ዘመዓልት᎓ ወዘሌሊት። ቀዳሚሁ᎓ ለለኵሉ᎓ ጊዜ᎓ ትብል።
                  <foreign xml:lang="en">
                  In the name of the Threefold, Holy One, we commence with the help of God and goodness of His richness the writing of the seven hours&apos; prayers of the day and of the night. In the beginning, each time you will say.
                  </foreign>
                  </incipit>

Example 6

Within the text, all TEI markup can be used to indicate mistakes, lacunas, editorial interventions, etc.

The use of <explicit>↗ follows the TEI definition.

Subscriptions stating that the text is completed, which have not been added later to the text, are encoded as <explicit type="subscription">↗:


                <explicit type="subscription" xml:lang="gez">ተፈጸመ፡ ነገር፡ ዘጦቢት፡ ወጦቢያ፡ ወልዱ፡፡
                    በረከቶሙ፡ ትኲን፡ ምስለ፡ ንጉሥነ፡ ኢያሱ፡ ለዓለመ፡ ዓለም፡፡ አሜን፡፡</explicit>

Example 7

Similarly, supplications written at the same time as the main text should be encoded, depending on their location in the text, as <incipit type="supplication">↗ or <explicit type="supplication">↗. See colophons, titles and supplications.

Musical notation

Information about musical notation can be given in <notatedMusic>↗ 


                <notatedMusic>
                    <desc>Extensive musical notation.</desc>
                </notatedMusic>

Example 8

msItem for contents of a work

You can also nest into a <msItem>↗ other <msItems>↗ which describe part of a work. If the content is partial, you can use @defective with the value true. Default is false and is not encoded.


            <msItem xml:id="p1_i1.2">
                <locus from="122v"></locus>
                <title type="complete" ref="LIT1828Mahale"></title>
                <textLang mainLang="gez"></textLang>

                <msItem xml:id="p1_i1.2.1">
                    <locus from="122v"></locus>
                    <title type="complete" ref="LIT1828Mahale#Moses1"></title>
                </msItem>

                <msItem xml:id="p1_i1.2.2">
                    <locus from="123v"></locus>
                    <title type="complete" ref="LIT1828Mahale#Moses2"></title>
                </msItem>
            </msItem>

Example 9

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
  • Dorothea Reule on 2018-05-16: Edited and updated examples,, split additions page