Introduction to the Repertorium Model for Description of Medieval Slavic Manuscripts
by Andrej Bojadžiev (Sofia University)
General Content
- About this document
- Sources for the XML mode
- Text Encoding Initiative Models and Repertorium
- The Beginning of the Description
- Parts of the Repertorium Initiative Model
- Technical documentation
- Changes in the structure of TEI models
Table of Contents
- 1. About this document
- 2. Sources for the XML model
- 3. Text Encoding Initiative Models and Repertorium
- 4. The Beginning of the Description
- 5. Parts of the Repertorium Initiative Model
- 5.1. An Overview. The Main Element.
- 5.2. Cataloguing Information
- 5.3. The Manuscript Name
- 5.4. A Paragraph Between the Name(s) of the Manuscripts and Its Location
- 5.5. Location of the Manuscript
- 5.5.1. Country
- 5.5.2. The city or other place where the manuscript is kept
- 5.5.3. Information on repository (library, archive, etc.)
- 5.5.4. Signatures or Shelf-marks
- 5.5.5. Catalogue Number(s)
- 5.5.6. Information on Collection(s)
- 5.5.7. Secundo Folio
- 5.5.8. Bibliographical information in the manuscriptLocation and catalogueStmt elements
- 5.6. Codicological Information
- 5.6.1. General Notes
- 5.6.2. The element msPart
- 5.6.3. Number of leaves or folia
- 5.6.4. Material
- 5.6.4.1. Description of the parchment
- 5.6.4.2. Description of different kind of parchment in the manuscript
- 5.6.4.3. Description of paper
- 5.6.4.4. Description of different kind of paper in the manuscript
- 5.6.4.5. Watermark
- 5.6.4.6. Motif
- 5.6.4.7. Countermark
- 5.6.4.8. Disposition
- 5.6.4.9. Page range
- 5.6.4.10. List of watermarks
- 5.6.4.11. Paragraph as an element inside paperDesc
- 5.6.4.12. Dimensions
- 5.6.4.13. Columns
- 5.6.4.14. Lines per page
- 5.6.4.15. Alphabet
- 5.6.4.16. Binding
- 5.6.4.16.1. Boards
- 5.6.4.16.2. Box
- 5.6.4.16.3. Cover
- 5.6.4.16.4. Edges
- 5.6.4.16.5. Fly leaves
- 5.6.4.16.6. Fastening
- 5.6.4.16.7. Furnishing
- 5.6.4.16.8. Pastedowns
- 5.6.4.16.9. Sewing and attachment to the boards
- 5.6.4.16.10. Spine
- 5.6.4.17. Quires
- 5.6.4.17.1. Description of the Quires
- 5.6.4.17.2. Quire Composition
- 5.6.4.17.3. Gregory Rule or the rule of parchment arrangement in the quire
- 5.6.4.17.4. Ruling patterns and types
- 5.6.4.17.5. Observations on the pricking
- 5.6.4.17.6. Markings
- 5.6.4.17.7. Foliation and Pagination
- 5.6.4.17.8. Ink
- 5.6.4.17.9. Decoration
- 5.6.4.17.9.1. Miniatures
- 5.6.4.17.9.2. Headpieces
- 5.6.4.17.9.3. Borders
- 5.6.4.17.9.4. Tailpieces
- 5.6.4.17.9.5. Wash
- 5.6.4.17.9.6. Linefillers
- 5.6.4.17.9.7. Initials
- 5.6.4.17.9.8. Heraldry
- 5.6.4.18. Damages, Restorarions, and notes on the manuscript condition
- 5.6.5. The Scribe. Paleographical and Language Features in the
Manuscript
- 5.6.5.1. General Remarks. The elements<scribe> and <scribeList>
- 5.6.5.2. Paleographical Analysis of the Manuscript
- 5.6.5.2.1. General Reamarks
- 5.6.5.2.2. Paleographical characteristics of the scribe's writing system
- 5.6.5.2.3. The description of the shape of each sign
- 5.6.5.2.4. Cadels
- 5.6.5.2.5. Musical notation
- 5.6.5.2.6. Cryptography
- 5.6.5.3. Description of Orthography
- 5.6.5.3.1. General Remarks
- 5.6.5.3.2. The Element letters
- 5.6.5.3.2.1. The Orthography of the jers
- 5.6.5.3.2.2. The Orthography of the Juses
- 5.6.5.3.2.3. The Orthography of the Letters for Jotated Vowels
- 5.6.5.3.2.4. Description of the Orthography of the Other Letters
- 5.6.5.3.3. Ligatures
- 5.6.5.3.4. Abbreviations
- 5.6.5.3.5. Numerals
- 5.6.5.3.6. Supralinear Signs
- 5.6.5.3.7. Other Signs
- 5.6.5.3.8. Orthography of foreign words
- 5.6.5.3.9. Orthography of all other cases
- 5.6.5.4. Description of the Language characteristics
- 5.6.6. Conclusions on creation of the manuscript. Time and
Place.
- 5.6.6.1. General Remerks
- 5.6.6.2. Manuscript's Date
- 5.6.6.3. The Place of Manuscript's Origin
- 5.6.7. The Manuscript Contents
- 5.6.7.1. General Overview
- 5.6.7.2. The Content of the whole manuscript
- 5.6.7.2.1. Number of texts
- 5.6.7.2.2. Texttological Information On the Level of the Whole Manuscript
- 5.6.7.2.3. The original text on the level of the whole manuscript
- 5.6.7.3. The textological comment on each text
- 5.6.7.3.1. The location of the text
- 5.6.7.3.1.1. The number of the text
- 5.6.7.3.1.2. The position of the text
- 5.6.7.3.1.3. The text neighbourhood
- 5.6.7.3.2. The name of the text given by the researcher
- 5.6.7.3.3. The Author of the text
- 5.6.7.3.4. Texttological, linguistic or other data related with the text
- 5.6.7.3.5. The text source
- 5.6.7.3.6. The text translation
- 5.6.7.3.7. Special elements for textual criticism
- 5.6.7.3.1. The location of the text
- 5.6.7.4. Description of the notes
- 5.6.7.4.1. General remarks. The<noteDesc> element
- 5.6.7.4.2. The description of each note
- 5.6.7.4.2.1. The location of the note
- 5.6.7.4.2.2. The date of the note
- 5.6.7.4.2.3. Note contents
- 5.6.7.4.2.4. The author of the note
- 5.6.7.4.2.5. The formula of the note
- 5.6.7.4.2.6. The elements in<noteItem> from the element <scribe>
- 5.6.7.4.2.7. The elements in<noteItem> from the element <articleContentDesc>
- 5.6.7.4.2.8. The decoration in the element<noteItem>
- 5.6.7.5. The elements history and additional
- 6. Technical documentation
- 7. Changes in the structure of TEI models
- 7.1. Inclusion of element msDesc
- 7.2. New elements at the beginning (at the top) and at the end (at the bottom) of the text divisions
- 7.3. New element for encoding the original texts
- 7.4. Some elements in the middle of the divisions
- 7.5. Changes in the models
- 7.6. Changes in the parametrization classes
- 7.7. Changes in attribute classes
- 7.8. Character entities
1. About this document
The purpose of this document is to serve as an introduction to the model of description of Medieval Manuscripts also known as Repertorium Initiative. The Repertorium model relies fully on markup technologies: the first variant was compiled in 1994-1995 as an SGML document. The model presented is based on the Extensible Markup Language, a simplified and web-orinted variant of SGML.
This document illustrates the use of the full Document Type Definition (DTD) features of the Repertorium model. If you would like the use some "light" version, please read information in the document Repertorium Lite Version.
Templates, DTD files and accompanying information could be downlauded as archive here.
This document is work in progress. The recent updates will be published on the Internet site of the project: http://clover.slavic.pitt.edu/~repertorium.
2. Sources for the XML model
The XML model is build as a successor of the SGML DTD (Document Type Definition) but with some extensions, rearangements and redefinitions of the elements and attributes. It reflects more than 10 years of electronic philological descriptions of more than 300 Slavic Medieval and Early Modern Manuscripts.
From the very beginning, the Manuscript Description Model, also called the Template for Slavic Manuscripts (TSM), is closely related with the ideas and of the Text Encoding Initiative and the DTD fragments used there (TEI). The Repertorium Initiative scheme for manuscript description is build on top of the TEI DTD fragments, thus extending them with the opportunity to describe medieval codices and texts. For the publication of Repertorium descriptions, the project uses the TEI XSL (Extensible Stylesheet Language) scripts compiled by Sebastian Rahtz (Oxford University).
The recent Repertorium uses some parts of the MASTER project, an European Initiative for description of Western European Manuscripts, the successor of which is now the Menota project. The TEI Consortium is developing a manuscript description model for the P5 Edition of its "Guidelines", which is based mainly on the experience of these two projects.
3. Text Encoding Initiative Models and Repertorium
The Repertorium Initiative uses the TEI models as a principal framework for encoding and interchange. However, the Repertorium model extends some of the TEI element and attribute definitions thus providing more opportunities for the encoder to describe fully the Medieval texts. The formal definitions of the changes and additions to the TEI models could be found at the end of this document.
4. The Beginning of the Description
Unlike the previous SGML model and also the TEI proposals, in the XML model of Repertorium there is only one way to enter the description: as a part of the element body. In principle, the description could be considered as an example of metadata information and then its place is inside the teiHeader element. A good example is the introductions of Medieval text editions. However, when the element is designed as a holder of a separate and complicated structure, as it is the case with the Repertorium model, the discussion has more or less only theoretical implications.
5. Parts of the Repertorium Initiative Model
5.1. An Overview. The Main Element.
The main element of the description is called msDesc (manuscript description) and it serves as a container for seven additional parts: general cataloguing information (element catalogueStmt), information on physical characteristics and layout of the manuscript (element codicology, paleographical and linguistic data (elements scribe or scribeList), conclusions about the time and place of writing of the manuscript(element manuscriptCreation), the description of the manuscript content as a whole, as separate texts, and its notes and colophon(s) (element contentDesc), a sketch of the manuscript's history (element history), as well as a place for additional information the describer may need to encode (element additional).
The formal declaration of this element is as follows:
This means that five from the elements are mandatory — they should appear at least once. These are the elements catalogueStmt, codicology, manuscriptCreation, contentDesc. The encoder can choose between the scribe and scribeList elements but one of them should necessarily appear in the description.
The element msDeschas two special attributes: form and unity. The allowed values for form depend on the condition of the manuscript: whether it is a codex or a roll, whether is it preserved fully or is just a part or a fragment (leaf, part of the leaf (fragLeaf). The attribute unity could help the encoder to answer the question whether the codex is formed at once or it consists of various parts bound later (a convolute).
5.2. Cataloguing Information
The cataloguing information is an obligatory part of each manuscript description which should provide a necessary introduction for the researchers in their work with Medieval texts and manuscripts. This information consists of a) identification of manuscript name, both as type or genre (e.g. Menaion or Triodion), or as name given in its modern research; b) the information about different location of the manuscript; c) between these two mandatory records could be inserted a brief information about the fact how many pieces the codex is divided, before entering the exact names of places, signatures (shelf-marks), etc.; d) this part of the description completes with the section, providing references to the bibliography being consulted for the electronic description.
The description begins with questions like what is the name of the manuscript, where it is now kept, and whether there are earlier descriptions of it or not. The answers to all these questions the medievalist could encode with the element catalogueStmt (i.e. catalogue statement).
The formal declaration of this element is:
The element catalogueStmt (catalogue statement) has two special attributes: the type is provided here to give an answer: is this cataloguing information current, or it reflects some old documentation. An answer of such a question is necessary for example, when the manuscript is now lost or its place now is unknown. In this cases the electronic description represents an old description which is not a genuine work of the encoder. The attribute source means the "source of the manuscript description": is this catalogue record compiled from de visu investigations, or some other resource which was used as a source for the information. The possible values include also the value other which means that in this case the source should be explicitly described. The possible case for this could be an unpublished remarks on the source.
The encoder should enter records as content of the two elements: about the name of the manuscript (manuscriptName) and about the place where it is kept (manuscriptLocation).
5.3. The Manuscript Name
The name of the manuscript is an word or a short phrase which purpose is to classify the manuscript into the some known classification and to provide the special or supplied during the research tradition name(s) of the book.
There are many characteristics of the name of one manuscript. The most important is the so-called 'generic' or 'unified' name. This includes some typological characteristics such as Psalter or Miscellany. In some cases the manuscripts have some unique names such as Codex Marianus or Kodov Triodion. These names should be provided separetedly.
The formal declaration of the element is:
This element may contain only elements on the phrase level or just a plain text. The attribute codexType could give further information whether this name is general (i. e. unified or generic) or individual. Further refinement of the definition could be done with the aattribute current with values yes or no to characterize it as being the name recently in use or not.
The following example from the description of Codex Marianus demonstrates the use of this element:
Here we have the following information: the general information on the manuscript name is encoded with the value general of the attribute codexType in English and in Bulgarian. The manuscript name currently accepted among scholars is Codex Marianus and the older names are Grigorovič tetraeuangelion, Athonite tetraeuangelion, Mihanović folia, Miklošič folia. The former two names are used to signify the whole codex. The latter two are related only to the part of the manuscript kept in Vienna.
5.4. A Paragraph Between the Name(s) of the Manuscripts and Its Location
The use of this paragraph is resctricted onlyto the cases that a special notion is necessary to summarize the locations of different parts of the same manuscript. The current location in different countries, archives, or collections could require a special introduction to this state with the possible link to the sections of manuscript history, acquisition and to the various signatures or numbers in the catalogues.
This short introduction to the cataloguing information in the description of Manuilev Apostolosis needed to understand the rest of the description. The formal declaration of the element p (meaning paragraph) is used as exactly the same element in TEI models.
5.5. Location of the Manuscript
The meaning of the next element manuscriptLocation is to record all the repositories, signatures, and catalogue numbers in one file. The information on the manuscript location is provided in a single element which contains information on exact location of the manuscript in question. The declaration of this element is:
The order of each element is important. For example, the researcher could not enter the information in a signature without first invoking or inserting the element repository.
5.5.1. Country
Nothing special has to be entered as information in the element repositCountry. This element however is mandatory for the electronic description and should give information on all possible ranges of descriptions. The XML declaration is:
5.5.2. The city or other place where the manuscript is kept
The next part of the information is related to the place where the manuscript is now. Two different elements are provided for this purpose. In most cases the manuscript is kept in libraries or archives in cities. For such a cases an element repositCity is provided. Its declaration is:
When the codex is kept in some other place, e.g. in monastery, an alternative element placeName should be used. This element is part of the TEI element infrastructure and could contain plain text, or sub-elements like region (for some places which are smaller than country, but bigger than cities) or geogName, for names of non-administrative, geographical places.
5.5.3. Information on repository (library, archive, etc.)
This is the next manadatory information, which should be entered in the electronic description. The markup characteristics are the the same as the above mentioned ones:
‘ <!ELEMENT repository %phrase.seq;> <!ATTLIST repository %a.global; >’5.5.4. Signatures or Shelf-marks
This information forms the content of the element repositSignature. This element has one special attribute type which provides information on whether the signature is used now or is older. This attribute values are especially important in the archives with the several fonds re-arranging where the signatures could be formed from the initials or special codes for separate collections. The declration is as follows:
By using the special attribute type, the encoder can choose between the values current and old repository signature. Additional information related to this topic could be supplied with the element bibl and references or pointers e.g. ref, ptr.
5.5.5. Catalogue Number(s)
Some collections of manuscripts in the world are still not described. In such cases this element should be left empty. Much more common is the situation when more than one description or catalogue entry is availlable. In such cases an attribute type is used in the same way as the repositSignature element. The declaration is:
5.5.6. Information on Collection(s)
Some repositories use a complex archiving system with a special divisions between the separate collections and archives. Very often the names of the sections bear the names of their previous owners or commissioners. In such a case a special element is needed in the description. Here it is called collection. It has an attribute type to provide some relevant typology on the subject. The declaration is:
The additional attribute type is available for cases where a more detailed characteristic is necessary.
The element may contain unstructured (plain) text.As part of its content other elements like name or numcould be entered, as well as some references to the bibliographical or other information on the collection. Consider the following example of structured content of the element collection:
In this fragment is stated that the collection belongs to the gatherings of P. Syrku under the number 15. this
5.5.7. Secundo Folio
This tradition is very rare in the Slavic medieval tradition but for the Medieval western manuscripts it was common in the past. The element secFol is borrowed from the project MASTER in order to provide compatibility to their model. Therefore, here will be cited their definition of the element: Secundo folio is "the word or words that a cataloguer, typically medieval but possibly modern as well, might take from a fixed point in all the codices he is describing (the beginning of the second leaf, the beginning of the second column, the beginning of the penultimate leaf, the end of the penultimate leaf, and so on) in order to provide a unique identifier to the particular codex" (http://www.tei-c.org/Master/Reference/ref/SECFOL.html). The declaration is:
5.5.8. Bibliographical information in the manuscriptLocation and catalogueStmt elements
In both elements you may choose between one simple bibliographical reference (element bibl) or a list of such references (element listBibl. Both elements are described in TEI Guidelines. A full bibliographical record is not intended to be given as part neither of these two elements nor in the rest of the description. Here should be entered only references to some more full and probably extensive information at the end of particular description or, if this description is part of the larger project, in the separate file. (cf. the separate manual on entering bibliographic information)
5.6. Codicological Information
5.6.1. General Notes
This element is a wrapper for the all information concerned with the manuscript production. It unites data on the physical condition of the manuscript with the questions related to the binding and decoration.
The markup definition of the structure should be entered in the element codicology. There are several options to enter information into this element. For the strict structured description the encoder should enter as first the elements numFolio or msPart. The former is used for the cases where the manuscript is not convolute, or palimpsest. This is the usual way to describe manuscripts in the familiar hard-copy descriptions order. The later one is to use the element msPart in which you could further specify the parts or layers of the codex. If you would like to preserved the unstructured information from the already published description you may find useful to enter all the information as content of the element overview. The XML declaration of the element codicologyis as follows:
The only special attribute for the element is type. It defines the copy, i.e. whether it is composed from one source, whether it is convolute, palimpsest, etc.
5.6.2. The element msPart
The element msPart should be used in the cases when the manuscript is convolute, or when there is a palimpsest layer(s) below the upper text. There are several cases which could be distinguished when using this element:
- In the cases when a latter information is added on the original leaves of the copy, it should be entered as part of the information in the element scribe, not here;
- When the codex is re-bound and the latter end leaves and pastedowns are inserted by the rebounding process it should be entered in the corresponding sections of the element binding;
- The same is valid in the cases when the parchment or the paper are reinforced by the binder during the rebounding process.
- However, when the latter leaf or leaves are inserted in order to supplement the text and this part is obviously different, the element msPart should be used to describe the codicological features of this inserted part.
- The element msPart is not used to distinguish parts of the text written by the particular scribes. This information is part of the element scribe and its subelements.
The element has the following markup declaration:
Therefore, you have several possibilities for enetering data with the msPart element:
1. A manuscript with uniform structure and a supplemented part to fill in the lacuna in the text:
However, the more consistent encoding will be:
‘ <codicology><numFolio>325<ref target="latterInsertion1"> (f. 132 latter insretion)</ref></numFolio> <overview>... </overview> <msPart type="original" id="MS"><location>...</location><material>...</material> <numbColumn>...</numbColumn> <numbLines>...</numbLines><alphabet>...</alphabet></msPart> <msPart type="supplement" id="latterInsertion1"><location>...</location> <alphabet>...</alphabet> <binding>...</binding></msPart></codicology> ’The same technique could be applied to the description of convolutes.
2. In the case of palimpsests the encoding can look in such a way:
In this approach all other information, regarding paleographical, language or text characteristics goes into the corresponding parts of the description with the links to the mentioned descriptions of codicological information.
5.6.3. Number of leaves or folia
The number of folia in the manuscript are enetered in the element numFolio. This information could be accompanied by some additional data. Consider the following example from the description of the manuscript 369 from the Church Historical and Archival Institute in Sofia:
It is possible to give some links to the information in this file or outside it. Consider the example:
Here is shown the location of the folia in both repositories. The Codex Marianus (this electronic description is part of this fragment) consists of 2 ff. kept in Vienna and 171 in Moscow. The element ref adds the links to the corresponding part of the description (element manuscriptLocation).
The markup declaration of this element is:
No special attributes are provided for this element.
5.6.4. Material
The element material is the next important element in the structure of the electronic description. It unites information on description of paper (paperDesc), parchment (parchmentDesc) possibly preceded by some common characteristics (the element overview). The declaration of the element is:
The elements parchmentList and paperList are explained below. No special attributes are provided for this element.
5.6.4.1. Description of the parchment
The description of the parchment is restricted to the technological process and its outer appearance. The element parchmentDesc does not have any special sub-elements for such information. However, the encoder should add some statement regarding the quality, colour and thickness of the parchment.
The markup declaration is:
The element parchmentDesc has one special attribute use. The meanings of its values are:
- original: an original use;
- supplement: a supplement writen for the original manuscript
- restoration: a parchment added during the restoration process
- endleave: a parchment use for the endleaves
- pastedown: a parchment glued to the inside of a coverboard
- bindingPart: a parchment composing a binding (but not the only part of it)
- wrapper: a wrapper for the manuscript
- distinctSource: an originally distinct ms (bound with this ms at a latter date)
- other: all other possible cases which could not be formalized clearly in advance.
5.6.4.2. Description of different kind of parchment in the manuscript
The element parchmentList is used for description of obviously different kind of parchment, possibly from various animals or of varying quality. This element contains a list of parchment descriptions which could be preceded by of some kind of comment (an element overview).
The markup declaration of the element is:
5.6.4.3. Description of paper
Unlike the descriptiion of the parchment, the paper description in the recent descriptions is a much more complicated task. On one hand, there are various levels of detailed information in the catalogues, and on the other — there are much more specialized research initiatives in the field of paper and watermark studies. In the Repertorium model the field for the paper description is invoked by the element paperDesc.
Its markup definition is:
Therefore, the description of the paper in the manuscript could consist of overviews and comments followed by the description of watermark(s) and by a non-obligatory description of other aspects of the paper production.
The attribute use and its possible values are the same as the elemenet parchmentDesc. The attribute format represents a standard way to distinguish between the possible dimensions of the paper.
5.6.4.4. Description of different kind of paper in the manuscript
The description of obviously different kind of paper, possibly from various manifactures, quality and age could be accomplished by entering an element paperList. This element contains a list of paper descriptions which could be preceded by some kind of comment (an element overview).
The markup declaration of the element is:
This element is used in very detailed manuscript descriptions. If the encoder decided to use this method, it she or he may find useful to supplement their description with the introductory notes about different papers in the element overview.
5.6.4.5. Watermark
The central and most important information in the description of the paper is the watermark. The information on its characteristics is part of the element watermark. For the description of its content is used a special content consisting of the elements on the phrase level as well as elements like countermark, disposition, motif and pageRange. All of them are included in the special entity called waterPara.
The markup declaration of the element is:
‘ <!ELEMENT watermark %waterPara; > <!ATTLIST watermark %a.global; tracing (hand|machine|other) "hand"> ’There is one special attribute called tracing. It is used to describe very briefly (with one word) the method of watermark tracing. By default is meant hand tracing.
5.6.4.6. Motif
The element motif is the most important part of the watermark desciption because it is intended to give a special terminological apparatus of the watermark design.
The markup declaration of the element is:
There are several ways to add information on this subject:
- In the absence of reference books and watermark albums you could enter simply #PCDATA or elements containing in the model %m.phrase;.
- The same approach is possible if only the basic motif is present, without the supplemental or secondary motifs.
- If more complicated motif is presented and the encoder would like to provide full compatibility with the professional watermark databases, he/she could use values of the attribute type as is described below;
- by secondary is meant designs above or below the basic motif. Frequently used motifs above the basic one: bird, cross, cross/greek, flower above, flower/4-petals, flower/5-petals, various kinds of monograms, monograms with the combination with figures (e.g. monogram BA & cross), ramrod, combinations of figures (e.g. staff & flower, staff & snake), different star shapes (star/6-point, star/5-point), star & monogram, trefoil, or some other. Frequently used motifs below the basic one are: grapes, various kinds of monograms, etc.
- by supplemental is meant supplemental characteristics of the basic motif, e.g. in circle, in oval, in shield, etc.
In this approach the usual description of the motif "anchor in circle with 5-point star above" could be encoded as:
5.6.4.7. Countermark
The countermark has the same content and attributes as the watermark element.
The markup declaration of the element is:
It has no special attributes.
5.6.4.8. Disposition
This element gives information on where exactly on the page are the watermark and the countermark. This could be described with relation to the wirelines and chainlines. The possible content of the element could be a choice between terms like, chain lines regularly spaced, between chain lines more widely spaced, on a chain line, on a supplemental chain line, across 2 chain lines, across 3 chain lines, or could be expressed in some other terms, e.g. in mm between various points of the leaf.
The markup definition of the element is:
‘ <!ELEMENT disposition (#PCDATA | %m.phrase;)*> <!ATTLIST disposition %a.global;> ’No special attributes are provided for this element.
5.6.4.9. Page range
The element pageRange gives information on where the particular watermark is to be seen inside the manuscript.
The markup definition is:
No special attributes are provided for this element.
An alternative method for defining the appearance of paricular watermark in the manuscript is to use the global attribute range as part of the elements watermark and countermark.
5.6.4.10. List of watermarks
When for some reason (lack of the manuscript itself, orientation toward the short catalogue, etc. or nearly the same quality and outlook of papers) the encoder decides to introduce information not as a sequence of several paperDesc elements but information only on watermarks, he or she could do this by entering the watermarkList element. In this case an example of possible use could be the following example:
The markup definition of this element is:
‘ <!ELEMENT watermarkList (watermark)+> <!ATTLIST watermarkList %a.global; > ’However, the same element could serve as a very detailed description and could be part of the description of each paper. In this case it should be entered as a structured part of every paperDesc as could be seen in the following example:
No special attributes are provided for this element and it contents should be at least element watermark element.
5.6.4.11. Paragraph as an element inside paperDesc
The meaning of this paragraph is to enable the encoder to describe the other features of the paper. Although not yet structured, there are several portions of information to be enter here:
- Wire lines: The relevant information of wire lines could contain: a) The density of the wire lines as the measure of 20 wirelines (in mm) — a standard procedure common in the paper descriptions; b) description of wire lines. Usualy it is done in terms like: thin wire lines; thick wire lines; alternating thick and thin; very thick wire lines; thick wire lines, thin lines at edges; wirelines in corrugated pattern; wires wrapped around the chain lines; alternate wires wrapped around the chains; or there could be some other specification which is relevant to the paper description.
- Chain lines: The most important feature of the chain
lines is the spacing between them. It could be described by
entering the element dim and its subelement height. The following are recommendations from the Watermark Initiative:
"If the watermark is on the chain line the spaces on either side of it should be given in parentheses: 28,25,(15,14),28,25 If the watermark is positioned between or across two chain lines, the space between them should be given in parentheses: 44,45,(50),47,43 " (http://abacus.bates.edu/Faculty/wmarchive/FORM_descriptions.html) An example of such description is provided as well: "04. Wire/Chainline description: Density of Wirelines: 26 mm. for 20 wirelines. (style: thin wirelines) Chainline Interval(s): / 50 mm." (http://abacus.bates.edu/Faculty/wmarchive/INTRO_papers.html)
- Paper thickness: The data on paper thickness could be entered as information in the element thickness. It could be relative and could contain values as: very thin, thin, medium thin, medium, medium thick, thick, very thick, or, alternatively, could be measured in some way.
- Paper colour: This information could be entered as content of the element colour.
- Texture: The possible terms which could be entered as more or less definetely known to the researchers are: smooth, matte, fuzzy, patina, glazed, bumpy, etc. Here you can add information information whether the dark fibres and wire lines are visible on the surface of the paper or not.
- Stiffness: Rarely in the information about paper's look and quality could be found information on the paper stiffness. If the encoder would like to enter such information the range of possible values could include: stiff, crisp, supple, limp, etc. This information could be entered as plain text.
- Date of the paper: Usually the dating of the paper is part of the watermark description. This is the most familiar place because the watermark image is the most characteristic part of the paper description. You could provide not only exact date or date range in your paper description but you could further specify the reasons for doing so. The possible values could include: published watermark(s) cited in references; codex date given in scribal note; codex dated on paleographical grounds; codex dated by comparison of papers; codex dated from other evidence; the paper associated with binding, etc. The date range could be entered as a regular expression. For example: sign * matches zero or more matches of the regular expression. So the expression 15** means the range from 1500 to 1599, 156*, from 1560 to 1569, and 156*-157* - each year from the 1560 up to the 1579.
- References: The references are given as external reference element inside the elements bibl or listBibl.
5.6.4.12. Dimensions
All sorts of dimensions could be entered into this element. The attribute type gives a hint to the encoder for what purposes could the element be used. The attribute unit provides three possible characteristics and scope emphasizes the range of these dimensions.
The markup declaration is:
The element dim could be entered in many places of manuscript descriptions. Therefore it has three special attributes. The attribute type provides some common typology of the dimensions of given manuscript source. The possible values comprise all important parts of the manuscript physical description and layout. Commonly used dimensions are these of the leaves, pagewritten area and the height of the characters or lines. Author of the description however may find usefull to mentioned the dimensions of the ruled or pricked region of the page and quire, as well as to provide measures for the plates as part of the binding. It is even possible to distinguished the dimension of the single letter in comparison to the whole line.
The most useful units of measurement in the manuscript description are mm and cm but sometimes, especially in the description of the initials a measurement in the lines per page or characters per line could be more useful than the exact measures.
To suply information on the possible range of dimensions the descriptor may find convinient to use the attribute scope or to use the attribute range from the global attributes with the exact value of particular part of the manuscript. The following example illustrates the usage of the both attributes:
5.6.4.12.1. Height
The height of some object given in units as part of the element dim. The markup declaration is:
No special attributes are provided for this element.
5.6.4.12.2. Width
The width of an object given in units as part of the element dim. The markup declaration is:
No special attributes are provided for this element.
5.6.4.12.3. Depth
The width of an object given in units as part of the element dim. The markup declaration is:
No special attributes are provided for this element.
5.6.4.12.4. Thickness
The thickness of an object given in units as part of the element dim. The markup declaration is:
No special attributes are provided for this element.
5.6.4.13. Columns
The number of columns could only be a digit and may also contain a phrase serving as a comment. No special attributes are necessary. The markup declaration is:
5.6.4.14. Lines per page
The number of pages could be only a digit or combination of digits with some comments regarding the place and the sequence of lines per columns or per page. No special attributes are necessary for this information. The markup definition is:
5.6.4.15. Alphabet
This element contains the alphabet of the manuscript. It could only be a word, e.g.
or could be accompanied with some comments, e.g.
Alternatively, you could use the attribute type:
The markup definition of the element is:
5.6.4.16. Binding
The information about binding in the most descriptions is very brief. It consists of statements like "Wooden panels covered with ornamented leathers. Not original. Done probably in 16th century". In most cases this information is entered in the brief descriptions. Such information could be entered in the sub-element overview of the element binding.
The formal declaration of the element is:
The encoder can make a short statement before continuing the description of the binding or provide only this information. In the latter case he/she could give information on all the main parts of the book-binding structure and decoration.
A special attribute condition is assigned to this element to give a short information on the condition of the bookbinding. If the descriptor would like to give more details on the book-binding several elements are provided for this purpose.
5.6.4.16.1. Boards
The first part of the detailed book-binding description are details about the boards: their material and the the technologies used in their manufacturing.
The formal declaration of the element is:
The attribute visibility is provided to give information on whtether the board could be directly seen or the information on it is more or less hypothetical.
5.6.4.16.2. Box
Sometimes codices, rolls, or fragments are kept in the boxes. The element box is intended to provide information on that matter.
The formal declaration of the element is:
No special attributes are provided for this element.
5.6.4.16.3. Cover
All the aspects of the description of the cover should be entered in the content of the element cover. The material of the cover should be described in the attribute material; further specifications could include the decoration of the cover, e.g. whether there are traces of blind or gold tooling, stamps, and all various aspects of cover decoration and art technique.
The formal declaration of the element is:
5.6.4.16.4. Edges
The information regarding the edges is part of the element edge. It should contain observations on edge decoration or technology, e.g. beveling of the edges.
The formal declaration is:
No special attributes are provided for this element.
5.6.4.16.5. Fly leaves
The element flyLeaf is used for cases when a leaf or leaves are inserted in the book-binding process at the beginning and end of the book (these are not the leaf or leaves pasted to the boards or covers of the book).
The formal declaration is:
No special attributes are provided for this element.
5.6.4.16.6. Fastening
It is assumed that the whole technology on the fastening could be described as a part of one element (fastening). The observations should include how the fastening is done, e.g. by peg and strap, by hook and clasp, the length or width of the elements could be measured, their place(s) could be described, etc.
The formal declaration of the element is:
‘ <!ELEMENT fastening %paraContent;> <!ATTLIST fastening %a.global;> ’No special attributes are provided for this element.
5.6.4.16.7. Furnishing
The term furnishing covers all metal parts of the book binding but is in most cases part of the cover characteristics. Therefore, the encoder should describe all the bosses, corner pieces, etc. which could be observed on the book binding.
The formal declaration of this element is:
No special attributes are provided for this element.
5.6.4.16.8. Pastedowns
The description of the pastedowns are closely related to those of fly leaves and should be made together.
The formal declaration of this element is:
No special attributes are provided for this element.
5.6.4.16.9. Sewing and attachment to the boards
The description of the sewing has two parts depending on what kind of attachments are made: to the quires and leaves or to the main boards.
Attachments to the quires or leaves: A textblock can be sewn through the side of the leaves, such as oversewing or side sewing, etc. In addition, the textblock can be also sewn through the fold of the sections by hand. Three different patterns are observed sewing structure, sewing stitches, and sewing pattern. (The following definitions and information are based on Pamela Spitzmueller's paper — "Trial Terminology for Describing Sewing Through the Fold," (the Paper Conservator, vol.7, 1982/83, and on the web-article "Paper Conservation Course" (http://www.scmre.org/bookbinding.html):
Sewing structures: supported = parts other than thread involved in the connection of the sections. Materials for support usually are: cord, parchment, skin, linen tape, etc. unsupported = only sewing thread connecting the sections to each other. The unsupported structure is commonly found in Greek, Islamic, and Oriental books.
Sewing stitches, which is the motion of a thread from sewing station (hole) exit to a sewing station entry. The classification could be as follows:
- Slip: thread passes under itself
- Link: thread passes under another thread
- Loop: circle around a support
- Lap: passes over a support
- Forward: continues in the direction of progression
- Reverse: continues to the previous direction of progression
- Drop: moves downward
- Climb: moves upward
- Incline: moves diagonalyl
Sewing patterns. The main patterns are:
- Fold patterns: sequence of thread visible inside the fold of the section. They are of two types: Continuous pattern: thread passing in and out each sewing station to form a pattern and Periodic pattern: thread skipping sewing holes and leavesintervals between some of the stations.
- Spine patterns: the pattern is formed by the stitches across the uncovered spine of the book. Some spine patterns are: (1) Chain (formed by link stitches), (2) Bridge (by span), (3) Ribs (by loop), (4) Herringbone (by loop and link), (5) Steps (by lap), etc.
The formal definition of the element sewing is:
No special attributes are provided for this element.
5.6.4.16.10. Spine
The element spine should provide information on the form and constituents of the spine of the codex. The possible problems are:
- whether the form of the spine is rounded or flat (as an attribute type);
- are there raised bands or the bands are smooth;
- Information on the process of reinforcing the spine of a sewn book after gluing-up, rounding and backing, and before covering or casing-in known as lining or spine lining.
- Are there headbands, if yes, are they double or triple, etc.; how they are connected to the board; what are their colours; what material are they made from.
The formal declaration of the element is:
5.6.4.17. Quires
Each quire is described in the quireStructure element. This element contains a set of quire's. At least one such element should be present.
The formal definition of the element quireStructure is:
The special attribute type provides a convinient typology for the quires in terms of their composition and consequence.
5.6.4.17.1. Description of the Quires
The element quire provides a detailed analysis of each quire.
The formal definition of the element is:
This definition is common for the description of each type of quires: parchment, paper, or mixed quires. Therefore the element quire brings together all possible features for the characterisation of the quire: on the first place their number, and composition, how and where there are marked, with the assistance of what tool. Provided are features like rule for the composition of the parchment leaves in the quire (rule of Gregory, or rule for the flesh and hair side -
5.6.4.17.2. Quire Composition
The element compositionQuire provides information on how the quire is composed, of how many folia, etc. The content of this element is a formula. Consider the following example:
This means that first quire of the manuscript consists of 8 ff. all of which, with the exception of the f. 7, are missing now. The quires II to XXI have 8 ff. each. From quire XXII one f. (7) is missing. The last, XXIII quire, consisted originally of 6 ff. but only 2 of them are preserved intact.
The formal definition of the element is:
5.6.4.17.3. Gregory Rule or the rule of parchment arrangement in the quire
The arrangement of the parchment folia as part of the quire structure is entered here. Only de visu observations on the manuscript could answer the quiestion in what sequence and order are parchment folia arranged. There are two common abbreviations: HS — for the hair (dark) side, and FS — for the flesh (light) side of the parchment.
Therefore the content of this element could be a sequence of HS and FS abbreviations, e.g:
In the case that there is no rule, or there are deviations from it should be stated explicitly. If the deviations are caused by the loss of leaves, it is possible to insert a link pointing to the place where this loss is explained.
The formal definition of the element is:
The attribute type is provided in case some more convinient typology is needed.
5.6.4.17.4. Ruling patterns and types
Two kinds of information regarding the medieval manuscripts could be entered in the element ruling. The first one is related to the ruling type defined by researchers like Gilissen or Leroy, who made an attempt to propose a well-defined typology on ruling types.The other information is related to the place of ruling in the quire or the so called ‘scheme’.
The former could be expressed as a formula of ruled lines for writins and for suppling additional information on the codex pages.
The later could be visualised as simple graphic showing the places in the quire where the ruling is accomplished, e.g.:
This scheme means that in this quire the ruling is made for each of the two folia: once for the outer double leave and once for the inner one. The symbols > or < mean that on the leaf is just a trace of the ruling made on the previous leaf.
The formal declaration of the element is:
The attribute type should provide information which classification scheme is used for the description.
5.6.4.17.5. Observations on the pricking
Such observations are relatively rare in the literature. However, as described by Johns in 1948, they could bear information on scriptorial techniques. Thus, it is necessary to provide an element for such types of information.
The formal definition of the element is:
The attribute type is provided for the conviniency.
5.6.4.17.6. Markings
An important part of the description of quires is the observation how they are marked at their beginning and ending. The description should include a phrase defining the place of their existence, both at the beginning and in the end of the quire, are there changes in their form or place, etc.
The formal declaration of the element is:
There are several special attributes for this element. The attribute presence holds brief information on whether all, some, or none of the markings are left. The attribute orientation describes the direction of the markings and the form should be choosen from the list of attribute values. Signature is the most common way of marking the quire. In most cases it consists of number symbol and sign(s) near of it. Catchword is used in the later tradition and usualy appear at the bottom of each page, although there are some cases when it is possible to decide that it was on the level of the quire. Numbers are for the latter tradions. The reclames in the Slavic tradtion are very rare, perhaps with the exception of Glagolitic Psalterium Sinaiticum from the 10th century.
5.6.4.17.7. Foliation and Pagination
The both elements have the same content and structure. Here several kind of information could be enetered: when the foliation or pagination is made, is it original or not, as well as how the folia or pages are marked or numbered. The latter information is entered by inserting the element markings which content is decribed above.
The formal definition of the elements foliation and pagination are:
‘<!ELEMENT foliation (p | date | dateRange | markings)*> <!ATTLIST foliation %a.global; original (yes|no|unknown) "no"> <!ELEMENT pagination (p | date | dateRange | markings)*> <!ATTLIST pagination %a.global; original (yes|no|unknown) "no"> ’5.6.4.17.8. Ink
The valuable information about the ink is presentend usualy as a simple phrase like "brown dark ink for the basic text and red ink for the headings and small initials". However, such decriptions could then be further developed in order to supply information on ink composition, its brightness or its loss of colour.
The formal declaration of this element is:
‘<!ELEMENT ink %phrase.seq;> <!ATTLIST ink %a.global;> ’No special attributes are defined for this element.
5.6.4.17.9. Decoration
The element decoration is used to give information on the various aspects of the manuscript illumination. There could be several ways of using this element and the subelements of its structure. The first one is to provide so basic notions on the styles and art objects in the codex with the help of the element overview. The other choice for the encoder is to prefer a direct list of all the elements like miniatures, headpieces or initials possibly preceded by some general characteristics.
The formal declaration of the element decoration is:
‘<!ELEMENT decoration (overview*, miniatures*, headpieces*, borders*, tailpieces*, wash*, linefillers*, initials*, marg*, heraldry*)> <!ATTLIST decoration %a.global; > ’No special attributes are provided for this element.
The element for the miniatures in the manuscript. The questions of styles and form should be choosen from the encoder. No further specifications is made in this respect.
The example of appropriate markup could be:
‘<miniatures><p>Three miniatures of St. Mark, St. Luke, and St. John, crude drawings in ink and pink, green or ocher washes.</p> <list><item><location>F. 44r</location>, St. Matthew in full length, under arch, holding the Gospel.</item> <item><location>F. 77v</location>, St. Luke in full length, under ornamented arch.</item> <item><location>F. 133v</location>, St. John in full length, under arch. The image is stylisticly different from the others.</item></list> </miniatures> ’The formal definition of this element is:
‘<!ELEMENT miniatures %specialPara;> <!ATTLIST miniatures %a.global; > ’No special attributes are provided for this element.
The element for the headpieces in the manuscript. As by the miniatures no speculations are made on the terminological apparatus. An example could be:
‘<headpieces><list><item><location> f. 43, the Chapters of St. Mark's Gospel, </location> an interlaced headband with floral endings at the corners and the short sides of the band.</item> <item><location>f. 44v, the beginning of St. Mark's Gospel</location>, an interlaced headband with floral endings at the corners and a central motif on the upper rim.</item> </list></headpieces> ’The formal definition of this element is:
‘<!ELEMENT headpieces %specialPara;> <!ATTLIST headpieces %a.global;> ’No special attributes are provided for this element.
The definition and usage of the element<borders> is exactly the same as by the element <miniatures> and <headpieces>
The formal definition of the element is:
‘<!ELEMENT borders %specialPara;> <!ATTLIST borders %a.global; > ’No special attributes are provided for this element.
The tailpieces are used to form the endings of some texts. And therefore they are the mirror of the headpieces. So the definition of this two are the same. Only the place of their usage and its function are different in the manuscripts.
The formal definition of the element is:
‘<!ELEMENT tailpieces %specialPara;> <!ATTLIST tailpieces %a.global; > ’No special attributes are provided for this element.
There element which gathers together the information on the wash element that may be used in the manuscript.
The formal definition of the element is:
‘<!ELEMENT wash %specialPara;> <!ATTLIST wash %a.global; > ’No special attributes are provided for this element.
The formal definition of the element is:
‘<!ELEMENT linefillers %specialPara;> <!ATTLIST linefillers %a.global; > ’No special attributes are provided for this element.
The formal definition of the element is:
‘<!ELEMENT initials %specialPara;> <!ATTLIST initials %a.global; > ’No special attributes are provided for this element.
The formal definition of the element is:
‘<!ELEMENT heraldry %phrase.seq;> <!ATTLIST heraldry %a.global;> ’No special attributes are provided for this element.
5.6.4.18. Damages, Restorarions, and notes on the manuscript condition
The information is eneter in the element called miscObservat. It is used mainly to dscribe various kinds of damages on the various levels: part of the folia, quire, binding or the whole manuscript.
The ancient or moder restoration process could be encoded in this element as well.
The formal declaration of the element is:
‘<!ELEMENT miscObservat %paraContent;> <!ATTLIST miscObservat %a.global; type (miscDamage | restoration) #IMPLIED kind CDATA #IMPLIED> ’The value of the attribute type should be choosen when entering the information in this element. It must be miscDamage or restorarion. The attribute kind is provided to provide some more information on damages or restoration process, e.g.
‘ <miscObservat type="miscDamage" kind="humidity"gt;Due to the humidity the ink on most of the pages loss its color and now on most of the pages the text is hardly to read. </miscObservat> ’5.6.5. The Scribe. Paleographical and Language Features in the Manuscript
5.6.5.1. General Remarks. The elements<scribe> and <scribeList>
‘<!ELEMENT scribe (overview*, (num*, name*, pageRange*, palaeoCharact?, orthogrCharact?, langCharact?, (ref | xref)?, (bibl | listBibl)?, respStmt?)*)*> <!ATTLIST scribe %a.global; > <!ELEMENT scribeList (overview*, scribe+, (ref | xref)?, (bibl | listBibl)?)> <!ATTLIST scribeList %a.global; > <!ELEMENT pageRange %phrase.seq;> <!ATTLIST pageRange %a.global; > ’5.6.5.2. Paleographical Analysis of the Manuscript
5.6.5.2.1. General Reamarks
The analysis of the paleographical features of the manuscript should accomplished in the element<palaeCharact>.
The formal definition of the element is:
‘<!ELEMENT palaeoCharact %palaeoPara; > <!ATTLIST palaeoCharact %a.global; type CDATA #IMPLIED > ’This element has a special content description the content of which is a combination of the elements on the level of the paragraph (%paraContent;) with some special elements intended for the description of the paleography.
The formal definition of this entity called palaeoPara is:
‘<!ENTITY % palaeoPara '(#PCDATA | %m.phrase; | %m.inter; | %m.Incl; | writing | letterForm | cadels | crypto | musicNotation)*'> ’This definition means that the encoder could enter either unstructured information or, if necessary, this information could be enter in the form of some special element.Both approaches are legal, though, if in some place of the manuscript appear musical notation or crypted noted, their system should be described in the specialized tags.
5.6.5.2.2. Paleographical characteristics of the scribe's writing system
This information could be entered either in unstructured way as a content of the palaeoCharact element or in some cases, as is in the detailed description it could prefereable to use a special element for it. This element is called writing. Its purpose of it is to give a characteristics of the script in some general terms, e.g.
‘<writin>Uncial script very close to the writing in Enina Apostle and Vatikana Palimpsest </writing>g’The formal declaration of the element is:
‘<!ELEMENT writing %paraContent;> <!ATTLIST writing %a.global;> ’No special attributes are provided for this element.
5.6.5.2.3. The description of the shape of each sign
As by the latter element this one is not mandatory too, but it could be useful in some cases when the exact shape of the letters or other signs is important and could supply some valuable information to the readers and users of the electronic description.
Therefore, an example of the usage of this element could be:
‘<letterForm>The letter a is written ... </letterForm> <letterForm>The letter c is written ... </letterForm> ’The formal definition of this element is:
‘<!ELEMENT letterForm %paraContent;> <!ATTLIST letterForm %a.global;> ’No special attributes are provided for this element.
5.6.5.2.4. Cadels
The cadels are special extensions of some letters in the margins of the manuscript. There are usualy to be seen at the top and the bottom margin. Their appearance could provide some extra material for the scribal's technique.
The formal definition of this element is:
‘<!ELEMENT cadels %specialPara;> <!ATTLIST cadels %a.global; > ’No special attributes are provided for this element.
5.6.5.2.5. Musical notation
If musical signs are found in the manuscript, the system of their usage along with the places in the manuscript where they are found, are described in the element musicNotation.
The formal definition of the element is:
‘<!ELEMENT musicNotation %phrase.seq;> <!ATTLIST musicNotation %a.global;> ’No special attributes are provided for this element.
5.6.5.2.6. Cryptography
The element for the description of the cryptographical system in Repertorium model is called crypto and should be used in the cases where some encrypted letters or passages of the text are used. The text itself, its classification and edition is part of the noteDesc element.
The formal definition of the element is:
‘<!ELEMENT crypto %phrase.seq;> <!ATTLIST crypto %a.global; > ’No special attributes are provided for this element.
5.6.5.3. Description of Orthography
5.6.5.3.1. General Remarks
The encoder of the Slavonic manuscripts have two possible ways to describe the orthographical features of the given copy. The first of them is to provide only a brief characteristics in the element<overview> in the form
‘<orthogrCharact><overview>The scribe writes with two jers and with nonetymological appearance of juses. After the letters ш, ж, in the word-initial position (after j), and after the vowel letters front nasal is turned to the back one. After ч this change is not observed. A relatively small amount of ligatures and supralinear signs. A few examples of accent signs ... </overview></orthogrCharact> ’The other way to describe the orthography of the scribe is to make a structured description and to enter each piece of this description as a separate element.
The formal ddefinition of this element is:
‘<!ELEMENT orthogrCharact (overview*, letters*, ligatures*, abbrev*, numeral*, supralinear*, punct*, marg*, explain*, final*, foreignOrth*, otherOrth*)> <!ATTLIST orthogrCharact %a.global; > ’No special attributes are provided for this element.
5.6.5.3.2. The Element letters
The rules for the usage of different letters are described as content of the element letters. It contains four subelements which goal is to typologize the orthography of the scribe in some convinient way. For the Medieval Slavonic tradition three groups of letters and their usage are important: jers, juses and letters for jotated vowels. The combination of the three groups together with the imformation for usage of other signs could help to draw a clear pictures of the scribe's orthography.
The formal declaration of this element is:
‘<!ELEMENT letters (jer, jus, jotVowel?, otherLetters?)> <!ATTLIST letters %a.global; > ’No special attributes are provided for this element.
The subelements should appear in exactly the same order and the first two of them are mandatory.
The first of the three most important letters in the Medieval Slavonic texts are jers and their orthography. The information regarding this feature is entered by the element jer. The encoder could describe in length a various position of jers and their relationship to the etymological condtion, as well as could provide examples of its usage.
The formal definition of this element is:
‘<!ELEMENT jer %paraContent;> <!ATTLIST jer %a.global; type (front | back | etymReg | nonEtymReg | irregular) #REQUIRED > ’This element has one special and very important attribute called type. The encoder shoud choose one value of this attribute otherwise the file will not-valid. The meaning of the attributes are as folows:
- front: only front jer is used
- back: only back jer is used
- etymReg: etymologically regular usages of jers
- nonEtymReg: not etymologically but regular uses of jers
- irregular: the usage of jers could not be formalized in some clearly distinguished rules.
For example, the manuscripts written with Tărnovo orthographic norms use non etymologically but regularly both jers. The same is correct for such an ancient manuscript as Zograph Folia from the 10th century.
The description of the orthography of the juses is very similar to that of jers. The encoder could provide a lenghty explanation of different positions where juses are met or not. Are there on the etymologically correct positions, etc.
The formal definition of this element is:
‘<!ELEMENT jus %paraContent;> <!ATTLIST jus %a.global; type (etymReg | nonEtymReg | nonConsis | nonJus | jusTrace) #REQUIRED > ’Like the element jer, the element jus also has a special element type which is required for the system. The values of this element are:
- etymReg: etymologically regular usage of juses (in most cases the Old Bulgarian stage)
- nonEtymReg: non etymologically, but otherwise regular usage of the juses (Middle Bulgarian manuscripts, and in part East Slavic mauscripts)
- nonConsis: non consistent usage of the juses
- nonJus: orthography without juses
- jusTrace: orthography without or with very examples of the juses but with its traces, e.g. manuscript written with non-jus orthography but with traces of Middle Bulgarian alternation of juses
The two of the mentioned above elements jer and jus could provide enough data to decide the characteristics of the main features of the Medieval Slavic orthographic system. To be more precise however, the description of letters for jotated vowels is also important. This characteristics is made as part of the element jotVowel, which has the following formal definition:
No special attributes are provided for this element.
The distribution of all other letters with the exception of cases of words from foreign origin which are described in the element<foreignOrthogr> could be analyzed here. The formal declaration is:
‘<!ELEMENT otherLetters %paraContent;> <!ATTLIST otherLetters %a.global; > ’No special attributes are provided for this element.
5.6.5.3.3. Ligatures
The usage of ligatures is disscussed in this element. The shape of the ligatures is described in the paleographical section.
The formal declaration of the element is:
‘<!ELEMENT ligatures %phrase.seq;> <!ATTLIST ligatures %a.global; > ’No special attributes for this element is provided.
5.6.5.3.4. Abbreviations
The element abbrev is especially included in the electronic description where there is needed to make distinction between various signs for the abbreviations as well as between the various ways to abbreviate words or phrases. The element abbrev is not intended to be used for discussion on the form of the abbreviation signs, but rather should provide discussion on their usage.
The formal definition of the element is:
‘<!ELEMENT abbrev %phrase.seq;> <!ATTLIST abbrev %a.global; > ’No sprecial attributes are provided for this element.
5.6.5.3.5. Numerals
Various ways of usage of numerals could be described here. For the Slavonic tradition the questions on the signs of 90, and 900. The position of the element for tens as part of the numerals from 13 to 19 could be inportant.
The formal definition of the element is:
‘<!ELEMENT numeral %phrase.seq;> <!ATTLIST numeral %a.global; > ’No special attributes are provided for this element.
5.6.5.3.6. Supralinear Signs
In the orthography of the supralinear signs in the Slavonic tradition should be distinguished two categories: signs for an easier reading of the texts and accent signs. The signs which are related with the musical notation should be described separetly in the section musicNotation.
‘<!ELEMENT supralinear %phrase.seq;> <!ATTLIST supralinear %a.global; >xts ’5.6.5.3.7. Other Signs
All signs related with the various text segmentation or with some addtion of the text and its explanations are described as a usage in the their respective elements.
Their formal declarations are:
For the punctuations: ‘<!ELEMENT punct %phrase.seq;> <!ATTLIST punct %a.global; > ’ For the marginal signs: ‘<!ELEMENT marg %specialPara;> <!ATTLIST marg %a.global; > ’ For the explanational signs: ‘<!ELEMENT explain %phrase.seq;> <!ATTLIST explain %a.global; > ’ For the end of the texts: ‘<!ELEMENT final %phrase.seq;> <!ATTLIST final %a.global; > ’None of these elements have any special attributes.
5.6.5.3.8. Orthography of foreign words
Sometimes it is worth to distinguished the orthography of the loaned words, most of them from Greek, Hebrew or Latin origin from the others. The orthography of these words coud give an important clue for resreachers in linguistics and textology.
Therefore, a special element<foreignOrthogr> is provided for this reason.
The formal declaration of the element is:
‘<!ELEMENT foreignOrth %phrase.seq;> <!ATTLIST foreignOrth %a.global; > ’No special attributes are provided for this element.
5.6.5.3.9. Orthography of all other cases
In the case that all these elements are not enough for the description and there cases which could not be part of such taxonomy, an element<otherOrth> is foreseen.
The formal definition of this element is:
‘<!ELEMENT otherOrth %phrase.seq;> <!ATTLIST otherOrth %a.global; > ’No special attributes are provided for this element.
5.6.5.4. Description of the Language characteristics
The description of language is structured into separate units. The reason is that there is no previously defined list of criteria in the description of manuscripts. If the researcher would like to make the description in more systematic way, then the use of some simple structure would be useful.
Consider the following example:
‘<langCharact> <list> <item id="phonology">The adjective forms preffer the archaic <m lang="os">-сц-</m> to <m lang="os">-ст-</m>. Cases with <m lang="os">-ст-</m> are rare. The uncontracted forms of pronominal adjectives and of verbs of the -je-conjugation in Ind. Praes. Act. and of verbs in Imperfect are much more frequent than the contracted ones. Verbal forms (Ind. Praes. Act., p.3, -je-conjugation) with assimilation, such as <w lang="os">б ѣгаат</w>, <w lang="os">радоуоутъ</w> are frequent. In Imperativus there is variation of forms with <c lang="os">ъѣ</> and with <c lang="os">и</c>, such as <w lang="os">покажcѣт</w> 290.17, but also <w lang="os">покажите</w> 80.5.</item> <item id="verbs">The manuscript uses non-sigmatic Aoristus (e.g. <w lang="os">вьнидъ</w>, <w lang="os">сънидъ</w>, <w lang="os">идомъ</w>, <w lang="os">отидеѫ</>) and first sigmatic Aoristus of verbs with stems ending in a consonant (e.g. <w lang="os">привwѣс</w>, <w lang="os">въвъѣсом</w>, <w lang="os">възнъѣсѧ</>). Verbs with infinitive stems ending in a vowel often preserve the archaic ending <m lang="os">-тъ</m> in Ind. Aor. Act, p. 2 and 3, Sg., e.g. <w lang="os">обитъ</w>, <w lang="os">оумрwѣт</w>. Three cases of ommited ending <m lang="os">-тъ</m> for Ind. Praes. Act., p. 3. Sg. are found (<w lang="os">e</w> instead of <w lang="os">естъ</w>, <w lang="os">нъѣ</> for <w lang="os">нwѣст</w>, and <w lang="os">бъѫд</w> for <w lang="os">bеѫдет</w>). </item> <item id="nomina">The old suffix <m lang="os">-нье</m> is written frequently as <m lang="os">-ние</m>, e.g. <w lang="os">знамение</w>, but this orthography is not consistently followed. In other forms <m lang="os">-ье</m> is preffered (cf. <w lang="os">абье</w>, 24r.20). </item> <item id="lexis">The manuscript uses lexis which is believed to be typical of the earliest Gospel translation from Greek, cf. the use of the archaic lexemes <eg lang="os"> баль, жаль, миса, шюи, братръ, небесьскъ, неприъѣзнь, пропѧти, иночѧдъ, врътъ, искрьнъ, грѧсти </eg>could prove this hypothesis. Also, in word-formation the manuscript prefers the old suffix -<m lang="os">ице ѫ</> and not <m lang="os">-ждmы</>. Still, the following forms are considered to be relatively later: <eg lang="os">благодать, написание, дрmѧхл</eg>. </item></list></langCharact> ъ’In this example various parts of the description of Slavonic Codex Marianus are formed as a list of items with the values of the attribute id phonology, verbs, nomina and lexis but this distinction is not absolute and in the description of some other manuscript it could be defined differently.
The formal declaration of this element is:
‘<!ELEMENT langCharact %paraContent;> <!ATTLIST langCharact %a.global; > ’No special attributes are provided for this element.
5.6.6. Conclusions on creation of the manuscript. Time and Place.
5.6.6.1. General Remerks
The place of the manuscript date and place differs in great range in various descriptions. This deviations are not caused by the description of the particular medieval culture, say Byzantine Greek, Slavonic, Latin, Armenian, Georgian, or Hebrew, but rather reflect the more general assumptions. Very often the date of some manuscript is put as part of the heading of the manuscript description.Sometimes, it is accompanied by the place, but more often it is not.
In the electronic model of Repertorium, the place of manuscript date or place of origin is thought as a deduction from the codicological, paleographic and language features of the copy. Therefore, it is put after them, as a conclusion.
The element manuscriptCreation is designed to be a wrapper for the several elements in this section.
The formal declaration of this element is:
‘<!ELEMENT manuscriptCreation (manuscriptDate?, manuscriptPlace?, respStmt?, (bibl | listBibl)?)*> <!ATTLIST manuscriptCreation %a.global; > ’No special attributes are provided for this element.
5.6.6.2. Manuscript's Date
This important information is put as phrase defining the date and on what reasons such a conclusion is made. If it is on the bases of the scribal note, a link to the note description is inserted, if the dating is based on the watermarks and paper description here the pointer should be made. Very kinds of tags for representation of dates are possible to be inserted here, e.g. date, dateRange, or dateStruct.
The formal declaration of this element is:
‘<!ELEMENT manuscriptDate %phrase.seq;> <!ATTLIST manuscriptDate %a.global;> ’No special attributes are provided for this element.
5.6.6.3. The Place of Manuscript's Origin
If there aren't any notes this conclusion should be made only on paleographical and language ground.
The formal definition of this element is:
‘<!ELEMENT manuscriptPlace %phrase.seq;> <!ATTLIST manuscriptPlace %a.global;> ’No special attributes are provided for this element.
5.6.7. The Manuscript Contents
5.6.7.1. General Overview
The manuscript contents in the Repertorium electronic description model is done in three main parts: description of the whole manuscript as single gatherings of texts, description of each text, and if available, description of notes.
The formal declaration of the main element for the content analysis (contentDesc) is:
‘<!ELEMENT contentDesc (manuscriptContentDesc+, articleContentDesc*, noteDesc*)*> <!ATTLIST contentDesc %a.global; > ’No special attributes are provided for this element.
The only mandatory element here is the first one - manuscriptContentDesc. The content of this element should be presented in the catalogues of all possible ranges.
5.6.7.2. The Content of the whole manuscript
The content of the whole manuscript is described in the element <manuscriptContentDesc>. Nothing in this element is mandatory, but the element itself is need to be the XML file valid. The describer could start with the definition of the range of texts in terms of some research tradition, e.g.
‘<manuscriptContentDesc> <overview>Psalter with Prayers and Liturgical Texts</overview> ... </manuscriptContentDesc> ’The formal declaration of this element is:
‘<!ELEMENT manuscriptContentDesc (overview*, numberTexts*, source*, translation*, protograph*, antigraph*, apograph*, litRedaction*, churchCal?, sampleText*, listBibl?, bibl?)> <!ATTLIST manuscriptContentDesc %a.global; type (original | compilation | translation) #IMPLIED style (narrative | non-narrative) #IMPLIED> ’There are two special attributes for this element. By the first one, type, the encoder is expected to answer to the question whether the manuscript collection of texts is originally made by some writer, or it is a compilation or translation. By the second attribute, style, some general answer is expected in terms of very broad typology.
5.6.7.2.1. Number of texts
Sometimes, when the texts of some particular content are compared it could be useful to compare, whether they content some similar amount of texts or not. Of course, this element is not mandatory.
The formal declaration of the element is:
‘<!ELEMENT numberTexts %phrase.seq;> <!ATTLIST numberTexts %a.global; > ’No special elements are provided for this element.
5.6.7.2.2. Texttological Information On the Level of the Whole Manuscript
The textological information on the level of the whole manuscripts is part of the content of the series of elements, like <source>, <translation>, <protograph>, <antigraph>, <apograph>, <litRedaction>, etc. All of them are explained below as part of the structure of the content of each text. What is important for their usage on the level of the whole manuscripts is that they are invoked only in the cases whenconclusions the respectively on the <source>, <protograph>, <litRedaction> etc. for the whole manuscript could be drawn.
5.6.7.2.3. The original text on the level of the whole manuscript
Sometimes, there are collections of texts with some common title or heading, and steady incipit and sometimes even explicit. In this cases, the element<sampleText> could be used. In all other cases the element <sampleText> should be used to illustrate particular texts from the manuscripts, not the whole body of the codex.
5.6.7.3. The textological comment on each text
The information on each text has a structure of 14 elements only two of each are mandatory: text location<textLocation>, and the name of this text given by the researchers (<articleName>). In some cases the texts themselves are composed from various texts, and text parts. In such a cases, the possibility is provided to described such a texts as part of the the other texts. Therefore, it is possible to make description of one text as part of the other texts. In such cases the identification of such dependence could explicitly shown, as in this example:
‘<articleContentDesc id=ACD1> ... (Here is the description of the main text) <articleContentDesc id=ACD1.1> ... (Here is the description of the text which is part of the text identified as ACD1) </articleContentDesc> = end of the description of the "ACD1.1" </articleContentDesc> = end of the description of the "ACD1" ’The formal declaration of this element is:
‘<!ELEMENT articleContentDesc ((textLocation+, articleName+, articleAuthor*, articleData*, source*, translation*, protograph*, antigraph*, apograph*, litRedaction*, churchCal?, sampleText*, listBibl?, respStmt*)+ | (articleContentDesc)*)*> <!ATTLIST articleContentDesc %a.global; type (original | compilation | translation) #IMPLIED style (narrative | non-narrative) #IMPLIED > ’The attributes for this element are the same as in the <manuscriptContentDesc> but as a part of the content of this element they applied on the level of particular text.
5.6.7.3.1. The location of the text
The first group of elements is called<textLocation> and the elements in this group are related with the location of the given text . Three elements form the content of this group: <locNumber>, <position>, and <neighbour>.
The formal declaration of this element is:
‘<!ELEMENT textLocation (locNumber?, position*, neighbour*)> <!ATTLIST textLocation %a.global; > ’No special attributes are provided for this element.
This is non-mandatory but useful element provided for the place of simple numbering. This number could be not the same as is the identification of the text in <articleContentDesc>. The identification of the latter could follow the internal structure of the text, unlike the numbering in <locNumber>.
The formal declaration of the element is:
‘<!ELEMENT locNumber %phrase.seq;> <!ATTLIST locNumber %a.global; > ’No special attributes for this element are provided.
The position of the text is simply identified by enetering a string of pages and lines, e.g. 12r12-15v10 for the manuscripts written in 1 column, or 12b12-15c10 for the manuscripts written in two columns (ab/cd), or three columns (abc/def).
The formal definition of this element is:
‘<!ELEMENT position %phrase.seq;> <!ATTLIST position %a.global;> ’No special attributes for this element are provided.
Sometimes, when the manuscripts consists of texts with no predefined order, for example when they are not in consequence of some calendar or not defined by some external entity, like a Typikon, arise the questions regarding the preceeding or following texts. That is the reason to define such an element with the following formal declaration:
‘<!ELEMENT neighbour %phrase.seq;> <!ATTLIST neighbour %a.global; type (preceding | following) #IMPLIED > ’The attribute type is provided here to give answer whether the text mention in the element content is preceeds or follows the described text.
5.6.7.3.2. The name of the text given by the researcher
In the approach of Repertorium Initiative, there is strict distinction between the text supplied by the researcher (the so called "scientific title" and the original title of the text met in the manuscript copy. It is done because of the great variation among the given titles and headings in the manuscripts and because of the need of attribution of this title to certain author.
Consider the following example:
‘<articleContentDesc n="RM4-14" id="ACD6" style="narrative" type="translation"><textLocation> <locNumber>6. </locNumber> <position>200r-203v: </position></textLocation> <articleName lang="en">Interpretation of the Acts of Apostles. </articleName> <articleAuthor>St. Hyppolitus of Rome. </articleAuthor> <articleData>Interpretation on the 9th Proverb: "Wisdom has built her house".</articleData> <source type="Greek">Migne, PG 10, kol. 952-953. </source> <translation><num>1?</num></translation> <protograph>Bulgarian, </protograph> ... </articleContentDesc> ’If the title is automatically transferred from the original text of the manuscript it should the text should be entitled "About the 12th Apostles. Where each one of them preached". With such a title however we will be not able to compare other copies, where most likely the heading in the manuscript will be completely different. So, the element <articleName> should provide comparable title with other Slavonic and non-Slavonic traditions.
The formal definition of this element is:
‘<!ELEMENT articleName %phrase.seq;> <!ATTLIST articleName %a.global; type CDATA #IMPLIED > ’The attribute type is provided to give some typology of the title.
5.6.7.3.3. The Author of the text
The author of the text supplied by the author is given as content of the element<articleAuthor>. It is the name of the attributed from the encoder author of the text and this author is not always the same which is to be found in the manuscript copy.
The formal definition of this element is:
‘<!ELEMENT articleAuthor %phrase.seq;> <!ATTLIST articleAuthor %a.global; > ’No special attributes are provided for this element.
5.6.7.3.4. Texttological, linguistic or other data related with the text
The data of text which is useful to explain the text tradition but is not directly related with the questions of text's redaction, protograph, etc. but could provide some valuebale information for the explanation of the text tradition, is encoded as part of the content of the element <articleData>. In the example given above, the content of this element is:
‘<articleData>Interpretation on the 9th Proverb: "Wisdom has built her house".</articleData> ’In this example, the element's content explains the title given by the researcher. Without the knowledge that this is just a part of the bigger text, which has its own tradition is impossible to undertake the further steps in the text investigation.
The other possible use of this element is for adding some linguistic data. Unlike the element<langCharact> which is intended to give more or less information on the whole manuscript, the <articleData> could provide some material for the linguistic analysis for the particular text. Consider the example:
‘<articleData type="language"> Only in this text we could find the older forms of the stemmatic Aoristus ...</articleData> ’The third possible application of this element is explanation of some text loses and interpolations which could provide some key for the understanding the text tradition.
The formal declaration of the element is:
‘<!ELEMENT articleData %paraContent;> <!ATTLIST articleData %a.global; type CDATA #IMPLIED > ’The attribute type is provide in order to facilitate the content typology and processes of searching the information.
5.6.7.3.5. The text source
Usually by the source in the Slavonic tradition is meant a Greek or Latin original who served as a base for the translation. In the example above
‘<source type="Greek">Migne, PG 10, col. 952-953. </source> ’is meant not that the given text is a direct source for the translation, but rather it is cited as a parallel to the Slavic text in the described manuscript.
The formal definition of the element is:
‘<!ELEMENT source %paraContent;> <!ATTLIST source %a.global; levelOfCorresp CDATA #IMPLIED type (Greek | other) #IMPLIED > ’The attribute type is given to facilitate the typology of the sources. The attribute levelOfCorrespis provided to give answer whether the text is exact source of the described text or not.
5.6.7.3.6. The text translation
If the text is translated from some other sources, then in the element<translation> the encoder may enter an information on this translation. Usually, it consists of the number of the translation. If the researcher is not sure he/she could add a question mark, e.g.
‘<translation><num>1?</num></translation> ’The formal declaration of this element is:
‘<!ELEMENT translation %paraContent;> <!ATTLIST translation %a.global; > ’No special attributes are provided for this element.
5.6.7.3.7. Special elements for textual criticism
Four elements are provided for the definition of the precise place of the manuscript text among the other copies in the textual tradition. These elements are:<protograph>, <antigraph>, <apograph>, and <litRedaction>. The meaning of these elements is to provide a sound base for research in textual criticism of the medieval texts.
Their formal definition is as follows:
‘<!ELEMENT protograph %paraContent;> <!ATTLIST protograph %a.global; levelOfCorresp CDATA #IMPLIED > <!ELEMENT antigraph %paraContent;> <!ATTLIST antigraph %a.global; levelOfCorresp CDATA #IMPLIED > <!ELEMENT apograph %paraContent;> <!ATTLIST apograph %a.global; levelOfCorresp CDATA #IMPLIED > <!ELEMENT litRedaction %paraContent;> <!ATTLIST litRedaction %a.global; > ’With the exception of<litRedaction> all others have a special attribute levelCorresp which usage is the same as by the element <source>.
5.6.7.4. Description of the notes
5.6.7.4.1. General remarks. The<noteDesc> element
The description of the notes is the third and last element from the description of the manuscript content. In the Repertorium model it is done as part of the<noteDesc> element which could contain description of each note possibly preceeded by the an overview. When the notes are edited and known to the readers a link could be provided for the publication of the material or to its study.
The formal definition of the element is:
‘<!ELEMENT noteDesc (overview | noteItem)*> <!ATTLIST noteDesc %a.global; > ’No special attributes are provided for this element.
5.6.7.4.2. The description of each note
The description of each note consists of a bundle of elements most of which are already explained above.
The formal definition of the element<noteItem> is:
‘<!ELEMENT noteItem (location*, date*, noteContent*, noteAuthor*, noteFormula*, noteData*, palaeoCharact*, orthogrCharact*, langCharact*, source*, translation*, churchCal?, (sampleText | div | div0)*, listBibl?, respStmt*)> <!ATTLIST noteItem %a.global; type (colophon | inscription) #IMPLIED > ’None of this elements is manadatory. A special attribute type is provided to make distinction between the colophon and other type of notes.
The first of the content of element<noteItem> is <location>. Here the position of the note's text should be given relatively to the basic text or as place which appears in the margins, fly leaves, etc.
The formal definition of the element is:
‘<!ELEMENT location %phrase.seq;> <!ATTLIST location %a.global; > ’No special attributes for this element are provided.
The element<date> is provided to give information on the note's date. This element is a standard TEI element and will be explained elsewhere.
For some typology of the particular and for defining its place using some standard terminology an element <noteContent> is provided. A simple example of its usage could be:
‘<noteContent>Inscription of possession</noteContent> ’The formal definition of this element is:
‘<!ELEMENT noteContent %phrase.seq;> <!ATTLIST noteContent %a.global; type CDATA #IMPLIED > ’The type attribute could follow some convinient scheme for typologisation.
Here the name of the author should be given, if known.
The formal definition of the element is:
‘<!ELEMENT noteAuthor %phrase.seq;> <!ATTLIST noteAuthor %a.global; scribe (copyist | editor | binder | reader | commissioner | other) #IMPLIED > ’The attrubute scribe is provided to give a list of the most likely persons who could be in touch with the book or fragment.
Sometimes is useful to have comments on the note in some formalized way. For this reason the element<noteFormula> is provided.
The formal definition of the element is:
‘<!ELEMENT noteFormula %phrase.seq;> <!ATTLIST noteFormula %a.global; type CDATA #IMPLIED > ’The attribute type could provide link to some convinient typology scheme.
The elements<palaeoCharact>, <orthogrChract> and <langCharact> have the same content as explained above, but here they are provided to give characteristics to the note. It is without any doubt that the note could have its own language or paleographic features.
Elements for text history are same as in the element <articleContentDesc>. They are: <source>, <translation>, and <churchCal>. The element <articleData> here is renamed to <noteData> but the meaning of this element is the same. The same is done with the element <articleAuthor> which here is <noteAuthor> in the case that there could be examples in which the one and same author uses various ways to identify himself.
The features of the decoration in the note are invoked by using the element<decoration> which is already explained elsewhere.
5.6.7.5. The elements history and additional
These elements will be present in the next major revision of TEI "Guidelines ..." — P5. The current practice of Repertorium in using these elements could be changed in accordance to the TEI practice.
6. Technical documentation
The technical docmentation of the model is availlable in a separate file here (automatically created 2Mb HTML file).
7. Changes in the structure of TEI models
The Repertorium Initiative model have extended some of declarations of the TEI entities: classes, models and elements. Here is the preliminary scetch of this changes.
7.1. Inclusion of the element msDesc in the body
The elements msDesc is included on the same level as the component, thus allowing a specialized description to appear at the same level as the elements in text divisions, (such as div) paragraphs or in the phrase elements. At the same the msDesc is not a part of the %component;. That means that the element could appear only once immediately after the element bodyas part of its structure. The formal declaration of the element body is changed in this way:
7.2. New elements at the beginning (at the top) and at the end (at the bottom) of the text divisions
To encode the beginnings and endings of the texts was necessary to include new elements to the divtop and divbot. The new elements in these classes are: incipit for the class divtop, explicit for the class divbot and rubric for the both classes. So, the declarations are changed to:
‘ <!ENTITY % m.divbot 'byline | closer | dateline | epigraph | explicit | salute | rubric | signed | trailer'> <!ENTITY % m.divtop 'argument | byline | dateline | docAuthor | docDate | epigraph | incipit | head | opener | rubric | salute | signed | title'> ’These new elements have the following markup declarations:
7.3. New element for encoding the original texts
In addition to element of un-numbered and numbered divisions of TEI, the Repertorium model introduces the new element sampleText. This model is provided to separate the data written by the encoder from the original Medieval text. The element has the same structure as the element div with one exception. It has an attribute type with the legal values normative and nonnormative. This is necessary to distinguished between the text with the original orthography and the text which is entered according to some encoding principles of the project.
7.4. Some elements in the middle of the divisions
Sometimes, it is necessary to define some additional elements in the encoding of the Medieval text. They are used to provide an extra information in the text edition. The Repertorium introduces the following elements:
The element sup is used in cases there is a need to encode that the element is written above the normal level of the text. The element ligature encodes the possible fusion of two or more chararacter objects. The element mood is provided to encode the different musical levels in the melody (moodes) . The formal declarations of these elements are:
7.5. Changes in the models
Some specialized elements were necessary to be introduced on the level of phrase. The following changes were made:
Inclusion of elements churchCal (i. e. church calendar), colour, saintName (i. e. to encode the name of some saint in the text) in the content of the model class data. The declaration of this model is now as follows:
7.6. Changes in the parametrization classes
In the parametrization classes the several changes are introduced:
The %specialPara; is extended to include the element location. Now the declaration is:
‘<!ENTITY % specialPara '(#PCDATA | %m.phrase; | %m.inter; | %m.chunk; | %m.Incl; | location)*'> ’There are two new parameter classes in the model. The first one (%waterPara;) is used to serve as a content for the elements watermark and countermark, the second one, palaeoPara is used for the paleographic description of the manuscripts. The both have the following formal definitions:
7.7. Changes in attribute classes
The content of the attribute class %a.pointer;is extended to include XLINK structure. Now the definition is:
7.8. Character entities
In addition to the character enetities provided with the TEI DTD and schema fragments, the Repertorium uses a special inventory of Old Cyrillic character enities (the file ocyr.ent) and the XML formulation of Ancient Greek characters (the file ISOgrk5r.ent). It is possible that in future practice, using XML Schema mechanisms instead of DTD and the full potential of UNICODE tables, they will be dropped entirely.