-
-
- Syriac Manuscripts in the British Library: TEI P5 Customization and Encoding
- Guidelines for Manuscript Description
-
-
-
-
-
-
-
-
-
-
Syriac Manuscripts in the British Library: TEI P5
- Customization and Encoding Guidelines for Manuscript Description
-
This version of the encoding
- guidelines for Syriac Manuscripts in the British Library: A New Digital Edition of Wright’s
- Catalogue were drafted in 2024 by David A. Michelson with assistance
- from William L. Potter and Daniel L. Schwartz. These guidelines are part of a larger a
- community effort to develop uniform good practice in the cataloguing manuscripts using
- TEI. They are derived from a common consolidated schema currently used by cataloguers at
- a number of institutions including the British Library, the Bodleian Libraries,
- Cambridge University Library, the John Rylands Library, and the Wellcome Trust. They
- remain under development and contributions are welcome via pull requests or issues
- submitted to the GitHub repository hosted by Syriaca.org. They are licensced under a Creative
- Commons Attribution 4.0 International license. Users may cite the guidelines in
- this way: David A. Michelson, et. al., eds. Syriac Manuscripts in
- the British Library: TEI P5 Customization and Encoding Guidelines for Manuscript
- Description (Syriaca.org: 2024), https://github.com/srophe/britishLibrary/blob/main/documentation/schema/Syriacamsdesc.html.
Welcome to the encoding guidelines for Syriac Manuscripts in
- the British Library: A New Digital Edition of Wright’s Catalogue.
- These guidelines describe the methodology used to create TEI XML files for describing Syriac
- manuscripts according to the schema implemented by Syriaca.org in the project Syriac
- Manuscripts in the British Library. For the moment, these
- guidelines cover only the description rather than the transcription of
- manuscripts. Syriaca,org hopes to expand these guidelines to include
- transcription in the future. We have chosen to use the TEI guidelines because
- they allow both a high level of detail and flexibility. We anticipate that this
- schema can be easily adapted for other Syriac manuscript catalogues and we
- invite comments and suggestions for improvement.
-
-
-
1.2. Acknowledgements
-
These guidelines are based on the following sources. The general editors began by
- following the encoding guidelines for the Fihrist Union
- Catalogue of Manuscripts from the Islamicate World and the ENRICH TEI P5 ODD, which were then
- modified by Syriaca.org into a Syriaca TEI for MSS Manual (now
- deprecated). In many cases, we reproduced the Fihrist guidelines
- verbatim. In turn these earlier encoding guidelines were updated in 2024 to be
- largely compatible with the Consolidated TEI P5 Customization and Encoding Guidelines
- for Manuscript Description for western medieval manuscripts
- jointly created by Cambridge University Library (James Freeman, with Suzanne
- Paul) and the Bodleian Library (Matthew Holford) with contributions by Andrew
- Dunning (formerly British Library) and James Cummings. When applicable, we have
- reproduced the consolidated guidelines verbatim in our own guidelines. (Those
- consolidated guidelines in turn draw in places on earlier western medieval
- manuscript guidelines created by Patrick Granholm and Eva Nyström for manuscripta.se.)
-
-
-
1.3. General
- Principles
-
It is essential to note that we have customized these guidelines specifically for
- use in digitally encoding the manuscript descriptions made by William Wright in
- his Catalogue of Syriac Manuscripts in the British
- Museum (3 vols., 1870-1872). Due to this specialized use, these
- guidelines do not include all possible TEI XML features which might be desired
- either for cataloguing Syriac manuscripts or for medieval manuscripts in
- general. For example, because Wright does not provide detailed descriptions
- ofthe modern custodial history of the manuscripts we have not utlized those
- features in these guidelines. Similarly, because the main language of Wright's
- catalogue is English, these guidelines assume that each file will have English
- as its main language.
-
In addition, we have followed the guidelines below with the assumption that the
- resulting XML files for the Syriac Manuscripts in the British
- Library project (hereafter SMBL) will
- be displayed using the custom Srophe App developed by Syriaca.org. We
- have also made an effort to ensure compatibility (as much as possible) with the
- HTML tools and transformations developed for the Consolidated TEI P5 Guidelines for Manuscript
- Description.
-
-
1.3.1. Editorial Notes
- and Interventions
-
Syriac
- Manuscripts in the British Library: A New Digital Edition of
- Wright’s Catalogue has been concieved of as a digital
- representation of William Wright's catalogue. SMBL is not intended to be a revision of Wright or a
- re-cataloguing of the manuscripts themselves. For the vast majority of
- manuscripts described in this project, we (the editors of SMBL) have reproduced Wright's prose verbatim
- without verifying his descriptions against the manuscripts. While that level
- of comparison is beyond the scope of this present project, we hope that the
- digital encoding of SMBL might serve as a
- foundation for such a new cataloguing effort in the future.
-
In general we make no claims about the reliability of Wright's descriptions
- as reproduced in SMBL. Because our goal was to
- encode Wright's catalogue as written, we have reproduced his attributions of
- authorship and his dating of the manuscripts, even in cases where these may
- now be disputed or revised by subsequent scholarship. We, ofcourse, agree
- that such an update to his catalogue would be valuable in the future. SMBL is published under an open access license and
- we would be delighted to collaborate with any interested scholars in such a
- future update. Such a revision, however, needs a base text as a starting
- point, hence our decision to encode Wright's catalogue "as is" in the first
- edition of SMBL.
-
Even with the stated goal of verbatim reproduction, we have had to make a few
- editorial interventions during the course of encoding. In most casese, these
- interventions were necessitated by the precision of encoding which required
- us to make explicit some data which Wright may have left implicit or
- imprecise in his prose. These interventions have occured in the following
- primary cases (each of which follow the principles of Wright's own
- descriptions):
-
-
When our editors have found a clear typographical or
- internal inconsistency in Wright's descriptions, we have corrected these
- errors for the sake of clarity.
-
When our editors have discovered inconsistency in Wright's
- identification of codicological units, we have further divided single
- shelfmarks into further manuscript parts in a method similar to that
- used by Wright himself. Most often our editorial interventions in this
- regard have been to identify fly-leaves as separate manuscript fragments
- when Wright may have grouped them together. These new codicological
- divisions are identifiable because they will share the same roman
- numeral from Wright's print catalogue but each have a different
- URI.
-
When Wright has lapsed from his usually methodical listing
- and numbering of manuscript items, we have attempted in some cases to
- adapt Wright's prose back to the form of a list of manuscript contents.
- For example, we have frequently made this editorial intervention when
- Wright has chosen to describe the undertext of a palimpsest in a
- paragraph rather than an as an outline of contents.
-
-
Finally, SMBL has made one further type of
- modern editorial intervention in Wright's prose. In the century and a half
- that have passed since Wright wrote, scholarly values concerning the
- preservation of cultural heritage have changed profoundly. In some cases,
- Wright's descriptions reflect his prejudices as a European scholar in the
- nineteenth century. Because SMBL is an open
- access resource widely available on the internet, we did not wish to
- reproduce Wright's prose without context. Accordingly, in some places in
- which Wright expressed pejorative or other derogratory opinions, we have
- added an editorial note to indicate that these opinions do not reflect the
- opinions of the editors of SMBL nor do they
- represent the approach of contemporary scholars in the field of Syriac
- studies. ]
-
Editorial notes made by SMBL related
- to the various interventions described above have been encoded with the <note>
- element with type of ‘editorial’. This type distinguishes
- these editorial notes from notes made by Wright himself which are either
- without any type or marked as type of ‘footnote’. An example of an
- modern editorial note is as follows:
- <note type="editorial">
- <!-- Need to make example from
- https://bl.syriac.uk/ms/363 -->
- </note>
-
-
-
-
1.3.2. References to
- Locations within a Manuscript
-
References to a specific location or range of folia within a
- manuscripts are given in a <locus> element which can be inserted
- within a number of different elements. The <locus> element marks
- the location of the parent element’s material within the manuscript and thus
- should be nested within the element it modifies. Typically the <locus> will refer to a folio or a range of folio numbers
- within the manuscript. When describing folio numbers, it is our policy to
- follow Wright's usage and use ‘a’ to refer to the
- recto of a folio, and ‘b’ to refer to the verso.
- Where Wright does not specify recto or verso, we encoded a folio number
- without ‘a’ or ‘b’. In prose,
- there should always be a whitespace between the folio number and the ‘a’ or ‘b’. But in attribute
- values, there should be no whitespace, e.g. ‘232b’:
-
<locus from="232b">Fol. 232 b</locus>
-
A text node (eg. ‘foll. 21 a-22 b’) is not required
- for many uses of <locus> (such as when it is used nested in an <msItem>), but least one attribute value must also be encoded
- with every <locus>, either from or to or both. (Since Wright's catalogue does not often
- give ending ranges, the to occurs less in the
- data). These attribute values may be used in the future to enable links to
- folio images or calculation of lengths of manuscript items. Frequently in
- Wright’s catalogue the beginning location of a manuscript item is given, but
- not the ending location. In this situation, our policy is to record only the
- listed opening location in Wright’s catalogue as the beginning of the range
- in the attribute from. We do not supply a to attribute unless Wright has indicated on what
- folio the msItem ends, for example by citing an <explicit> or <finalRubric>.
-
The following examples illustrate common uses of <locus>. Whenever possible, the designation folio/folia and
- their abbreviations were included in the text node of <locus>. as in the
- exampls below. (Please be aware that Wright uses "Fol." for a single folio
- and "Foll." for a range of folia. We adapt Wright's capitalization of based
- on context. If "Fol." stands alone in a list it is capitalized. If "fol."
- occurs in the middle of other prose it is capitalized according to the rules
- of the sentence.):
<msItem><locus from="232b">Fol. 232 b</locus><title ref="http://syriaca.org/work/9687"
- xml:lang="en">The Gospel of S.
- Matthew</title>
- </msItem>
- <!--...-->
- <additions><list><item>
- <label>Colophon</label><locus from="184a"/><p>Of the note written by the scribe on
- <locus from="184a">fol. 184 a</locus> the greater part has been erased, but
- from what remains it appears that this book was copied for <persName>a priest named
- Lazarus</persName>.</p></item></list>
- </additions>
-
Notes for Review Editors (2024)
-
Please ignore the missing white space in the text node of <locus> For example, in the text nodes of locus for folia
- numbers, such as
<locus from="81a">fol. 81a</locus>
this text node should have a space
- between ‘81’ and ‘a’ like this
-
<locus from="81a">fol. 81 a</locus>
, but you do not need to
- change it, we have a script make this correction across all the data. Note:
- This section is provided for the convenience of the editors undertaking a
- revision of the data in 2024 and will be deleted from the final
- documentation.
-
Deprecated Practices and Legacy Data:
-
As a legacy of an earlier encoding model, the SMBL data contains some folio ranges encoded as numerals in
- to without "a" or "b". In this earlier data
- model, we attempted to deduce the end of ranges for manuscript items when
- not specified by Wright. Similarly when Wright's prose indicated that his
- description applied only to a single folio (for example when describing a
- marginal note), our policy was previously to list that location in both
- from and to
- attributes. After 2022, we ceased to encode in this way. While we have left
- these estimates in the data, documents revised since 2022 longer add
- estimated data in this way.
-
Divergences from Consolidated Schema:
-
In SMBL we have assumed that <locus> refers to a
- folio or folio range unless otherwise indicated. Accordingly, we do not use
- the scheme attribute to indicate the foliation
- scheme except in cases where the <locus> refers to something other than a
- folio, such as a column.
-
-
-
1.3.3. Indentification
- of Persons, Places, Titles, Citations, and Manuscripts with Syriaca.org
- URIs
In these authority files, each entity is an individual abstract concept
- identified by a unique URI. For example, the person known as Ephrem the
- Syrian is identified by the URI: http://syriaca.org/person/13 and
- the city of Edessa where he spent much of his life is identified as http://syriaca.org/place/78. The necessity of using unique strings
- of characters instead of traditional names arises from the occurrence of
- homonymous entities. For example, The Syriac
- Gazetteer has entries for 69 different churches and monasteries
- each with the name ‘Mar George’. Accordingly, all
- Syriaca.org URIs are unique—each identifying only one conceptual entity.
- Thus, every ‘Church of Mar George’ is assigned a
- separate URI.
-
Syriaca.org URIs are not merely random strings of text and numbers; they are
- HTTP URIs, meaning that each URI is also a URL (a Uniform Resource Locator,
- e.g. an HTTP address). Thus, Syriaca.org’s URI for Ephrem the Syrian, http://syriaca.org/person/13, is also a valid HTTP address. The
- benefit of using HTTP URIs is that these URIs are ‘self-descriptive’ in that each URI is also an HTTP link to a
- web document describing or defining the concept identified by the URI.
- Although perhaps obvious to state, the web document which is returned from a
- Syriaca.org URI is only a definition of the concept named by the URI, not
- the entity itself (thus the address http://syriaca.org/place/78 does
- not allow one to download the real-world city of Edessa, but a web page
- describing that city!).
-
In the Syriaca.org data model, each URI represents a conceptual thing with a
- mental existence related to, but not reducible to, its historical or
- physical manifestation. Syriaca.org adopted this broad definition so that
- mythological and other ahistorical persons, places, and concepts can be
- assigned URIs. For example, the concept identified by the URI http://syriaca.org/person/13 identifies not only the historical
- person Ephrem the Syrian, but also the supra-historical hagiographical and
- pseudepigraphal traditions about him. Following this same logic, any
- historical concept can be described in the Syriaca.org URI model, even if
- its historical existence was only in the cultural imaginary.
-
The Syriaca.org authority files and URIs are central to the data model of
- SMBL, accordingly the sections below
- describe in greater detail how we have encoded these entities throughout the
- data.
-
Notes for Review Editors (2024)
-
If you find that a <persName>, a <placeName>,
- or a <bibl> used for a modern bibliographic citation is missing a
- URI, please follow these steps: Search for a URI at Syriaca.org or the Comprehensive Syriac Bibliography If you do not find a URI, create
- a temporary URI following the guidelines provided to you. Insert the new
- temporary id into the ref for the <persName> or <placeName> or in bibl/ref/target (you will need to create the <ref> and
- add it inside the <bibl>). Note: You do NOT need to add URIs to <title> or <ref> elements for Syriac literary works
- except in the case of books of the Bible. There are Syriaca.org URIs
- available for those, so please mark those if possible. Note: This section is
- provided for the convenience of the editors undertaking a revision of the
- data in 2024 and will be deleted from the final documentation.
-
-
1.3.3.1. Personal
- Names
-
As a general rule personal names have been tagged, for
- example when they occure inside the elements <author>, <editor> or in any descriptive element such as the <handNote> or an <item> in <additions>. In these cases, the name is wrapped with the
- element <persName> and the language(s) of
- the name supplied with attribute xml:lang.
- Exceptions to this rule were made when a personal names occurs as part
- of a title of a work (Extracts from the Homilies of
- John Chrysostom) or as part of a place name (e.g. The Convent
- of Mar Isaac). In these cases the prose was marked as a title or place
- name instead and the personal names were not tagged:
<msItem><title xml:lang="en">Works of Gregory
- bar Hebraeus</title>
- </msItem>
<origPlace ref="http://syriaca.org/place/360">Convent of
- S. Mary Deipara.</origPlace>
-
All <persName> elements (or else the
- containing <author> or <editor> element) are required to
- have a ref attribute which points to a
- Syriaca.org person URI published in the Syriac Biographical Dictionary. A URI is a Uniform
- Resource Identifier which is a unique identifying number for each
- person. For example the URI https://syriaca.org/person/13 identifies Ephrem the Syrian in
- this first example:
The <persName> element can also be
- used inside prose descriptions.
<note>
- <persName ref="http://syriaca.org/person/51">Severus</persName> is cited on <locus from="224a">fol. 224 a</locus>. </note>
-
Notes for Review Editors (2024)
-
In some files we may have previously over-normalized the spelling of
- author names compared to what Wright provides (e.g., changing Jacob of
- Batnae to Jacob of Serugh). We now wish to revert these changes, so
- please check and restore the name spelling as Wright provides it. Note:
- This section is provided for the convenience of the editors undertaking
- a revision of the data in 2024 and will be deleted from the final
- documentation.
-
Deprecated Practices and Legacy Data:
-
Our policy is to report the names in the same prose given by
- Wright. In a future update of SMBL, we may
- also provide a uniform name where the spelling or name used by Wright is
- no longer commonly used in scholarship. A few examples of these are
- already present in our data in the form below (where the "supplied"
- type reflects Wright's Romanization of the
- name. Encoders should not enter these "uniform" names as they will be
- inserted later by a script.
Because Syriaca.org already provides an integrated authority file for
- persons using Syriaca.org URIs, we do not use the key attribute required by the Consolidated Schema. We also
- do not use the element <orgName> since it
- is not a useful entity for our historical data, instead Syriaca.org uses
- the <persName> element in a slightly broader manner than the
- TEI guidelines. A <persName> element may be used to
- refer to a name for a single person or a group of persons.
-
-
-
1.3.3.2. Place
- Names
-
As a general rule place names have been tagged with either <origPlace> or with <placeName>, for example when they occur inside in any
- descriptive element such as <note>, <handNote>,
- or an <item> in <additions>. In most cases, the
- place name is wrapped with the element <placeName> and the language(s) of the name supplied with
- attribute xml:lang. Exceptions to this rule are
- as follows:
-
-
In the description of the manuscript origin (on which,
- see more documentation below), the prose place name is placed
- directly in the text node of the <origPlace> element (without using <placeName>) while any other place names mentioned in
- reference to the place of origin are wrapped in <placeName>:
<origPlace ref="http://syriaca.org/place/360">Convent
- of S. Mary Deipara, in the desert of <placeName ref="http://syriaca.org/place/289">Scete</placeName>.</origPlace>
.
-
When a place name occurs as part of a title of a work,
- it is not marked as a <placeName>:
<title>Hom. liii. On the
- calamities reported to have befallen the city of Alexandria</title>
nor is a place
- name marked when it is part of a personal name:
<persName>Paul of
- Callinicus</persName>
In these cases (shown above) the
- prose was marked as a title (using either <title> or <ref>) or <persName> instead and the
- internal references t0 place names were not tagged.
-
-
All <placeName> elements or <origPlace> elements are required to have a ref attribute which points to a Syriaca.org place
- URI published in The
- Syriac Gazetteer. A URI is a Uniform Resource
- Identifier which is a unique identifying number for each place. For
- example the URI http://syriaca.org/place/78 identifies the city of Edessa in
- these examples:
<p>On <locus from="258a">fol. 258
- a</locus>, after the
- doxology, we read the following note, giving the date and stating
- that the volume was written at <placeName ref="http://syriaca.org/place/78">Edessa</placeName>, at the expense of the
- deacon <persName>Thomas of
- Zěmārtā Castra</persName>.</p>
-
Our policy is to report the place names in exactly the same prose given
- by Wright. In a future update of SMBL, we
- may also provide a uniform name where the spelling or name used by
- Wright is no longer commonly used in scholarship.
-
Divergences from Consolidated Schema:
-
Because Syriaca.org already provides an integrated authority file for
- places using Syriaca.org URIs, we do not use the key attribute required by the Consolidated Schema nor do we
- include the nested information in <origPlace> such as <country>, <region> and <settlement>. These
- relationships can be found separately in The
- Syriac Gazetteer.
-
-
-
1.3.3.3. References to Literary Works
-
As a general rule references to titles of literary works have been tagged
- in one of two methods.
-
-
When the title is identifying the intellectual contents
- of a manuscript item, it is encoded with <title> as a
- child of <msItem>. When encoding with
- the <title> element, the language of the prose in the <title> text node must also be indicated with
- attribute xml:lang. Rules for encoding
- titles as part of manuscript items are discussed in greater detail
- below.
-
When a reference to a literary work is made elsewhere
- in the XML document it is encoded with <ref> as a child
- of <note>.
-
-
At present the state of authority control for titles of
- Syriac works is incomplete, so we have not required references to URIs
- for works in SMBL. When possible we have
- included URIs published in The
- New Handbook of Syriac Literature . A URI is a
- Uniform Resource Identifier which is a unique identifying number for
- each literary work (as a conceptual entity). References to URIs for
- literary works, (using either <title> or <ref>) are marked up
- in an attribute value. For <title> the URI is placed in a ref attribute. For the element <ref>
- the URI is placed in a target attribute. For
- example the URI http://syriaca.org/work/1 identifies the book of Genesis in the
- Peshitta Version in this <title>:
<msItem xml:id="a1" n="1" defective="true"><locus from="1a"/><title xml:lang="en" ref="http://syriaca.org/work/1">The book of
- Genesis, according to the Peshitta version.</title><rubric xml:lang="syr"><locus from="2b" to="2b"/>ܒܪܝܬܐ ܣ̣ܦܪܐ ܩܕܡܝܐ ܕܐܘܪܝܬܐ</rubric>
- </msItem>
In this example, a
- <note> refers to a work, the Constitutiones Apostolorum,
- for which there is no Syriaca.org URI. In this case no target is used, but the instead a type attribute value of "work" must be applied (to
- distiguish from other uses of <ref> in the XML document.
<note>These are extracts from <ref type="work">the eighth book of the Constitutiones
- Apostolorum</ref>; see <bibl>Labbe, t. i., coll. 153,
- seqq.</bibl>.</note>
-
Our policy is to report the references to works in exactly the same prose
- given by Wright. In a future update of SMBL,
- we may also provide a uniform name where the form used by Wright is no
- longer commonly used in scholarship.
-
Divergences from Consolidated Schema:
-
Because Syriaca.org already provides an integrated URI authority file for
- works using Syriaca.org URIs, we do not use the key attribute recommended by the Consolidated Schema.
-
-
-
1.3.3.4. Bibliographic Citations
-
Citations of printed biblographic items (books, articles, etc.) have been
- tagged with the <bibl> element. These citations can
- be found in two places:
-
-
They may be grouped in a bibliography located in the <additional> section of
- each entry. Guidelines for this bibliography (including examples of
- child elements nested in <bibl>) are given below.
-
Citations have also been marked up with <bibl> throughout the manuscript description occuring
- as child elements of <msItem>, <note>, or other
- descriptive elements. For this second form of citation, we have
- generally refrained from adding additional markup inside the <bibl> element except for linking to URIs.
-
-
In both cases, the bibliographic citation may be linked with a URI by
- using a child element <ref> with the URI is placed in a
- target attribute on <ref>. At present the
- state of authority control for Syriac bibliography is incomplete.
- Accordingly, we have only encoded URIs for bibliographic citations when
- available. Currently we rely on two sources of URIs. Some citations are
- linked with uris of the format ‘http://syriaca.org/bibl/8’ from Syriaca.org. Others are
- marked with URIs from The Comprehensive Bibliography on Syriac Studies
- of the format ‘https://www.zotero.org/groups/4861694/a_comprehensive_bibliography_on_syriac_studies/items/WMADLJWW/library’.
- In a future development, all of these citation URIs will be merged to a
- format of ‘http://syriaca.org/cbss/WMADLJWW’.
-
This modified example from https://bl.syriac.uk/ms/28
- illustrates the use of the second type of citation:
<note>See<bibl>Assemani, Bibl. Or., t. ii., p. 335 <ref target="https://www.zotero.org/groups/4861694/a_comprehensive_bibliography_on_syriac_studies/items/WMADLJWW/library"/>
- </bibl>.</note>
-
Our policy is to report the references to bibliography in exactly the
- same prose given by Wright. In a future update of SMBL, we may also provide a uniform citation where the form
- used by Wright is no longer commonly used in scholarship.
-
-
-
1.3.3.5. Cross-References to Other Manuscripts
-
Cross-references in the description to other manuscripts should be
- enclosed in <bibl> tags with type of value
- MS. When possible the cross-reference may
- also be linked linked with a child <ptr> element with target attribute pointing to the URI for the other
- manuscript.
-
At present the state of authority control for Syriac
- manuscripts is incomplete. Accordingly, we have only encoded URIs in the
- case of cross-reference to manuscripts within SMBL. This example from manuscript Add. 14,533 https://bl.syriac.uk/ms/260 shows how SMBL URIs are encoded to show a relationship between Add.
- 14,533 and two other manuscripts (Add. 12,155 and Add. 14,532):
<note>In part identical with the
- contents of <bibl type="MS">Add. 12,155<ptr target="https://bl.syriac.uk/ms/30"/></bibl> and <bibl type="MS">Add. 14,532<ptr target="https://bl.syriac.uk/ms/259"/></bibl>.</note>
When a manuscript reference refers
- either to a folio locus or to an entry number in Wright's catalogue,
- then a <citedRange> element should be
- added inside the <bibl>.
For references to manuscripts outside of SMBL we do not include a URI as illustrated in this modifed
- example from https://bl.syriac.uk/ms/739
-
<note type="footnote" xml:lang="en">See the similar heading in the <bibl type="MS">Bodleian manuscript, Hunt. 109</bibl>.</note>
-
Our policy is to report the references to manuscripts in exactly the same
- prose given by Wright. In a future update of SMBL, we may also provide a uniform shelfmark where the form
- used by Wright is no longer commonly used in scholarship.
-
Divergences from Consolidated Schema:
-
SMBL has used <citedRange> which is not mentioned in the Consolidated
- Schema guidelines but is conformant with the TEI guidelines.
-
-
-
-
1.3.4. Formatting
-
We have avoided marking up formatting using the <hi> element. The empty
- element <lb>
- has been used to indicate line breaks (e.g. line beginnings) when Wright
- provides transcriptions of Syriac or Arabic text.
-
-
-
1.3.5. Attribute
- values
-
Some attributes can take more than one value, in which case the
- values are separated by a single whitespace. For example, in this case two
- Syriaca.org work URIs are included in the same ref:
-
<title xml:lang="en" ref="http://syriaca.org/work/9568
- http://syriaca.org/work/9542">Jeremiah and
- Lamentations</title>
-
Attribute values forming more than one word in natural language
- have been separated by a hyphen, - (U+2010), as in this example of medium:
<handNote xml:id="handNote2" scope="minor" script="syr" medium="red-ink"><ref target="#a2"/>The Ammonian sections and Eusebian
- canons are marked in the text with red ink. </handNote>
-
In a few rare cases, ‘camelCase’, has been used for
- attribute values forming more than one word in natural language.
-
Divergences from Consolidated Schema:
-
SMBL has prefered to use a hyphen rather that
- camelCase for attribute values longer than one word in length.
-
-
-
1.3.6. Transcription
-
The <rubric>, <incipit>, <explicit>, <finalRubric>, and <quote> elements are used to encode
- Syriac text transcribed from the manuscripts. The have been reproduced
- verbatim from William Wright's catalogue. Caveat lector! Transcriptions have not been re-checked against
- the original manuscripts. In addition, the <quote> element has
- been used to encode prose (in any language) which Wright marked with
- quotation marks (e.g. inverted commas).
-
In all cases these elements should be marked with the an xml:lang attribute to indicate the language of the transcribed
- text.
-
-
1.3.6.1. Abbreviations and Expansions
-
Sometimes Wright offers an expansion of abbreviations found
- in the manuscripts. In these cases we have provided Wright's expanded
- prose using the nesting elements <choice> and children <abbr>, and <expan>. In these cases, Wright is
- credited as the one responsible for the expansion through the use of
- resp with a value pointing to the xml:id
- for Wright: https://bl.syriac.uk/documentation/editors.xml#wwright. See
- this modified example from Add. 17,262 (https://bl.syriac.uk/ms/1078) in which Wright expands a Syriac
- abbreviation:
For the sake of clarity, the SMBL
- editors have sometimes expanded abbreviations in Wright's own prose
- using the nesting elements <choice> and children <abbr>, and <expan>. This is one of the few ways
- in which we have modified Wright's original publication. See this
- example in which we have expanded ‘Ps.’ to ‘Psalm’ to facilitate search results:
<title>Commentary on <choice><abbr>Ps.</abbr><expan>Psalm</expan></choice> xcii.</title>
-
Divergences from Consolidated Schema:
-
SMBL has prefered to use a <abbr>, and <expan> rather than <ex> as
- used in the Consolidated Schema.
-
-
-
1.3.6.2. Sic
- [UNDER REVISION]
-
SMBL uses <sic> to both to mark errors reported
- by Wright using ‘sic’ and to report mistakes made
- by Wright identified by the SMBL editors. At
- present we are still revising our guidelines on the use of <sic>
- and those will be added here once this revision is complete. We are also
- considering how to represent questions marks used by Wright in the
- text.
-
Notes for Review Editors (2024)
-
Please ignore the use of <sic> as an element or in prose.
- Similarly please ignore Wright's use of square brackets [...]. These
- will be normalized by a script at a later stage. Note: This section is
- provided for the convenience of the editors undertaking a revision of
- the data in 2024 and will be deleted from the final documentation.
-
-
-
1.3.6.3. Supplied
- [UNDER REVISION]
-
The <supplied> element has been used both for Wright's own
- editorial additions and for editorial additions to Wright's catalogue
- made by the editors of SMBL, At present we
- are still revising our guidelines on the use of <supplied>
- and those will be added here once this revision is complete. These
- guidelines will include the use of resp with a
- value pointing to the xml:id for Wright or the modern SMBL editors and
- the use of the nesting elements <choice> and children <orig>, and <reg>.
-
Notes for Review Editors (2024)
-
Please ignore the use of <supplied> as an element, as an
- attribute value or in prose. These will be normalized by a script at a
- later stage. Note: This section is provided for the convenience of the
- editors undertaking a revision of the data in 2024 and will be deleted
- from the final documentation.
-
-
-
1.3.6.4. Deletions
- [UNDER REVISION]
-
in rare cases, deletions by the scribe or later annotators which are
- reported by Wright have be recorded using the <del> element. At
- present we are still revising our guidelines on the use of <supplied> and those will be added here once this
- revision is complete.
-
-
-
1.3.6.5. Gaps
- [UNDER REVISION]
-
In rare cases, gaps in the manuscriptwhich are reported by Wright have be
- recorded using the <gap> element. At present we are still
- revising our guidelines on the use of <supplied>
- and those will be added here once this revision is complete.
-
-
-
-
1.3.7. Quotations from
- the Manuscript
-
When Wright gives a quotations from a manuscript, outside of elements such as
- <incipit>, <explicit> and so on, these have been
- enclosed in the <quote> element and marked with an xml:lang attribute.
-
In addition, <quote> has been used whenever Wright provides text in
- quotation marks, which may be a quotation of a third source (beyond the
- manuscripts and his catalogue) or which may be his English translation of a
- quotation from a manuscript.
-
Divergences from Consolidated Schema:
-
SMBL uses the <quote> element
- instead of the <q> element used in the Consolidated Schema.
-
-
-
1.3.8. Phrases and
- Words in Languages Other Than English
-
Phrases or words in other languages than English are tagged by adding the
- xml:lang attribute to the element enclosing the
- text, or where no other element is available with a <foreign> element
- and a xml:lang attribute.
By default the Srophe App will display text in the <foreign> in
- italic unless it is marked as Syriac, in which case additional right-to-left
- formatting will be applied. For a list of allowed language attribute values
- see
- below.
-
-
-
1.3.9. Transcription
- of Characters, Symbols, and Diacritics in Unicode
-
All text and symbols have been encoded using the Unicode Standard. When Wright has
- Romanized Syriac characters, we have followed his Romanization system and
- used unicode diacritics for macrons, dots above, below, etc. For
- representation of alaph (ܐ) and ʿayin (ʿē, ܥ) we have changed Wright's use
- of apostrophe (') for the unicode half-ring characters, U+02BE ʾ Modifier
- Letter Right Half Ring and U+02BF ʿ Modifier Letter Left Half Ring,
- respectively.
-
-
1.3.9.1. Images
- and Characters that Cannot be Encoded
-
Wright's printed catalogue includes characters and symbols for which
- there is not yet a unicode character or code point. Examples include the
- use of omega as a Syriac vowel or the use of crosses, circles, and dots
- as end of paragraph markers. In the cases where unicode characters are
- not available or where Wright provides a diagram or image which cannot
- be reproduced using XML (for example characters arranged as a cross or
- circle), we have included a note in the <decoDesc>
- referring users to a .pdf version of Wright's catalogue.
<decoDesc><decoNote type="missingContent">The
- printed edition of Wright's catalogue contains characters or
- images which cannot be encoded for display as electronic text.
- Please refer to the printed catalogue to view these characters
- or images. </decoNote>
- </decoDesc>
-
Notes for Review Editors (2024)
-
If you need to enter transliterated or Romanized Syriac using Latin
- characters, please use combined Unicode characters (e.g. U+1E6D Latin
- Small Letter T with Dot Below) for dots and diacritics to represent
- characters such as ḥ, ṭ, ṣ, š, etc. For representation of alaph (ܐ) and
- ʿayin (ʿē, ܥ), please change Wright's use of apostrophe to the unicode
- half-ring characters, U+02BE ʾ MODIFIER LETTER RIGHT HALF RING (for
- aleph) and U+02BF ʿ MODIFIER LETTER LEFT HALF RING (for ʿayin,
- respectively). You can cut and paste most of these characters from the
- list here. In some cases you may find the characters $ or % in the
- text. These were used in an early stage to mark where to enter non-Roman
- text. $ indicates Syriac text should be entered. In most cases you
- should check to see if the Syriac is complete, most likely it was
- entered but this character was not deleted, if so you may delete it. If
- needed, add the missing Syriac and then delete. The % character was used
- to indicate that text in Arabic, Greek, Armenian or other non-Roman
- script should be entered. If you are able, enter that text as described
- above. Lastly, when you find that the PDF of Wright's catalogue contains
- either images or special characters which cannot be displayed using
- Syriac or Greek unicode fonts, please open a GitHub issue, apply the
- label "cannot display", and include this message in the title of your
- issue: “PDF contains characters or images which cannot be displayed in
- XML.” Note: This section is provided for the convenience of the editors
- undertaking a revision of the data in 2024 and will be deleted from the
- final documentation.
-
-
-
-
-
1.4. The TEI
- Header
-
The TEI root element contains a declaration of the TEI namespace, a language
- declaration, and a unique identifier for the manuscript.
-
The namespace declaration (xmlns) is the
- same in every file:
The xml:lang value indicates the language of Wright's
- manuscript description (and thus the language of file as a whole) and should
- always be marked as English (‘en’) in every file.
-
The <TEI>
- element itself takes an xml:id attribute whose value is
- constructed from the unique identifier for the XML file and the top level
- manuscript described in that file. In the example above, the file ‘1.xml’ (which contains manuscript
- https://bl.syriac.uk/ms/1) has the following xml:id on the root TEI element:
- ‘manuscript_1’.
The <titleStmt> element describes the TEI XML file, and the
- cataloguing project of which it is a part, rather than for the
- manuscript itself (which is described in the <sourceDesc>). Every <titleStmt> contains
-
-
a <title> element containing the
- manuscript shelfmark
editor amd responsibility information giving credit to
- those responsible for the creation, encoding, and editing of the
- file (using the <editor> and <respStmt> elements)
<titleStmt><title xml:lang="en">London, BL, Add.
- 12133</title><sponsor>Syriaca.org: The Syriac
- Reference Portal</sponsor><funder>National Endowment for the
- Humanities</funder><funder>Andrew W. Mellon
- Foundation</funder><principal>David A. Michelson</principal>
- <!--...-->
- </titleStmt>
in the example
- above, we identify Syriaca.org as the sponsoring institution, the
- National Endowment for the Humanities and the Andrew W. Mellon
- Foundation as the funding bodies, and the principal researcher
- undertaking the project as David A. Michelson. This encoding of the <sponsor>, <funder>, and <principal> elements should be identical across all
- records in SMBL
-
-
-
1.4.1.2. Editorial
- Credit
-
Syriaca.org's digital projects are highly collaborative, and
- so the general editors of SMBL place a high
- value on giving editorial credit to everyone who contributed in any
- substantive way to each entry (e.g. each XML document). All editors on
- the SMBL project are assigned a unique
- xml:id which is recorded in this reference document https://bl.syriac.uk/documentation/editors.xml. The <titleStmt> gives credit by name to both the general
- editors for SMBL and the specific editor
- with authorial or editorial responsibility for the individual XML file
- so that these can be included in citations of the document. These editor
- names are encoded in an <editor> element in the following
- way:
<editor role="general-editor" ref="https://bl.syriac.uk/documentation/editors.xml#dmichelson">David
- A. Michelson</editor>
- <editor role="general-editor" ref="https://bl.syriac.uk/documentation/editors.xml#wpotter">William
- L. Potter</editor>
- <editor role="technical-editor" ref="https://bl.syriac.uk/documentation/editors.xml#dschwartz">Daniel
- L. Schwartz</editor>
- <editor role="creator"
- ref="https://bl.syriac.uk/documentation/editors.xml#dmichelson">David
- A. Michelson</editor>
- <editor role="creator"
- ref="https://bl.syriac.uk/documentation/editors.xml#dgreeson">Daniel
- J. Greeson</editor>
- <editor role="creator"
- ref="https://bl.syriac.uk/documentation/editors.xml#thannah">Tucker
- D. Hannah</editor>
- <editor role="creator"
- ref="https://bl.syriac.uk/documentation/editors.xml#raydin">Robert
- Aydin</editor>
In the
- example above (from the file 1.xml, https://bl.syriac.uk/ms/1/tei), the following types of credit
- are given using the role attribute:
-
‘general-editor’ identifies
- the general editors for the entire SMBL publication
-
‘technical-editor’
- identifies the technical editors for the entire SMBL publication
-
‘creator’ identifies any
- editor who created, edited, proofread, or revised the specific
- XML document (e.g. 1.xml)
-
As can been seen in the example above, it will be the case that
- the same person might receive credit for multiple editorial roles.
-
Divergences from Consolidated Schema:
-
This use of <editor> is not mentioned in the Consolidated Schema
- guidelines but is conformant with the TEI guidelines.
-
-
-
1.4.1.3. Responsibility Statment
-
In addition to using <editor> elements to name the
- editors with authorial responsibility, each XML file also includes a
- more detailed description which we have used to assign credit for
- particular efforts. The <respStmt> element is used to
- describe each stage in the development of the data or the document. The
- <respStmt> provides a mechanism for recognizing research
- assistants who made contributions to processing or cleaning the data,
- but who are not considered authors or editors of the XML file. (In many
- cases, the research assistants named here helped to compile the data
- before it was encoded in XML.
-
The contents of the <respStmt> element are, in any
- order, the name of the responsible party contained in a <name> element and a phrase describing the nature of the
- responsibility (e.g. creator, proofreader, etc.) which is wrapped in a
- <resp> element. The <name> element should take first a
- type attribute indicating whether the name
- refers to a person or a group (with the values ‘person’ or ‘org’). The <name> element should also take a ref attribute which points to the @xml:id of the editor
- listed at https://bl.syriac.uk/documentation/editors.xml. The creator of
- the TEI file is identified with a <respStmt>
- giving the content of the <resp> element as ‘creator’. Additional participants in the creation of the
- data or the file, for example by entering Syriac or Arabic text, are
- given additional <respStmt> entries. A modified
- example from file 1.xml, https://bl.syriac.uk/ms/1/tei is as follows:
<respStmt><resp>Created by</resp><name type="person" ref="https://bl.syriac.uk/documentation/editors.xml#dgreeson">Daniel
- J. Greeson</name>
- </respStmt>
- <respStmt><resp>Edited by</resp><name type="person" ref="https://bl.syriac.uk/documentation/editors.xml#thannah">Tucker
- D. Hannah</name>
- </respStmt>
- <respStmt><resp>Syriac text entered by</resp><name type="person" ref="https://bl.syriac.uk/documentation/editors.xml#raydin">Robert
- Aydin</name>
- </respStmt>
- <respStmt><resp>Greek and coptic text entry and proofreading
- by</resp><name type="person"
- ref="https://bl.syriac.uk/documentation/editors.xml#rstitt">Ryan
- Stitt</name>
- </respStmt>
- <respStmt><resp>Project management by</resp><name type="person" ref="https://bl.syriac.uk/documentation/editors.xml#ewalston">Elizabeth
- Walston</name>
- </respStmt>
- <respStmt><resp>English text entry and proofreading by</resp><name type="org" ref="https://bl.syriac.uk/documentation/editors.xml#uasyriacaresearchgroup">Syriac
- Research Group, University of Alabama</name>
- </respStmt>
- <respStmt><resp>Folio extent edited by</resp><name type="person" ref="https://bl.syriac.uk/documentation/editors.xml#kurban">Kurt
- Urban</name>
- </respStmt>
-
Divergences from Consolidated Schema:
-
SMBL identifies its editors using a different
- xml:id method than the Consolidated Schema guidelines but in a way that
- is still conformant with the TEI guidelines. SMBL uses <name> rather than <persName>.
-
-
-
1.4.1.4. Edition
- Statement
-
The 2024 release of SMBL is the
- first edition. If funding permits, there may be later editions. All XML
- files are marked with an identical <editionStmt> as follows:
<editionStmt><edition n="1.0"/>
- </editionStmt>
The <edition> element contains no human-readable text.
-
-
-
1.4.1.5. Publication Statement
-
The <publicationStmt>
- summarizes the publication of the TEI document, rather than the
- manuscript itself (which is described in the <sourceDesc>). Our <publicationStmt> contains information about the
- publishing body (Syriaca.org), a URI for the TEI XML file, the open
- access license information (Creative Commons Attribution 3.0 Unported
- License), and the date of publication.
-
<publicationStmt><authority>Syriaca.org: The Syriac
- Reference Portal</authority>
- <idno type="URI">https://bl.syriac.uk/ms/1/tei</idno><availability><licence target="http://creativecommons.org/licenses/by/3.0/">
- <p>Distributed under a
- Creative Commons Attribution 3.0 Unported License</p></licence></availability><date calendar="Gregorian">2023-04-21-05:00</date>
- </publicationStmt>
While
- the URI and the date will vary, the rest of the encoding above should be
- identical for each file.
-
-
-
-
1.4.2. Revision
- Description
-
The <revisionDesc> element follows its sibling element the <msDesc> (for which see 1.6. Manuscript Description) as a
- child element of the <sourceDesc> . The revision
- description is a detailed log of which changes have been made to this file,
- when, and by whom.
-
At present a status attribute on each record has the
- value ‘draft’. The General Editprs will updated this
- value to ‘reviewed’ after the peer review editors
- revisions of the file have been completed.
-
Each revision is encapsulated in a <change> element,
- ordered in a reverse chronological order from newest to oldest. The <change> element must have the who
- attribute and may have the when which indicates the
- person who made the change and he date of the change. The value of when is a date in yyyy-mm-dd format for
- year-month-day, whereas who will have the value of
- an xml:id attribute published in https://bl.syriac.uk/documentation/editors.xml. The text node of
- the <change> element describes the revision that was made.
<revisionDesc status="draft"><change who="https://bl.syriac.uk/documentation/editors.xml#kurban"
- when="2023-04-21-05:00">CHANGED: added or corrected folio
- extent values</change><change who="https://bl.syriac.uk/documentation/editors.xml#dgreeson"
- when="2013-07-01">Created
- file</change><change who="https://bl.syriac.uk/documentation/editors.xml#thannah"
- when="2013-08-14">Edited
- file</change><change who="https://bl.syriac.uk/documentation/editors.xml#jarnwine"
- when="2014-04-07">Edited file
- to reflect our definition of colophons. Multiple a-levels changed to
- one and only one in part 2.</change><change who="https://bl.syriac.uk/documentation/editors.xml#jarnwine"
- when="2014-04-10">Added
- @syriacatags to colophon in p1addition1, p1addition2, and
- p2addition1.</change><change type="planned" subtype="arabic" who="https://bl.syriac.uk/documentation/editors.xml#smbl-general-editors">Add
- missing Arabic text.</change><change type="planned" subtype="missing" who="https://bl.syriac.uk/documentation/editors.xml#smbl-general-editors">Add
- missing Syriac vowels.</change>
- <change type="planned"
- subtype="arithmetical" who="https://bl.syriac.uk/documentation/editors.xml#smbl-general-editors">Enter
- arithmetical figures.</change><change who="https://bl.syriac.uk/documentation/editors.xml#pgmiller"
- when="2016-07-06">Changed:
- Files moved to srophe-app-data/data/manuscripts/tei repository.</change>
- </revisionDesc>
-
The editors of SMBL also use the <change> element to track items that need revision in the
- future. These are marked with type of ‘planned’ and a subtype from a
- controlled list of types of changes. All ‘planned’
- changes are assigned to an xml:id for the general editors: ‘https://bl.syriac.uk/documentation/editors.xml#smbl-general-editors’.
-
Notes for Review Editors (2024)
-
Please begin by checking the <revisionDesc> to see if there
- are any change/type=‘planned’ that you are able to complete (such as adding in
- Arabic). Please do not edit the revisionDesc/change after you complete the
- revision. Instead, leave the change description there even after you
- complete the requested change as we will use it to find the changes you made
- and proofread them. If you are not able to make the change, please create an
- issue noting such on GitHub online so we can make the change later. (For
- example, if you do not work in Arabic, do not add Arabic text. Or for
- example, if the Syriac characters needed in the document do not exist in
- unicode fonts and cannot be added create an issue noting this). Note: This
- section is provided for the convenience of the editors undertaking a
- revision of the data in 2024 and will be deleted from the final
- documentation.
-
Divergences from Consolidated Schema:
-
SMBL requires the <change> element
- have the who attribute but when is optional (this is the reverse of the Consolidated
- Schema). SMBL uses status on <revisionDesc> and type and subtype on <change> which are not mentioned in the Consolidated Schema
- guidelines but are conformant with the TEI guidelines.
-
-
-
-
1.5. Subject
- Classifications [UNDER REVISION]
-
SMBL reproduces the subject classifications used by
- Wright in his catalogue. A further description of this taxonomy will be added
- here.
-
-
-
1.6. Manuscript
- Description
-
All manuscript description takes place in the <msDesc> element which
- is contained in a parent <sourceDesc> element. Within <msDesc> and its descendent elements is all the information about
- the manuscript as a physical object, its constituent parts, and intellectual
- works represented within.
-
All manuscript descriptions must be informed by attention to codicological units.
- In other words, whether the manuscript was created in one place, over one period
- of time, or is a composite of parts from multiple sources, assembled at a later
- date. In the case of the Syriac manuscripts in the British Library, it is often
- the case that manuscripts which were originally physically distinct, are now
- bound together. In such cases, multiple codicological units can be found sharing
- a single shelfmark. Add.
- 12,133 is an example of one binding containing multiple manuscripts.
-
If the manuscript forms a single codicological unit, its intellectual content,
- physical description, and history are described directly under the <msDesc> element.
-
If the manuscript comprises multiple codicological units, each unit has been described in a
- separate <msPart> element, and only information common to the whole
- manuscript is described directly under the <msDesc> element in this
- manner:
<msDesc xml:id="manuscript-1">
- <!-- Common information --><msPart xml:id="Part1" n="1">
- <!-- Codicological unit 1 --></msPart><msPart xml:id="Part2" n="2">
- <!-- Codicological unit 2 --></msPart>
- </msDesc>
As show above, the <msDesc> element should always have a unique xml:id which is formed from the URI for the manuscript according to
- the pattern manuscript-(URI number). For mult-part manuscript, the <msPart> element will also have an xml:id and an n created from the number of
- the manuscript part.
The Syriac manuscripts in the British Library have had a number
- of variant indentifiers. Not only can the current shelfmarks be expressed
- with or without commas (Add. 12,178 or Add. 12178) or the prefixes ‘Additional’, ‘Add’. or ‘MS’, but Wright also assigned roman numerals to his
- entries which have been widely used in later scholarship. One goal of
- publishing SMBL is to create permanent URIs to
- facilitate easier citation of the manuscripts in digital databases.
- Accordingly, SMBL has assigned a URI as the
- primary identifier encoded in the <idno> in the <msIdentifier>. Using these URIs, the <msIdentifier> in each file looks similar to this example
- from Add. 12,178 which is URI https://bl.syriac.uk/ms/10:
<msIdentifier><country>United Kingdom</country><settlement>London</settlement><repository>British Library</repository><collection>Oriental Manuscripts</collection><idno type="URI">https://bl.syriac.uk/ms/10</idno><altIdentifier><idno type="BL-Shelfmark">Add. 12,178</idno></altIdentifier><altIdentifier><idno type="BL-Shelfmark-display">London, BL, Add.
- 12,178</idno></altIdentifier><altIdentifier><idno type="BL-Shelfmark-simplified">BL Add MS 12178</idno></altIdentifier><altIdentifier><collection>William Wright, Catalogue of the Syriac
- Manuscripts in the British Museum Acquired since the Year
- 1838</collection><idno type="Wright-BL-Arabic">161</idno></altIdentifier><altIdentifier><collection>William Wright, Catalogue of the Syriac
- Manuscripts in the British Museum Acquired since the Year
- 1838</collection><idno type="Wright-BL-Roman">CLXI</idno></altIdentifier>
- </msIdentifier>
In the example
- above the type values on the element <idno>
- are controlled to facilitate searching by type of shelfmark or URI.
-
For a multi-part manuscript, the <msIdentifier> which is a direct child of <msDesc> will
- contain the shelfmarks which are shared by both parts (for example if both
- are part of Add.
- 12,133). The identifiers and shelfmarks which are unique to the
- individual parts will be contained by separate <msIdentifier> elements which are direct children of <msPart>, as in this example:
<sourceDesc><msDesc xml:id="manuscript-1"><msIdentifier><country>United Kingdom</country><settlement>London</settlement><repository>British Library</repository><collection>Oriental Manuscripts</collection><idno type="URI">https://bl.syriac.uk/ms/1</idno><altIdentifier><idno type="BL-Shelfmark">Add.
- 12,133</idno></altIdentifier><altIdentifier><idno type="BL-Shelfmark-display">London, BL, Add.
- 12,133</idno></altIdentifier><altIdentifier><idno type="BL-Shelfmark-simplified">BL Add MS
- 12133</idno></altIdentifier></msIdentifier>
- <!--...--><msPart xml:id="Part1" n="1">
- <msIdentifier><idno type="URI">https://bl.syriac.uk/ms/2</idno><altIdentifier><idno type="BL-Shelfmark">Add.
- 12,133, foll. 1–108</idno>
- </altIdentifier><altIdentifier><idno type="BL-Shelfmark-display">London, BL, Add.
- 12,133, foll. 1–108</idno></altIdentifier><altIdentifier><idno type="BL-Shelfmark-simplified">BL Add MS
- 12133, foll. 1-108</idno></altIdentifier><altIdentifier><collection>William Wright, Catalogue
- of the Syriac Manuscripts in the British Museum Acquired
- since the Year 1838</collection><idno type="Wright-BL-Arabic">9</idno></altIdentifier><altIdentifier><collection>William Wright, Catalogue of the
- Syriac Manuscripts in the British Museum Acquired
- since the Year 1838</collection>
- <idno type="Wright-BL-Roman">IX</idno></altIdentifier></msIdentifier></msPart>
- <!--...--><msPart xml:id="Part2" n="2">
- <msIdentifier><idno type="URI">https://bl.syriac.uk/ms/3</idno><altIdentifier><idno type="BL-Shelfmark">Add.
- 12,133, foll. 109–169</idno></altIdentifier><altIdentifier><idno type="BL-Shelfmark-display">London, BL, Add.
- 12,133, foll. 109–169</idno>
- </altIdentifier><altIdentifier><idno type="BL-Shelfmark-simplified">BL Add MS
- 12133, foll. 109-169</idno></altIdentifier><altIdentifier><collection>William Wright, Catalogue
- of the Syriac Manuscripts in the British Museum Acquired
- since the Year 1838</collection><idno type="Wright-BL-Arabic">51</idno></altIdentifier><altIdentifier><collection>William Wright, Catalogue of the
- Syriac Manuscripts in the British Museum Acquired
- since the Year 1838</collection>
- <idno type="Wright-BL-Roman">LI</idno></altIdentifier></msIdentifier></msPart></msDesc>
- </sourceDesc>
-
Divergences from Consolidated Schema:
-
SMBL uses a different set of type values.
-
-
-
1.6.2. The Heading
- [UNDER REVISION]
-
An auto-generated paragraph describing the masnucript contents
- has been inserted into the <head> section of each file.
<head><note type="contents-note">This
- manuscript contains: Philoxenus of Mabūg. The discourses of
- Philoxenus of Mabūg on Christian life and character. In total,
- including sub-sections, this manuscript contains 9 items.</note><listRelation type="Wright-BL-Taxonomy">
- <relation name="dcterms:type"
- ref="http://purl.org/dc/terms/type" active="https://bl.syriac.uk/ms/332" passive="#theo-single"><desc>Individual Authors</desc></relation></listRelation>
- </head>
-
Notes for Review Editors (2024)
-
Please ignore any errors in the <head> element and its summary. These
- will be regenerated by a script at a later stage. Note: This section is
- provided for the convenience of the editors undertaking a revision of the
- data in 2024 and will be deleted from the final documentation.
-
-
-
1.6.3. Intellectual
- Content
-
The element <msContents> is used to describe
- the intellectual content of the manuscript (title, author, editor, textual
- additions, filiation and bibliographical references). Every conceptual work
- contained in the manuscript is treated as a separate <msItem>.
-
-
1.6.3.1. Language(s) of the Manuscript as a Whole [UNDER
- REVISION]
-
The element <textLang> encodes a description
- of the languages and writing systems used in the manuscript. The element
- itself contains a prose description of the language or languages and
- scripts used. The mainLang and otherLangs attributes contain the ISO 639-1 and
- -3 codes for the languages as well as a script code if relevant. Either
- attribute can take multiple values, as a space-separated list.
-
We have conformed to the BCP 47
- standard which recommends using the two letter language code
- when available from ISO
- 639-1 codes and then using three letter language codes from ISO
- 639-3 only for languages not included in ISO 639-1, then an ISO
- 15924code for the script, and finally IANA language subtags for other information, such as methods of
- transliteration.
-
The accepted language codes are: CONTENT PENDING
-
Notes for Review Editors (2024)
-
Please ignore the <textLang> and the mainLang contents. These will be updated by
- script. Note: This section is provided for the convenience of the
- editors undertaking a revision of the data in 2024 and will be deleted
- from the final documentation.
-
-
-
1.6.3.2. Manuscript Item
-
The element <msItem> contains the intellectual information for each
- individual work contained within the manuscript. If a manuscript
- contains multiple works, it will have multiple <msItem>
- elements; if a manuscript contains a single work, it will only have one
- <msItem>.
All manuscript items have been numbered with the n attribute in a sequential manner without regard for
- the location of the items in the hierarchy of items and sub-items.
- This sequential number is relative to the manuscript part. Thus a
- multi-part manuscript would restart the numbering at n=‘1’ in each part. In
- addition, we have used a pattern for the creation of xml:id values which reflects nesting in
- manuscript parts and/or the position of the item in the outline
- hierarchy (with ‘a’ being the top level, then
- ‘b’, etc.
-
In this example from https://bl.syriac.uk/ms/3the msItem is in the second part of
- the multi-part manuscript and is the second item at the ‘b’ level of the outline. It is also the 3rd
- msItem in the second part of the manuscript based on sequence.
NOTA BENE:
- SMBL has not used Wright's outline
- numbering system, but instead has re-numbered the manuscript items
- sequentially. While there is some loss to not continuing to use
- Wright's numbering, we found the re-numbering to be necessary for
- two reasons. First, the sequential numbering allows one to navigate
- the nested elements much easier than Wright's system (where the same
- manuscript could potentially have repeated numbers due to outline
- levels). Second, in our encoding we occaisionally discovered
- manuscript items which Wright had conflated. The need to number
- these items necessitated re-numbering.
-
Notes for Review Editors (2024)
-
Please ignore any errors in numbering in either n or xml:id. You do not need to
- renumber if you delete an <msItem> or add a new <msItem> or find errors in the numbering. These will
- be renumbered by a script at a later stage. Similarly, if you delete
- an item, there is no change needed to the xml:id or the n values of the
- other items, leave them numbered as. If you add a new <msItem>, you should just use the letter ‘x’ as place holders: xml:id=‘x1’
- n=‘x’ (if you insert
- multiple items, the XML validation rules require that every xml:id have a unique value, so please
- increment use xml:id=‘x2’, etc.). These will be renumbered by a script at a
- later stage. Note: This section is provided for the convenience of
- the editors undertaking a revision of the data in 2024 and will be
- deleted from the final documentation.
-
-
-
1.6.3.2.2. Defective Manuscript Items
-
defective can be used to indicate if any
- text or folia originally present are now missing (as determined by
- Wright based on missing intellectual content or physical state of
- the manuscript). Defective here refers only to the physical state of
- the manuscript. In a case where the manuscript, contains only a
- portion of a literary work by design (such as an abbreviated text or
- an extract), the manuscript item is not considered defective. The
- following values are permitted:
-
-
‘true’ means that the item
- is defective either because Wright states as much (‘leaves are wanting’ or ‘fragments of’) or because clear deduction by the
- SMBL editor indicates missing
- content.
-
‘unknown’ means that the
- SMBL editor suspects the
- manuscript is incomplete but it is not discussed by Wright.
-
‘false’ is the default value
- and it is not necessary to enter it. If the item is not
- defective our altogether.
-
-
In the case of nested <msItem> elements, the
- defective value was also marked for any higher-level items if one of
- their child items was defective.
-
-
-
1.6.3.2.3. What is a Manuscript Item?
-
We have followed the definition proposed by the Consolidated
- Guidelines where a manuscript item is defined as ‘a
- complete work or item, or a self-contained part of a larger work
- with (potentially) independent circulation’. A ‘self-contained part of a larger work’ could be
- a letter in a letter-collection, or a sermon in a homiliary; it
- could also represent the biblical text or the commentary in a
- glossed biblical manuscript.
-
As a guiding principle, where possible and practicable we have used
- the <msItem> element to markup up both the work as a
- whole its self-contained parts through the nesting of <msItem> elements. In a few cases (primarily with
- florilegia or catenae) is has not been possible to encode individual
- manuscript items based on Wright's descriptions. In those cases, we
- have placed his descriptions into <note>
- elements.
-
-
- 1.6.3.2.3.1.
- Encoding the Outline of Nested Manuscript
- Items
-
-
For the most part, Wright's catalogue employs an sequential
- outline pattern that describes manuscript items and their
- sub-items in a way compatible with the TEI Guidlines. In a few
- cases, however, we have had to modify Wright's outlines to
- better model the manuscript in the tree structure of the .xml
- file. Specifically, in some instances we have had to create a
- new top-level manuscript item which contains all of the items in
- a manuscript. Often in such cases, Wright provided a title and
- description of this top-level item, but he did not include this
- item in his numbered outline. At other times, we have found
- Wright's outline to be partial or incomplete. For example,
- Wright might only list some but not all of the sub-items in a
- manuscript. In these cases, our policy has been to encode only
- the sub-items that Wright mentions. In these cases, our .xml
- document matches Wright's description but not the actual
- contents of the manuscript (of course, we hope the a future
- recataloguing will capture the contents which Wright did not
- describe in detail). The examples below illustrate what this
- might look like.
-
In this modified example from https://bl.syriac.uk/ms/763 Wright notes that there are
- 18 hymns in the collection but he only provides information
- about two of them, thus only two <msItem>
- elements are encoded as child elements:
In this modified example from https://bl.syriac.uk/ms/265 Wright describes a large
- collection but he only provides information about the first two
- parts of the collection, thus only two <msItem>
- elements are encoded as child elements. In this case we did not
- create a third <msItem> which might
- contain ‘everything else after the definitions
- and introduction’ even though it is clear by context
- that the manuscript containts more thanjust these two sections.
- In this case, the top-level <msItem>
- is assumed to contain the other sections not specifically
- identified by Wright.
<msItem xml:id="a1" n="1" defective="true">
- <locus from="1b"/><title xml:lang="en">A large collection of chapters
- on the Body and its Members, the Soul, the
- Resurrection, the Incarnation, the holy Eucharist,
- Baptism, etc.</title>
- <msItem xml:id="b1" n="2"><locus from="1b"/><title xml:lang="en">A section containing
- definitions of various scientific terms</title></msItem><msItem xml:id="b2" n="3" defective="true">
- <locus from="1b"/>
- <title xml:lang="en">The
- introductory section</title></msItem>
- </msItem>
-
Notes for Review Editors (2024)
-
As described above, it is not necessary to create extra <msItem> elements for itemns not described
- directly by Wright. Alternately, in some cases these may have
- already been added to the file, in which case it is not
- necessary to delete these extra <msItem>
- elements if they exist. Note: This section is provided for the
- convenience of the editors undertaking a revision of the data in
- 2024 and will be deleted from the final documentation.
-
Deprecated Practices and Legacy Data:
-
In an earlier stage of the project, we did attempt to create
- placeholder <msItem> elements for
- content not described by Wright so some files do contain
- sub-items with minimal description which were not found in
- Wright's description. We discontinued this practice after 2022
- but have left the legacy data in place, since it may be of use
- to future cataloguing.
-
-
-
- 1.6.3.2.3.2.
- Alternate Encoding with <note> in <msItem>
-
-
While Wright usually describes the manuscript
- contents in a methodical manner creating an outline sequentially
- in order from the first folio to the last, there are places
- where he abandons this approach and offers a prose description
- of the contents that does not follow the order of the document.
- In the most frequent example, Wright may choose to describe a
- florilegium in a manner
- organized by alphabetically by author cited rather than by folio
- order. In this modified example from https://bl.syriac.uk/ms/265, Wright offers the an
- alphabetical list: ‘The authorities cited
- are--Didymus of Alexandria. Fol. 24 b. Dionysius the
- Areopagite: epistle to Timothy, fol. 19 b; to Titus, fol. 27
- b. Epiphanius: the Ancoratus. Fol. 26 a. Ephraim: foll. 21
- a, 25 a, 30 a, 31 b;’. Wright's description does not
- offer enough information to encode individual manuscript items.
- In those cases, we have placed these descriptions into one or
- more <note> elements with the following XPath:
- msItem/note/p. Inside this <note>, we have encoded as
- much of the relevant information about authors, titles, and loci
- as possible. As illustrated in this modified example from https://bl.syriac.uk/ms/265:
<msItem xml:id="a1" n="1" defective="true">
- <locus from="1b"/><title xml:lang="en">A large collection of chapters
- on the Body and its Members, the Soul, the
- Resurrection, the Incarnation, the holy Eucharist,
- Baptism, etc.</title>
- <!-- ... --><note><p>The authorities cited
- are--</p>
- <!-- ... --><p><persName>Didymus of
- Alexandria</persName>. Fol. <locus from="24b">24 b</locus>.</p><p><persName ref="http://syriaca.org/person/452">Dionysius
- the Areopagite</persName>: <title xml:lang="en">epistle to Timothy </title>, fol. <locus from="19b">19 b</locus>; <title xml:lang="en">to Titus </title>, fol. <locus from="27b">27 b</locus>.</p><p><persName ref="http://syriaca.org/person/477">Epiphanius</persName>: <title xml:lang="en">the Ancoratus</title>. Fol. <locus from="26a">26 a</locus>.</p><p><persName ref="http://syriaca.org/person/13">Ephraim</persName>: foll. <locus from="21a">21 a</locus>, <locus from="25a">25 a</locus>, <locus from="30a">30 a</locus>, <locus from="31b">31 b</locus>; <rubric xml:lang="syr">ܥܠ ܣܒܐ ܝܘܠܝܢܐ</rubric>, fol. <locus from="25a">25 a</locus>; <rubric xml:lang="syr">ܡܢ ܩܠܐ ܕܚܡܫܐ
- ܕܦܪܕܝܣܐ</rubric>,
- fol. <locus from="30a">30 a</locus>.</p>
- <!-- ... --></note>
- </msItem>
-
-
-
-
1.6.3.2.4. Wright's Notes on the Manuscript Item
-
When Wright provides a comment related to an <msItem> or another aspect of the contents, we have
- encoded his commentary as a <note> within each <msItem> or other element as applicable. When
- Wright's catalogue has a footnote, we have inserted the <note> element at the point in the prose where the
- footnote marker occurs and marked the <note> with
- type of ‘footnote’. Some examples are:
<msItem xml:id="a2" n="2" defective="true"><locus from="1" to="100">Foll. 1-100</locus><title ref="http://syriaca.org/work/26" xml:lang="en">Ezekiel,
- according to the Peshitta version</title><note>The following portions of the text are
- missing: Ch. 14:14-16:17, 16:32-53, 17:3-22:2, and
- 24:18-25:3.</note><note>The lessons are
- rubricated in the text.</note>
- </msItem>
As described
- above, when a note contains
- a bibliographic citation, that citation is wrapped in a <bibl> element and linked to a Syriaca.org URI using
- <ref> and target:
<msItem xml:id="a1" n="1" defective="true"><locus from="1b"/><title xml:lang="en">The Acts of the Second Council of
- Ephesus</title><note type="footnote">A small part of this volume
- has been edited by the <persName>Rev. S. G. F. Perry</persName>, under the title of
- <bibl><ref target="https://www.zotero.org/groups/4861694/a_comprehensive_bibliography_on_syriac_studies/items/P4VVZ7P6/library"/>"An
- Ancient Syriac Document, purporting to be the record, in
- its chief features, of the second Synod of Ephesus," etc.,
- Oxford, 1867.</bibl></note>
- </msItem>
-
-
-
1.6.3.2.5. Locus
-
We have given the starting folio of each manuscript item according to
- the guidelines specified above for <locus>. If Wright does not give
- a folio location for a <msItem>, we have added one
- using the closest folio that he mentions in his description, even
- though this may not be very accurate. For example if Wright mentions
- an msItem on folio 12 b and then fails to give a locus for the next
- msItem, we have reused the locus so that both items are listed as
- being on 12 b.
-
-
-
1.6.3.2.6. Author
-
The author of a manuscript item, if given by Wright, was
- recorded inside the <author> element and wrapped
- with a <persName> child element
- (with xml:lang attribute). As described above in the discussion of URIs, all <author>
- elements are required to have a Syriaca.org person URI as the value
- of a ref, For anonymous works, no <author> was included in the <msItem>.
- The form of the name given by Wright was encoded as given without
- standardization. Where Wright records multiple name variants for the
- same person (e.g. translations or transliterations) we added these
- as child <persName> elements (with
- xml:lang attributes) within the <author> element (see further below for an example of
- multiple names for George, bishop of the Arabs).
When a <msItem> contains nested <msItem>
- elements, the author element should be repeated if applicable to the
- sub-items.
-
Divergences from Consolidated Schema:
-
SMBL uses Syriaca.org URIs and thus does
- not use key as specified in the
- Consolidated Schema.
-
-
- 1.6.3.2.6.1.
- Multiple Authors
-
-
Multiple authors have been indicated using repeated
- <author> elements.
<msItem xml:id="p2a1" n="1"><locus from="65"/><author ref="http://syriaca.org/person/376">
- <persName xml:lang="en">Basil</persName></author><author ref="http://syriaca.org/person/511">
- <persName xml:lang="en">Gregory
- (Nazianzen)</persName></author><title xml:lang="en">Questions and answers of Basil
- and Gregory (Nazianzen) </title>
- </msItem>
-
When a <msItem> contains nested <msItem> elements, the author element should be
- repeated if applicable to the sub-items. When a top-level <msItem> contains sub-items with different
- authors, all authors should be encoded in the top level <msItem> as seen in this example from https://bl.syriac.uk/ms/427. Note: When Wright gives
- multiple name variants, those varients were recorded only in the
- first/highest-level instance.
<msItem xml:id="a1" n="1" defective="true">
- <locus from="1a" to="263b">foll.
- 1 a-263 b</locus><author ref="http://syriaca.org/person/122">
- <persName xml:lang="en">George,
- bishop of the Arabs</persName><persName xml:lang="en">George the Jacobite</persName><persName xml:lang="syr">ܓܘܪܓܝ (ܓܝܘܪܓܝ)
- ܕܥܡ̈ܡܐ</persName>
- <persName xml:lang="syr">ܓܝܘܪܓܝ
- ܝܥܩܘܒܝܐܐ</persName>
- </author>
- <!-- ... --><author ref="http://syriaca.org/person/342">
- <persName xml:lang="en">Aristotle</persName></author><title xml:lang="en">Part of the Organon of
- Aristotle, with introductions, notes and commentaries by
- George, bishop of the Arabs </title>
- <!-- ... --><msItem xml:id="b1" n="2" defective="true">
- <locus from="1a" to="59">foll.
- 1a-59</locus><title xml:lang="en">The Ten Categories</title><author ref="http://syriaca.org/person/122">
- <persName xml:lang="en">George,
- bishop of the Arabs</persName></author><author ref="http://syriaca.org/person/342">
- <persName xml:lang="en">Aristotle</persName></author><msItem xml:id="c1" n="3" defective="true">
- <locus from="1a" to="2b">foll.
- 1a-2b</locus>
- <author ref="http://syriaca.org/person/122">
- <persName xml:lang="en">George,
- bishop of the Arabs</persName></author><title xml:lang="en">Introduction</title>
- <!-- ... --></msItem><msItem xml:id="c2" n="4"><locus from="3a" to="28">foll.
- 3a-28</locus>
- <author ref="http://syriaca.org/person/342">
- <persName xml:lang="en">Aristotle</persName></author><title xml:lang="en">Text</title>
- <!-- ... --></msItem></msItem>
- </msItem>
Guidelines for these cases will be added in the future.
-
-
-
-
1.6.3.2.7. Translator
-
When Wright's description or a manuscript mentions the translator of
- a manuscript item, we have encoded the name of the translator in
- addition to any authors of the manuscript item. Such secondary
- statements of responsibility for the intellectual content in an <msItem> are marked with an <editor>
- element and a role attribute with the value
- ‘translator’. An <msItem> may
- have both an <editor> element and an <author> element if both are given in Wright's
- catalogue entry.
-
In all other respects, <editor> elements should
- contain the same child elements as <author>
- (eg. multiple <persName> elements) and
- attributes (e.g. a ref attribute with a
- Syriaca.org URI linking them to an entry The Syriac Biographical
- Dictionary. If Wright provides details about their role
- in the creation of the work that has been be encoded in a separate
- <note>.
-
-
<msItem xml:id="p2a1" n="1"><locus from="82a">Fol. 82 a</locus><editor role="translator" ref="http://syriaca.org/person/82"><persName xml:lang="en">Paul of Tellā</persName></editor><title ref="http://syriaca.org/work/158" xml:lang="en">The Psalms,
- translated from the Septuagint by Paul of Tellā</title>
- </msItem>
-
-
Divergences from Consolidated Schema:
-
SMBL does not, yet, use the three-letter
- code (or multiple codes separated by spaces) selected from the MARC
- relators list (https://www.loc.gov/marc/relators/relaterm.html by the
- Consolidated Schema. This may be added at a later date.
-
SMBL uses Syriaca.org URIs and thus does
- not use key as specified in the
- Consolidated Schema.
-
-
-
1.6.3.2.8. Title
-
Within the <msItem>, we have used the <title> element to encode the descriptive titles
- which Wright gives for each manuscript item. These descriptive
- titles are usually in English, though occaisionally in Latin or a
- mixture of languages. These are not standardized titles and at times
- can be very long sentence or paragraph type titles (as was more
- common in 19th-century English) as in this example:
<msItem><title xml:lang="en">Fragments of the second volume of
- the Commentary of Daniel of Salach on the Psalms, viz. part
- of the homilies on Pss. li., lviii., and lxii </title>
- </msItem>
We have made
- every effort to encode these titles exactly as written by Wright,
- though in some cases we have made silent emmendations for grammar or
- when Wright's prose was not clear. One change we have made
- throughout is to capitalize the first word of each title. More
- notably, if Wright's title was abbreviated due to context, we have
- supplied additional words to make the context clear. In addition, in
- the cases where Wright did not supply an English title we have
- constructed one so that every <msItem> has a non-Syriac title
- (usually in English) to appear in search and browse results (see
- discussion below).
-
As can be seen in the example just given (‘Fragments of the second volume of the Commentary of Daniel of
- Salach on the Psalms, viz. part of the homilies on Pss. li.,
- lviii., and lxii’), many manuscript items are themselves
- composed of sub-items. In these cases, we have taken advantage ofthe
- tree structure of the XML encoding since it is possible to
- infinitely nest <msItem> elements inside of
- parent <msItem> elements. Thus in many cases a manuscript
- may contain one parent <msItem> to which Wright has
- given a general title, such as ‘The metrical works
- of Ephraim, containing 160 discourses on the Church, the
- Mysteries of our Lord, Virginity, and against Heresies’.
- Whenever Wright gives such a title, we have tried to encode such a
- parent <msItem>, even when Wright's own numbering system did
- not account for it. Within this parent item, multiple levels of
- sub-items (each encoded with <msItem>) have been encoded. In
- this modified example there are three levels of nested <msItem> which are a tree model of ‘The metrical works of Ephraim’ which contains ‘Discourses on the Church’ which itself
- contains individual hymns numbered ‘11’,
- ‘12’, etc.:
<msItem xml:id="p2a1" n="1" defective="true"><locus from="20" to="33">Foll.
- 20-33</locus><author ref="http://syriaca.org/person/13"><persName xml:lang="en">Ephrem</persName></author><title xml:lang="en">The metrical works of Ephraim,
- containing 160 discourses on the Church, the Mysteries of our
- Lord, Virginity, and against Heresies</title><msItem xml:id="p2b1" n="2" defective="true"><locus from="20a" to="29b">Foll.
- 20a-29b</locus><author ref="http://syriaca.org/person/13">
- <persName xml:lang="en">Ephrem</persName></author><title xml:lang="en">Discourses on the Church</title><msItem xml:id="p2c1" n="3" defective="true"><locus from="20a" to="20b">Foll.
- 20a-20b</locus><author ref="http://syriaca.org/person/13">
- <persName xml:lang="en">Ephrem</persName></author><title xml:lang="en">Number 11</title></msItem><msItem xml:id="p2c2" n="4"><locus from="20b" to="21">Foll.
- 20b-21</locus><author ref="http://syriaca.org/person/13">
- <persName xml:lang="en">Ephrem</persName></author><title xml:lang="en">Number 12</title></msItem></msItem>
- </msItem>
-
As noted above in the guidelines for encoding URI entities, when the
- prose given by Wright for a <title> also contains a person
- name or a place name, we have NOT tagged those names with <persName> or <placeName>. See the example above from the ‘Fragments of the second volume of the Commentary of
- Daniel of Salach’.
-
Divergences from Consolidated Schema:
-
SMBL does not use the same type values on <title> as
- used in the Consolidated Schema. We may choose to do so in a future
- revision.
-
-
- 1.6.3.2.8.1.
- Untitled Parts
-
-
In some cases of such nested sub-items, Wright will only give a
- Roman or Greek numeral/character in lieu of an English title.
- This is particularly the case for lower-level nested <msItem> elements for which he has already given
- a longer descriptive title for the containing <msItem>. In such cases, we have pre-pended the
- word ‘Part’ to the Roman or Greek
- character according to the following pattern ‘Part c’. According to rules of XML, the enclosing
- <msItem> element's title is
- assumed to be inherited by the nested <msItem>. Thus the part designation is unambiguously
- associated with the work of which it is a part, and the <title> element of the child <msItem>
- needs only indicate the part.
-
In rare cases, Wright describes excerpts of a single work which
- are broken up among non-contiguous manuscript items. That is,
- the work may begin, be interrupted by another <msItem>, and then resume. In such cases, whe
- have pre-pended "Continuation of " to the title of any
- subsequent non-contiguous instances of a work.
-
-
-
-
1.6.3.2.9. Paratextual Materials: Rubrics, Incipits, Explicits, Quotes,
- Final Rubrics, and Colophons.
-
We have used a number of differen elements to encode the paratextual
- phrases which Wright transcribes in his catalogue. These include <rubric>, <incipit>, <explicit>, <finalRubric>, and <quote>. In a
- related way, the <colophon> and <item> elements are also used to encode data related
- to paratextual materials. As noted above, the same
- principles have been used to encode the transcriptions given
- Wright's catalogue across all of these elements. When Wright records
- the location of the transcription, a <locus>
- element is used within each of these elements to specify the
- location of the component within the manuscript. Because these
- elements imply verbatim quotation we have not added any additional
- markup (e.g. quotation marks) to convey that fact. In addition all
- elements containing transcription of text are required to have an
- xml:lang to specify the language.
-
Divergences from Consolidated Schema:
-
Because of the variety of languages found in the paratextual
- materials of Syriac manuscripts, SMBL
- requires an xml:lang where the Consolidated
- Schema does not. In addition, we report whatever punctuation is
- reported in Wright's catalogue and do not remove final punctuation
- for the transcriptions.
-
-
- 1.6.3.2.9.1.
- Rubic
-
-
We have used the TEI element <rubric>
- to encode the original language titles given in the manuscripts
- and reported by Wright. While Wright may sometimes denote this
- Syriac title with the phrase ‘entitled...’ or ‘Title:...’,
- most commonly he simply records it without any designation
- immediately after he provides an English language title.
- Sometimes Wright only provides a Syriac language title and no
- English translation. In both cases, we have encoded the Syriac
- titles reported by Wright within <rubric>
- with an xml:lang to specify the
- language.
-
In some cases, a manuscript item will have multiple Syriac
- titles. For instance, a liturgical manuscript may include both a
- traditional title of the work and a title which indicates the
- liturgical occasion on which the work should be read. In such
- cases, we have encoded both the literary title and the
- liturgical calendar title with multiple <rubric>
- elements.
-
Because every <msItem> element already
- has a <title> element where a
- Syriaca.org work URI could be linked, we have not linked
- Syriaca.org URIs to Syriac titles.
-
When Wright indicates that a title is a running title, we have
- encoded this by wrapping the title in both a <fw> (forme
- work) element with type of ‘header’and a containing <rubric> element.
-
<msItem xml:id="d1" n="8" defective="unknown"><locus from="91" to="161">Foll.
- 91-161</locus><title ref="http://syriaca.org/work/154" xml:lang="en">The second
- book of Samuel, according to the recension of Jacob of
- Edessa</title><rubric xml:lang="syr">ܟܬܒܐ ܕܬܪ̈ܝܢ ܕܡ̈ܠܟܘܬܐ<locus from="91b" to="91b"/></rubric><rubric xml:lang="syr"><fw type="header">ܫܡܘܐܝܠ</fw></rubric>
- </msItem>
-
-
-
- 1.6.3.2.9.2.
- Incipit
-
-
If Wright records the the opening lines of the text
- proper of the <msItem> we record this
- transcription in an <incipit> element. Wright
- sometimes denotes the incipit with the phrase ‘it begins...’ or ‘beginning...’. The incipit should not be confused
- with the rubic. The TEI defines the incipit as ‘the opening words of the text proper, exclusive of any
- rubric which might precede it, of sufficient length to
- identify the work uniquely.’ In most cases, if Wright
- provides an incipit he also provides a rubric (though the
- reverse is not the case). See this example:
In the exceedingly rare cases in which Wright records
- the the closing lines of the text proper of the <msItem>, we marked this transcription in an
- <expicit> element. The
- explicit should not be confused with the final rubic
- (subscription) or colophon. The TEI defines the explicit as
- ‘the closing words of the text proper,
- exclusive of any rubric or colophon which might follow
- it.’ (In other scholarly usage, what the TEI defines
- as ‘explicit’ is also called a ‘desinit’). Here is an example of how we
- have encoded an <expicit>:
Wright frequently records a ‘subscription’ or Syriac phrase in the manuscript
- which denotes the end or division of one manuscript item from
- the next. We have encoded these subscriptions with the TEI
- element <finalRubric>. The TEI
- guidelines distinguish between a <finalRubric> which contains a statement relating
- to the end of a particular work, and the <colophon>, which indentifies a statement about
- the end of an entire manuscript or about the scribe and/or date
- and/or place of writing.
<msItem xml:id="b7" n="32"><locus from="207b">Foll. 207 b</locus><title xml:lang="en">Madrāshē for all ranks.</title><rubric xml:lang="syr">ܡܕܪ̈ܫܐ ܥܠ ܟܗ̈ܢܐ ܘܪ̈ܫܝ ܟܗ̈ܢܐ
- ܘܟܠܢܫ</rubric><finalRubric xml:lang="syr">ܫܠܡܸܘ ܡܕܪ̈ܫܐ ܕܥܠ ܟܠ ܬܓܡ̈ܝܢ
- ܕܗ̇ܘܝܢ ܒܡܢܝܢܐ ܫܒܥܝܢ ܘܬܠܬܐ </finalRubric><note>They are 73 in number, according to
- the subscription.</note>
- </msItem>
-
In the case of <msItem> elements nested
- inside other <msItem> elements, it may
- be that Wright has quoted a <finalRubric> (e.g. a subscription) immediately
- after the last lower level <msItem>
- (for example after the last of 12 homilies in a collection).
- Since this subscription applies to the higher level <msItem> (for example it is a subscription noting
- the end of the whole collection of homilies), in these cases we
- have included this <finalRubric> inside
- the appropriate higher-level <msItem>
- rather than as part of the last sub-item.
-
Notes for Review Editors (2024)
-
In the case of <msItem> elements nested
- inside other <msItem> elements, it may
- be that a <finalRubric> (e.g. a
- subscription) has been nested inside a lower level <msItem> (say inside xml:id=‘b12’, the last of 12
- homilies in a collection) when in fact the subscription applies
- to the higher level <msItem> (for example it is
- a subscription noting the end of the whole collection of
- homilies). In these cases delete the <finalRubric> from the lower level <msItem> (b12) and move it up in the document and
- higher in the outline so that you paste it into the appropriate
- higher level <msItem> (a1, etc.). Note:
- This section is provided for the convenience of the editors
- undertaking a revision of the data in 2024 and will be deleted
- from the final documentation.
The TEI guidelines define a colophon as ‘the
- original statement providing information regarding the date,
- place, agency, or reason for production of the
- manuscript’. Unfortunately, Wright did not always
- report the presence of colophons in a standardized way. He only
- sometimes uses the word ‘colophon’ in the
- same sense as the definition of the TEI. Sometimes he uses the
- word to describe a doxology written by the scribe. Accordingly
- it has been difficult to distinguish his transcription of
- colophons from other marginalia and additions to the
- manuscripts. In our encoding, we have choosen to encode all
- colophons together the additions of the manuscript (see the
- guidelines for <additions>
- below. We have,
- however, also made an effort to mark manuscripts in which either
- Wright reports the existence of a colophon in the sense meant by
- the TEI or in which we determine (based on Wright's description)
- that a colophon is present. In these cases, we have included a
- <colophon> element in the
- <msItem> either as an empty
- element or with a prose note referring the reader to consult the
- additions section of the manuscript description. The inclusion
- of this element allows users to search for manuscripts with
- colophons. This is an example of that encoding:
-
<msItem xml:id="a3" n="22"><locus from="137a"/><title xml:lang="en">Supplicatory hymns for the
- Resurrection</title>
- <rubric xml:lang="syr">ܬܟܫ̈ܦܬܐ ܕܩܝܡ̣ܬܐ</rubric><colophon>See additions.</colophon>
- </msItem>
- <!-- -->
- <physDesc><additions><list><item xml:id="addition4" n="4"><label>Colophon</label><locus from="138a"/>
- <p>The colophon, fol.
- 138 a, states that the first part of this book (foll.
- 1—110) was written in the year 1386 (A.D. 1075) by one
- Benjamin, and the remainder by one of his disciples,
- whose name appears from a subsequent note to have been
- Theodore</p>
- <p><quote xml:lang="syr">ܫܘ: ܠܐܒܐ: ܘܠܒܪܐ: ܘܠܪܘܚܐ:
- ܩܕ ܠܥܠܡ: ܥܠܡܝܢ: ܫܩܠ ܣܟܐ ܟܬܒܘܢܐ ܗܢܐ ܒܥܘܕܪܢ
- ܬܠܝܬܝܘܬܐ ܕܡ̈ܥܢܝܬܐ ܕܩܝܫܐ (sic) ܡ̇ܪܝ ܣܘܐܝܪܐ ܘܕܐܢ̈ܫܝܢ
- ܐܚܪ̈ܢܐ. ܫܢܬ ܐܠܦ ܘܬܠܬܡܐ ܘܬܡ̈ܢܥܝܢ (sic) ܘܫܝܬ. ܒܕ̈ܝܘܢܝܐ
- ܡܒܪ̈ܟܐ. ܟܬܒܗ ܪܒܐ ܕܝܠܢ ܒܢܝܡܢ ܡܚܣܐ ܡܪܝܐ ܠܢܦܗ (sic)
- ܘܚܬܡܗ ܬܠܡܝܕܐ ܕܝܠܗ ܐܢܫ ܚܛܝܐ ܘܡܦܠܦܠ ܒܣܝܢܐ. ܟܠ ܕܩܪܐ ܢܨܠܐ
- ܥܠܝܗܘܢ ܘܫ.</quote></p></item></list></additions>
- </physDesc>
-
The colophon reported by Wright is encoded using <quote> and following the guidelines for
- additions.
-
Divergences from Consolidated Schema:
-
Our method of encoding colophons diverges from the Consolidated
- Schema but was chosen because it allows a greater amount of
- descriptive markup
-
-
-
-
1.6.3.2.10. Filiation [UNDER REVISION]
-
In one test case we have used the <filiation> element to encode information that Wright
- provides about the relationship of one manuscript to other surviving
- manuscripts in terms of their content. For example:
<msItem xml:id="a1" n="1" defective="true"><locus from="1" to="148">Foll. 1-148</locus><author ref="http://syriaca.org/person/51"><persName xml:lang="en">Severus of Antioch</persName></author><title xml:lang="en">The sixth book of the select
- epistles of Severus of Antioch</title><filiation>The sixth book of the select
- epistles of Severus of Antioch, in the same translation as
- <bibl type="MS">Add. 12,181<ptr target="https://bl.syriac.uk/ms/80"/></bibl>.</filiation>
- </msItem>
In the
- future, we may chose to convert other references to this usage of <filiation>.
-
-
-
-
-
-
1.7. Physical
- Description
-
We have used the physical description section <physDesc> to encode
- several different aspects of the manuscript (or part of a manuscript)
- including:
-
-
aspects of the form, support, extent, and quire structure of
- the manuscript object and of the way in which the text is laid out on the
- page.
-
the script used, any decorative features, any annotations or
- marginalia, and transcription of colophons.
-
-
Wright typically presents his physical description of the manuscript in a concise
- paragraph at the start of each entry. For ease of use, we have encoded this
- paragraph as a <p>
- (TEI paragraph) at the start of each <physDesc> in this way:
-
<physDesc><p>Paper, about
- 6 5/8 in. by 5 1/8, consisting of 138 leaves, many of which are much stained
- and torn, especially foll. 1, 5, 18, 24, 33, and 34. The quires, signed with
- letters, are 17 in number; but the first six are very imperfect, leaves being
- wanting at the beginning, as well as after foll. 4, 5, 12, 17, 23, 25, and
- 31. There are from 16 to 25 lines in each page.</p><objectDesc form="codex">
- <!-- ... --></objectDesc>
- <!-- ... -->
- </physDesc>
-
In addition we have used several of the child elements of <physDesc> to encode
- the same data in more detail.
-
-
1.7.1. Object
- Description
-
The <objectDesc> element is used to
- group together those parts of the physical description which relate
- specifically to the text-bearing object. We have encoded the form attribute of the <objectDesc>
- element to refer to the form of the object in its original state, before any
- mutilation, rebinding etc. Since all of the British Library MSS are
- currently codices, the majority of our MSS are marked as codex, unless we
- were aware of a point in time in which the item circulated as membra disjecta. We have used the following
- values :
-
‘codex’: used for multiple
- gatherings of leaves, held within a binding of some kind
-
‘leaf’: used for single leaves
- which may now be bound in a codex, but must, by definition, be membra disjecta from an earlier codex or
- a single leaf created for insertion or repair
-
‘other’: used for all cases
- which do not fit either codex or leaf for which Wright does not
- provide sufficient information to describe in greater detail
The <supportDesc> element may
- contain the following elements:
-
-
support (support) contains a description of the materials etc. which
- make up the physical support for the written part of a
- manuscript or other object.
-
extent
- (extent) describes the
- approximate size of a text stored on some carrier medium or of
- some other object, digital or non-digital, specified in any
- convenient units.
-
foliation (foliation)
- describes the numbering system or systems used
- to count the leaves or pages in a codex or similar
- object.
-
collation (collation)
- contains a description of how the leaves,
- bifolia, or similar objects are physically arranged.
-
condition (condition)
- contains a description of the physical condition
- of the manuscript or object.
-
-
We have reported the support material for the codicological unit(s) in
- the material attribute of <supportDesc>. Allowed values are: ‘chart’ (for all kinds of paper), ‘perg’ (for parchment and vellum), ‘mixed’, ‘unknown’, or ‘other’. For example:
As a legacy of an earlier encoding model, in some files we used the
- embedded <dimensions> element to
- specify leaf dimensions, including unit of measurement. After 2022,
- we ceased to encode in this way. While we have left these dimensions
- in the data, documents revised since 2022 no longer add data in this
- way.
-
-
-
1.7.1.1.2. Foliation
-
We have used the <foliation> element only
- rarely to provide information about the ordering of folios in the
- manuscript. We have not included numerica data, only prose comments
- by Wright. For example:
-
<foliation><p>Evidently one of the fly leaves of a
- manuscript.</p>
- </foliation>
-
-
-
1.7.1.1.3. Condition
-
Deprecated Practices and Legacy Data:
-
As a legacy of an earlier encoding model, in some files we used the
- <condition> element is used
- to provide a brief description of the overall condition of the
- manuscript. After 2022, we ceased to encode in this way. While we
- have left these <condition> in the data,
- documents revised since 2022 no longer add data in this way.
-
-
-
-
1.7.1.2. Layout
- Description
-
We have used the layout description element, <layoutDesc> to record the number of columns and number
- of written lines if reported by Wright.
-
We give the number of columns and lines in the <layout> element
- using the columns and ruledLines or writtenLines
- attribute. If the number of columns and/or written or ruled lines varies
- give the minimum and maximum values with whitespace in-between.
-
<layoutDesc><layout columns="1" writtenLines="19
- 21"><locus from="1" to="10"/><p>The number of lines in each page
- varies from 19 to 21.</p></layout>
- </layoutDesc>
-
-
-
-
1.7.2. Hand
- Description [UNDER REVISION]
-
Further documentation will be added here.
-
-
-
1.7.3. Decoration
- Description [UNDER REVISION]
-
Further documentation will be added here.
-
-
-
1.7.4. Additions
- [UNDER REVISION]
-
We have used the <additions> element to describe any
- additions to the manuscript such as marginalia, notes by readers or owners,
- colophons, and other additions of interest.
-
Notes for Review Editors (2024)
-
You may come across examples of additions/list/item with empty content which
- were generated by a script in an earlier stage of encoding. If the
- manuscript does not have anything to report in additions, then you can
- delete the whole additions element (triple-clicking on the element name in
- oXygen will select the full element). Note: This section is provided for the
- convenience of the editors undertaking a revision of the data in 2024 and
- will be deleted from the final documentation.
-
-
-
-
1.8. History [UNDER
- REVISION]
-
The <history> element is used to include information about the
- origin, provenance and acquisition of the manuscript, if such is reported by
- Wright.
-
-
1.8.1. Origin
-
Within the <origin> element we have specified the date (<origDate>) and place (<origPlace>)
- (if known) of the manuscript's production. As has been our policy throughout
- SMBL, we have encoded the information as
- reported by Wright. We have not corrected his estimated dates for
- manuscripts based on subsequent scholarship.
-
Divergences from Consolidated Schema:
-
When a Wright does not mention a date, we have not indicated date unknown.
- The absence of an <origDate> element itself indicates
- that there is no date reported. This is a divergence from the Consolidated
- Schema which includes such a statement of date unknown in a <p>.
-
-
1.8.1.1. origDate
-
Dating attributes from the set notBefore, notAfter, from, to and when MUST be used
- for <origDate>
-
from and to denote a
- known period of writing, presumed to be more or less continuous,
- beginning at one date and ending at another. notBefore and notAfter denote the
- terminus a quo and terminus ad quem within which the writing is believed
- to have occured.
-
The values of those attributes are a date, starting with the year, then
- the month, then the day, separated by hyphens (but most often just a
- year, always expressed using four-digits) must be in the Gregorian
- calendar. the calendar attribute records the
- calendar system used by the expression of the date in the text enclosed
- by the <origDate> tags. The text is for display, the attributes
- are the machine-readable interpretation. For example:
When a precise date was not given by Wright, we have use the tables for conversion of approximate dates published by
- Syriaca.org to create numberic ranges. For example, if Wright describes
- a manuscript as being ‘early 9th century’ we have
- used a 50-year (half-century) range from 0800 to 0850.
In all cases we have silently change Wright's Roman numerals for
- centuries to a more readable Arabic numeral equivalent.
-
Information about use of alternate calendars and regnal years will be
- added soon.
-
-
-
1.8.1.2. origPlace
- [Under Revision]
-
-
-
-
-
1.9. Provenance [UNDER
- REVISION]
-
We have used the <provenance> to record notes by Wright
- about the provenance of the manuscript.
-
-
-
1.10. Acquisition [UNDER
- REVISION]
-
Guidelines will be added here in the future.
-
-
-
1.11. Additional
-
The <additional> element is used to provide: information about the
- source of the description; information about the availability and custodial
- history of the manuscript; information about surrogates; bibliography; and links
- to online resources.
-
-
1.11.1. Record source
- and history
-
The <source> element, contained in <recordHist>, provides a prose description of the source(s) from
- which the description has been derived; this information will overlap with
- the information in <respStmt>. It may contain <listBibl> and <bibl> elements.
-
-
<additional><adminInfo><recordHist><source>Manuscript description based on <bibl><ref target="#Wrightpart3">Wright's
- Catalogue</ref></bibl>. abbreviated by the Syriaca.org
- editors.</source></recordHist></adminInfo><listBibl><bibl xml:id="Wrightpart3"><author>William Wright</author><title xml:lang="en">Catalogue of Syriac Manuscripts in
- the British Museum Acquired since the Year 1838</title><pubPlace>London</pubPlace><date>1870</date>
- <ptr target="http://syriaca.org/bibl/8"/><citedRange unit="entry">LXXV. III.</citedRange><citedRange unit="p">1:51</citedRange><ref type="internet-archive-pdf" target="https://archive.org/details/catalogueofsyria01brituoft/page/51"/>
- </bibl></listBibl>
- </additional>
-
-
-
-
1.11.2. Bibliography
-
The bibliography of works from which the manuscript description was derived
- (i.e. Wright's catalogue) are recorded in the <additional>
- element in a <listBibl> element..
-
This section is also used to provide links to online resources such as
- Archive.org.
-
-
<listBibl><bibl xml:id="Wrightpart"><author>William Wright</author><title xml:lang="en">Catalogue of Syriac
- Manuscripts in the British Museum Acquired since the Year 1838</title><pubPlace>London</pubPlace><date>1870</date>
- <ptr target="http://syriaca.org/bibl/8"/><citedRange unit="entry">LXIII</citedRange><citedRange unit="p">1:40-41</citedRange><ref type="internet-archive-pdf" target="https://archive.org/details/catalogueofsyria01brituoft/page/40"/>
- </bibl>
- </listBibl>
-
-
-
-
-
1.12. Palimpsests and
- Other Composite or Multi-Part Manuscripts [UNDER REVISION]
-
-
-
2. Schema
-
-
2.1. Elements
-
-
2.1.1. <TEI>
-
-
-
-
<TEI> (TEI document)
- contains a single TEI-conformant document,
- combining a single TEI header with one or more members of
- the model.resource class.
- Multiple <TEI> elements may be
- combined within a <TEI> (or <teiCorpus>) element. [4. Default Text Structure
- 15.1. Varieties of Composite Text]
Major editions of the
- Guidelines have long been informally referred to
- by a name made up of the letter P (for Proposal)
- followed by a digit. The current release is one of
- the many releases of the fifth major edition of
- the Guidelines, known as P5. This attribute may be
- used to associate a TEI document with a specific
- release of the P5 Guidelines, in the absence of a
- more precise association provided by the source attribute on the
- associated <schemaSpec>.
This element is required. It is
- customary to specify the TEI namespace
- http://www.tei-c.org/ns/1.0 on it, using
- the xmlns attribute.
-
-
-
Example
-
<TEI version="3.3.0"
- xmlns="http://www.tei-c.org/ns/1.0"><teiHeader><fileDesc><titleStmt><title>The shortest TEI
- Document Imaginable</title></titleStmt><publicationStmt><p>First published as part
- of TEI P2, this is the P5 version using a name
- space.</p></publicationStmt><sourceDesc><p>No source: this is an
- original work.</p>
- </sourceDesc>
- </fileDesc></teiHeader><text><body><p>This is about the
- shortest TEI document imaginable.</p></body></text>
- </TEI>
-
-
-
Example
-
<TEI version="2.9.1"
- xmlns="http://www.tei-c.org/ns/1.0"><teiHeader><fileDesc><titleStmt><title>A TEI Document
- containing four page images </title></titleStmt><publicationStmt><p>Unpublished
- demonstration file.</p>
- </publicationStmt>
- <sourceDesc>
- <p>No source:
- this is an original work.</p></sourceDesc></fileDesc></teiHeader><facsimile><graphic url="page1.png"/><graphic url="page2.png"/><graphic url="page3.png"/><graphic url="page4.png"/></facsimile>
- </TEI>
-
-
-
Schematron
-
- <sch:rule context="tei:TEI">
- <sch:assert test="matches(@xml:id, '^manuscript_\d+$') or
- contains(base-uri(.), 'genizah-mss')" role="fatal"> The
- root TEI element must have an @xml:id beginning with
- "manuscript_" then a number (which must also be unique
- across the entire catalogue). </sch:assert>
- <sch:assert test="matches(@xml:id, '^volume_\d+$') or
- not(contains(base-uri(.), 'genizah-mss'))" role="fatal">
- The root TEI element must have an @xml:id beginning with
- "volume_" then a number (which must also be unique across
- the entire catalogue). </sch:assert> </sch:rule>
- <sch:rule context="//tei:TEI/@xml:id">
- <sch:let name="fileNo" value="replace(document-uri(/),
- '.*?(\d{1,5}).xml', '$1')"/> <sch:let name="TEIIDno"
- value="replace(., '.+?(\d+)', '$1')"/>
- <sch:assert test="$TEIIDno = $fileNo"> The @xml:id
- attribute must match the number portion of the file name:
- "manuscript_<sch:value-of select="$fileNo"/>".
- </sch:assert> </sch:rule>
+Syriac Manuscripts in the British Library: TEI P5 Customization and Encoding Guidelines for Manuscript Description
Syriac Manuscripts in the British Library: TEI P5 Customization and Encoding Guidelines for Manuscript Description
This version of the encoding guidelines for Syriac Manuscripts in the British Library: A New Digital Edition of Wright’s Catalogue were drafted in 2024 by David A. Michelson with assistance from William L. Potter and Daniel L. Schwartz. These guidelines are part of a larger a community effort to develop uniform good practice in the cataloguing manuscripts using TEI. They are derived from a common consolidated schema currently used by cataloguers at a number of institutions including the British Library, the Bodleian Libraries, Cambridge University Library, the John Rylands Library, and the Wellcome Trust. They remain under development and contributions are welcome via pull requests or issues submitted to the GitHub repository hosted by Syriaca.org. They are licensced under a Creative Commons Attribution 4.0 International license. Users may cite the guidelines in this way: David A. Michelson, et. al., eds. Syriac Manuscripts in the British Library: TEI P5 Customization and Encoding Guidelines for Manuscript Description (Syriaca.org: 2024), https://github.com/srophe/britishLibrary/blob/main/documentation/schema/Syriacamsdesc.html.
Welcome to the encoding guidelines for Syriac Manuscripts in the British Library: A New Digital Edition of Wright’s Catalogue. These guidelines describe the methodology used to create TEI XML files for describing Syriac manuscripts according to the schema implemented by Syriaca.org in the project Syriac Manuscripts in the British Library. For the moment, these guidelines cover only the description rather than the transcription of manuscripts. Syriaca,org hopes to expand these guidelines to include transcription in the future. We have chosen to use the TEI guidelines because they allow both a high level of detail and flexibility. We anticipate that this schema can be easily adapted for other Syriac manuscript catalogues and we invite comments and suggestions for improvement.
1.2. Acknowledgements
These guidelines are based on the following sources. The general editors began by following the encoding guidelines for the Fihrist Union Catalogue of Manuscripts from the Islamicate World and the ENRICH TEI P5 ODD, which were then modified by Syriaca.org into a Syriaca TEI for MSS Manual (now deprecated). In many cases, we reproduced the Fihrist guidelines verbatim. In turn these earlier encoding guidelines were updated in 2024 to be largely compatible with the Consolidated TEI P5 Customization and Encoding Guidelines for Manuscript Description for western medieval manuscripts jointly created by Cambridge University Library (James Freeman, with Suzanne Paul) and the Bodleian Library (Matthew Holford) with contributions by Andrew Dunning (formerly British Library) and James Cummings. When applicable, we have reproduced the consolidated guidelines verbatim in our own guidelines. (Those consolidated guidelines in turn draw in places on earlier western medieval manuscript guidelines created by Patrick Granholm and Eva Nyström for manuscripta.se.)
1.3. General Principles
It is essential to note that we have customized these guidelines specifically for use in digitally encoding the manuscript descriptions made by William Wright in his Catalogue of Syriac Manuscripts in the British Museum (3 vols., 1870-1872). Due to this specialized use, these guidelines do not include all possible TEI XML features which might be desired either for cataloguing Syriac manuscripts or for medieval manuscripts in general. For example, because Wright does not provide detailed descriptions ofthe modern custodial history of the manuscripts we have not utlized those features in these guidelines. Similarly, because the main language of Wright's catalogue is English, these guidelines assume that each file will have English as its main language.
In addition, we have followed the guidelines below with the assumption that the resulting XML files for the Syriac Manuscripts in the British Library project (hereafter SMBL) will be displayed using the custom Srophe App developed by Syriaca.org. We have also made an effort to ensure compatibility (as much as possible) with the HTML tools and transformations developed for the Consolidated TEI P5 Guidelines for Manuscript Description.
1.3.1. Editorial Notes and Interventions
Syriac Manuscripts in the British Library: A New Digital Edition of Wright’s Catalogue has been concieved of as a digital representation of William Wright's catalogue. SMBL is not intended to be a revision of Wright or a re-cataloguing of the manuscripts themselves. For the vast majority of manuscripts described in this project, we (the editors of SMBL) have reproduced Wright's prose verbatim without verifying his descriptions against the manuscripts. While that level of comparison is beyond the scope of this present project, we hope that the digital encoding of SMBL might serve as a foundation for such a new cataloguing effort in the future.
In general we make no claims about the reliability of Wright's descriptions as reproduced in SMBL. Because our goal was to encode Wright's catalogue as written, we have reproduced his attributions of authorship and his dating of the manuscripts, even in cases where these may now be disputed or revised by subsequent scholarship. We, ofcourse, agree that such an update to his catalogue would be valuable in the future. SMBL is published under an open access license and we would be delighted to collaborate with any interested scholars in such a future update. Such a revision, however, needs a base text as a starting point, hence our decision to encode Wright's catalogue "as is" in the first edition of SMBL.
Even with the stated goal of verbatim reproduction, we have had to make a few editorial interventions during the course of encoding. In most casese, these interventions were necessitated by the precision of encoding which required us to make explicit some data which Wright may have left implicit or imprecise in his prose. These interventions have occured in the following primary cases (each of which follow the principles of Wright's own descriptions):
When our editors have found a clear typographical or internal inconsistency in Wright's descriptions, we have corrected these errors for the sake of clarity.
When our editors have discovered inconsistency in Wright's identification of codicological units, we have further divided single shelfmarks into further manuscript parts in a method similar to that used by Wright himself. Most often our editorial interventions in this regard have been to identify fly-leaves as separate manuscript fragments when Wright may have grouped them together. These new codicological divisions are identifiable because they will share the same roman numeral from Wright's print catalogue but each have a different URI.
When Wright has lapsed from his usually methodical listing and numbering of manuscript items, we have attempted in some cases to adapt Wright's prose back to the form of a list of manuscript contents. For example, we have frequently made this editorial intervention when Wright has chosen to describe the undertext of a palimpsest in a paragraph rather than an as an outline of contents.
Finally, SMBL has made one further type of modern editorial intervention in Wright's prose. In the century and a half that have passed since Wright wrote, scholarly values concerning the preservation of cultural heritage have changed profoundly. In some cases, Wright's descriptions reflect his prejudices as a European scholar in the nineteenth century. Because SMBL is an open access resource widely available on the internet, we did not wish to reproduce Wright's prose without context. Accordingly, in some places in which Wright expressed pejorative or other derogratory opinions, we have added an editorial note to indicate that these opinions do not reflect the opinions of the editors of SMBL nor do they represent the approach of contemporary scholars in the field of Syriac studies. ]
Editorial notes made by SMBL related to the various interventions described above have been encoded with the <note> element with type of ‘editorial’. This type distinguishes these editorial notes from notes made by Wright himself which are either without any type or marked as type of ‘footnote’. An example of an modern editorial note is as follows:
<note type="editorial">
+<!-- Need to make example from https://bl.syriac.uk/ms/363 -->
+</note>
1.3.2. References to Locations within a Manuscript
References to a specific location or range of folia within a manuscripts are given in a <locus> element which can be inserted within a number of different elements. The <locus> element marks the location of the parent element’s material within the manuscript and thus should be nested within the element it modifies. Typically the <locus> will refer to a folio or a range of folio numbers within the manuscript. When describing folio numbers, it is our policy to follow Wright's usage and use ‘a’ to refer to the recto of a folio, and ‘b’ to refer to the verso. Where Wright does not specify recto or verso, we encoded a folio number without ‘a’ or ‘b’. In prose, there should always be a whitespace between the folio number and the ‘a’ or ‘b’. But in attribute values, there should be no whitespace, e.g. ‘232b’:
<locus from="232b">Fol. 232
+ b</locus>
A text node (eg. ‘foll. 21 a-22 b’) is not required for many uses of <locus> (such as when it is used nested in an <msItem>), but least one attribute value must also be encoded with every <locus>, either from or to or both. (Since Wright's catalogue does not often give ending ranges, the to occurs less in the data). These attribute values may be used in the future to enable links to folio images or calculation of lengths of manuscript items. Frequently in Wright’s catalogue the beginning location of a manuscript item is given, but not the ending location. In this situation, our policy is to record only the listed opening location in Wright’s catalogue as the beginning of the range in the attribute from. We do not supply a to attribute unless Wright has indicated on what folio the msItem ends, for example by citing an <explicit> or <finalRubric>.
The following examples illustrate common uses of <locus>. Whenever possible, the designation folio/folia and their abbreviations were included in the text node of <locus>. as in the exampls below. (Please be aware that Wright uses "Fol." for a single folio and "Foll." for a range of folia. We adapt Wright's capitalization of based on context. If "Fol." stands alone in a list it is capitalized. If "fol." occurs in the middle of other prose it is capitalized according to the rules of the sentence.):
<msItem>
+ <locus from="232b">Fol. 232 b</locus>
+ <title ref="http://syriaca.org/work/9687"
+ xml:lang="en">The
+ Gospel of S. Matthew</title>
+</msItem>
+<!--...-->
+<additions>
+ <list>
+ <item>
+ <label>Colophon</label>
+ <locus from="184a"/>
+ <p>Of the note written by the scribe on <locus from="184a">fol. 184 a</locus> the greater part
+ has been erased, but from what remains it appears
+ that this book was copied for <persName>a priest
+ named Lazarus</persName>.</p>
+ </item>
+ </list>
+</additions>
Notes for Review Editors (2024)
Please ignore the missing white space in the text node of <locus> For example, in the text nodes of locus for folia numbers, such as
<locus from="81a">fol. 81a</locus>
this text node should have a space between ‘81’ and ‘a’ like this
<locus from="81a">fol. 81
+ a</locus>
, but you do not need to change it, we have a script make this correction across all the data. Note: This section is provided for the convenience of the editors undertaking a revision of the data in 2024 and will be deleted from the final documentation.
Deprecated Practices and Legacy Data:
As a legacy of an earlier encoding model, the SMBL data contains some folio ranges encoded as numerals in to without "a" or "b". In this earlier data model, we attempted to deduce the end of ranges for manuscript items when not specified by Wright. Similarly when Wright's prose indicated that his description applied only to a single folio (for example when describing a marginal note), our policy was previously to list that location in both from and to attributes. After 2022, we ceased to encode in this way. While we have left these estimates in the data, documents revised since 2022 longer add estimated data in this way.
Divergences from Consolidated Schema:
In SMBL we have assumed that <locus> refers to a folio or folio range unless otherwise indicated. Accordingly, we do not use the scheme attribute to indicate the foliation scheme except in cases where the <locus> refers to something other than a folio, such as a column.
1.3.3. Indentification of Persons, Places, Titles, Citations, and Manuscripts with Syriaca.org URIs
In these authority files, each entity is an individual abstract concept identified by a unique URI. For example, the person known as Ephrem the Syrian is identified by the URI: http://syriaca.org/person/13 and the city of Edessa where he spent much of his life is identified as http://syriaca.org/place/78. The necessity of using unique strings of characters instead of traditional names arises from the occurrence of homonymous entities. For example, The Syriac Gazetteer has entries for 69 different churches and monasteries each with the name ‘Mar George’. Accordingly, all Syriaca.org URIs are unique—each identifying only one conceptual entity. Thus, every ‘Church of Mar George’ is assigned a separate URI.
Syriaca.org URIs are not merely random strings of text and numbers; they are HTTP URIs, meaning that each URI is also a URL (a Uniform Resource Locator, e.g. an HTTP address). Thus, Syriaca.org’s URI for Ephrem the Syrian, http://syriaca.org/person/13, is also a valid HTTP address. The benefit of using HTTP URIs is that these URIs are ‘self-descriptive’ in that each URI is also an HTTP link to a web document describing or defining the concept identified by the URI. Although perhaps obvious to state, the web document which is returned from a Syriaca.org URI is only a definition of the concept named by the URI, not the entity itself (thus the address http://syriaca.org/place/78 does not allow one to download the real-world city of Edessa, but a web page describing that city!).
In the Syriaca.org data model, each URI represents a conceptual thing with a mental existence related to, but not reducible to, its historical or physical manifestation. Syriaca.org adopted this broad definition so that mythological and other ahistorical persons, places, and concepts can be assigned URIs. For example, the concept identified by the URI http://syriaca.org/person/13 identifies not only the historical person Ephrem the Syrian, but also the supra-historical hagiographical and pseudepigraphal traditions about him. Following this same logic, any historical concept can be described in the Syriaca.org URI model, even if its historical existence was only in the cultural imaginary.
The Syriaca.org authority files and URIs are central to the data model of SMBL, accordingly the sections below describe in greater detail how we have encoded these entities throughout the data.
Notes for Review Editors (2024)
If you find that a <persName>, a <placeName>, or a <bibl> used for a modern bibliographic citation is missing a URI, please follow these steps: Search for a URI at Syriaca.org or the Comprehensive Syriac Bibliography If you do not find a URI, create a temporary URI following the guidelines provided to you. Insert the new temporary id into the ref for the <persName> or <placeName> or in bibl/ref/target (you will need to create the <ref> and add it inside the <bibl>). Note: You do NOT need to add URIs to <title> or <ref> elements for Syriac literary works except in the case of books of the Bible. There are Syriaca.org URIs available for those, so please mark those if possible. Note: This section is provided for the convenience of the editors undertaking a revision of the data in 2024 and will be deleted from the final documentation.
1.3.3.1. Personal Names
As a general rule personal names have been tagged, for example when they occure inside the elements <author>, <editor> or in any descriptive element such as the <handNote> or an <item> in <additions>. In these cases, the name is wrapped with the element <persName> and the language(s) of the name supplied with attribute xml:lang. Exceptions to this rule were made when a personal names occurs as part of a title of a work (Extracts from the Homilies of John Chrysostom) or as part of a place name (e.g. The Convent of Mar Isaac). In these cases the prose was marked as a title or place name instead and the personal names were not tagged:
<msItem>
+ <title xml:lang="en">Works of Gregory bar Hebraeus</title>
+</msItem>
<origPlace ref="http://syriaca.org/place/360">Convent of S.
+ Mary Deipara.</origPlace>
All <persName> elements (or else the containing <author> or <editor> element) are required to have a ref attribute which points to a Syriaca.org person URI published in the Syriac Biographical Dictionary. A URI is a Uniform Resource Identifier which is a unique identifying number for each person. For example the URI https://syriaca.org/person/13 identifies Ephrem the Syrian in this first example:
The <persName> element can also be used inside prose descriptions.
<note>
+ <persName ref="http://syriaca.org/person/51">Severus</persName> is cited on <locus from="224a">fol.
+ 224 a</locus>.
+</note>
Notes for Review Editors (2024)
In some files we may have previously over-normalized the spelling of author names compared to what Wright provides (e.g., changing Jacob of Batnae to Jacob of Serugh). We now wish to revert these changes, so please check and restore the name spelling as Wright provides it. Note: This section is provided for the convenience of the editors undertaking a revision of the data in 2024 and will be deleted from the final documentation.
Deprecated Practices and Legacy Data:
Our policy is to report the names in the same prose given by Wright. In a future update of SMBL, we may also provide a uniform name where the spelling or name used by Wright is no longer commonly used in scholarship. A few examples of these are already present in our data in the form below (where the "supplied" type reflects Wright's Romanization of the name. Encoders should not enter these "uniform" names as they will be inserted later by a script.
Because Syriaca.org already provides an integrated authority file for persons using Syriaca.org URIs, we do not use the key attribute required by the Consolidated Schema. We also do not use the element <orgName> since it is not a useful entity for our historical data, instead Syriaca.org uses the <persName> element in a slightly broader manner than the TEI guidelines. A <persName> element may be used to refer to a name for a single person or a group of persons.
1.3.3.2. Place Names
As a general rule place names have been tagged with either <origPlace> or with <placeName>, for example when they occur inside in any descriptive element such as <note>, <handNote>, or an <item> in <additions>. In most cases, the place name is wrapped with the element <placeName> and the language(s) of the name supplied with attribute xml:lang. Exceptions to this rule are as follows:
In the description of the manuscript origin (on which, see more documentation below), the prose place name is placed directly in the text node of the <origPlace> element (without using <placeName>) while any other place names mentioned in reference to the place of origin are wrapped in <placeName>:
<origPlace ref="http://syriaca.org/place/360">Convent of S.
+ Mary Deipara, in the desert of <placeName ref="http://syriaca.org/place/289">Scete</placeName>.</origPlace>
.
When a place name occurs as part of a title of a work, it is not marked as a <placeName>:
<title>Hom.
+ liii. On the calamities reported to have befallen
+ the city of Alexandria</title>
nor is a place name marked when it is part of a personal name:
<persName>Paul
+ of Callinicus</persName>
In these cases (shown above) the prose was marked as a title (using either <title> or <ref>) or <persName> instead and the internal references t0 place names were not tagged.
All <placeName> elements or <origPlace> elements are required to have a ref attribute which points to a Syriaca.org place URI published in The Syriac Gazetteer. A URI is a Uniform Resource Identifier which is a unique identifying number for each place. For example the URI http://syriaca.org/place/78 identifies the city of Edessa in these examples:
<p>On <locus from="258a">fol. 258 a</locus>, after the doxology,
+ we read the following note, giving the date and stating that
+ the volume was written at <placeName ref="http://syriaca.org/place/78">Edessa</placeName>, at
+ the expense of the deacon <persName>Thomas of Zěmārtā
+ Castra</persName>.</p>
Our policy is to report the place names in exactly the same prose given by Wright. In a future update of SMBL, we may also provide a uniform name where the spelling or name used by Wright is no longer commonly used in scholarship.
Divergences from Consolidated Schema:
Because Syriaca.org already provides an integrated authority file for places using Syriaca.org URIs, we do not use the key attribute required by the Consolidated Schema nor do we include the nested information in <origPlace> such as <country>, <region> and <settlement>. These relationships can be found separately in The Syriac Gazetteer.
1.3.3.3. References to Literary Works
As a general rule references to titles of literary works have been tagged in one of two methods.
When the title is identifying the intellectual contents of a manuscript item, it is encoded with <title> as a child of <msItem>. When encoding with the <title> element, the language of the prose in the <title> text node must also be indicated with attribute xml:lang. Rules for encoding titles as part of manuscript items are discussed in greater detail below.
When a reference to a literary work is made elsewhere in the XML document it is encoded with <ref> as a child of <note>.
At present the state of authority control for titles of Syriac works is incomplete, so we have not required references to URIs for works in SMBL. When possible we have included URIs published in The New Handbook of Syriac Literature . A URI is a Uniform Resource Identifier which is a unique identifying number for each literary work (as a conceptual entity). References to URIs for literary works, (using either <title> or <ref>) are marked up in an attribute value. For <title> the URI is placed in a ref attribute. For the element <ref> the URI is placed in a target attribute. For example the URI http://syriaca.org/work/1 identifies the book of Genesis in the Peshitta Version in this <title>:
<msItem xml:id="a1" n="1" defective="true">
+ <locus from="1a"/>
+ <title xml:lang="en"
+ ref="http://syriaca.org/work/1">The
+ book of Genesis, according to the Peshitta
+ version.</title>
+ <rubric xml:lang="syr">
+ <locus from="2b" to="2b"/>ܒܪܝܬܐ ܣ̣ܦܪܐ
+ ܩܕܡܝܐ ܕܐܘܪܝܬܐ</rubric>
+</msItem>
<note>See <ref target="http://syriaca.org/work/9578">2
+ Maccabees, ch. i. 18, seqq.</ref>
+</note>
In this example, a <note> refers to a work, the Constitutiones Apostolorum, for which there is no Syriaca.org URI. In this case no target is used, but the instead a type attribute value of "work" must be applied (to distiguish from other uses of <ref> in the XML document.
<note>These are extracts from <ref type="work">the eighth book
+ of the Constitutiones Apostolorum</ref>; see
+<bibl>Labbe, t. i., coll. 153, seqq.</bibl>.</note>
Our policy is to report the references to works in exactly the same prose given by Wright. In a future update of SMBL, we may also provide a uniform name where the form used by Wright is no longer commonly used in scholarship.
Divergences from Consolidated Schema:
Because Syriaca.org already provides an integrated URI authority file for works using Syriaca.org URIs, we do not use the key attribute recommended by the Consolidated Schema.
1.3.3.4. Bibliographic Citations
Citations of printed biblographic items (books, articles, etc.) have been tagged with the <bibl> element. These citations can be found in two places:
They may be grouped in a bibliography located in the <additional> section of each entry. Guidelines for this bibliography (including examples of child elements nested in <bibl>) are given below.
Citations have also been marked up with <bibl> throughout the manuscript description occuring as child elements of <msItem>, <note>, or other descriptive elements. For this second form of citation, we have generally refrained from adding additional markup inside the <bibl> element except for linking to URIs.
In both cases, the bibliographic citation may be linked with a URI by using a child element <ref> with the URI is placed in a target attribute on <ref>. At present the state of authority control for Syriac bibliography is incomplete. Accordingly, we have only encoded URIs for bibliographic citations when available. Currently we rely on two sources of URIs. Some citations are linked with uris of the format ‘http://syriaca.org/bibl/8’ from Syriaca.org. Others are marked with URIs from The Comprehensive Bibliography on Syriac Studies of the format ‘https://www.zotero.org/groups/4861694/a_comprehensive_bibliography_on_syriac_studies/items/WMADLJWW/library’. In a future development, all of these citation URIs will be merged to a format of ‘http://syriaca.org/cbss/WMADLJWW’.
This modified example from https://bl.syriac.uk/ms/28 illustrates the use of the second type of citation:
<note>See<bibl>Assemani, Bibl. Or., t. ii., p. 335 <ref target="https://www.zotero.org/groups/4861694/a_comprehensive_bibliography_on_syriac_studies/items/WMADLJWW/library"/>
+ </bibl>.</note>
Our policy is to report the references to bibliography in exactly the same prose given by Wright. In a future update of SMBL, we may also provide a uniform citation where the form used by Wright is no longer commonly used in scholarship.
1.3.3.5. Cross-References to Other Manuscripts
Cross-references in the description to other manuscripts should be enclosed in <bibl> tags with type of value MS. When possible the cross-reference may also be linked linked with a child <ptr> element with target attribute pointing to the URI for the other manuscript.
At present the state of authority control for Syriac manuscripts is incomplete. Accordingly, we have only encoded URIs in the case of cross-reference to manuscripts within SMBL. This example from manuscript Add. 14,533 https://bl.syriac.uk/ms/260 shows how SMBL URIs are encoded to show a relationship between Add. 14,533 and two other manuscripts (Add. 12,155 and Add. 14,532):
<note>In part identical with the contents of <bibl type="MS">Add. 12,155<ptr target="https://bl.syriac.uk/ms/30"/>
+ </bibl> and <bibl type="MS">Add. 14,532<ptr target="https://bl.syriac.uk/ms/259"/>
+ </bibl>.</note>
When a manuscript reference refers either to a folio locus or to an entry number in Wright's catalogue, then a <citedRange> element should be added inside the <bibl>.
For references to manuscripts outside of SMBL we do not include a URI as illustrated in this modifed example from https://bl.syriac.uk/ms/739
<note type="footnote" xml:lang="en">See the similar heading in
+ the <bibl type="MS">Bodleian manuscript, Hunt.
+ 109</bibl>.</note>
Our policy is to report the references to manuscripts in exactly the same prose given by Wright. In a future update of SMBL, we may also provide a uniform shelfmark where the form used by Wright is no longer commonly used in scholarship.
Divergences from Consolidated Schema:
SMBL has used <citedRange> which is not mentioned in the Consolidated Schema guidelines but is conformant with the TEI guidelines.
1.3.4. Formatting
We have avoided marking up formatting using the <hi> element. The empty element <lb> has been used to indicate line breaks (e.g. line beginnings) when Wright provides transcriptions of Syriac or Arabic text.
1.3.5. Attribute values
Some attributes can take more than one value, in which case the values are separated by a single whitespace. For example, in this case two Syriaca.org work URIs are included in the same ref:
<title xml:lang="en"
+ ref="http://syriaca.org/work/9568 http://syriaca.org/work/9542">Jeremiah and Lamentations</title>
Attribute values forming more than one word in natural language have been separated by a hyphen, - (U+2010), as in this example of medium:
<handNote xml:id="handNote2" scope="minor"
+ script="syr" medium="red-ink">
+ <ref target="#a2"/>The Ammonian sections and Eusebian canons are
+ marked in the text with red ink.
+</handNote>
In a few rare cases, ‘camelCase’, has been used for attribute values forming more than one word in natural language.
Divergences from Consolidated Schema:
SMBL has prefered to use a hyphen rather that camelCase for attribute values longer than one word in length.
1.3.6. Transcription
The <rubric>, <incipit>, <explicit>, <finalRubric>, and <quote> elements are used to encode Syriac text transcribed from the manuscripts. The have been reproduced verbatim from William Wright's catalogue. Caveat lector! Transcriptions have not been re-checked against the original manuscripts. In addition, the <quote> element has been used to encode prose (in any language) which Wright marked with quotation marks (e.g. inverted commas).
In all cases these elements should be marked with the an xml:lang attribute to indicate the language of the transcribed text.
1.3.6.1. Abbreviations and Expansions
Sometimes Wright offers an expansion of abbreviations found in the manuscripts. In these cases we have provided Wright's expanded prose using the nesting elements <choice> and children <abbr>, and <expan>. In these cases, Wright is credited as the one responsible for the expansion through the use of resp with a value pointing to the xml:id for Wright: https://bl.syriac.uk/documentation/editors.xml#wwright. See this modified example from Add. 17,262 (https://bl.syriac.uk/ms/1078) in which Wright expands a Syriac abbreviation:
For the sake of clarity, the SMBL editors have sometimes expanded abbreviations in Wright's own prose using the nesting elements <choice> and children <abbr>, and <expan>. This is one of the few ways in which we have modified Wright's original publication. See this example in which we have expanded ‘Ps.’ to ‘Psalm’ to facilitate search results:
<title>Commentary on <choice>
+ <abbr>Ps.</abbr>
+ <expan>Psalm</expan>
+ </choice> xcii.</title>
Divergences from Consolidated Schema:
SMBL has prefered to use a <abbr>, and <expan> rather than <ex> as used in the Consolidated Schema.
1.3.6.2. Sic [UNDER REVISION]
SMBL uses <sic> to both to mark errors reported by Wright using ‘sic’ and to report mistakes made by Wright identified by the SMBL editors. At present we are still revising our guidelines on the use of <sic> and those will be added here once this revision is complete. We are also considering how to represent questions marks used by Wright in the text.
Notes for Review Editors (2024)
Please ignore the use of <sic> as an element or in prose. Similarly please ignore Wright's use of square brackets [...]. These will be normalized by a script at a later stage. Note: This section is provided for the convenience of the editors undertaking a revision of the data in 2024 and will be deleted from the final documentation.
1.3.6.3. Supplied [UNDER REVISION]
The <supplied> element has been used both for Wright's own editorial additions and for editorial additions to Wright's catalogue made by the editors of SMBL, At present we are still revising our guidelines on the use of <supplied> and those will be added here once this revision is complete. These guidelines will include the use of resp with a value pointing to the xml:id for Wright or the modern SMBL editors and the use of the nesting elements <choice> and children <orig>, and <reg>.
Notes for Review Editors (2024)
Please ignore the use of <supplied> as an element, as an attribute value or in prose. These will be normalized by a script at a later stage. Note: This section is provided for the convenience of the editors undertaking a revision of the data in 2024 and will be deleted from the final documentation.
1.3.6.4. Deletions [UNDER REVISION]
in rare cases, deletions by the scribe or later annotators which are reported by Wright have be recorded using the <del> element. At present we are still revising our guidelines on the use of <supplied> and those will be added here once this revision is complete.
1.3.6.5. Gaps [UNDER REVISION]
In rare cases, gaps in the manuscriptwhich are reported by Wright have be recorded using the <gap> element. At present we are still revising our guidelines on the use of <supplied> and those will be added here once this revision is complete.
1.3.7. Quotations from the Manuscript
When Wright gives a quotations from a manuscript, outside of elements such as <incipit>, <explicit> and so on, these have been enclosed in the <quote> element and marked with an xml:lang attribute.
In addition, <quote> has been used whenever Wright provides text in quotation marks, which may be a quotation of a third source (beyond the manuscripts and his catalogue) or which may be his English translation of a quotation from a manuscript.
Divergences from Consolidated Schema:
SMBL uses the <quote> element instead of the <q> element used in the Consolidated Schema.
1.3.8. Phrases and Words in Languages Other Than English
Phrases or words in other languages than English are tagged by adding the xml:lang attribute to the element enclosing the text, or where no other element is available with a <foreign> element and a xml:lang attribute.
By default the Srophe App will display text in the <foreign> in italic unless it is marked as Syriac, in which case additional right-to-left formatting will be applied. For a list of allowed language attribute values see below.
1.3.9. Transcription of Characters, Symbols, and Diacritics in Unicode
All text and symbols have been encoded using the Unicode Standard. When Wright has Romanized Syriac characters, we have followed his Romanization system and used unicode diacritics for macrons, dots above, below, etc. For representation of alaph (ܐ) and ʿayin (ʿē, ܥ) we have changed Wright's use of apostrophe (') for the unicode half-ring characters, U+02BE ʾ Modifier Letter Right Half Ring and U+02BF ʿ Modifier Letter Left Half Ring, respectively.
1.3.9.1. Images and Characters that Cannot be Encoded
Wright's printed catalogue includes characters and symbols for which there is not yet a unicode character or code point. Examples include the use of omega as a Syriac vowel or the use of crosses, circles, and dots as end of paragraph markers. In the cases where unicode characters are not available or where Wright provides a diagram or image which cannot be reproduced using XML (for example characters arranged as a cross or circle), we have included a note in the <decoDesc> referring users to a .pdf version of Wright's catalogue.
<decoDesc>
+ <decoNote type="missingContent">The printed edition of
+ Wright's catalogue contains characters or images which
+ cannot be encoded for display as electronic text. Please
+ refer to the printed catalogue to view these characters
+ or images. </decoNote>
+</decoDesc>
Notes for Review Editors (2024)
If you need to enter transliterated or Romanized Syriac using Latin characters, please use combined Unicode characters (e.g. U+1E6D Latin Small Letter T with Dot Below) for dots and diacritics to represent characters such as ḥ, ṭ, ṣ, š, etc. For representation of alaph (ܐ) and ʿayin (ʿē, ܥ), please change Wright's use of apostrophe to the unicode half-ring characters, U+02BE ʾ MODIFIER LETTER RIGHT HALF RING (for aleph) and U+02BF ʿ MODIFIER LETTER LEFT HALF RING (for ʿayin, respectively). You can cut and paste most of these characters from the list here. In some cases you may find the characters $ or % in the text. These were used in an early stage to mark where to enter non-Roman text. $ indicates Syriac text should be entered. In most cases you should check to see if the Syriac is complete, most likely it was entered but this character was not deleted, if so you may delete it. If needed, add the missing Syriac and then delete. The % character was used to indicate that text in Arabic, Greek, Armenian or other non-Roman script should be entered. If you are able, enter that text as described above. Lastly, when you find that the PDF of Wright's catalogue contains either images or special characters which cannot be displayed using Syriac or Greek unicode fonts, please open a GitHub issue, apply the label "cannot display", and include this message in the title of your issue: “PDF contains characters or images which cannot be displayed in XML.” Note: This section is provided for the convenience of the editors undertaking a revision of the data in 2024 and will be deleted from the final documentation.
1.4. The TEI Header
The TEI root element contains a declaration of the TEI namespace, a language declaration, and a unique identifier for the manuscript.
The namespace declaration (xmlns) is the same in every file:
The xml:lang value indicates the language of Wright's manuscript description (and thus the language of file as a whole) and should always be marked as English (‘en’) in every file.
The <TEI> element itself takes an xml:id attribute whose value is constructed from the unique identifier for the XML file and the top level manuscript described in that file. In the example above, the file ‘1.xml’ (which contains manuscript https://bl.syriac.uk/ms/1) has the following xml:id on the root TEI element: ‘manuscript_1’.
The <titleStmt> element describes the TEI XML file, and the cataloguing project of which it is a part, rather than for the manuscript itself (which is described in the <sourceDesc>). Every <titleStmt> contains
a <title> element containing the manuscript shelfmark
editor amd responsibility information giving credit to those responsible for the creation, encoding, and editing of the file (using the <editor> and <respStmt> elements)
<titleStmt>
+ <title xml:lang="en">London, BL, Add. 12133</title>
+ <sponsor>Syriaca.org: The Syriac Reference Portal</sponsor>
+ <funder>National Endowment for the Humanities</funder>
+ <funder>Andrew W. Mellon Foundation</funder>
+ <principal>David A. Michelson</principal>
+<!--...-->
+</titleStmt>
in the example above, we identify Syriaca.org as the sponsoring institution, the National Endowment for the Humanities and the Andrew W. Mellon Foundation as the funding bodies, and the principal researcher undertaking the project as David A. Michelson. This encoding of the <sponsor>, <funder>, and <principal> elements should be identical across all records in SMBL
1.4.1.2. Editorial Credit
Syriaca.org's digital projects are highly collaborative, and so the general editors of SMBL place a high value on giving editorial credit to everyone who contributed in any substantive way to each entry (e.g. each XML document). All editors on the SMBL project are assigned a unique xml:id which is recorded in this reference document https://bl.syriac.uk/documentation/editors.xml. The <titleStmt> gives credit by name to both the general editors for SMBL and the specific editor with authorial or editorial responsibility for the individual XML file so that these can be included in citations of the document. These editor names are encoded in an <editor> element in the following way:
<editor role="general-editor"
+ ref="https://bl.syriac.uk/documentation/editors.xml#dmichelson">David A. Michelson</editor>
+<editor role="general-editor"
+ ref="https://bl.syriac.uk/documentation/editors.xml#wpotter">William L. Potter</editor>
+<editor role="technical-editor"
+ ref="https://bl.syriac.uk/documentation/editors.xml#dschwartz">Daniel L. Schwartz</editor>
+<editor role="creator"
+ ref="https://bl.syriac.uk/documentation/editors.xml#dmichelson">David A. Michelson</editor>
+<editor role="creator"
+ ref="https://bl.syriac.uk/documentation/editors.xml#dgreeson">Daniel J. Greeson</editor>
+<editor role="creator"
+ ref="https://bl.syriac.uk/documentation/editors.xml#thannah">Tucker D. Hannah</editor>
+<editor role="creator"
+ ref="https://bl.syriac.uk/documentation/editors.xml#raydin">Robert Aydin</editor>
In the example above (from the file 1.xml, https://bl.syriac.uk/ms/1/tei), the following types of credit are given using the role attribute:
‘general-editor’ identifies the general editors for the entire SMBL publication
‘technical-editor’ identifies the technical editors for the entire SMBL publication
‘creator’ identifies any editor who created, edited, proofread, or revised the specific XML document (e.g. 1.xml)
As can been seen in the example above, it will be the case that the same person might receive credit for multiple editorial roles.
Divergences from Consolidated Schema:
This use of <editor> is not mentioned in the Consolidated Schema guidelines but is conformant with the TEI guidelines.
1.4.1.3. Responsibility Statment
In addition to using <editor> elements to name the editors with authorial responsibility, each XML file also includes a more detailed description which we have used to assign credit for particular efforts. The <respStmt> element is used to describe each stage in the development of the data or the document. The <respStmt> provides a mechanism for recognizing research assistants who made contributions to processing or cleaning the data, but who are not considered authors or editors of the XML file. (In many cases, the research assistants named here helped to compile the data before it was encoded in XML.
The contents of the <respStmt> element are, in any order, the name of the responsible party contained in a <name> element and a phrase describing the nature of the responsibility (e.g. creator, proofreader, etc.) which is wrapped in a <resp> element. The <name> element should take first a type attribute indicating whether the name refers to a person or a group (with the values ‘person’ or ‘org’). The <name> element should also take a ref attribute which points to the @xml:id of the editor listed at https://bl.syriac.uk/documentation/editors.xml. The creator of the TEI file is identified with a <respStmt> giving the content of the <resp> element as ‘creator’. Additional participants in the creation of the data or the file, for example by entering Syriac or Arabic text, are given additional <respStmt> entries. A modified example from file 1.xml, https://bl.syriac.uk/ms/1/tei is as follows:
<respStmt>
+ <resp>Created by</resp>
+ <name type="person"
+ ref="https://bl.syriac.uk/documentation/editors.xml#dgreeson">Daniel J. Greeson</name>
+</respStmt>
+<respStmt>
+ <resp>Edited by</resp>
+ <name type="person"
+ ref="https://bl.syriac.uk/documentation/editors.xml#thannah">Tucker D. Hannah</name>
+</respStmt>
+<respStmt>
+ <resp>Syriac text entered by</resp>
+ <name type="person"
+ ref="https://bl.syriac.uk/documentation/editors.xml#raydin">Robert Aydin</name>
+</respStmt>
+<respStmt>
+ <resp>Greek and coptic text entry and proofreading by</resp>
+ <name type="person"
+ ref="https://bl.syriac.uk/documentation/editors.xml#rstitt">Ryan Stitt</name>
+</respStmt>
+<respStmt>
+ <resp>Project management by</resp>
+ <name type="person"
+ ref="https://bl.syriac.uk/documentation/editors.xml#ewalston">Elizabeth Walston</name>
+</respStmt>
+<respStmt>
+ <resp>English text entry and proofreading by</resp>
+ <name type="org"
+ ref="https://bl.syriac.uk/documentation/editors.xml#uasyriacaresearchgroup">Syriac Research Group, University of Alabama</name>
+</respStmt>
+<respStmt>
+ <resp>Folio extent edited by</resp>
+ <name type="person"
+ ref="https://bl.syriac.uk/documentation/editors.xml#kurban">Kurt Urban</name>
+</respStmt>
Divergences from Consolidated Schema:
SMBL identifies its editors using a different xml:id method than the Consolidated Schema guidelines but in a way that is still conformant with the TEI guidelines. SMBL uses <name> rather than <persName>.
1.4.1.4. Edition Statement
The 2024 release of SMBL is the first edition. If funding permits, there may be later editions. All XML files are marked with an identical <editionStmt> as follows:
The <edition> element contains no human-readable text.
1.4.1.5. Publication Statement
The <publicationStmt> summarizes the publication of the TEI document, rather than the manuscript itself (which is described in the <sourceDesc>). Our <publicationStmt> contains information about the publishing body (Syriaca.org), a URI for the TEI XML file, the open access license information (Creative Commons Attribution 3.0 Unported License), and the date of publication.
While the URI and the date will vary, the rest of the encoding above should be identical for each file.
1.4.2. Revision Description
The <revisionDesc> element follows its sibling element the <msDesc> (for which see 1.6. Manuscript Description) as a child element of the <sourceDesc> . The revision description is a detailed log of which changes have been made to this file, when, and by whom.
At present a status attribute on each record has the value ‘draft’. The General Editprs will updated this value to ‘reviewed’ after the peer review editors revisions of the file have been completed.
Each revision is encapsulated in a <change> element, ordered in a reverse chronological order from newest to oldest. The <change> element must have the who attribute and may have the when which indicates the person who made the change and he date of the change. The value of when is a date in yyyy-mm-dd format for year-month-day, whereas who will have the value of an xml:id attribute published in https://bl.syriac.uk/documentation/editors.xml. The text node of the <change> element describes the revision that was made.
<revisionDesc status="draft">
+ <change who="https://bl.syriac.uk/documentation/editors.xml#kurban"
+ when="2023-04-21-05:00">CHANGED: added or corrected folio
+ extent values</change>
+ <change who="https://bl.syriac.uk/documentation/editors.xml#dgreeson"
+ when="2013-07-01">Created file</change>
+ <change who="https://bl.syriac.uk/documentation/editors.xml#thannah"
+ when="2013-08-14">Edited file</change>
+ <change who="https://bl.syriac.uk/documentation/editors.xml#jarnwine"
+ when="2014-04-07">Edited file to reflect our definition of
+ colophons. Multiple a-levels changed to one and only one in
+ part 2.</change>
+ <change who="https://bl.syriac.uk/documentation/editors.xml#jarnwine"
+ when="2014-04-10">Added @syriacatags to colophon in
+ p1addition1, p1addition2, and p2addition1.</change>
+ <change type="planned" subtype="arabic"
+ who="https://bl.syriac.uk/documentation/editors.xml#smbl-general-editors">Add missing Arabic text.</change>
+ <change type="planned" subtype="missing"
+ who="https://bl.syriac.uk/documentation/editors.xml#smbl-general-editors">Add missing Syriac vowels.</change>
+ <change type="planned"
+ subtype="arithmetical"
+ who="https://bl.syriac.uk/documentation/editors.xml#smbl-general-editors">Enter arithmetical figures.</change>
+ <change who="https://bl.syriac.uk/documentation/editors.xml#pgmiller"
+ when="2016-07-06">Changed: Files moved to
+ srophe-app-data/data/manuscripts/tei repository.</change>
+</revisionDesc>
The editors of SMBL also use the <change> element to track items that need revision in the future. These are marked with type of ‘planned’ and a subtype from a controlled list of types of changes. All ‘planned’ changes are assigned to an xml:id for the general editors: ‘https://bl.syriac.uk/documentation/editors.xml#smbl-general-editors’.
Notes for Review Editors (2024)
Please begin by checking the <revisionDesc> to see if there are any change/type=‘planned’ that you are able to complete (such as adding in Arabic). Please do not edit the revisionDesc/change after you complete the revision. Instead, leave the change description there even after you complete the requested change as we will use it to find the changes you made and proofread them. If you are not able to make the change, please create an issue noting such on GitHub online so we can make the change later. (For example, if you do not work in Arabic, do not add Arabic text. Or for example, if the Syriac characters needed in the document do not exist in unicode fonts and cannot be added create an issue noting this). Note: This section is provided for the convenience of the editors undertaking a revision of the data in 2024 and will be deleted from the final documentation.
Divergences from Consolidated Schema:
SMBL requires the <change> element have the who attribute but when is optional (this is the reverse of the Consolidated Schema). SMBL uses status on <revisionDesc> and type and subtype on <change> which are not mentioned in the Consolidated Schema guidelines but are conformant with the TEI guidelines.
1.5. Subject Classifications [UNDER REVISION]
SMBL reproduces the subject classifications used by Wright in his catalogue. A further description of this taxonomy will be added here.
1.6. Manuscript Description
All manuscript description takes place in the <msDesc> element which is contained in a parent <sourceDesc> element. Within <msDesc> and its descendent elements is all the information about the manuscript as a physical object, its constituent parts, and intellectual works represented within.
All manuscript descriptions must be informed by attention to codicological units. In other words, whether the manuscript was created in one place, over one period of time, or is a composite of parts from multiple sources, assembled at a later date. In the case of the Syriac manuscripts in the British Library, it is often the case that manuscripts which were originally physically distinct, are now bound together. In such cases, multiple codicological units can be found sharing a single shelfmark. Add. 12,133 is an example of one binding containing multiple manuscripts.
If the manuscript forms a single codicological unit, its intellectual content, physical description, and history are described directly under the <msDesc> element.
If the manuscript comprises multiple codicological units, each unit has been described in a separate <msPart> element, and only information common to the whole manuscript is described directly under the <msDesc> element in this manner:
<msDesc xml:id="manuscript-1">
+<!-- Common information -->
+ <msPart xml:id="Part1" n="1">
+<!-- Codicological unit 1 -->
+ </msPart>
+ <msPart xml:id="Part2" n="2">
+<!-- Codicological unit 2 -->
+ </msPart>
+</msDesc>
As show above, the <msDesc> element should always have a unique xml:id which is formed from the URI for the manuscript according to the pattern manuscript-(URI number). For mult-part manuscript, the <msPart> element will also have an xml:id and an n created from the number of the manuscript part.
The Syriac manuscripts in the British Library have had a number of variant indentifiers. Not only can the current shelfmarks be expressed with or without commas (Add. 12,178 or Add. 12178) or the prefixes ‘Additional’, ‘Add’. or ‘MS’, but Wright also assigned roman numerals to his entries which have been widely used in later scholarship. One goal of publishing SMBL is to create permanent URIs to facilitate easier citation of the manuscripts in digital databases. Accordingly, SMBL has assigned a URI as the primary identifier encoded in the <idno> in the <msIdentifier>. Using these URIs, the <msIdentifier> in each file looks similar to this example from Add. 12,178 which is URI https://bl.syriac.uk/ms/10:
<msIdentifier>
+ <country>United Kingdom</country>
+ <settlement>London</settlement>
+ <repository>British Library</repository>
+ <collection>Oriental Manuscripts</collection>
+ <idno type="URI">https://bl.syriac.uk/ms/10</idno>
+ <altIdentifier>
+ <idno type="BL-Shelfmark">Add. 12,178</idno>
+ </altIdentifier>
+ <altIdentifier>
+ <idno type="BL-Shelfmark-display">London, BL, Add.
+ 12,178</idno>
+ </altIdentifier>
+ <altIdentifier>
+ <idno type="BL-Shelfmark-simplified">BL Add MS 12178</idno>
+ </altIdentifier>
+ <altIdentifier>
+ <collection>William Wright, Catalogue of the Syriac
+ Manuscripts in the British Museum Acquired since the
+ Year 1838</collection>
+ <idno type="Wright-BL-Arabic">161</idno>
+ </altIdentifier>
+ <altIdentifier>
+ <collection>William Wright, Catalogue of the Syriac
+ Manuscripts in the British Museum Acquired since the
+ Year 1838</collection>
+ <idno type="Wright-BL-Roman">CLXI</idno>
+ </altIdentifier>
+</msIdentifier>
In the example above the type values on the element <idno> are controlled to facilitate searching by type of shelfmark or URI.
For a multi-part manuscript, the <msIdentifier> which is a direct child of <msDesc> will contain the shelfmarks which are shared by both parts (for example if both are part of Add. 12,133). The identifiers and shelfmarks which are unique to the individual parts will be contained by separate <msIdentifier> elements which are direct children of <msPart>, as in this example:
<sourceDesc>
+ <msDesc xml:id="manuscript-1">
+ <msIdentifier>
+ <country>United Kingdom</country>
+ <settlement>London</settlement>
+ <repository>British Library</repository>
+ <collection>Oriental Manuscripts</collection>
+ <idno type="URI">https://bl.syriac.uk/ms/1</idno>
+ <altIdentifier>
+ <idno type="BL-Shelfmark">Add. 12,133</idno>
+ </altIdentifier>
+ <altIdentifier>
+ <idno type="BL-Shelfmark-display">London, BL, Add.
+ 12,133</idno>
+ </altIdentifier>
+ <altIdentifier>
+ <idno type="BL-Shelfmark-simplified">BL Add MS
+ 12133</idno>
+ </altIdentifier>
+ </msIdentifier>
+<!--...-->
+ <msPart xml:id="Part1" n="1">
+ <msIdentifier>
+ <idno type="URI">https://bl.syriac.uk/ms/2</idno>
+ <altIdentifier>
+ <idno type="BL-Shelfmark">Add. 12,133, foll.
+ 1–108</idno>
+ </altIdentifier>
+ <altIdentifier>
+ <idno type="BL-Shelfmark-display">London, BL, Add.
+ 12,133, foll. 1–108</idno>
+ </altIdentifier>
+ <altIdentifier>
+ <idno type="BL-Shelfmark-simplified">BL Add MS
+ 12133, foll. 1-108</idno>
+ </altIdentifier>
+ <altIdentifier>
+ <collection>William Wright, Catalogue of the
+ Syriac Manuscripts in the British Museum Acquired
+ since the Year 1838</collection>
+ <idno type="Wright-BL-Arabic">9</idno>
+ </altIdentifier>
+ <altIdentifier>
+ <collection>William Wright, Catalogue of the
+ Syriac Manuscripts in the British Museum Acquired
+ since the Year 1838</collection>
+ <idno type="Wright-BL-Roman">IX</idno>
+ </altIdentifier>
+ </msIdentifier>
+ </msPart>
+<!--...-->
+ <msPart xml:id="Part2" n="2">
+ <msIdentifier>
+ <idno type="URI">https://bl.syriac.uk/ms/3</idno>
+ <altIdentifier>
+ <idno type="BL-Shelfmark">Add. 12,133, foll.
+ 109–169</idno>
+ </altIdentifier>
+ <altIdentifier>
+ <idno type="BL-Shelfmark-display">London, BL, Add.
+ 12,133, foll. 109–169</idno>
+ </altIdentifier>
+ <altIdentifier>
+ <idno type="BL-Shelfmark-simplified">BL Add MS
+ 12133, foll. 109-169</idno>
+ </altIdentifier>
+ <altIdentifier>
+ <collection>William Wright, Catalogue of the
+ Syriac Manuscripts in the British Museum Acquired
+ since the Year 1838</collection>
+ <idno type="Wright-BL-Arabic">51</idno>
+ </altIdentifier>
+ <altIdentifier>
+ <collection>William Wright, Catalogue of the
+ Syriac Manuscripts in the British Museum Acquired
+ since the Year 1838</collection>
+ <idno type="Wright-BL-Roman">LI</idno>
+ </altIdentifier>
+ </msIdentifier>
+ </msPart>
+ </msDesc>
+</sourceDesc>
Divergences from Consolidated Schema:
SMBL uses a different set of type values.
1.6.2. The Heading
SMBL has used the <head> element to provide summary information about the manuscript or manuscript part.
An auto-generated paragraph describing the masnucript contents has been inserted into the <head> element as a <note> with a type attribute whose value is contents-note. This note provides the title(s) of the first five top-level <msItem> elements. Their values are copied from the <title> element of each item; final elipsis indicates that there are more than five top-level manuscript items. Finally, the total number of <msItem> elements, including descendant manuscript items, is included in the note.
<note type="contents-note">This manuscript contains: Severus. The Hymns of Severus, etc., here only 159 (ܩܢܛ) in number.;
+ Supplicatory hymns of every kind, arranged according to the eight tones.; Cantus ad Magnificat, arranged according to the eight tones.;
+ Additional hymns, arranged according to the eight tones.; Additional.; ...
+ In total, including sub-sections, this manuscript contains 26 items.</note>
For composite manuscripts, the contents note will instead direct the reader to the individual parts for a summary of the contents.
Following the contents note, the <head> element may have a number of <listRelation> elements.
SMBL has recorded the genre classification provided in Wright's Catalogue in a <listRelation> element with type whose value is Wright-BL-Taxonomy. The taxonomy is recorded in a child <relation> element given a name attribute of dcterms:type and a ref attribute of http://purl.org/dc/terms/type. The manuscript or part URI is given as the value of the active attribute. A corresponding xml:id attribute value from the <category> in the <taxonomy> element is referenced as the value of the passive attribute. Finally, the human-readable label from the same <category> element is used as a text node of the relation's child <desc> element.
An example of Wright's taxonomy encoded in the <head> element:
For composite manuscripts, which contain one or more <msPart> elements, the manuscript record as well as each individual part will have a <listRelation> element defining the part-to-whole relationships between the composite manuscript and its parts.
The <listRelation> element has been given a type attribute with the values composite-to-parts or part-to-composite. A child <desc> element provides a human-readable explanation of the list of relations. It is followed by a series of <relation> elements that define the part-to-whole or whole-to-part relationships.
The <relation> element includes active and passive attributes whose values are the SMBL URIs for the composite manuscript and the specific manuscript part. Each element also includes a name attribute and ref attribute that define the relationship. The active, passive, and ref attributes can be understood as a triple, so in the example below one migh read: https://bl.syriac.uk/ms/100 has-unspecified-codicological-part https://bl.syriac.uk/ms/101. Finally, a child <desc> element provides a human-readable label consisting of the shelfmark, and folios if applicable, of the composite or part referenced in the passive attribute.
SMBL has used the following values for the name and ref attributes for composite-to-parts type <listRelation> elements:
<head>
+ <note type="contents-note">This manuscript contains:
+ The book of Deuteronomy, according to the Peshitta version. In total, including sub-sections,
+ this manuscript contains 1 item.</note>
+ <listRelation type="Wright-BL-Taxonomy">
+ <relation name="dcterms:type"
+ ref="http://purl.org/dc/terms/type" active="https://bl.syriac.uk/ms/101"
+ passive="#bible-ot">
+ <desc>Old Testament</desc>
+ </relation>
+ </listRelation>
+ <listRelation type="part-to-composite">
+ <desc>This unit is a part of a composite manuscript:</desc>
+ <relation name="syriaca:is-unspecified-codicological-part-of"
+ ref="#syriaca:is-unspecified-codicological-part-of" active="https://bl.syriac.uk/ms/101"
+ passive="https://bl.syriac.uk/ms/100">
+ <desc>Add. 14,438</desc>
+ </relation>
+ </listRelation>
+</head>
Notes for Review Editors (2024)
Please ignore any errors in the <head> element and its summary. These will be regenerated by a script at a later stage. Note: This section is provided for the convenience of the editors undertaking a revision of the data in 2024 and will be deleted from the final documentation.
Divergences from Consolidated Schema:
SMBL has used the <head> element differently than the Consolidated schema and has not provided a summary title or origin place and date information. Instead, we have used dedicated <note> and <listRelation> elements to record summary information about the manuscript and part records.
1.6.3. Intellectual Content
The element <msContents> is used to describe the intellectual content of the manuscript (title, author, editor, textual additions, filiation and bibliographical references). Every conceptual work contained in the manuscript is treated as a separate <msItem>.
1.6.3.1. Language(s) of the Manuscript as a Whole
The element <textLang> encodes a description of the languages and writing systems used in the manuscript. The element itself contains a prose description of the language or languages and scripts used. The mainLang and otherLangs attributes contain the ISO 639-1 and -3 codes for the languages as well as a script code if relevant. Either attribute can take multiple values, as a space-separated list.
We have conformed to the BCP 47 standard which recommends using the two letter language code when available from ISO 639-1 codes and then using three letter language codes from ISO 639-3 only for languages not included in ISO 639-1, then an ISO 15924 code for the script, and finally IANA language subtags for other information, such as methods of transliteration.
In the case of Christian Palestinian Aramaic, no ISO 639 code has been established. For this language, we use a code in the range (qaa-qtz) ISO 639 leaves 'reserved for local use'. While codes in this range are considered private, we follow the assignment published by Linguist List for Middle Aramaic, that is qhy, which is further specified via a private use subtag resulting in the language tag: qhy-x-cpas.
The accepted language codes are:
Arabic
ar
Syro-Arabic Garshuni
ar-Syrc
Coptic
cop
German
de
English
en
French
fr
Ancient Greek
grc
Hebrew
he
Armenian
hy
Italian
it
Latin
la
Syriac
syr
Arabo-Syriac Garshuni
syr-Arab
Turkish
tr
Syro-Turkish Garshuni
tr-Syrc
Christian Palestinian Aramaic
qhy-x-cpas
Classical Armenian
xcl
Undetermined
und
Divergences from Consolidated Schema:
SMBL uses a different set of language codes given its scope. SMBL has also chosen not to use the <textLang> at the <msItem> level; likewise, the mainLang attribute permits multiple, space-separated language codes to handle cases of bilingual or mutli-lingual manuscripts (e.g., bilingual, parallel Gospel manuscripts)
Notes for Review Editors (2024)
Please ignore the <textLang> and the mainLang contents. These will be updated by script. Note: This section is provided for the convenience of the editors undertaking a revision of the data in 2024 and will be deleted from the final documentation.
1.6.3.2. Manuscript Item
The element <msItem> contains the intellectual information for each individual work contained within the manuscript. If a manuscript contains multiple works, it will have multiple <msItem> elements; if a manuscript contains a single work, it will only have one <msItem>.
All manuscript items have been numbered with the n attribute in a sequential manner without regard for the location of the items in the hierarchy of items and sub-items. This sequential number is relative to the manuscript part. Thus a multi-part manuscript would restart the numbering at n=‘1’ in each part. In addition, we have used a pattern for the creation of xml:id values which reflects nesting in manuscript parts and/or the position of the item in the outline hierarchy (with ‘a’ being the top level, then ‘b’, etc.
In this example from https://bl.syriac.uk/ms/3the msItem is in the second part of the multi-part manuscript and is the second item at the ‘b’ level of the outline. It is also the 3rd msItem in the second part of the manuscript based on sequence.
NOTA BENE:SMBL has not used Wright's outline numbering system, but instead has re-numbered the manuscript items sequentially. While there is some loss to not continuing to use Wright's numbering, we found the re-numbering to be necessary for two reasons. First, the sequential numbering allows one to navigate the nested elements much easier than Wright's system (where the same manuscript could potentially have repeated numbers due to outline levels). Second, in our encoding we occaisionally discovered manuscript items which Wright had conflated. The need to number these items necessitated re-numbering.
Notes for Review Editors (2024)
Please ignore any errors in numbering in either n or xml:id. You do not need to renumber if you delete an <msItem> or add a new <msItem> or find errors in the numbering. These will be renumbered by a script at a later stage. Similarly, if you delete an item, there is no change needed to the xml:id or the n values of the other items, leave them numbered as. If you add a new <msItem>, you should just use the letter ‘x’ as place holders: xml:id=‘x1’n=‘x’ (if you insert multiple items, the XML validation rules require that every xml:id have a unique value, so please increment use xml:id=‘x2’, etc.). These will be renumbered by a script at a later stage. Note: This section is provided for the convenience of the editors undertaking a revision of the data in 2024 and will be deleted from the final documentation.
1.6.3.2.2. Defective Manuscript Items
defective can be used to indicate if any text or folia originally present are now missing (as determined by Wright based on missing intellectual content or physical state of the manuscript). Defective here refers only to the physical state of the manuscript. In a case where the manuscript, contains only a portion of a literary work by design (such as an abbreviated text or an extract), the manuscript item is not considered defective. The following values are permitted:
‘true’ means that the item is defective either because Wright states as much (‘leaves are wanting’ or ‘fragments of’) or because clear deduction by the SMBL editor indicates missing content.
‘unknown’ means that the SMBL editor suspects the manuscript is incomplete but it is not discussed by Wright.
‘false’ is the default value and it is not necessary to enter it. If the item is not defective our altogether.
In the case of nested <msItem> elements, the defective value was also marked for any higher-level items if one of their child items was defective.
1.6.3.2.3. What is a Manuscript Item?
We have followed the definition proposed by the Consolidated Guidelines where a manuscript item is defined as ‘a complete work or item, or a self-contained part of a larger work with (potentially) independent circulation’. A ‘self-contained part of a larger work’ could be a letter in a letter-collection, or a sermon in a homiliary; it could also represent the biblical text or the commentary in a glossed biblical manuscript.
As a guiding principle, where possible and practicable we have used the <msItem> element to markup up both the work as a whole its self-contained parts through the nesting of <msItem> elements. In a few cases (primarily with florilegia or catenae) is has not been possible to encode individual manuscript items based on Wright's descriptions. In those cases, we have placed his descriptions into <note> elements.
1.6.3.2.3.1. Encoding the Outline of Nested Manuscript Items
For the most part, Wright's catalogue employs an sequential outline pattern that describes manuscript items and their sub-items in a way compatible with the TEI Guidlines. In a few cases, however, we have had to modify Wright's outlines to better model the manuscript in the tree structure of the .xml file. Specifically, in some instances we have had to create a new top-level manuscript item which contains all of the items in a manuscript. Often in such cases, Wright provided a title and description of this top-level item, but he did not include this item in his numbered outline. At other times, we have found Wright's outline to be partial or incomplete. For example, Wright might only list some but not all of the sub-items in a manuscript. In these cases, our policy has been to encode only the sub-items that Wright mentions. In these cases, our .xml document matches Wright's description but not the actual contents of the manuscript (of course, we hope the a future recataloguing will capture the contents which Wright did not describe in detail). The examples below illustrate what this might look like.
In this modified example from https://bl.syriac.uk/ms/763 Wright notes that there are 18 hymns in the collection but he only provides information about two of them, thus only two <msItem> elements are encoded as child elements:
In this modified example from https://bl.syriac.uk/ms/265 Wright describes a large collection but he only provides information about the first two parts of the collection, thus only two <msItem> elements are encoded as child elements. In this case we did not create a third <msItem> which might contain ‘everything else after the definitions and introduction’ even though it is clear by context that the manuscript containts more thanjust these two sections. In this case, the top-level <msItem> is assumed to contain the other sections not specifically identified by Wright.
<msItem xml:id="a1" n="1" defective="true">
+ <locus from="1b"/>
+ <title xml:lang="en">A large collection of chapters
+ on the Body and its Members, the Soul, the
+ Resurrection, the Incarnation, the holy Eucharist,
+ Baptism, etc.</title>
+ <msItem xml:id="b1" n="2">
+ <locus from="1b"/>
+ <title xml:lang="en">A section containing
+ definitions of various scientific terms</title>
+ </msItem>
+ <msItem xml:id="b2" n="3" defective="true">
+ <locus from="1b"/>
+ <title xml:lang="en">The introductory
+ section</title>
+ </msItem>
+</msItem>
Notes for Review Editors (2024)
As described above, it is not necessary to create extra <msItem> elements for itemns not described directly by Wright. Alternately, in some cases these may have already been added to the file, in which case it is not necessary to delete these extra <msItem> elements if they exist. Note: This section is provided for the convenience of the editors undertaking a revision of the data in 2024 and will be deleted from the final documentation.
Deprecated Practices and Legacy Data:
In an earlier stage of the project, we did attempt to create placeholder <msItem> elements for content not described by Wright so some files do contain sub-items with minimal description which were not found in Wright's description. We discontinued this practice after 2022 but have left the legacy data in place, since it may be of use to future cataloguing.
1.6.3.2.3.2. Alternate Encoding with <note> in <msItem>
While Wright usually describes the manuscript contents in a methodical manner creating an outline sequentially in order from the first folio to the last, there are places where he abandons this approach and offers a prose description of the contents that does not follow the order of the document. In the most frequent example, Wright may choose to describe a florilegium in a manner organized by alphabetically by author cited rather than by folio order. In this modified example from https://bl.syriac.uk/ms/265, Wright offers an alphabetical list: ‘The authorities cited are--Didymus of Alexandria. Fol. 24 b. Dionysius the Areopagite: epistle to Timothy, fol. 19 b; to Titus, fol. 27 b. Epiphanius: the Ancoratus. Fol. 26 a. Ephraim: foll. 21 a, 25 a, 30 a, 31 b;’. Wright's description does not offer enough information to encode individual manuscript items. In those cases, we have placed these descriptions into one or more <note> elements with the following XPath: msItem/note/p. Inside this <note>, we have encoded as much of the relevant information about authors, titles, and loci as possible. As illustrated in this modified example from https://bl.syriac.uk/ms/265:
When Wright provides a comment related to an <msItem> or another aspect of the contents, we have encoded his commentary as a <note> within each <msItem> or other element as applicable. When Wright's catalogue has a footnote, we have inserted the <note> element at the point in the prose where the footnote marker occurs and marked the <note> with type of ‘footnote’. Some examples are:
<msItem xml:id="a2" n="2" defective="true">
+ <locus from="1" to="100">Foll. 1-100</locus>
+ <title ref="http://syriaca.org/work/26"
+ xml:lang="en">Ezekiel, according to the Peshitta version</title>
+ <note>The following portions of the text are missing:
+ Ch. 14:14-16:17, 16:32-53, 17:3-22:2, and
+ 24:18-25:3.</note>
+ <note>The lessons are rubricated in the text.</note>
+</msItem>
As described above, when a note contains a bibliographic citation, that citation is wrapped in a <bibl> element and linked to a Syriaca.org URI using <ref> and target:
<msItem xml:id="a1" n="1" defective="true">
+ <locus from="1b"/>
+ <title xml:lang="en">The Acts of the Second Council of
+ Ephesus</title>
+ <note type="footnote">A small part of this volume has
+ been edited by the <persName>Rev. S. G. F.
+ Perry</persName>, under the title of <bibl>
+ <ref target="https://www.zotero.org/groups/4861694/a_comprehensive_bibliography_on_syriac_studies/items/P4VVZ7P6/library"/>"An Ancient Syriac Document, purporting to be
+ the record, in its chief features, of the second
+ Synod of Ephesus," etc., Oxford, 1867.</bibl>
+ </note>
+</msItem>
1.6.3.2.5. Locus
We have given the starting folio of each manuscript item according to the guidelines specified above for <locus>. If Wright does not give a folio location for a <msItem>, we have added one using the closest folio that he mentions in his description, even though this may not be very accurate. For example if Wright mentions an msItem on folio 12 b and then fails to give a locus for the next msItem, we have reused the locus so that both items are listed as being on 12 b.
1.6.3.2.6. Author
The author of a manuscript item, if given by Wright, was recorded inside the <author> element and wrapped with a <persName> child element (with xml:lang attribute). As described above in the discussion of URIs, all <author> elements are required to have a Syriaca.org person URI as the value of a ref, For anonymous works, no <author> was included in the <msItem>. The form of the name given by Wright was encoded as given without standardization. Where Wright records multiple name variants for the same person (e.g. translations or transliterations) we added these as child <persName> elements (with xml:lang attributes) within the <author> element (see further below for an example of multiple names for George, bishop of the Arabs).
When a <msItem> contains nested <msItem> elements, the author element should be repeated if applicable to the sub-items. When a top-level <msItem> contains sub-items with different authors, all authors should be encoded in the top level <msItem> as seen in this example from https://bl.syriac.uk/ms/427. Note: When Wright gives multiple name variants, those varients were recorded only in the first/highest-level instance.
1.6.3.2.6.2. Pseudonymous, Uncertain, Disputed and Attributed Authorship [UNDER REVISION]
Guidelines for these cases will be added in the future.
1.6.3.2.7. Translator
When Wright's description or a manuscript mentions the translator of a manuscript item, we have encoded the name of the translator in addition to any authors of the manuscript item. Such secondary statements of responsibility for the intellectual content in an <msItem> are marked with an <editor> element and a role attribute with the value ‘translator’. An <msItem> may have both an <editor> element and an <author> element if both are given in Wright's catalogue entry.
In all other respects, <editor> elements should contain the same child elements as <author> (eg. multiple <persName> elements) and attributes (e.g. a ref attribute with a Syriaca.org URI linking them to an entry The Syriac Biographical Dictionary. If Wright provides details about their role in the creation of the work that has been be encoded in a separate <note>.
<msItem xml:id="p2a1" n="1">
+ <locus from="82a">Fol. 82 a</locus>
+ <editor role="translator"
+ ref="http://syriaca.org/person/82">
+ <persName xml:lang="en">Paul of Tellā</persName>
+ </editor>
+ <title ref="http://syriaca.org/work/158"
+ xml:lang="en">The Psalms, translated from the Septuagint by Paul
+ of Tellā</title>
+</msItem>
Divergences from Consolidated Schema:
SMBL does not, yet, use the three-letter code (or multiple codes separated by spaces) selected from the MARC relators list (https://www.loc.gov/marc/relators/relaterm.html by the Consolidated Schema. This may be added at a later date.
SMBL uses Syriaca.org URIs and thus does not use key as specified in the Consolidated Schema.
1.6.3.2.8. Title
Within the <msItem>, we have used the <title> element to encode the descriptive titles which Wright gives for each manuscript item. These descriptive titles are usually in English, though occaisionally in Latin or a mixture of languages. These are not standardized titles and at times can be very long sentence or paragraph type titles (as was more common in 19th-century English) as in this example:
<msItem>
+ <title xml:lang="en">Fragments of the second volume of
+ the Commentary of Daniel of Salach on the Psalms,
+ viz. part of the homilies on Pss. li., lviii., and
+ lxii </title>
+</msItem>
We have made every effort to encode these titles exactly as written by Wright, though in some cases we have made silent emmendations for grammar or when Wright's prose was not clear. One change we have made throughout is to capitalize the first word of each title. More notably, if Wright's title was abbreviated due to context, we have supplied additional words to make the context clear. In addition, in the cases where Wright did not supply an English title we have constructed one so that every <msItem> has a non-Syriac title (usually in English) to appear in search and browse results (see discussion below).
As can be seen in the example just given (‘Fragments of the second volume of the Commentary of Daniel of Salach on the Psalms, viz. part of the homilies on Pss. li., lviii., and lxii’), many manuscript items are themselves composed of sub-items. In these cases, we have taken advantage ofthe tree structure of the XML encoding since it is possible to infinitely nest <msItem> elements inside of parent <msItem> elements. Thus in many cases a manuscript may contain one parent <msItem> to which Wright has given a general title, such as ‘The metrical works of Ephraim, containing 160 discourses on the Church, the Mysteries of our Lord, Virginity, and against Heresies’. Whenever Wright gives such a title, we have tried to encode such a parent <msItem>, even when Wright's own numbering system did not account for it. Within this parent item, multiple levels of sub-items (each encoded with <msItem>) have been encoded. In this modified example there are three levels of nested <msItem> which are a tree model of ‘The metrical works of Ephraim’ which contains ‘Discourses on the Church’ which itself contains individual hymns numbered ‘11’, ‘12’, etc.:
As noted above in the guidelines for encoding URI entities, when the prose given by Wright for a <title> also contains a person name or a place name, we have NOT tagged those names with <persName> or <placeName>. See the example above from the ‘Fragments of the second volume of the Commentary of Daniel of Salach’.
Divergences from Consolidated Schema:
SMBL does not use the same type values on <title> as used in the Consolidated Schema. We may choose to do so in a future revision.
1.6.3.2.8.1. Untitled Parts
In some cases of such nested sub-items, Wright will only give a Roman or Greek numeral/character in lieu of an English title. This is particularly the case for lower-level nested <msItem> elements for which he has already given a longer descriptive title for the containing <msItem>. In such cases, we have pre-pended the word ‘Part’ to the Roman or Greek character according to the following pattern ‘Part c’. According to rules of XML, the enclosing <msItem> element's title is assumed to be inherited by the nested <msItem>. Thus the part designation is unambiguously associated with the work of which it is a part, and the <title> element of the child <msItem> needs only indicate the part.
In rare cases, Wright describes excerpts of a single work which are broken up among non-contiguous manuscript items. That is, the work may begin, be interrupted by another <msItem>, and then resume. In such cases, whe have pre-pended "Continuation of " to the title of any subsequent non-contiguous instances of a work.
1.6.3.2.9. Paratextual Materials: Rubrics, Incipits, Explicits, Quotes, Final Rubrics, and Colophons.
We have used a number of differen elements to encode the paratextual phrases which Wright transcribes in his catalogue. These include <rubric>, <incipit>, <explicit>, <finalRubric>, and <quote>. In a related way, the <colophon> and <item> elements are also used to encode data related to paratextual materials. As noted above, the same principles have been used to encode the transcriptions given Wright's catalogue across all of these elements. When Wright records the location of the transcription, a <locus> element is used within each of these elements to specify the location of the component within the manuscript. Because these elements imply verbatim quotation we have not added any additional markup (e.g. quotation marks) to convey that fact. In addition all elements containing transcription of text are required to have an xml:lang to specify the language.
Divergences from Consolidated Schema:
Because of the variety of languages found in the paratextual materials of Syriac manuscripts, SMBL requires an xml:lang where the Consolidated Schema does not. In addition, we report whatever punctuation is reported in Wright's catalogue and do not remove final punctuation for the transcriptions.
1.6.3.2.9.1. Rubic
We have used the TEI element <rubric> to encode the original language titles given in the manuscripts and reported by Wright. While Wright may sometimes denote this Syriac title with the phrase ‘entitled...’ or ‘Title:...’, most commonly he simply records it without any designation immediately after he provides an English language title. Sometimes Wright only provides a Syriac language title and no English translation. In both cases, we have encoded the Syriac titles reported by Wright within <rubric> with an xml:lang to specify the language.
In some cases, a manuscript item will have multiple Syriac titles. For instance, a liturgical manuscript may include both a traditional title of the work and a title which indicates the liturgical occasion on which the work should be read. In such cases, we have encoded both the literary title and the liturgical calendar title with multiple <rubric> elements.
Because every <msItem> element already has a <title> element where a Syriaca.org work URI could be linked, we have not linked Syriaca.org URIs to Syriac titles.
When Wright indicates that a title is a running title, we have encoded this by wrapping the title in both a <fw> (forme work) element with type of ‘header’and a containing <rubric> element.
<msItem xml:id="d1" n="8"
+ defective="unknown">
+ <locus from="91" to="161">Foll. 91-161</locus>
+ <title ref="http://syriaca.org/work/154"
+ xml:lang="en">The second book of Samuel, according to the
+ recension of Jacob of Edessa</title>
+ <rubric xml:lang="syr">ܟܬܒܐ ܕܬܪ̈ܝܢ ܕܡ̈ܠܟܘܬܐ<locus from="91b" to="91b"/>
+ </rubric>
+ <rubric xml:lang="syr">
+ <fw type="header">ܫܡܘܐܝܠ</fw>
+ </rubric>
+</msItem>
1.6.3.2.9.2. Incipit
If Wright records the the opening lines of the text proper of the <msItem> we record this transcription in an <incipit> element. Wright sometimes denotes the incipit with the phrase ‘it begins...’ or ‘beginning...’. The incipit should not be confused with the rubic. The TEI defines the incipit as ‘the opening words of the text proper, exclusive of any rubric which might precede it, of sufficient length to identify the work uniquely.’ In most cases, if Wright provides an incipit he also provides a rubric (though the reverse is not the case). See this example:
In the exceedingly rare cases in which Wright records the the closing lines of the text proper of the <msItem>, we marked this transcription in an <expicit> element. The explicit should not be confused with the final rubic (subscription) or colophon. The TEI defines the explicit as ‘the closing words of the text proper, exclusive of any rubric or colophon which might follow it.’ (In other scholarly usage, what the TEI defines as ‘explicit’ is also called a ‘desinit’). Here is an example of how we have encoded an <expicit>:
Wright frequently records a ‘subscription’ or Syriac phrase in the manuscript which denotes the end or division of one manuscript item from the next. We have encoded these subscriptions with the TEI element <finalRubric>. The TEI guidelines distinguish between a <finalRubric> which contains a statement relating to the end of a particular work, and the <colophon>, which indentifies a statement about the end of an entire manuscript or about the scribe and/or date and/or place of writing.
<msItem xml:id="b7" n="32">
+ <locus from="207b">Foll. 207 b</locus>
+ <title xml:lang="en">Madrāshē for all ranks.</title>
+ <rubric xml:lang="syr">ܡܕܪ̈ܫܐ ܥܠ ܟܗ̈ܢܐ ܘܪ̈ܫܝ ܟܗ̈ܢܐ
+ ܘܟܠܢܫ</rubric>
+ <finalRubric xml:lang="syr">ܫܠܡܸܘ ܡܕܪ̈ܫܐ ܕܥܠ ܟܠ
+ ܬܓܡ̈ܝܢ ܕܗ̇ܘܝܢ ܒܡܢܝܢܐ ܫܒܥܝܢ ܘܬܠܬܐ </finalRubric>
+ <note>They are 73 in number, according to the
+ subscription.</note>
+</msItem>
In the case of <msItem> elements nested inside other <msItem> elements, it may be that Wright has quoted a <finalRubric> (e.g. a subscription) immediately after the last lower level <msItem> (for example after the last of 12 homilies in a collection). Since this subscription applies to the higher level <msItem> (for example it is a subscription noting the end of the whole collection of homilies), in these cases we have included this <finalRubric> inside the appropriate higher-level <msItem> rather than as part of the last sub-item.
Notes for Review Editors (2024)
In the case of <msItem> elements nested inside other <msItem> elements, it may be that a <finalRubric> (e.g. a subscription) has been nested inside a lower level <msItem> (say inside xml:id=‘b12’, the last of 12 homilies in a collection) when in fact the subscription applies to the higher level <msItem> (for example it is a subscription noting the end of the whole collection of homilies). In these cases delete the <finalRubric> from the lower level <msItem> (b12) and move it up in the document and higher in the outline so that you paste it into the appropriate higher level <msItem> (a1, etc.). Note: This section is provided for the convenience of the editors undertaking a revision of the data in 2024 and will be deleted from the final documentation.
The TEI guidelines define a colophon as ‘the original statement providing information regarding the date, place, agency, or reason for production of the manuscript’. Unfortunately, Wright did not always report the presence of colophons in a standardized way. He only sometimes uses the word ‘colophon’ in the same sense as the definition of the TEI. Sometimes he uses the word to describe a doxology written by the scribe. Accordingly it has been difficult to distinguish his transcription of colophons from other marginalia and additions to the manuscripts. In our encoding, we have choosen to encode all colophons together the additions of the manuscript (see the guidelines for <additions>below. We have, however, also made an effort to mark manuscripts in which either Wright reports the existence of a colophon in the sense meant by the TEI or in which we determine (based on Wright's description) that a colophon is present. In these cases, we have included a <colophon> element in the <msItem> either as an empty element or with a prose note referring the reader to consult the additions section of the manuscript description. The inclusion of this element allows users to search for manuscripts with colophons. This is an example of that encoding:
<msItem xml:id="a3" n="22">
+ <locus from="137a"/>
+ <title xml:lang="en">Supplicatory hymns for the
+ Resurrection</title>
+ <rubric xml:lang="syr">ܬܟܫ̈ܦܬܐ ܕܩܝܡ̣ܬܐ</rubric>
+ <colophon>See additions.</colophon>
+</msItem>
+<!-- -->
+<physDesc>
+ <additions>
+ <list>
+ <item xml:id="addition4" n="4">
+ <label>Colophon</label>
+ <locus from="138a"/>
+ <p>The colophon, fol. 138 a, states that the first
+ part of this book (foll. 1—110) was written in the
+ year 1386 (A.D. 1075) by one Benjamin, and the
+ remainder by one of his disciples, whose name
+ appears from a subsequent note to have been
+ Theodore</p>
+ <p>
+ <quote xml:lang="syr">ܫܘ: ܠܐܒܐ: ܘܠܒܪܐ: ܘܠܪܘܚܐ:
+ ܩܕ ܠܥܠܡ: ܥܠܡܝܢ: ܫܩܠ ܣܟܐ ܟܬܒܘܢܐ ܗܢܐ ܒܥܘܕܪܢ
+ ܬܠܝܬܝܘܬܐ ܕܡ̈ܥܢܝܬܐ ܕܩܝܫܐ (sic) ܡ̇ܪܝ ܣܘܐܝܪܐ ܘܕܐܢ̈ܫܝܢ
+ ܐܚܪ̈ܢܐ. ܫܢܬ ܐܠܦ ܘܬܠܬܡܐ ܘܬܡ̈ܢܥܝܢ (sic) ܘܫܝܬ.
+ ܒܕ̈ܝܘܢܝܐ ܡܒܪ̈ܟܐ. ܟܬܒܗ ܪܒܐ ܕܝܠܢ ܒܢܝܡܢ ܡܚܣܐ ܡܪܝܐ
+ ܠܢܦܗ (sic) ܘܚܬܡܗ ܬܠܡܝܕܐ ܕܝܠܗ ܐܢܫ ܚܛܝܐ ܘܡܦܠܦܠ
+ ܒܣܝܢܐ. ܟܠ ܕܩܪܐ ܢܨܠܐ ܥܠܝܗܘܢ ܘܫ.</quote>
+ </p>
+ </item>
+ </list>
+ </additions>
+</physDesc>
The colophon reported by Wright is encoded using <quote> and following the guidelines for additions.
Divergences from Consolidated Schema:
Our method of encoding colophons diverges from the Consolidated Schema but was chosen because it allows a greater amount of descriptive markup
1.6.3.2.10. Filiation
In one test case we have used the <filiation> element to encode information that Wright provides about the relationship of one manuscript to other surviving manuscripts in terms of their content. For example:
<msItem xml:id="a1" n="1" defective="true">
+ <locus from="1" to="148">Foll. 1-148</locus>
+ <author ref="http://syriaca.org/person/51">
+ <persName xml:lang="en">Severus of
+ Antioch</persName>
+ </author>
+ <title xml:lang="en">The sixth book of the select
+ epistles of Severus of Antioch</title>
+ <filiation>The sixth book of the select epistles of
+ Severus of Antioch, in the same translation as <bibl type="MS">Add. 12,181<ptr target="https://bl.syriac.uk/ms/80"/>
+ </bibl>.</filiation>
+</msItem>
In the future, we may chose to convert other references to this usage of <filiation>.
Notes for Review Editors (2024)
Please ignore instances of this element, and for now instead encode any information about the relationships between manuscripts in terms of their contents using a <note> element.
1.7. Physical Description
We have used the physical description section <physDesc> to encode several different aspects of the manuscript (or part of a manuscript) including:
aspects of the form, support, extent, and quire structure of the manuscript object and of the way in which the text is laid out on the page.
the script used, any decorative features, any annotations or marginalia, and transcription of colophons.
Wright typically presents his physical description of the manuscript in a concise paragraph at the start of each entry. For ease of use, we have encoded this paragraph as a <p> (TEI paragraph) at the start of each <physDesc> in this way:
<physDesc>
+ <p>Paper, about 6 5/8 in. by 5 1/8, consisting of 138 leaves, many of
+ which are much stained and torn, especially foll. 1, 5, 18, 24, 33,
+ and 34. The quires, signed with letters, are 17 in number; but the
+ first six are very imperfect, leaves being wanting at the beginning,
+ as well as after foll. 4, 5, 12, 17, 23, 25, and 31. There are from
+ 16 to 25 lines in each page.</p>
+ <objectDesc form="codex">
+<!-- ... -->
+ </objectDesc>
+<!-- ... -->
+</physDesc>
In addition we have used several of the child elements of <physDesc> to encode the same data in more detail.
1.7.1. Object Description
The <objectDesc> element is used to group together those parts of the physical description which relate specifically to the text-bearing object. We have encoded the form attribute of the <objectDesc> element to refer to the form of the object in its original state, before any mutilation, rebinding etc. Since all of the British Library MSS are currently codices, the majority of our MSS are marked as codex, unless we were aware of a point in time in which the item circulated as membra disjecta. We have used the following values :
‘codex’: used for multiple gatherings of leaves, held within a binding of some kind
‘leaf’: used for single leaves which may now be bound in a codex, but must, by definition, be membra disjecta from an earlier codex or a single leaf created for insertion or repair
‘other’: used for all cases which do not fit either codex or leaf for which Wright does not provide sufficient information to describe in greater detail
The <supportDesc> element may contain the following elements:
supportcontains a description of the materials etc. which make up the physical support for the written part of a manuscript or other object.
extentdescribes the approximate size of a text stored on some carrier medium or of some other object, digital or non-digital, specified in any convenient units.
foliationdescribes the numbering system or systems used to count the leaves or pages in a codex or similar object.
collationcontains a description of how the leaves, bifolia, or similar objects are physically arranged.
conditioncontains a description of the physical condition of the manuscript or object.
We have reported the support material for the codicological unit(s) in the material attribute of <supportDesc>. Allowed values are: ‘chart’ (for all kinds of paper), ‘perg’ (for parchment and vellum), ‘mixed’, ‘unknown’, or ‘other’. For example:
As a legacy of an earlier encoding model, in some files we used the embedded <dimensions> element to specify leaf dimensions, including unit of measurement. After 2022, we ceased to encode in this way. While we have left these dimensions in the data, documents revised since 2022 no longer add data in this way.
1.7.1.1.2. Foliation
We have used the <foliation> element only rarely to provide information about the ordering of folios in the manuscript. We have not included numerica data, only prose comments by Wright. For example:
<foliation>
+ <p>Evidently one of the fly leaves of a manuscript.</p>
+</foliation>
1.7.1.1.3. Condition
Deprecated Practices and Legacy Data:
As a legacy of an earlier encoding model, in some files we used the <condition> element is used to provide a brief description of the overall condition of the manuscript. After 2022, we ceased to encode in this way. While we have left these <condition> in the data, documents revised since 2022 no longer add data in this way.
1.7.1.2. Layout Description
We have used the layout description element, <layoutDesc> to record the number of columns and number of written lines if reported by Wright.
We give the number of columns and lines in the <layout> element using the columns and ruledLines or writtenLines attribute. If the number of columns and/or written or ruled lines varies give the minimum and maximum values with whitespace in-between.
<layoutDesc>
+ <layout columns="1" writtenLines="19 21">
+ <locus from="1" to="10"/>
+ <p>The number of lines in each page varies from 19 to
+ 21.</p>
+ </layout>
+</layoutDesc>
1.7.2. Hand Description
Each distinct hand and/or script in the codicological unit has been described in a separate <handNote> element in the <handDesc> element. The <handDesc> element itself has an attribute hands which has been used to record the number of hands identified, including both those involved in the original production of the unit and those contributing later additions.
Each <handNote> element must have an xml:id attribute.
The scope attribute can be used to indicate the extent of the hand's appearance in the manuscript. Its values can be one of:
sole
major
minor
The script attribute provides a classification of the script. Oftentimes, only the broadest classification is possible. SMBL has used a combination of an ISO 639 Language Code with an optional ISO 15924 script code to encode a hand's script information. The script can take multiple, space-separated script values
The accepted script values are:
ar
Unspecified Arabic script
ar-Syrc
Syro-Arabic garshunography in unspecified Syriac script
ar-Syrn
Syro-Arabic garshunography in East Syriac script
cop
Unspecified Coptic script
de
Unspecified German script
en
Unspecified English script
fr
Unspecified French script
grc
Unspecified Greek script
he
Unspecified Hebrew script
hy
Unspecified Armenian script
it
Unspecified Italian script
la
Unspecified Latin script
qhy-x-cpas
Christian Palestinian Aramaic script
syr
Unspecified Syriac script
syr-Arab
Arabo-Syriac garshunography in unspecified Arabic script
syr-Syre
Estrangela script
syr-Syrj
West Syriac script
syr-Syrn
East Syriac script
syr-x-syrm
Melkite Syriac script
tr
Unspecified Turkish script
tr-Syrc
Syro-Turkish garshunography in unspecified Syriac script
xcl
Unspecified Classical Armenian script
und
Undetermined
mul
Multiple scripts
Each <handNote> should contain a medium attribute describing the tint or type of ink used by the hand, if known. Typically this will be "unknown" unless Wright provides information about the ink, as in this modifed example from https://bl.syriac.uk/ms/25
<handNote xml:id="handNote1" scope="major"
+ script="syr-Syre" medium="black-green-and-yellow-paint"> This volume is written throughout in a beautiful Edessene character, and dated <date datingMethod="Seleucid"
+ when-custom="0723">A. Gr. 723</date>, <date calendar="Gregorian" when="0412">A.D. 412</date>. The colophon is written with green paint, and the doxology with yellow.
+</handNote>
A <handNote> may contain references to folios, optionally tagged with a <locus> element; composition dates, or paleographic estimates, tagged with <date> elements; or the name of the scribe(s), tagged with <persName> elements.
Divergences from Consolidated Schema:
SMBL has included in the calculation of the hands attribute, in <handDesc>, both the hands involved in the original production of the manuscript, and those responsible for later additions.
SMBL has not made use of the sameAs attribute for cross-referencing the occurence of a given hand across two codicological units.
SMBL employs a different set of values for the script attribute to better fit the scope of the British Library collection. Likewise, we have not used the execution attribute, as there is no standard classification for Syriac manuscripts. Nor have we used the <term> element for further classifying script or punctation characteristics. Wright's description, when present, of the execution and punctuation have been recorded but left untagged.
1.7.3. Decoration Description
SMBL has used <decoNote> elements within the <decoDesc> to record information about decorative features in a manuscript. Each <decoNote> element may have a <locus> element, which records the folio location(s) on which the decorative elements appear using from, and optionally to, attributes. A prose text node records Wright's description of the decorative feature, with the exception of rubrication where a text node was omitted if Wright does not provide additional details.
Each <decoNote> element has a type attribute. SMBL uses a subset of the Fihrist vocabulary, with one addition ornamentation which refers to any sort of undifferentiated ornamentation. The allowed values are as follows:
<decoDesc>
+ <decoNote type="initial"> Ornamented capitals in the <ref target="#a1">Ammonian sections and Eusebian canons</ref>.
+ </decoNote>
+ <decoNote type="ornamentation"> Ornamentation at the top of <locus from="14b" to="14b">fol. 14b</locus>.
+ </decoNote>
+ <decoNote type="illustration"> The figure of a fish on the lower margin of <locus from="14b" to="14b">fol. 14b</locus>.
+ </decoNote>
+</decoDesc>
A continuous decorative design which creates a frame around part or all of a page
hmml:canon-table
Canon table(s)
A Gospel concordance system devised in the fourth century by Eusebius of Caesarea, in which Gospel passages are numbered in the text (generally in the margins) and correspond to tables, arranged in columnar form, indicating the concordance of passages among the Gospels
hmm:chart
Chart(s)
Use for display of information arranged in graphic form other than a table
hmml:coat-of-arms
Coat(s) of arms
hmml:anthropomorphic
Decoration, Anthropomorphic
Decoration which incorporates all or part of the human body
hmml:architectural
Decoration, Architectural
hmml:calligraphic
Decoration, Calligraphic
Do not apply if it is 'plain' writing within a decorative element.
hmml:full-page
Decoration, Full-page
hmml:geometric
Decoration, Geometric
hmml:vegetative
Decoration, Vegetative
Decoration which incorporates plant forms
hmml:zoomorphic
Decoration, Zoomorphic
Decoration which incorporates animal forms
hmml:diagram
Diagram(s)
Representation of information graphically, excluding tables
hmml:drawing
Drawing(s)
Use for pen & ink drawings; some may have color. May or may not be Illustration(s) to the text.
hmml:drollery
Drolleries
Amusing figures, often of a grotesque character
hmml:engraving
Engraving(s)
A print taken from an engraved plate
hmml:genealogical-table
Genealogical table(s)
hmml:headpiece
Headpiece(s)
Decoration at the head of a book title/chapter/division. USE: particularly for Armenian, Islamic, Persian, and Western manuscripts
hmml:illumination
Illumination
Use of colors, especially gold or silver, for decoration
hmml:illustration
Illustration(s)
Use for printed works. For manuscripts, may be used in conjunction with Drawing(s) if appropriate
hmml:decorated-initial
Initial(s), Decorated
An initial composed of non-figural, non-zoomorphic decorative elements
hmml:historiated-initial
Initial(s), Historiated
A letter containing an identifiable scene or figures, sometimes relating to the text
hmml:zoomorphic-initial
Initial(s), Zoomorphic
An initial partly or wholly composed of animal forms
hmml:map
Map(s)
hmml:marginalia
Marginalia
Notes on the text written in the margins
hmml:miniature
Miniature(s)
A color illustration, not part of the decorative element. The term is from the Latin word 'miniare' (to color with red), and does not refer their size, which can be full-page. For pen & ink drawings in manuscripts, see Drawing(s) and Illustration(s)
hmml:music
Music
hmml:photograph
Photograph(s)
hmml:plan
Plan(s)
hmml:portrait
Portrait(s)
hmml:printer-device
Printer's device(s)
hmml:seal
Seal(s)
hmml:table
Table(s)
Use for display of information, typically in rectangular form, arranged in rows and/or columns. Do not use for Canon tables or for tables of contents
hmml:volvelle
Volvelle(s)
Wheel chart constructed with rotating parts of one or more layers attacted to a page/leaf. For examples, see: https://medievalbooks.nl/tag/volvelle for manuscripts, http://collation.folger.edu/2012/12/volvelles for early printed ones, and http://volvellery.tumblr.com/ for 20th century examples.
hmml:woodcut
Woodcut(s)
A print taken from an inked wood block with a raised design
The use of terms from the vHMML Features List allow greater specification, as in this example from https://bl.syriac.uk/ms/122:
<decoNote type="illustration"
+ subtype="hmml:zoomorphic"> On fol. <locus from="1b">1 b</locus> there is a rude drawing of an antelope.
+</decoNote>
Divergences from Consolidated Schema:
SMBL has not ordered <decoNote> elements according to any particular hierarchy. SMBL has likewise not employed the primary, hierarchical list of values for the type attribute. Instead, we have employed a subset of the Fihrist typology, with the addition of the generic ornamentation value. The following terms from the Fihrist typology have been excluded due to being outside the scope of the SMBL project:
frieze
map
miniature
paratext
secondary
tooling
unspecified
Given the scope of descriptions provided by Wright, SMBL does not employ <persName> elements for artist names; nor have we included additional structure in the <decoNote> elements, instead providing the prose description from Wright. Finally, SMBL has not employed the <term> element for classifying subjects of the decorations.
1.7.4. Additions [UNDER REVISION]
We have used the <additions> element to describe any additions to the manuscript such as marginalia, notes by readers or owners, colophons, and other additions of interest.
Notes for Review Editors (2024)
You may come across examples of additions/list/item with empty content which were generated by a script in an earlier stage of encoding. If the manuscript does not have anything to report in additions, then you can delete the whole additions element (triple-clicking on the element name in oXygen will select the full element). Note: This section is provided for the convenience of the editors undertaking a revision of the data in 2024 and will be deleted from the final documentation.
1.8. History [UNDER REVISION]
The <history> element is used to include information about the origin, provenance and acquisition of the manuscript, if such is reported by Wright.
1.8.1. Origin
Within the <origin> element we have specified the date (<origDate>) and place (<origPlace>) (if known) of the manuscript's production. As has been our policy throughout SMBL, we have encoded the information as reported by Wright. We have not corrected his estimated dates for manuscripts based on subsequent scholarship.
Divergences from Consolidated Schema:
When a Wright does not mention a date, we have not indicated date unknown. The absence of an <origDate> element itself indicates that there is no date reported. This is a divergence from the Consolidated Schema which includes such a statement of date unknown in a <p>.
1.8.1.1. origDate
Dating attributes from the set notBefore, notAfter, from, to and when MUST be used for <origDate>
from and to denote a known period of writing, presumed to be more or less continuous, beginning at one date and ending at another. notBefore and notAfter denote the terminus a quo and terminus ad quem within which the writing is believed to have occured.
The values of those attributes are a date, starting with the year, then the month, then the day, separated by hyphens (but most often just a year, always expressed using four-digits) must be in the Gregorian calendar. the calendar attribute records the calendar system used by the expression of the date in the text enclosed by the <origDate> tags. The text is for display, the attributes are the machine-readable interpretation. For example:
When a precise date was not given by Wright, we have use the tables for conversion of approximate dates published by Syriaca.org to create numberic ranges. For example, if Wright describes a manuscript as being ‘early 9th century’ we have used a 50-year (half-century) range from 0800 to 0850.
In all cases we have silently change Wright's Roman numerals for centuries to a more readable Arabic numeral equivalent.
Information about use of alternate calendars and regnal years will be added soon.
1.8.1.2. origPlace [Under Revision]
1.9. Provenance [UNDER REVISION]
We have used the <provenance> to record notes by Wright about the provenance of the manuscript.
1.10. Acquisition [UNDER REVISION]
Guidelines will be added here in the future.
1.11. Additional
The <additional> element is used to provide: information about the source of the description; information about the availability and custodial history of the manuscript; information about surrogates; bibliography; and links to online resources.
1.11.1. Record source and history
The <source> element, contained in <recordHist>, provides a prose description of the source(s) from which the description has been derived; this information will overlap with the information in <respStmt>. It may contain <listBibl> and <bibl> elements.
<additional>
+ <adminInfo>
+ <recordHist>
+ <source>Manuscript description based on <bibl>
+ <ref target="#Wrightpart3">Wright's
+ Catalogue</ref>
+ </bibl>. abbreviated by the Syriaca.org
+ editors.</source>
+ </recordHist>
+ </adminInfo>
+ <listBibl>
+ <bibl xml:id="Wrightpart3">
+ <author>William Wright</author>
+ <title xml:lang="en">Catalogue of Syriac Manuscripts in
+ the British Museum Acquired since the Year
+ 1838</title>
+ <pubPlace>London</pubPlace>
+ <date>1870</date>
+ <ptr target="http://syriaca.org/bibl/8"/>
+ <citedRange unit="entry">LXXV. III.</citedRange>
+ <citedRange unit="p">1:51</citedRange>
+ <ref type="internet-archive-pdf"
+ target="https://archive.org/details/catalogueofsyria01brituoft/page/51"/>
+ </bibl>
+ </listBibl>
+</additional>
1.11.2. Bibliography
The bibliography of works from which the manuscript description was derived (i.e. Wright's catalogue) are recorded in the <additional> element in a <listBibl> element..
This section is also used to provide links to online resources such as Archive.org.
<listBibl>
+ <bibl xml:id="Wrightpart">
+ <author>William Wright</author>
+ <title xml:lang="en">Catalogue of Syriac Manuscripts in the
+ British Museum Acquired since the Year 1838</title>
+ <pubPlace>London</pubPlace>
+ <date>1870</date>
+ <ptr target="http://syriaca.org/bibl/8"/>
+ <citedRange unit="entry">LXIII</citedRange>
+ <citedRange unit="p">1:40-41</citedRange>
+ <ref type="internet-archive-pdf"
+ target="https://archive.org/details/catalogueofsyria01brituoft/page/40"/>
+ </bibl>
+</listBibl>
1.12. Palimpsests and Other Composite or Multi-Part Manuscripts [UNDER REVISION]
2. Schema
2.1. Elements
2.1.1. <TEI>
<TEI> (TEI document) contains a single TEI-conformant document, combining a single TEI header with one or more members of the model.resource class. Multiple <TEI> elements may be combined within a <TEI> (or <teiCorpus>) element. [4. Default Text Structure15.1. Varieties of Composite Text]
Major editions of the Guidelines have long been informally referred to by a name made up of the letter P (for Proposal) followed by a digit. The current release is one of the many releases of the fifth major edition of the Guidelines, known as P5. This attribute may be used to associate a TEI document with a specific release of the P5 Guidelines, in the absence of a more precise association provided by the source attribute on the associated <schemaSpec>.
This element is required. It is customary to specify the TEI namespace http://www.tei-c.org/ns/1.0 on it, using the xmlns attribute.
Example
<TEI version="3.3.0" xmlns="http://www.tei-c.org/ns/1.0">
+ <teiHeader>
+ <fileDesc>
+ <titleStmt>
+ <title>The shortest TEI Document Imaginable</title>
+ </titleStmt>
+ <publicationStmt>
+ <p>First published as part of TEI P2, this is the P5
+ version using a name space.</p>
+ </publicationStmt>
+ <sourceDesc>
+ <p>No source: this is an original work.</p>
+ </sourceDesc>
+ </fileDesc>
+ </teiHeader>
+ <text>
+ <body>
+ <p>This is about the shortest TEI document imaginable.</p>
+ </body>
+ </text>
+</TEI>
+<sch:rule context="tei:TEI">
+<sch:assert test="matches(@xml:id, '^manuscript_\d+$') or contains(base-uri(.), 'genizah-mss')"
+ role="fatal"> The root TEI element must have an @xml:id
+ beginning with "manuscript_" then a number (which must also
+ be unique across the entire catalogue). </sch:assert>
+<sch:assert test="matches(@xml:id, '^volume_\d+$') or not(contains(base-uri(.), 'genizah-mss'))"
+ role="fatal"> The root TEI element must have an @xml:id
+ beginning with "volume_" then a number (which must also be
+ unique across the entire catalogue). </sch:assert>
+</sch:rule>
+<sch:rule context="//tei:TEI/@xml:id">
+<sch:let name="fileNo"
+ value="replace(document-uri(/), '.*?(\d{1,5}).xml', '$1')"/>
+<sch:let name="TEIIDno"
+ value="replace(., '.+?(\d+)', '$1')"/>
+<sch:assert test="$TEIIDno = $fileNo"> The @xml:id attribute
+ must match the number portion of the file name:
+ "manuscript_<sch:value-of select="$fileNo"/>".
+</sch:assert>
+</sch:rule>
(suspension) the abbreviation provides the first
- letter(s) of the word or phrase, omitting the
- remainder.
-
contraction
-
(contraction) the abbreviation omits some letter(s) in
- the middle.
-
brevigraph
-
the abbreviation comprises a
- special symbol or mark.
-
superscription
-
(superscription) the abbreviation includes writing above
- the line.
-
acronym
-
(acronym) the abbreviation comprises the initial
- letters of the words of a phrase.
-
title
-
(title) the abbreviation is for a title of address (Dr,
- Ms, Mr, …)
-
organization
-
(organization) the abbreviation is for the name of an
- organization.
-
geographic
-
(geographic) the abbreviation is for a geographic
- name.
-
-
-
-
Note
-
The type attribute is provided for the sake of
- those who wish to classify abbreviations at their
- point of occurrence; this may be useful in some
- circumstances, though usually the same
- abbreviation will have the same type in all
- occurrences. As the sample values make clear,
- abbreviations may be classified by the method used
- to construct them, the method of writing them, or
- the referent of the term abbreviated; the typology
- used is up to the encoder and should be carefully
- planned to meet the needs of the expected use. For
- a typology of Middle English abbreviations, see 6.2.
If abbreviations are expanded silently,
- this practice should be documented in the <editorialDecl>,
- either with a <normalization>
- element or a <p>.
the abbreviation provides the first letter(s) of the word or phrase, omitting the remainder.
contraction
the abbreviation omits some letter(s) in the middle.
brevigraph
the abbreviation comprises a special symbol or mark.
superscription
the abbreviation includes writing above the line.
acronym
the abbreviation comprises the initial letters of the words of a phrase.
title
the abbreviation is for a title of address (Dr, Ms, Mr, …)
organization
the abbreviation is for the name of an organization.
geographic
the abbreviation is for a geographic name.
Note
The type attribute is provided for the sake of those who wish to classify abbreviations at their point of occurrence; this may be useful in some circumstances, though usually the same abbreviation will have the same type in all occurrences. As the sample values make clear, abbreviations may be classified by the method used to construct them, the method of writing them, or the referent of the term abbreviated; the typology used is up to the encoder and should be carefully planned to meet the needs of the expected use. For a typology of Middle English abbreviations, see [[undefined PETTY]]
<accMat> (accompanying
- material) contains details of any
- significant additional material which may be closely
- associated with the manuscript or object being described,
- such as non-contemporaneous documents or fragments bound in
- with it at some earlier historical period. [10.7.3.3. Accompanying Material]
<accMat>A copy of a tax form from 1947 is
- included in the envelope with the letter. It is not
- catalogued separately.</accMat>
-
-
-
Content
- model
-
+}
2.1.3. <accMat>
<accMat> (accompanying material) contains details of any significant additional material which may be closely associated with the manuscript or object being described, such as non-contemporaneous documents or fragments bound in with it at some earlier historical period. [10.7.3.3. Accompanying Material]
<acquisition> (acquisition) contains any
- descriptive or other information concerning the process by
- which a manuscript or manuscript part or other object
- entered the holding institution. [10.8. History]
<acquisition> contains any descriptive or other information concerning the process by which a manuscript or manuscript part or other object entered the holding institution. [10.8. History]
<add> (addition) contains letters, words, or phrases inserted in
- the source text by an author, scribe, or a previous
- annotator or corrector. [3.5.3. Additions, Deletions, and Omissions]
In a diplomatic edition attempting to
- represent an original source, the <add>
- element should not be used for additions to the current TEI
- electronic edition made by editors or encoders. In these
- cases, either the <corr> or <supplied> element
- are recommended.
In a TEI edition of a historical text
- with previous editorial emendations in which such additions
- or reconstructions are considered part of the source text,
- the use of <add> may be appropriate,
- dependent on the editorial philosophy of the
- project.
-
-
-
Example
-
The story I am going to relate is
- true as to its main facts, and as to the consequences <add place="above">of these facts</add> from which this tale
- takes its title.
<add> (addition) contains letters, words, or phrases inserted in the source text by an author, scribe, or a previous annotator or corrector. [3.4.3. Additions, Deletions, and Omissions]
In a diplomatic edition attempting to represent an original source, the <add> element should not be used for additions to the current TEI electronic edition made by editors or encoders. In these cases, either the <corr> or <supplied> element are recommended.
In a TEI edition of a historical text with previous editorial emendations in which such additions or reconstructions are considered part of the source text, the use of <add> may be appropriate, dependent on the editorial philosophy of the project.
Example
The story I am
+ going to relate is true as to its main facts, and as to the
+ consequences <add place="above">of these facts</add> from which
+ this tale takes its title.
<addName> (additional
- name) contains an additional name
- component, such as a nickname, epithet, or alias, or any
- other descriptive phrase used within a personal name.
- [13.2.1. Personal Names]
<persName><forename>Frederick</forename><addName type="epithet">the Great</addName><roleName>Emperor of
- Prussia</roleName>
- </persName>
-
-
-
Content
- model
-
+}
2.1.6. <addName>
<addName> (additional name) contains an additional name component, such as a nickname, epithet, or alias, or any other descriptive phrase used within a personal name. [13.2.1. Personal Names]
<additional> (additional) groups additional
- information, combining bibliographic information about a
- manuscript or other object, or surrogate copies of it, with
- curatorial or administrative information. [10.9. Additional Information]
<additional><adminInfo><recordHist><p>
- <!-- record history here
- --></p>
- </recordHist>
- <custodialHist>
- <p>
- <!-- custodial history here
- --></p>
- </custodialHist>
- </adminInfo><surrogates><p>
- <!-- information about surrogates
- here --></p></surrogates><listBibl><bibl>
- <!-- ... --></bibl>
- <!-- full bibliography here
- --></listBibl>
- </additional>
-
-
-
Content
- model
-
+}
2.1.7. <additional>
<additional> groups additional information, combining bibliographic information about a manuscript or other object, or surrogate copies of it, with curatorial or administrative information. [10.9. Additional Information]
<additions> (additions)
- contains a description of any significant
- additions found within a manuscript or other object, such as
- marginalia or other annotations. [10.7.2. Writing, Decoration, and Other Notations]
<additions><p>There are several marginalia in this
- manuscript. Some consist of single characters and others
- are figurative. On 8v is to be found a drawing of a mans
- head wearing a hat. At times sentences occurs: On 5v: <q xml:lang="is">Her er skrif andres
- isslendin</q>, on
- 19r: <q xml:lang="is">þeim go</q>, on 21r: <q xml:lang="is">amen med aund ok munn halla
- rei knar hofud summu all huad batar þad mælgi ok
- mal</q>, On 21v:
- some runic letters and the sentence <q xml:lang="la">aue maria gracia plena
- dominus</q>.</p>
- </additions>
<additions> contains a description of any significant additions found within a manuscript or other object, such as marginalia or other annotations. [10.7.2. Writing, Decoration, and Other Notations]
<additions>
+ <p>There are several marginalia in this manuscript. Some consist of
+ single characters and others are figurative. On 8v is to be found a drawing of
+ a mans head wearing a hat. At times sentences occurs: On 5v:
+ <q xml:lang="is">Her er skrif andres isslendin</q>,
+ on 19r: <q xml:lang="is">þeim go</q>,
+ on 21r: <q xml:lang="is">amen med aund ok munn halla rei knar hofud summu all huad
+ batar þad mælgi ok mal</q>,
+ On 21v: some runic letters and the sentence <q xml:lang="la">aue maria gracia plena dominus</q>.</p>
+</additions>
Addresses may be encoded either as a
- sequence of lines, or using any sequence of component
- elements from the model.addrPart class. Other non-postal forms of
- address, such as telephone numbers or email, should not be
- included within an <address> element
- directly but may be wrapped within an <addrLine> if they form part of the printed
- address in some source text.
-
-
-
Example
-
<address><addrLine>Computing Center, MC 135</addrLine><addrLine>P.O. Box
- 6998</addrLine>
- <addrLine>Chicago,
- IL</addrLine><addrLine>60680 USA</addrLine>
- </address>
Addresses may be encoded either as a sequence of lines, or using any sequence of component elements from the model.addrPart class. Other non-postal forms of address, such as telephone numbers or email, should not be included within an <address> element directly but may be wrapped within an <addrLine> if they form part of the printed address in some source text.
Example
<address>
+ <addrLine>Computing Center, MC 135</addrLine>
+ <addrLine>P.O. Box 6998</addrLine>
+ <addrLine>Chicago, IL</addrLine>
+ <addrLine>60680 USA</addrLine>
+</address>
This element should be used for postal
- addresses only. Within it, the generic element <addrLine> may be
- used as an alternative to any of the more specialized
- elements available from the model.addrPart class, such as <street>, <postCode>
- etc.
-
-
-
Example
-
Using just the elements defined by the
- core module, an address could be represented as follows:
This element should be used for postal addresses only. Within it, the generic element <addrLine> may be used as an alternative to any of the more specialized elements available from the model.addrPart class, such as <street>, <postCode> etc.
Example
Using just the elements defined by the core module, an address could be represented as follows:
<adminInfo> (administrative
- information) contains information
- about the present custody and availability of the manuscript
- or other object, and also about the record description
- itself. [10.9.1. Administrative Information]
<adminInfo><recordHist><source>Record created <date>1 Aug 2004</date></source></recordHist><availability><p>Until 2015 permission to
- photocopy some materials from this collection has been
- limited at the request of the donor. Please ask repository
- staff for details if you are interested in obtaining
- photocopies from Series 1: Correspondence.</p></availability><custodialHist><p>Collection donated to the Manuscript
- Library by the Estate of Edgar Holden in 1993. Donor
- number: 1993-034.</p>
- </custodialHist>
- </adminInfo>
-
-
-
Content
- model
-
+}
2.1.11. <adminInfo>
<adminInfo> (administrative information) contains information about the present custody and availability of the manuscript or other object, and also about the record description itself. [10.9.1. Administrative Information]
<adminInfo>
+ <recordHist>
+ <source>Record created <date>1 Aug 2004</date>
+ </source>
+ </recordHist>
+ <availability>
+ <p>Until 2015 permission to photocopy some materials from this
+ collection has been limited at the request of the donor. Please ask repository staff for details
+ if you are interested in obtaining photocopies from Series 1:
+ Correspondence.</p>
+ </availability>
+ <custodialHist>
+ <p>Collection donated to the Manuscript Library by the Estate of
+ Edgar Holden in 1993. Donor number: 1993-034.</p>
+ </custodialHist>
+</adminInfo>
<altIdentifier> (alternative
- identifier) contains an alternative
- or former structured identifier used for a manuscript or
- other object, such as a former catalogue number. [10.4. The Manuscript Identifier]
<altIdentifier> (alternative identifier) contains an alternative or former structured identifier used for a manuscript or other object, such as a former catalogue number. [10.4. The Manuscript Identifier]
<am>
- (abbreviation marker) contains a sequence of letters or signs present in
- an abbreviation which are omitted or replaced in the
- expanded form of the abbreviation. [11.3.1.2. Abbreviation and Expansion]
<am> (abbreviation marker) contains a sequence of letters or signs present in an abbreviation which are omitted or replaced in the expanded form of the abbreviation. [11.3.1.2. Abbreviation and Expansion]
<analytic> (analytic
- level) contains bibliographic
- elements describing an item (e.g. an article or poem)
- published within a monograph or journal and not as an
- independent publication. [3.12.2.1. Analytic, Monographic, and Series
- Levels]
May contain titles and statements of
- responsibility (author, editor, or other), in any
- order.
The <analytic> element
- may only occur within a <biblStruct>, where its use is mandatory for
- the description of an analytic level bibliographic
- item.
-
-
-
Example
-
<biblStruct><analytic><author>Chesnutt, David</author><title>Historical Editions
- in the States</title>
- </analytic><monogr><title level="j">Computers and the Humanities</title><imprint><date when="1991-12">(December, 1991):</date></imprint><biblScope>25.6</biblScope><biblScope>377–380</biblScope></monogr>
- </biblStruct>
-
-
-
Content
- model
-
+}
2.1.14. <analytic>
<analytic> (analytic level) contains bibliographic elements describing an item (e.g. an article or poem) published within a monograph or journal and not as an independent publication. [3.11.2.1. Analytic, Monographic, and Series Levels]
<author> (author) in a bibliographic reference, contains the name(s)
- of an author, personal or corporate, of a work; for example
- in the same form as that provided by a recognized
- bibliographic name authority. [3.12.2.2. Titles, Authors, and Editors
- 2.2.1. The Title Statement]
1–∞ occurrences ofteidata.pointer
- separated by
- whitespace
-
-
-
-
-
-
role
-
may be used to
- specify further information about the entity
- referenced by this name in the form of a set of
- whitespace-separated values, for example the
- occupation of a person, or the status of a
- place.
Particularly where cataloguing is
- likely to be based on the content of the header, it is
- advisable to use a generally recognized name authority file
- to supply the content for this element. The attributes key or ref
- may also be used to reference canonical information about
- the author(s) intended from any appropriate authority, such
- as a library catalogue or online resource.
In the case
- of a broadcast, use this element for the name of the company
- or network responsible for making the broadcast.
Where
- an author is unknown or unspecified, this element may
- contain text such as Unknown
- or Anonymous. When the
- appropriate TEI modules are in use, it may also contain
- detailed tagging of the names used for people, organizations
- or places, in particular where multiple names are
- given.
-
-
-
Example
-
<author>British Broadcasting
- Corporation</author>
- <author>La Fayette, Marie
- Madeleine Pioche de la Vergne, comtesse de (1634–1693)</author>
- <author>Anonymous</author>
- <author>Bill and Melinda
- Gates Foundation</author>
- <author><persName>Beaumont,
- Francis</persName>
- and <persName>John
- Fletcher</persName>
- </author>
- <author><orgName key="BBC">British Broadcasting
- Corporation</orgName>: Radio 3 Network </author>
-
-
-
Content
- model
-
+}
2.1.15. <author>
<author> in a bibliographic reference, contains the name(s) of an author, personal or corporate, of a work; for example in the same form as that provided by a recognized bibliographic name authority. [3.11.2.2. Titles, Authors, and Editors2.2.1. The Title Statement]
may be used to specify further information about the entity referenced by this name in the form of a set of whitespace-separated values, for example the occupation of a person, or the status of a place.
Particularly where cataloguing is likely to be based on the content of the header, it is advisable to use a generally recognized name authority file to supply the content for this element. The attributes key or ref may also be used to reference canonical information about the author(s) intended from any appropriate authority, such as a library catalogue or online resource.
In the case of a broadcast, use this element for the name of the company or network responsible for making the broadcast.
Where an author is unknown or unspecified, this element may contain text such as Unknown or Anonymous. When the appropriate TEI modules are in use, it may also contain detailed tagging of the names used for people, organizations or places, in particular where multiple names are given.
Example
<author>British Broadcasting Corporation</author>
+<author>La Fayette, Marie Madeleine Pioche de la Vergne, comtesse de (1634–1693)</author>
+<author>Anonymous</author>
+<author>Bill and Melinda Gates Foundation</author>
+<author>
+ <persName>Beaumont, Francis</persName> and
+<persName>John Fletcher</persName>
+</author>
+<author>
+ <orgName key="BBC">British Broadcasting
+ Corporation</orgName>: Radio 3 Network
+</author>
<authority> (release
- authority) supplies the name of a
- person or other agency responsible for making a work
- available, other than a publisher or distributor. [2.2.4. Publication, Distribution, Licensing, etc.]
<authority> (release authority) supplies the name of a person or other agency responsible for making a work available, other than a publisher or distributor. [2.2.4. Publication, Distribution, Licensing, etc.]
<availability> (availability) supplies information
- about the availability of a text, for example any
- restrictions on its use or distribution, its copyright
- status, any licence applying to it, etc. [2.2.4. Publication, Distribution, Licensing, etc.]
<availability status="restricted"><p>Available for academic
- research purposes only.</p>
- </availability>
- <availability status="free">
- <p>In the public
- domain</p>
- </availability>
- <availability status="restricted">
- <p>Available under
- licence from the publishers.</p>
- </availability>
-
-
-
Example
-
<availability><licence target="http://opensource.org/licenses/MIT">
- <p>The MIT License
- applies to this document.</p><p>Copyright (C) 2011 by The University of
- Victoria</p><p>Permission is hereby
- granted, free of charge, to any person obtaining a copy
- of this software and associated documentation files (the
- "Software"), to deal in the Software without
- restriction, including without limitation the rights to
- use, copy, modify, merge, publish, distribute, sublicense,
- and/or sell copies of the Software, and to permit
- persons to whom the Software is furnished to do so,
- subject to the following conditions:</p><p>The above copyright notice and this
- permission notice shall be included in all copies or
- substantial portions of the Software.</p><p>THE SOFTWARE IS PROVIDED "AS IS",
- WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
- INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
- MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
- NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
- COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
- LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
- OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH
- THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
- SOFTWARE.</p></licence>
- </availability>
<availability> supplies information about the availability of a text, for example any restrictions on its use or distribution, its copyright status, any licence applying to it, etc. [2.2.4. Publication, Distribution, Licensing, etc.]
<availability status="restricted">
+ <p>Available for academic research purposes only.</p>
+</availability>
+<availability status="free">
+ <p>In the public domain</p>
+</availability>
+<availability status="restricted">
+ <p>Available under licence from the publishers.</p>
+</availability>
Example
<availability>
+ <licence target="http://opensource.org/licenses/MIT">
+ <p>The MIT License
+ applies to this document.</p>
+ <p>Copyright (C) 2011 by The University of Victoria</p>
+ <p>Permission is hereby granted, free of charge, to any person obtaining a copy
+ of this software and associated documentation files (the "Software"), to deal
+ in the Software without restriction, including without limitation the rights
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+ copies of the Software, and to permit persons to whom the Software is
+ furnished to do so, subject to the following conditions:</p>
+ <p>The above copyright notice and this permission notice shall be included in
+ all copies or substantial portions of the Software.</p>
+ <p>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+ THE SOFTWARE.</p>
+ </licence>
+</availability>
Contains phrase-level elements, together with any
- combination of elements from the model.biblPart class
-
-
-
Example
-
<bibl>Blain, Clements and Grundy: Feminist
- Companion to Literature in English (Yale, 1990)</bibl>
-
-
-
Example
-
<bibl><title level="a">The Interesting story of the
- Children in the Wood</title>. In <author>Victor E Neuberg</author>, <title>The Penny
- Histories</title>.
- <publisher>OUP</publisher><date>1968</date>. </bibl>
-
-
-
Example
-
<bibl type="article" subtype="book_chapter" xml:id="carlin_2003"><author><name><surname>Carlin</surname> (<forename>Claire</forename>)</name></author>, <title level="a">The Staging of Impotence : France’s
- last congrès</title>
- dans <bibl type="monogr"><title level="m">Theatrum mundi : studies in honor
- of Ronald W. Tobin</title>, éd. <editor><name><forename>Claire</forename><surname>Carlin</surname></name></editor> et <editor><name><forename>Kathleen</forename><surname>Wine</surname></name></editor>, <pubPlace>Charlottesville, Va.</pubPlace>, <publisher>Rookwood
- Press</publisher>,
- <date when="2003">2003</date>. </bibl>
- </bibl>
-
-
-
Schematron
-
- <sch:rule context="//tei:bibl[not(ancestor::tei:additional)]">
- <sch:report test="tei:author"> Element <author>
- not allowed here. </sch:report> </sch:rule>
- <sch:rule context="//tei:bibl[not(ancestor::tei:additional)]">
- <sch:report test="tei:date"> Element <date> not
- allowed here. </sch:report> </sch:rule>
- <sch:rule context="//tei:bibl[not(ancestor::tei:additional)]">
- <sch:report test="tei:pubPlace"> Element
- <pubPlace> not allowed here. </sch:report>
- </sch:rule>
- <sch:rule context="//tei:bibl[not(ancestor::tei:additional)]">
- <sch:report test="tei:title"> Element <title>
- not allowed here. </sch:report>
- </sch:rule>
Contains phrase-level elements, together with any combination of elements from the model.biblPart class
Example
<bibl>Blain, Clements and Grundy: Feminist Companion to Literature in English (Yale,
+ 1990)</bibl>
Example
<bibl>
+ <title level="a">The Interesting story of the Children in the Wood</title>. In
+<author>Victor E Neuberg</author>, <title>The Penny Histories</title>.
+<publisher>OUP</publisher>
+ <date>1968</date>.
+</bibl>
Example
<bibl type="article" subtype="book_chapter"
+ xml:id="carlin_2003">
+ <author>
+ <name>
+ <surname>Carlin</surname>
+ (<forename>Claire</forename>)</name>
+ </author>,
+<title level="a">The Staging of Impotence : France’s last
+ congrès</title> dans
+<bibl type="monogr">
+ <title level="m">Theatrum mundi : studies in honor of Ronald W.
+ Tobin</title>, éd.
+ <editor>
+ <name>
+ <forename>Claire</forename>
+ <surname>Carlin</surname>
+ </name>
+ </editor> et
+ <editor>
+ <name>
+ <forename>Kathleen</forename>
+ <surname>Wine</surname>
+ </name>
+ </editor>,
+ <pubPlace>Charlottesville, Va.</pubPlace>,
+ <publisher>Rookwood Press</publisher>,
+ <date when="2003">2003</date>.
+ </bibl>
+</bibl>
Schematron
+<sch:rule context="//tei:bibl[not(ancestor::tei:additional)]">
+<sch:report test="tei:author"> Element <author> not
+ allowed here. </sch:report>
+</sch:rule>
+<sch:rule context="//tei:bibl[not(ancestor::tei:additional)]">
+<sch:report test="tei:date"> Element <date> not allowed
+ here. </sch:report>
+</sch:rule>
+<sch:rule context="//tei:bibl[not(ancestor::tei:additional)]">
+<sch:report test="tei:pubPlace"> Element <pubPlace> not
+ allowed here. </sch:report>
+</sch:rule>
+<sch:rule context="//tei:bibl[not(ancestor::tei:additional)]">
+<sch:report test="tei:title"> Element <title> not allowed
+ here. </sch:report>
+</sch:rule>
<biblScope> (scope of
- bibliographic reference) defines the
- scope of a bibliographic reference, for example as a list of
- page numbers, or a named subdivision of a larger
- work. [3.12.2.5. Scopes and Ranges in Bibliographic
- Citations]
When a single page is being cited, use
- the from and to attributes with an identical value. When no
- clear endpoint is provided, the from attribute may be used without to; for example a citation such as
- ‘p. 3ff’ might be encoded
- <biblScope from="3">p.
- 3ff</biblScope>.
It is now considered
- good practice to supply this element as a sibling (rather
- than a child) of <imprint>, since it
- supplies information which does not constitute part of the
- imprint.
<biblScope> (scope of bibliographic reference) defines the scope of a bibliographic reference, for example as a list of page numbers, or a named subdivision of a larger work. [3.11.2.5. Scopes and Ranges in Bibliographic Citations]
When a single page is being cited, use the from and to attributes with an identical value. When no clear endpoint is provided, the from attribute may be used without to; for example a citation such as ‘p. 3ff’ might be encoded <biblScope from="3">p. 3ff<biblScope>.
It is now considered good practice to supply this element as a sibling (rather than a child) of <imprint>, since it supplies information which does not constitute part of the imprint.
<biblStruct><monogr><author>Blain, Virginia</author><author>Clements,
- Patricia</author>
- <author>Grundy,
- Isobel</author>
- <title>The Feminist
- Companion to Literature in English: women writers from the
- middle ages to the present</title><edition>first edition</edition><imprint><publisher>Yale University
- Press</publisher>
- <pubPlace>New
- Haven and London</pubPlace><date>1990</date></imprint></monogr>
- </biblStruct>
<binding> (binding)
- contains a description of one binding, i.e.
- type of covering, boards, etc. applied to a manuscript or
- other object. [10.7.3.1. Binding Descriptions]
The value true indicates that the binding
- is contemporaneous with its contents; the value
- false that it is not. The
- value unknown should be
- used when the date of either binding or manuscript
- is unknown
<binding contemporary="true"><p>Contemporary blind stamped leather over
- wooden boards with evidence of a fore edge clasp closing
- to the back cover.</p>
- </binding>
-
-
-
Example
-
<bindingDesc><binding contemporary="false"><p>Quarter bound by the Phillipps' binder,
- Bretherton, with his sticker on the front
- pastedown.</p></binding><binding contemporary="false"><p>Rebound by an unknown 19th c. company;
- edges cropped and gilt.</p></binding>
- </bindingDesc>
-
-
-
Schematron
-
- <sch:rule context="//tei:binding">
- <sch:assert test="@when or @notBefore or @notAfter or
- @contemporary='true' or @contemporary='unknown'"
- role="warn"> The binding element should have dating
- attributes (when or notBefore/notAfter) or a contemporary
- attribute (with the value 'true'). </sch:assert>
- </sch:rule>
-
-
-
Content
- model
-
+}
2.1.21. <binding>
<binding> contains a description of one binding, i.e. type of covering, boards, etc. applied to a manuscript or other object. [10.7.3.1. Binding Descriptions]
The value true indicates that the binding is contemporaneous with its contents; the value false that it is not. The value unknown should be used when the date of either binding or manuscript is unknown
<binding contemporary="true">
+ <p>Contemporary blind stamped leather over wooden boards with evidence of a fore edge clasp
+ closing to the back cover.</p>
+</binding>
Example
<bindingDesc>
+ <binding contemporary="false">
+ <p>Quarter bound by the Phillipps' binder, Bretherton, with his sticker on the front
+ pastedown.</p>
+ </binding>
+ <binding contemporary="false">
+ <p>Rebound by an unknown 19th c. company; edges cropped and gilt.</p>
+ </binding>
+</bindingDesc>
Schematron
+<sch:rule context="//tei:binding">
+<sch:assert test="@when or @notBefore or @notAfter or @contemporary='true' or @contemporary='unknown'"
+ role="warn">
+ The binding element should have dating attributes (when or
+ notBefore/notAfter) or a contemporary attribute (with the
+ value 'true'). </sch:assert>
+</sch:rule>
<bindingDesc> (binding
- description) describes the present
- and former bindings of a manuscript or other object, either
- as a series of paragraphs or as a series of distinct <binding> elements,
- one for each binding of the manuscript. [10.7.3.1. Binding Descriptions]
<bindingDesc><p>Sewing not visible; tightly rebound
- over 19th-cent. pasteboards, reusing panels of 16th-cent.
- brown leather with gilt tooling à la fanfare, Paris c.
- 1580-90, the centre of each cover inlaid with a
- 17th-cent. oval medallion of red morocco tooled in gilt
- (perhaps replacing the identifying mark of a previous
- owner); the spine similarly tooled, without raised bands
- or title-piece; coloured endbands; the edges of the
- leaves and boards gilt.Boxed.</p>
- </bindingDesc>
-
-
-
Content
- model
-
+}
2.1.22. <bindingDesc>
<bindingDesc> (binding description) describes the present and former bindings of a manuscript or other object, either as a series of paragraphs or as a series of distinct <binding> elements, one for each binding of the manuscript. [10.7.3.1. Binding Descriptions]
<bindingDesc>
+ <p>Sewing not visible; tightly rebound over
+ 19th-cent. pasteboards, reusing panels of 16th-cent. brown leather with
+ gilt tooling à la fanfare, Paris c. 1580-90, the centre of each
+ cover inlaid with a 17th-cent. oval medallion of red morocco tooled in
+ gilt (perhaps replacing the identifying mark of a previous owner); the
+ spine similarly tooled, without raised bands or title-piece; coloured
+ endbands; the edges of the leaves and boards gilt.Boxed.</p>
+</bindingDesc>
<catDesc> (category
- description) describes some category
- within a taxonomy or text typology, either in the form of a
- brief prose description or in terms of the situational
- parameters used by the TEI formal <textDesc>. [2.3.7. The Classification Declaration]
<catDesc> (category description) describes some category within a taxonomy or text typology, either in the form of a brief prose description or in terms of the situational parameters used by the TEI formal <textDesc>. [2.3.7. The Classification Declaration]
<catchwords> (catchwords) describes the system
- used to ensure correct ordering of the quires or similar
- making up a codex, incunable, or other object typically by
- means of annotations at the foot of the page. [10.3.7. Catchwords, Signatures, Secundo Folio]
<catchwords> describes the system used to ensure correct ordering of the quires or similar making up a codex, incunable, or other object typically by means of annotations at the foot of the page. [10.3.7. Catchwords, Signatures, Secundo Folio]
<category> (category)
- contains an individual descriptive category,
- possibly nested within a superordinate category, within a
- user-defined taxonomy. [2.3.7. The Classification Declaration]
<category> contains an individual descriptive category, possibly nested within a superordinate category, within a user-defined taxonomy. [2.3.7. The Classification Declaration]
<row><cell role="label">General conduct</cell><cell role="data">Not satisfactory, on account
- of his great unpunctuality and inattention to duties</cell>
- </row>
<row>
+ <cell role="label">General conduct</cell>
+ <cell role="data">Not satisfactory, on account of his great unpunctuality
+ and inattention to duties</cell>
+</row>
The who
- attribute may be used to point to any other element, but
- will typically specify a <respStmt> or <person> element elsewhere in the header,
- identifying the person responsible for the change and their
- role in making it.
It is recommended that changes be
- recorded with the most recent first. The status attribute may be used to indicate the
- status of a document following the change
- documented.
<profileDesc><creation><listChange><change xml:id="DRAFT1">First draft in pencil</change><change xml:id="DRAFT2" notBefore="1880-12-09">First revision, mostly
- using green ink</change><change xml:id="DRAFT3" notBefore="1881-02-13">Final corrections as
- supplied to printer.</change></listChange></creation>
- </profileDesc>
The who attribute may be used to point to any other element, but will typically specify a <respStmt> or <person> element elsewhere in the header, identifying the person responsible for the change and their role in making it.
It is recommended that changes be recorded with the most recent first. The status attribute may be used to indicate the status of a document following the change documented.
Because the children of a <choice> element all
- represent alternative ways of encoding the same sequence, it
- is natural to think of them as mutually exclusive. However,
- there may be cases where a full representation of a text
- requires the alternative encodings to be considered as
- parallel.
Where
- the purpose of an encoding is to record multiple witnesses
- of a single work, rather than to identify multiple possible
- encoding decisions at a given point, the <app> element and associated elements
- discussed in section 12.1. The Apparatus Entry, Readings, and Witnesses
- should be preferred.
-
-
-
Example
-
An American encoding of Gulliver's Travels which retains the
- British spelling but also provides a version regularized to
- American spelling might be encoded as follows.
<p>Lastly, That, upon his
- solemn oath to observe all the above articles, the said
- man-mountain shall have a daily allowance of meat and drink
- sufficient for the support of <choice><sic>1724</sic><corr>1728</corr></choice> of our subjects, with free
- access to our royal person, and other marks of our <choice><orig>favour</orig><reg>favor</reg></choice>.</p>
Because the children of a <choice> element all represent alternative ways of encoding the same sequence, it is natural to think of them as mutually exclusive. However, there may be cases where a full representation of a text requires the alternative encodings to be considered as parallel.
Where the purpose of an encoding is to record multiple witnesses of a single work, rather than to identify multiple possible encoding decisions at a given point, the <app> element and associated elements discussed in section 12.1. The Apparatus Entry, Readings, and Witnesses should be preferred.
Example
An American encoding of Gulliver's Travels which retains the British spelling but also provides a version regularized to American spelling might be encoded as follows.
<p>Lastly, That, upon his solemn oath to observe all the above
+ articles, the said man-mountain shall have a daily allowance of
+ meat and drink sufficient for the support of <choice>
+ <sic>1724</sic>
+ <corr>1728</corr>
+ </choice> of our subjects,
+ with free access to our royal person, and other marks of our
+<choice>
+ <orig>favour</orig>
+ <reg>favor</reg>
+ </choice>.</p>
<cit> (cited quotation)
- contains a quotation from some other
- document, together with a bibliographic reference to its
- source. In a dictionary it may contain an example text with
- at least one occurrence of the word form, used in the sense
- being described, or a translation of the headword, or an
- example. [3.3.3. Quotation
- 4.3.1. Grouped Texts
- 9.3.5.1. Examples]
<cit><quote>and the breath of the whale is
- frequently attended with such an insupportable smell, as
- to bring on disorder of the brain.</quote><bibl>Ulloa's South America</bibl>
- </cit>
-
-
-
Example
-
<entry><form><orth>horrifier</orth></form><cit type="translation" xml:lang="en"><quote>to horrify</quote></cit><cit type="example"><quote>elle était horrifiée par la
- dépense</quote>
- <cit type="translation" xml:lang="en"><quote>she was horrified at the
- expense.</quote>
- </cit></cit>
- </entry>
-
-
-
Example
-
<cit type="example">
- <quote xml:lang="mix">Ka'an yu tsa'a Pedro.</quote><media url="soundfiles-gen:S_speak_1s_on_behalf_of_Pedro_01_02_03_TS.wav"
- mimeType="audio/wav"/>
- <cit type="translation"><quote xml:lang="en">I'm speaking on behalf of
- Pedro.</quote></cit><cit type="translation"><quote xml:lang="es">Estoy hablando de parte de
- Pedro.</quote></cit>
- </cit>
<cit> (cited quotation) contains a quotation from some other document, together with a bibliographic reference to its source. In a dictionary it may contain an example text with at least one occurrence of the word form, used in the sense being described, or a translation of the headword, or an example. [3.3.3. Quotation4.3.1. Grouped Texts9.3.5.1. Examples]
<cit>
+ <quote>and the breath of the whale is frequently attended with such an insupportable smell,
+ as to bring on disorder of the brain.</quote>
+ <bibl>Ulloa's South America</bibl>
+</cit>
Example
<entry>
+ <form>
+ <orth>horrifier</orth>
+ </form>
+ <cit type="translation" xml:lang="en">
+ <quote>to horrify</quote>
+ </cit>
+ <cit type="example">
+ <quote>elle était horrifiée par la dépense</quote>
+ <cit type="translation" xml:lang="en">
+ <quote>she was horrified at the expense.</quote>
+ </cit>
+ </cit>
+</entry>
When a single page is being cited, use
- the from and to attributes with an identical value. When no
- clear endpoint is provided, the from attribute may be used without to; for example a citation such as
- ‘p. 3ff’ might be encoded
- <citedRange from="3">p.
- 3ff</citedRange>.
When a single page is being cited, use the from and to attributes with an identical value. When no clear endpoint is provided, the from attribute may be used without to; for example a citation such as ‘p. 3ff’ might be encoded <biblScope from="3">p. 3ff<biblScope>.
<collation> (collation)
- contains a description of how the leaves,
- bifolia, or similar objects are physically arranged.
- [10.7.1. Object Description]
<collation>The written leaves preceded by
- an original flyleaf, conjoint with the pastedown.</collation>
-
-
-
Example
-
<collation><p><formula>1-5.8 6.6 (catchword, f. 46, does
- not match following text) 7-8.8 9.10, 11.2 (through f.
- 82) 12-14.8 15.8(-7)</formula><catchwords>Catchwords are written
- horizontally in center or towards the right lower
- margin in various manners: in red ink for quires 1-6
- (which are also signed in red ink with letters of the
- alphabet and arabic numerals); quires 7-9 in ink of
- text within yellow decorated frames; quire 10 in red
- decorated frame; quire 12 in ink of text; quire 13 with
- red decorative slashes; quire 14 added in cursive
- hand.</catchwords>
- </p>
- </collation>
<collation>The written leaves preceded by an original flyleaf,
+ conjoint with the pastedown.</collation>
Example
<collation>
+ <p>
+ <formula>1-5.8 6.6 (catchword, f. 46, does not match following text)
+ 7-8.8 9.10, 11.2 (through f. 82) 12-14.8 15.8(-7)</formula>
+ <catchwords>Catchwords are written horizontally in center
+ or towards the right lower margin in various manners:
+ in red ink for quires 1-6 (which are also signed in red
+ ink with letters of the alphabet and arabic numerals);
+ quires 7-9 in ink of text within yellow decorated frames;
+ quire 10 in red decorated frame; quire 12 in ink of text;
+ quire 13 with red decorative slashes; quire 14 added in
+ cursive hand.</catchwords>
+ </p>
+</collation>
<collection> (collection) contains the name of a
- collection of manuscripts or other objects, not necessarily
- located within a single repository. [10.4. The Manuscript Identifier]
<collection> contains the name of a collection of manuscripts or other objects, not necessarily located within a single repository. [10.4. The Manuscript Identifier]
<colophon> (colophon)
- contains the colophon of an item: that is, a statement
- providing information regarding the date, place, agency, or
- reason for production of the manuscript or other
- object. [10.6.1. The msItem and msItemStruct Elements]
<colophon>Explicit venenum viciorum domini
- illius, qui comparavit Anno domini Millessimo Trecentesimo
- nonagesimo primo, Sabbato in festo sancte Marthe virginis
- gloriose. Laus tibi criste quia finitur libellus iste.</colophon>
<colophon> contains the colophon of an item: that is, a statement providing information regarding the date, place, agency, or reason for production of the manuscript or other object. [10.6.1. The msItem and msItemStruct Elements]
<colophon>Explicit venenum viciorum domini illius, qui comparavit Anno
+ domini Millessimo Trecentesimo nonagesimo primo, Sabbato in festo
+ sancte Marthe virginis gloriose. Laus tibi criste quia finitur
+ libellus iste.</colophon>
<condition><p>There are lacunae in three places in
- this manuscript. After 14v two leaves has been cut out
- and narrow strips leaves remains in the spine. After 68v
- one gathering is missing and after 101v at least one
- gathering of 8 leaves has been lost. </p><p>Several leaves are damaged with tears
- or holes or have a irregular shape. Some of the damages
- do not allow the lines to be of full length and they are
- apparently older than the script. There are tears on fol.
- 2r-v, 9r-v, 10r-v, 15r-18v, 19r-v, 20r-22v, 23r-v, 24r-28v,
- 30r-v, 32r-35v, 37r-v, 38r-v, 40r-43v, 45r-47v, 49r-v,
- 51r-v, 53r-60v, 67r-v, 68r-v, 70r-v, 74r-80v, 82r-v,
- 86r-v, 88r-v, 89r-v, 95r-v, 97r-98v 99r-v, 100r-v. On fol.
- 98 the corner has been torn off. Several leaves are in a
- bad condition due to moist and wear, and have become
- dark, bleached or wrinkled. </p><p>The script has been touched up in
- the 17th century with black ink. The touching up on the
- following fols. was done by <name>Bishop Brynjólf Sveinsson</name>: 1v, 3r, 4r, 5r,
- 6v, 8v,9r, 10r, 14r, 14v, 22r,30v, 36r-52v, 72v,
- 77r,78r,103r, 104r,. An AM-note says according to the
- lawman <name>Sigurður
- Björnsson</name> that
- the rest of the touching up was done by himself and
- another lawman <name>Sigurður Jónsson</name>. <name>Sigurður Björnsson</name> did the touching up
- on the following fols.: 46v, 47r, 48r, 49r-v, 50r, 52r-v.
- <name>Sigurður
- Jónsson</name> did
- the rest of the touching up in the section 36r-59r
- containing <title>Bretasögur</title></p>
- </condition>
<condition>
+ <p>There are lacunae in three places in this
+ manuscript. After 14v two
+ leaves has been cut out and narrow strips leaves remains in the spine. After
+ 68v one gathering is missing and after 101v at least one gathering of 8 leaves
+ has been lost. </p>
+ <p>Several leaves are damaged with tears or holes or have a
+ irregular shape. Some of the damages do not allow the lines to be of full
+ length and they are apparently older than the script. There are tears on fol.
+ 2r-v, 9r-v, 10r-v, 15r-18v, 19r-v, 20r-22v, 23r-v, 24r-28v, 30r-v, 32r-35v,
+ 37r-v, 38r-v, 40r-43v, 45r-47v, 49r-v, 51r-v, 53r-60v, 67r-v, 68r-v, 70r-v,
+ 74r-80v, 82r-v, 86r-v, 88r-v, 89r-v, 95r-v, 97r-98v 99r-v, 100r-v. On fol. 98
+ the corner has been torn off. Several leaves are in a bad condition due to
+ moist and wear, and have become dark, bleached or
+ wrinkled. </p>
+ <p>The script has been
+ touched up in the 17th century with black ink. The touching up on the following
+ fols. was done by
+ <name>Bishop Brynjólf Sveinsson</name>: 1v, 3r, 4r, 5r,
+ 6v, 8v,9r, 10r, 14r, 14v, 22r,30v, 36r-52v, 72v, 77r,78r,103r, 104r,. An
+ AM-note says according to the lawman
+ <name>Sigurður Björnsson</name> that the rest of the
+ touching up was done by himself and another lawman
+ <name>Sigurður Jónsson</name>.
+ <name>Sigurður Björnsson</name> did the touching up
+ on the following fols.: 46v, 47r, 48r, 49r-v, 50r, 52r-v.
+ <name>Sigurður Jónsson</name> did the rest of the
+ touching up in the section 36r-59r containing
+ <title>Bretasögur</title>
+ </p>
+</condition>
If all that is desired is to call
- attention to the fact that the copy text has been corrected, <corr> may be used alone:
I
- don't know, Juan. It's so far in the past now — how <corr>can we</corr> prove or disprove
- anyone's theories?
-
-
-
Example
-
It is also possible, using the <choice> and <sic> elements, to provide an
- uncorrected reading:
I don't know, Juan. It's so far in
- the past now — how <choice><sic>we can</sic><corr>can we</corr>
- </choice> prove or
- disprove anyone's theories?
If all that is desired is to call attention to the fact that the copy text has been corrected, <corr> may be used alone:
I don't know,
+ Juan. It's so far in the past now — how <corr>can we</corr> prove
+ or disprove anyone's theories?
Example
It is also possible, using the <choice> and <sic> elements, to provide an uncorrected reading:
I don't know, Juan. It's so far in the past now —
+ how <choice>
+ <sic>we can</sic>
+ <corr>can we</corr>
+</choice> prove or
+ disprove anyone's theories?
<country> (country)
- contains the name of a geo-political unit,
- such as a nation, country, colony, or commonwealth, larger
- than or administratively superior to a region and smaller
- than a bloc. [13.2.3. Place Names]
The recommended source for codes to
- represent coded country names is ISO 3166.
-
-
-
Example
-
<country key="DK">Denmark</country>
-
-
-
Content
- model
-
+}
2.1.39. <country>
<country> contains the name of a geo-political unit, such as a nation, country, colony, or commonwealth, larger than or administratively superior to a region and smaller than a bloc. [13.2.3. Place Names]
<custodialHist> (custodial
- history) contains a description of a
- manuscript or other object's custodial history, either as
- running prose or as a series of dated custodial
- events. [10.9.1.2. Availability and Custodial History]
<custodialHist><custEvent type="conservation" notBefore="1961-03" notAfter="1963-02">Conserved between March
- 1961 and February 1963 at Birgitte Dalls
- Konserveringsværksted.</custEvent><custEvent type="photography" notBefore="1988-05-01" notAfter="1988-05-30">Photographed in May
- 1988 by AMI/FA.</custEvent><custEvent type="transfer-dispatch" notBefore="1989-11-13" notAfter="1989-11-13">Dispatched to Iceland
- 13 November 1989.</custEvent>
- </custodialHist>
-
-
-
Content
- model
-
+}
2.1.41. <custodialHist>
<custodialHist> (custodial history) contains a description of a manuscript or other object's custodial history, either as running prose or as a series of dated custodial events. [10.9.1.2. Availability and Custodial History]
<custodialHist>
+ <custEvent type="conservation"
+ notBefore="1961-03" notAfter="1963-02">Conserved between March 1961 and February 1963 at
+ Birgitte Dalls Konserveringsværksted.</custEvent>
+ <custEvent type="photography"
+ notBefore="1988-05-01" notAfter="1988-05-30">Photographed in
+ May 1988 by AMI/FA.</custEvent>
+ <custEvent type="transfer-dispatch"
+ notBefore="1989-11-13" notAfter="1989-11-13">Dispatched to Iceland
+ 13 November 1989.</custEvent>
+</custodialHist>
Since damage to text witnesses
- frequently makes them harder to read, the <damage> element will
- often contain an <unclear> element. If
- the damaged area is not continuous (e.g. a stain affecting
- several strings of text), the group
- attribute may be used to group together several related <damage> elements;
- alternatively the <join>
- element may be used to indicate which <damage> and <unclear> elements are part of the same
- physical phenomenon.
Since damage to text witnesses frequently makes them harder to read, the <damage> element will often contain an <unclear> element. If the damaged area is not continuous (e.g. a stain affecting several strings of text), the group attribute may be used to group together several related <damage> elements; alternatively the <join> element may be used to indicate which <damage> and <unclear> elements are part of the same physical phenomenon.
Given on the <date when="1977-06-12">Twelfth Day of June in the
- Year of Our Lord One Thousand Nine Hundred and Seventy-seven
- of the Republic the Two Hundredth and first and of the
- University the Eighty-Sixth.</date>
Given on the <date when="1977-06-12">Twelfth Day
+ of June in the Year of Our Lord One Thousand Nine Hundred and Seventy-seven of the Republic
+ the Two Hundredth and first and of the University the Eighty-Sixth.</date>
<decoDesc><p>The start of each book of the Bible
- with a 10-line historiated illuminated initial; prefaces
- decorated with 6-line blue initials with red penwork
- flourishing; chapters marked by 3-line plain red initials;
- verses with 1-line initials, alternately blue or
- red.</p>
- </decoDesc>
<decoDesc>
+ <p>The start of each book of the Bible with a 10-line historiated
+ illuminated initial; prefaces decorated with 6-line blue initials with red
+ penwork flourishing; chapters marked by 3-line plain red initials; verses
+ with 1-line initials, alternately blue or red.</p>
+</decoDesc>
<decoNote> (note on
- decoration) contains a note
- describing either a decorative component of a manuscript or
- other object, or a fairly homogenous class of such
- components. [10.7.3. Bindings, Seals, and Additional Material]
The decoration note concerns the
- illustration(s)
-
initial
-
The decoration note concerns the
- initial(s)
-
marginal
-
The decoration note concerns the
- marginal decoration
-
ornamentation
-
The decoration note concerns any sort of
- undifferentiated ornamentation. This term is more
- general than those found in the vocabulary of the
- consolidated schema.
-
other
-
The decoration note concerns
- other/unspecified aspects (you may also provide a
- custom value)
-
paratext
-
-
rubrication
-
The decoration note concerns the
- rubrication or other highlighting
-
-
-
-
-
-
-
subtype
-
(subtype) provides a
- sub-categorization of the element, if
- needed
<decoDesc><decoNote type="initial"><p>The start of each book of the Bible
- with a 10-line historiated illuminated initial;
- prefaces decorated with 6-line blue initials with red
- penwork flourishing; chapters marked by 3-line plain
- red initials; verses with 1-line initials, alternately
- blue or red.</p></decoNote>
- </decoDesc>
<decoNote> (note on decoration) contains a note describing either a decorative component of a manuscript or other object, or a fairly homogenous class of such components. [10.7.3. Bindings, Seals, and Additional Material]
The decoration note concerns the marginal decoration
ornamentation
The decoration note concerns any sort of undifferentiated ornamentation. This term is more general than those found in the vocabulary of the consolidated schema.
other
The decoration note concerns other/unspecified aspects (you may also provide a custom value)
paratext
rubrication
The decoration note concerns the rubrication or other highlighting
subtype
provides a sub-categorization of the element, if needed
<decoDesc>
+ <decoNote type="initial">
+ <p>The start of each book of the Bible with
+ a 10-line historiated illuminated initial;
+ prefaces decorated with 6-line blue initials
+ with red penwork flourishing; chapters marked by
+ 3-line plain red initials; verses with 1-line initials,
+ alternately blue or red.</p>
+ </decoNote>
+</decoDesc>
<del> (deletion) contains a letter, word, or passage deleted,
- marked as deleted, or otherwise indicated as superfluous or
- spurious in the copy text by an author, scribe, or a
- previous annotator or corrector. [3.5.3. Additions, Deletions, and Omissions]
This element should be used for
- deletion of shorter sequences of text, typically single
- words or phrases. The <delSpan> element should be used for
- longer sequences of text, for those containing structural
- subdivisions, and for those containing overlapping additions
- and deletions.
The text deleted must be at least
- partially legible in order for the encoder to be able to
- transcribe it (unless it is restored in a <supplied> tag).
- Illegible or lost text within a deletion may be marked using
- the <gap> tag to signal that text is present but
- has not been transcribed, or is no longer visible.
- Attributes on the <gap> element may be used
- to indicate how much text is omitted, the reason for
- omitting it, etc. If text is not fully legible, the <unclear> element
- (available when using the additional tagset for
- transcription of primary sources) should be used to signal
- the areas of text which cannot be read with confidence in a
- similar way.
Degrees of uncertainty over what can
- still be read, or whether a deletion was intended may be
- indicated by use of the <certainty> element (see 21. Certainty, Precision, and
- Responsibility).
There is a clear distinction in
- the TEI between <del> and <surplus> on the one hand and <gap> or <unclear> on the other. <del>
- indicates a deletion present in the source being
- transcribed, which states the author's or a later scribe's
- intent to cancel or remove text. <surplus> indicates material present in
- the source being transcribed which should have been so
- deleted, but which is not in fact. <gap> or
- <unclear>, by
- contrast, signal an editor's or encoder's decision to omit
- something or their inability to read the source text. See
- sections 11.3.1.7. Text Omitted from or Supplied in the
- Transcription and 11.3.3.2. Use of the gap, del, damage, unclear, and
- supplied Elements in Combination for the
- relationship between these and other related elements used
- in detailed transcription.
-
-
-
Example
-
<l><del rend="overtyped">Mein</del> Frisch <del rend="overstrike" type="primary">schwebt</del> weht der Wind </l>
<del> (deletion) contains a letter, word, or passage deleted, marked as deleted, or otherwise indicated as superfluous or spurious in the copy text by an author, scribe, or a previous annotator or corrector. [3.4.3. Additions, Deletions, and Omissions]
This element should be used for deletion of shorter sequences of text, typically single words or phrases. The <delSpan> element should be used for longer sequences of text, for those containing structural subdivisions, and for those containing overlapping additions and deletions.
The text deleted must be at least partially legible in order for the encoder to be able to transcribe it (unless it is restored in a <supplied> tag). Illegible or lost text within a deletion may be marked using the <gap> tag to signal that text is present but has not been transcribed, or is no longer visible. Attributes on the <gap> element may be used to indicate how much text is omitted, the reason for omitting it, etc. If text is not fully legible, the <unclear> element (available when using the additional tagset for transcription of primary sources) should be used to signal the areas of text which cannot be read with confidence in a similar way.
Degrees of uncertainty over what can still be read, or whether a deletion was intended may be indicated by use of the <certainty> element (see 21. Certainty, Precision, and Responsibility).
There is a clear distinction in the TEI between <del> and <surplus> on the one hand and <gap> or <unclear> on the other. <del> indicates a deletion present in the source being transcribed, which states the author's or a later scribe's intent to cancel or remove text. <surplus> indicates material present in the source being transcribed which should have been so deleted, but which is not in fact. <gap> or <unclear>, by contrast, signal an editor's or encoder's decision to omit something or their inability to read the source text. See sections 11.3.1.7. Text Omitted from or Supplied in the Transcription and 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for the relationship between these and other related elements used in detailed transcription.
<depth> (depth) contains a measurement from the front to the back
- of an object, perpendicular to the measurement given by the
- <width> element.
- [10.3.4. Dimensions]
<depth> contains a measurement from the front to the back of an object, perpendicular to the measurement given by the <width> element. [10.3.4. Dimensions]
<desc> (description)
- contains a short description of the purpose,
- function, or use of its parent element, or when the parent
- is a documentation element, describes or defines the object
- being documented. [22.4.1. Description of Components]
When used in a specification element
- such as <elementSpec>, TEI
- convention requires that this be expressed as a finite
- clause, begining with an active verb.
-
-
-
Example
-
Example of a <desc>
- element inside a documentation element.
<dataSpec module="tei" ident="teidata.point"><desc versionDate="2010-10-17" xml:lang="en">defines the data type used to
- express a point in cartesian space.</desc><content><dataRef name="token" restriction="(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)"/>
- </content>
- <!-- ... -->
- </dataSpec>
-
-
-
Example
-
Example of a <desc>
- element in a non-documentation element.
A <desc>
- with a type of deprecationInfo should only occur when its
- parent element is being deprecated. Furthermore, it should
- always occur in an element that is being deprecated when <desc> is a valid child of that
- element.
- <sch:rule context="tei:desc[ @type eq
- 'deprecationInfo']">
- <sch:assert test="../@validUntil">Information about a
- deprecation should only be present in a specification
- element that is being deprecated: that is, only an element
- that has a @validUntil attribute should have a child
- <desc type="deprecationInfo">.</sch:assert>
- </sch:rule>
<desc> (description) contains a brief description of the object documented by its parent element, typically a documentation element or an entity. [22.4.1. Description of Components]
When used in a specification element such as <elementSpec>, TEI convention requires that this be expressed as a finite clause, begining with an active verb.
Example
<desc>contains a brief description of the purpose and intended use of a documentation element, or a brief characterisation of a parent entity </desc>
Schematron
A <desc> with a type of deprecationInfo should only occur when its parent element is being deprecated. Furthermore, it should always occur in an element that is being deprecated when <desc> is a valid child of that element.
+<sch:rule context="tei:desc[ @type eq 'deprecationInfo']">
+<sch:assert test="../@validUntil">Information about a
+ deprecation should only be present in a specification element
+ that is being deprecated: that is, only an element that has a
+ @validUntil attribute should have a child <desc
+ type="deprecationInfo">.</sch:assert>
+</sch:rule>
Contains no more than one of each of
- the specialized elements used to express a three-dimensional
- object's height, width, and depth, combined with any number
- of other kinds of dimensional specification.
This
- might be used to show that the inscribed panels on some
- (imaginary) monument are all the same size (7004 by 1803 cm) and
- stand out from the rest of the monument by 345 mm.
-
-
-
Example
-
When simple numeric quantities are
- involved, they may be expressed on the quantity attribute of any or all of the child
- elements, as in the following example:
- <sch:rule context="//tei:dimensions">
- <sch:assert test="@unit" role="error"> The unit of
- measurement must be specified in the unit attribute on the
- dimensions element </sch:assert>
- </sch:rule>
-
-
-
Schematron
-
- <s:report test="count(tei:width)> 1">The element
- <s:name/> may appear once only </s:report>
- <s:report test="count(tei:height)> 1">The element
- <s:name/> may appear once only </s:report>
- <s:report test="count(tei:depth)> 1">The element
- <s:name/> may appear once only
- </s:report>
Contains no more than one of each of the specialized elements used to express a three-dimensional object's height, width, and depth, combined with any number of other kinds of dimensional specification.
This might be used to show that the inscribed panels on some (imaginary) monument are all the same size (7004 by 1803 cm) and stand out from the rest of the monument by 345 mm.
Example
When simple numeric quantities are involved, they may be expressed on the quantity attribute of any or all of the child elements, as in the following example:
+<sch:rule context="//tei:dimensions">
+<sch:assert test="@unit" role="error"> The unit of measurement
+ must be specified in the unit attribute on the dimensions
+ element </sch:assert>
+</sch:rule>
Schematron
+<s:report test="count(tei:width)> 1">The element <s:name/> may appear once only
+</s:report>
+<s:report test="count(tei:height)> 1">The element <s:name/> may appear once only
+</s:report>
+<s:report test="count(tei:depth)> 1">The element <s:name/> may appear once only
+</s:report>
<district> (district)
- contains the name of any kind of subdivision
- of a settlement, such as a parish, ward, or other
- administrative or geographic unit. [13.2.3. Place Names]
<district> contains the name of any kind of subdivision of a settlement, such as a parish, ward, or other administrative or geographic unit. [13.2.3. Place Names]
<body><div type="part">
- <head>Fallacies of
- Authority</head>
- <p>The subject of
- which is Authority in various shapes, and the object, to
- repress all exercise of the reasoning faculty.</p><div n="1" type="chapter"><head>The Nature of Authority</head><p>With reference to any
- proposed measures having for their object the greatest
- happiness of the greatest number [...]</p><div n="1.1" type="section"><head>Analysis of
- Authority</head>
- <p>What on any
- given occasion is the legitimate weight or influence to be
- attached to authority [...] </p></div><div n="1.2" type="section">
- <head>Appeal to
- Authority, in What Cases Fallacious.</head><p>Reference to authority is open to the
- charge of fallacy when [...] </p></div></div></div>
- </body>
-
-
-
Schematron
-
- <s:report test="(ancestor::tei:l or ancestor::tei:lg) and
- not(ancestor::tei:floatingText)"> Abstract model
- violation: Lines may not contain higher-level structural
- elements such as div, unless div is a descendant of
- floatingText. </s:report>
-
-
-
Schematron
-
- <s:report test="(ancestor::tei:p or ancestor::tei:ab) and
- not(ancestor::tei:floatingText)"> Abstract model
- violation: p and ab may not contain higher-level structural
- elements such as div, unless div is a descendant of
- floatingText. </s:report>
-
-
-
Content
- model
-
+}
2.1.53. <div>
<div> (text division) contains a subdivision of the front, body, or back of a text. [4.1. Divisions of the Body]
<body>
+ <div type="part">
+ <head>Fallacies of Authority</head>
+ <p>The subject of which is Authority in various shapes, and the object, to repress all
+ exercise of the reasoning faculty.</p>
+ <div n="1" type="chapter">
+ <head>The Nature of Authority</head>
+ <p>With reference to any proposed measures having for their object the greatest
+ happiness of the greatest number [...]</p>
+ <div n="1.1" type="section">
+ <head>Analysis of Authority</head>
+ <p>What on any given occasion is the legitimate weight or influence to be attached to
+ authority [...] </p>
+ </div>
+ <div n="1.2" type="section">
+ <head>Appeal to Authority, in What Cases Fallacious.</head>
+ <p>Reference to authority is open to the charge of fallacy when [...] </p>
+ </div>
+ </div>
+ </div>
+</body>
Schematron
+<s:report test="ancestor::tei:l"> Abstract model violation: Lines may not contain higher-level structural elements such as div.
+</s:report>
Schematron
+<s:report test="ancestor::tei:p or ancestor::tei:ab and not(ancestor::tei:floatingText)"> Abstract model violation: p and ab may not contain higher-level structural elements such as div.
+</s:report>
<editor> contains a secondary
- statement of responsibility for a bibliographic item, for
- example the name of an individual, institution or
- organization, (or of several such) acting as editor,
- compiler, translator, etc. [3.12.2.2. Titles, Authors, and Editors]
may be used to
- specify further information about the entity
- referenced by this name in the form of a set of
- whitespace-separated values, for example the
- occupation of a person, or the status of a
- place.
Particularly where cataloguing is likely to
- be based on the content of the header, it is advisable to
- use generally recognized authority lists for the exact form
- of personal names.
-
-
-
Example
-
<editor role="Technical_Editor">Ron Van den
- Branden</editor>
- <editor role="Editor-in-Chief">John Walsh</editor>
- <editor role="Managing_Editor">Anne Baillot</editor>
<editor> contains a secondary statement of responsibility for a bibliographic item, for example the name of an individual, institution or organization, (or of several such) acting as editor, compiler, translator, etc. [3.11.2.2. Titles, Authors, and Editors]
may be used to specify further information about the entity referenced by this name in the form of a set of whitespace-separated values, for example the occupation of a person, or the status of a place.
Particularly where cataloguing is likely to be based on the content of the header, it is advisable to use generally recognized authority lists for the exact form of personal names.
Example
<editor role="Technical_Editor">Ron Van den Branden</editor>
+<editor role="Editor-in-Chief">John Walsh</editor>
+<editor role="Managing_Editor">Anne Baillot</editor>
<editorialDecl><normalization><p>All words converted to Modern American
- spelling using Websters 9th Collegiate dictionary
- </p></normalization><quotation marks="all"><p>All opening quotation marks converted
- to “ all closing quotation marks converted to
- &cdq;.</p>
- </quotation>
- </editorialDecl>
<editorialDecl>
+ <normalization>
+ <p>All words converted to Modern American spelling using
+ Websters 9th Collegiate dictionary
+ </p>
+ </normalization>
+ <quotation marks="all">
+ <p>All opening quotation marks converted to “ all closing
+ quotation marks converted to &cdq;.</p>
+ </quotation>
+</editorialDecl>
<encodingDesc><p>Basic encoding, capturing lexical
- information only. All hyphenation, punctuation, and
- variant spellings normalized. No formatting or layout
- information preserved.</p>
- </encodingDesc>
<encodingDesc>
+ <p>Basic encoding, capturing lexical information only. All
+ hyphenation, punctuation, and variant spellings normalized. No
+ formatting or layout information preserved.</p>
+</encodingDesc>
<ex>
- (editorial expansion) contains a sequence of letters added by an editor
- or transcriber when expanding an abbreviation. [11.3.1.2. Abbreviation and Expansion]
<ex> (editorial expansion) contains a sequence of letters added by an editor or transcriber when expanding an abbreviation. [11.3.1.2. Abbreviation and Expansion]
The content of this element should be
- the expanded abbreviation, usually (but not always) a
- complete word or phrase. The <ex> element
- provided by the transcr
- module may be used to mark up sequences of letters supplied
- within such an expansion.
If abbreviations are
- expanded silently, this practice should be documented in the
- <editorialDecl>,
- either with a <normalization>
- element or a <p>.
-
-
-
Example
-
The address is Southmoor <choice><expan>Road</expan><abbr>Rd</abbr>
- </choice>
The content of this element should be the expanded abbreviation, usually (but not always) a complete word or phrase. The <ex> element provided by the transcr module may be used to mark up sequences of letters supplied within such an expansion.
If abbreviations are expanded silently, this practice should be documented in the <editorialDecl>, either with a <normalization> element or a <p>.
Example
The address is Southmoor
+<choice>
+ <expan>Road</expan>
+ <abbr>Rd</abbr>
+</choice>
<explicit> (explicit)
- contains the explicit of a item, that is, the closing words
- of the text proper, exclusive of any rubric or colophon
- which might follow it. [10.6.1. The msItem and msItemStruct Elements]
- <sch:rule context="//tei:explicit/@xml:lang">
- <sch:let name="langIdents"
- value="//tei:profileDesc/tei:langUsage/tei:language/@ident"/>
- <sch:assert test=". = $langIdents">
- Attribute value must match one of the following
- language codes in the <profileDesc>:
- <sch:value-of select="string-join($langIdents,
- ' | ')"/>. </sch:assert>
- </sch:rule>
<explicit>sed libera nos a malo.</explicit>
- <rubric>Hic explicit
- oratio qui dicitur dominica.</rubric>
- <explicit type="defective">ex materia quasi et
- forma sibi proporti<gap/>
- </explicit>
- <explicit type="reverse">saued be shulle that
- doome of day the at </explicit>
-
-
-
Content
- model
-
+}
2.1.62. <explicit>
<explicit> contains the explicit of a item, that is, the closing words of the text proper, exclusive of any rubric or colophon which might follow it. [10.6.1. The msItem and msItemStruct Elements]
+<sch:rule context="//tei:explicit/@xml:lang">
+<sch:let name="langIdents"
+ value="//tei:profileDesc/tei:langUsage/tei:language/@ident"/>
+<sch:assert test=". = $langIdents"> Attribute value must
+ match one of the following language codes in the
+ <profileDesc>: <sch:value-of select="string-join($langIdents, ' | ')"/>.
+</sch:assert>
+</sch:rule>
<explicit>sed libera nos a malo.</explicit>
+<rubric>Hic explicit oratio qui dicitur dominica.</rubric>
+<explicit type="defective">ex materia quasi et forma sibi
+ proporti<gap/>
+</explicit>
+<explicit type="reverse">saued be shulle that doome of day the at
+</explicit>
<facsimile> contains a
- representation of some written source in the form of a set
- of images rather than as transcribed or encoded text.
- [11.1. Digital Facsimiles]
<facsimile> contains a representation of some written source in the form of a set of images rather than as transcribed or encoded text. [11.1. Digital Facsimiles]
<figDesc> (description of
- figure) contains a brief prose
- description of the appearance or content of a graphic
- figure, for use when documenting an image without displaying
- it. [14.4. Specific Elements for Graphic Images]
This element is intended for use as an
- alternative to the content of its parent <figure> element ; for example, to display
- when the image is required but the equipment in use cannot
- display graphic images. It may also be used for indexing or
- documentary purposes.
-
-
-
Example
-
<figure><graphic url="emblem1.png"/><head>Emblemi d'Amore</head><figDesc>A pair of naked
- winged cupids, each holding a flaming torch, in a rural
- setting.</figDesc>
- </figure>
-
-
-
Content
- model
-
+}
2.1.65. <figDesc>
<figDesc> (description of figure) contains a brief prose description of the appearance or content of a graphic figure, for use when documenting an image without displaying it. [14.4. Specific Elements for Graphic Images]
This element is intended for use as an alternative to the content of its parent <figure> element ; for example, to display when the image is required but the equipment in use cannot display graphic images. It may also be used for indexing or documentary purposes.
Example
<figure>
+ <graphic url="emblem1.png"/>
+ <head>Emblemi d'Amore</head>
+ <figDesc>A pair of naked winged cupids, each holding a
+ flaming torch, in a rural setting.</figDesc>
+</figure>
<figure> (figure) groups elements representing or containing graphic
- information such as an illustration, formula, or
- figure. [14.4. Specific Elements for Graphic Images]
<figure><head>The View from the Bridge</head><figDesc>A Whistleresque
- view showing four or five sailing boats in the foreground,
- and a series of buoys strung out between them.</figDesc><graphic url="http://www.example.org/fig1.png" scale="0.5"/>
- </figure>
<figure>
+ <head>The View from the Bridge</head>
+ <figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a
+ series of buoys strung out between them.</figDesc>
+ <graphic url="http://www.example.org/fig1.png"
+ scale="0.5"/>
+</figure>
The major source of information for
- those seeking to create a catalogue entry or bibliographic
- citation for an electronic file. As such, it provides a
- title and statements of responsibility together with details
- of the publication or distribution of the file, of any
- series to which it belongs, and detailed bibliographic notes
- for matters not addressed elsewhere in the header. It also
- contains a full bibliographic description for the source or
- sources from which the electronic text was derived.
-
-
-
Example
-
<fileDesc><titleStmt><title>The shortest possible TEI
- document</title>
- </titleStmt><publicationStmt><p>Distributed as part of
- TEI P5</p></publicationStmt><sourceDesc><p>No print source exists:
- this is an original digital text</p></sourceDesc>
- </fileDesc>
The major source of information for those seeking to create a catalogue entry or bibliographic citation for an electronic file. As such, it provides a title and statements of responsibility together with details of the publication or distribution of the file, of any series to which it belongs, and detailed bibliographic notes for matters not addressed elsewhere in the header. It also contains a full bibliographic description for the source or sources from which the electronic text was derived.
Example
<fileDesc>
+ <titleStmt>
+ <title>The shortest possible TEI document</title>
+ </titleStmt>
+ <publicationStmt>
+ <p>Distributed as part of TEI P5</p>
+ </publicationStmt>
+ <sourceDesc>
+ <p>No print source exists: this is an original digital text</p>
+ </sourceDesc>
+</fileDesc>
<filiation> (filiation)
- contains information concerning the
- manuscript or other object's filiation, i.e. its relationship to other
- surviving manuscripts or other objects of the same text or
- contents, its protographs, antigraphs and apographs. [10.6.1. The msItem and msItemStruct Elements]
In this
- example, the reference to ‘Dujchev N17’
- includes a link to some other manuscript description which has
- the identifier DN17.
-
-
-
Example
-
<msItem><title>Guan-ben</title><filiation><p>The "Guan-ben" was widely current among
- mathematicians in the Qing dynasty, and "Zhao Qimei
- version" was also read. It is therefore difficult to
- know the correct filiation path to follow. The study of
- this era is much indebted to Li Di. We explain the
- outline of his conclusion here. Kong Guangsen
- (1752-1786)(17) was from the same town as Dai Zhen, so he
- obtained "Guan-ben" from him and studied it(18). Li
- Huang (d. 1811) (19) took part in editing Si Ku Quan
- Shu, so he must have had "Guan-ben". Then Zhang Dunren
- (1754-1834) obtained this version, and studied "Da Yan
- Zong Shu Shu" (The General Dayan Computation). He wrote
- Jiu Yi Suan Shu (Mathematics Searching for One, 1803)
- based on this version of Shu Xue Jiu Zhang (20).</p><p>One of the most
- important persons in restoring our knowledge concerning
- the filiation of these books was Li Rui (1768(21)
- -1817)(see his biography). ... only two volumes remain of
- this manuscript, as far as chapter 6 (chapter 3 part 2)
- p.13, that is, question 2 of "Huan Tian San Ji" (square
- of three loops), which later has been lost.</p></filiation>
- </msItem>
- <!--http://www2.nkfust.edu.tw/~jochi/ed1.htm-->
<filiation> contains information concerning the manuscript or other object's filiation, i.e. its relationship to other surviving manuscripts or other objects of the same text or contents, its protographs, antigraphs and apographs. [10.6.1. The msItem and msItemStruct Elements]
In this example, the reference to ‘Dujchev N17’ includes a link to some other manuscript description which has the identifier DN17.
Example
<msItem>
+ <title>Guan-ben</title>
+ <filiation>
+ <p>The "Guan-ben" was widely current among mathematicians in the
+ Qing dynasty, and "Zhao Qimei version" was also read. It is
+ therefore difficult to know the correct filiation path to follow.
+ The study of this era is much indebted to Li Di. We explain the
+ outline of his conclusion here. Kong Guangsen
+ (1752-1786)(17) was from the same town as Dai Zhen, so he obtained
+ "Guan-ben" from him and studied it(18). Li Huang (d. 1811)
+ (19) took part in editing Si Ku Quan Shu, so he must have had
+ "Guan-ben". Then Zhang Dunren (1754-1834) obtained this version,
+ and studied "Da Yan Zong Shu Shu" (The General Dayan
+ Computation). He wrote Jiu Yi Suan Shu (Mathematics
+ Searching for One, 1803) based on this version of Shu Xue Jiu
+ Zhang (20).</p>
+ <p>One of the most important persons in restoring our knowledge
+ concerning the filiation of these books was Li Rui (1768(21)
+ -1817)(see his biography). ... only two volumes remain of this
+ manuscript, as far as chapter 6 (chapter 3 part 2) p.13, that is,
+ question 2 of "Huan Tian San Ji" (square of three loops),
+ which later has been lost.</p>
+ </filiation>
+</msItem>
+<!--http://www2.nkfust.edu.tw/~jochi/ed1.htm-->
<finalRubric> (final
- rubric) contains the string of words
- that denotes the end of a text division, often with an
- assertion as to its author and title, usually set off from
- the text itself by red ink, by a different size or type of
- script, or by some other such visual device. [10.6.1. The msItem and msItemStruct Elements]
- <sch:rule context="//tei:finalRubric/@xml:lang">
- <sch:let name="langIdents"
- value="//tei:profileDesc/tei:langUsage/tei:language/@ident"/>
- <sch:assert test=". = $langIdents">
- Attribute value must match one of the following
- language codes in the <profileDesc>:
- <sch:value-of select="string-join($langIdents,
- ' | ')"/>. </sch:assert>
- </sch:rule>
<finalRubric>Explicit le romans de la Rose
- ou l'art d'amours est toute enclose.</finalRubric>
- <finalRubric>ok lúkv ver
- þar Brennu-Nials savgv</finalRubric>
<finalRubric> contains the string of words that denotes the end of a text division, often with an assertion as to its author and title, usually set off from the text itself by red ink, by a different size or type of script, or by some other such visual device. [10.6.1. The msItem and msItemStruct Elements]
+<sch:rule context="//tei:finalRubric/@xml:lang">
+<sch:let name="langIdents"
+ value="//tei:profileDesc/tei:langUsage/tei:language/@ident"/>
+<sch:assert test=". = $langIdents"> Attribute value must
+ match one of the following language codes in the
+ <profileDesc>: <sch:value-of select="string-join($langIdents, ' | ')"/>.
+</sch:assert>
+</sch:rule>
<finalRubric>Explicit le romans de la Rose ou l'art
+ d'amours est toute enclose.</finalRubric>
+<finalRubric>ok lúkv ver þar Brennu-Nials savgv</finalRubric>
<foliation> (foliation)
- describes the numbering system or systems
- used to count the leaves or pages in a codex or similar
- object. [10.7.1.4. Foliation]
<foreign> (foreign)
- identifies a word or phrase as belonging to
- some language other than that of the surrounding
- text. [3.3.2.1. Foreign Words or Expressions]
- <sch:rule context="//tei:foreign/@xml:lang">
- <sch:let name="langIdents"
- value="//tei:profileDesc/tei:langUsage/tei:language/@ident"/>
- <sch:assert test=". = $langIdents">
- Attribute value must match one of the following
- language codes in the <profileDesc>:
- <sch:value-of select="string-join($langIdents,
- ' | ')"/>. </sch:assert>
- </sch:rule>
The global xml:lang attribute should be supplied for this
- element to identify the language of the word or phrase
- marked. As elsewhere, its value should be a language tag as
- defined in 6.1. Language Identification.
This element is
- intended for use only where no other element is available to
- mark the phrase or words concerned. The global xml:lang attribute should be used in
- preference to this element where it is intended to mark the
- language of the whole of some text element.
The <distinct> element may be used
- to identify phrases belonging to sublanguages or registers
- not generally regarded as true languages.
-
-
-
Example
-
This is heathen Greek to you still?
- Your <foreign xml:lang="la">lapis
- philosophicus</foreign>?
+<sch:rule context="//tei:foreign/@xml:lang">
+<sch:let name="langIdents"
+ value="//tei:profileDesc/tei:langUsage/tei:language/@ident"/>
+<sch:assert test=". = $langIdents"> Attribute value must
+ match one of the following language codes in the
+ <profileDesc>: <sch:value-of select="string-join($langIdents, ' | ')"/>.
+</sch:assert>
+</sch:rule>
The global xml:lang attribute should be supplied for this element to identify the language of the word or phrase marked. As elsewhere, its value should be a language tag as defined in 6.1. Language Identification.
This element is intended for use only where no other element is available to mark the phrase or words concerned. The global xml:lang attribute should be used in preference to this element where it is intended to mark the language of the whole of some text element.
The <distinct> element may be used to identify phrases belonging to sublanguages or registers not generally regarded as true languages.
Example
This is
+ heathen Greek to you still? Your <foreign xml:lang="la">lapis
+ philosophicus</foreign>?
<funder> (funding body)
- specifies the name of an individual,
- institution, or organization responsible for the funding of
- a project or text. [2.2.1. The Title Statement]
Funders provide financial support for a
- project; they are distinct from sponsors (see element <sponsor>), who provide intellectual support
- and authority.
-
-
-
Example
-
<funder>The National Endowment for the
- Humanities, an independent federal agency</funder>
- <funder>Directorate
- General XIII of the Commission of the European
- Communities</funder>
- <funder>The Andrew W.
- Mellon Foundation</funder>
- <funder>The Social
- Sciences and Humanities Research Council of Canada</funder>
-
-
-
Content
- model
-
+}
2.1.74. <funder>
<funder> (funding body) specifies the name of an individual, institution, or organization responsible for the funding of a project or text. [2.2.1. The Title Statement]
Funders provide financial support for a project; they are distinct from sponsors (see element <sponsor>), who provide intellectual support and authority.
Example
<funder>The National Endowment for the Humanities, an independent federal agency</funder>
+<funder>Directorate General XIII of the Commission of the European Communities</funder>
+<funder>The Andrew W. Mellon Foundation</funder>
+<funder>The Social Sciences and Humanities Research Council of Canada</funder>
<fw>
- (forme work) contains a running head (e.g. a header, footer), catchword,
- or similar material appearing on the current page.
- [11.6. Headers, Footers, and Similar Matter]
Where running heads are consistent
- throughout a chapter or section, it is usually more
- convenient to relate them to the chapter or section, e.g. by
- use of the rend attribute. The <fw> element is intended for cases where the
- running head changes from page to page, or where details of
- page layout and the internal structure of the running heads
- are of paramount importance.
<fw> (forme work) contains a running head (e.g. a header, footer), catchword, or similar material appearing on the current page. [11.6. Headers, Footers, and Similar Matter]
Where running heads are consistent throughout a chapter or section, it is usually more convenient to relate them to the chapter or section, e.g. by use of the rend attribute. The <fw> element is intended for cases where the running head changes from page to page, or where details of page layout and the internal structure of the running heads are of paramount importance.
The name g
- is short for gaiji, which is the
- Japanese term for a non-standardized character or
- glyph.
-
-
-
Example
-
<g ref="#ctlig">ct</g>
This example points to a <glyph> element with the identifier
- ctlig like the following:
- <glyph xml:id="ctlig">
- <!-- here we describe the
- particular ct-ligature intended -->
- </glyph>
-
-
-
-
Example
-
<g ref="#per-glyph">per</g>
The medieval brevigraph per
- could similarly be considered as an individual glyph, defined in
- a <glyph> element with the identifier
- per-glyph as follows:
The name g is short for gaiji, which is the Japanese term for a non-standardized character or glyph.
Example
<g ref="#ctlig">ct</g>
This example points to a <glyph> element with the identifier ctlig like the following:
<glyph xml:id="ctlig">
+<!-- here we describe the particular ct-ligature intended -->
+</glyph>
Example
<g ref="#per-glyph">per</g>
The medieval brevigraph per could similarly be considered as an individual glyph, defined in a <glyph> element with the identifier per-glyph as follows:
<gap> (gap) indicates a point where material has been omitted
- in a transcription, whether for editorial reasons described
- in the TEI header, as part of sampling practice, or because
- the material is illegible, invisible, or inaudible.
- [3.5.3. Additions, Deletions, and Omissions]
The <gap> tag simply signals
- the editors decision to omit or inability to transcribe a
- span of text. Other information, such as the interpretation
- that text was deliberately erased or covered, should be
- indicated using the relevant tags, such as <del> in the case of deliberate
- deletion.
<gap> indicates a point where material has been omitted in a transcription, whether for editorial reasons described in the TEI header, as part of sampling practice, or because the material is illegible, invisible, or inaudible. [3.4.3. Additions, Deletions, and Omissions]
The <gap> tag simply signals the editors decision to omit or inability to transcribe a span of text. Other information, such as the interpretation that text was deliberately erased or covered, should be indicated using the relevant tags, such as <del> in the case of deliberate deletion.
<geo> (geographical
- coordinates) contains any expression
- of a set of geographic coordinates, representing a point,
- line, or area on the surface of the earth in some
- notation. [13.3.4.1. Varieties of Location]
Uses of <geo> can
- be associated with a coordinate system, defined by a <geoDecl> element supplied in
- the TEI header, using the decls
- attribute. If no such link is made, the assumption is that
- the content of each <geo> element will be a
- pair of numbers separated by whitespace, to be interpreted
- as latitude followed by longitude according to the World
- Geodetic System.
-
-
-
Example
-
<geoDecl xml:id="WGS" datum="WGS84">World Geodetic System</geoDecl>
- <geoDecl xml:id="OS" datum="OSGB36">Ordnance Survey</geoDecl>
- <!-- ... -->
- <location><desc>A tombstone plus six
- lines of Anglo-Saxon text, built into the west tower (on
- the south side of the archway, at 8 ft. above the ground)
- of the Church of St. Mary-le-Wigford in Lincoln.</desc><geo decls="#WGS">53.226658 -0.541254</geo><geo decls="#OS">SK 97481 70947</geo>
- </location>
-
-
-
Example
-
<geo>41.687142 -74.870109</geo>
-
-
-
Content
- model
-
+}
2.1.78. <geo>
<geo> (geographical coordinates) contains any expression of a set of geographic coordinates, representing a point, line, or area on the surface of the earth in some notation. [13.3.4.1. Varieties of Location]
Uses of <geo> can be associated with a coordinate system, defined by a <geoDecl> element supplied in the TEI header, using the decls attribute. If no such link is made, the assumption is that the content of each <geo> element will be a pair of numbers separated by whitespace, to be interpreted as latitude followed by longitude according to the World Geodetic System.
Example
<geoDecl xml:id="WGS" datum="WGS84">World Geodetic System</geoDecl>
+<geoDecl xml:id="OS" datum="OSGB36">Ordnance Survey</geoDecl>
+<!-- ... -->
+<location>
+ <desc>A tombstone plus six lines of
+ Anglo-Saxon text, built into the west tower (on the south side
+ of the archway, at 8 ft. above the ground) of the
+ Church of St. Mary-le-Wigford in Lincoln.</desc>
+ <geo decls="#WGS">53.226658 -0.541254</geo>
+ <geo decls="#OS">SK 97481 70947</geo>
+</location>
<geogFeat> (geographical
- feature name) contains a common noun
- identifying some geographical feature contained within a
- geographic name, such as valley, mount, etc. [13.2.3. Place Names]
<geogFeat> (geographical feature name) contains a common noun identifying some geographical feature contained within a geographic name, such as valley, mount, etc. [13.2.3. Place Names]
<geogName> (geographical
- name) identifies a name associated
- with some geographical feature such as Windrush Valley or
- Mount Sinai. [13.2.3. Place Names]
<geogName> (geographical name) identifies a name associated with some geographical feature such as Windrush Valley or Mount Sinai. [13.2.3. Place Names]
<p>The <gi>xhtml:li</gi> element is roughly analogous to the
- <gi>item</gi> element, as is the
- <gi scheme="DBK">listItem</gi> element.</p>
This example shows the use of
- both a namespace prefix and the scheme
- attribute as alternative ways of indicating that the <gi> in question is not a TEI element name: in
- practice only one method should be adopted.
<p>The <gi>xhtml:li</gi> element is roughly analogous to the <gi>item</gi> element, as is the
+<gi scheme="DBK">listItem</gi> element.</p>
This example shows the use of both a namespace prefix and the scheme attribute as alternative ways of indicating that the <gi> in question is not a TEI element name: in practice only one method should be adopted.
<glyph xml:id="rstroke"><localProp name="Name" value="LATIN
- SMALL LETTER R WITH A FUNNY
- STROKE"/><localProp name="entity" value="rstroke"/><figure><graphic url="glyph-rstroke.png"/></figure>
- </glyph>
The mimeType
- attribute should be used to supply the MIME media type of
- the image specified by the url
- attribute.
Within the body of a text, a <graphic> element
- indicates the presence of a graphic component in the source
- itself. Within the context of a <facsimile> or <sourceDoc> element, however, a <graphic> element
- provides an additional digital representation of some part
- of the source being encoded.
-
-
-
Example
-
<figure><graphic url="fig1.png"/><head>Figure One: The View from the
- Bridge</head><figDesc>A Whistleresque
- view showing four or five sailing boats in the foreground,
- and a series of buoys strung out between them.</figDesc>
- </figure>
The mimeType attribute should be used to supply the MIME media type of the image specified by the url attribute.
Within the body of a text, a <graphic> element indicates the presence of a graphic component in the source itself. Within the context of a <facsimile> or <sourceDoc> element, however, a <graphic> element provides an additional digital representation of some part of the source being encoded.
Example
<figure>
+ <graphic url="fig1.png"/>
+ <head>Figure One: The View from the Bridge</head>
+ <figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a
+ series of buoys strung out between them.</figDesc>
+</figure>
<handDesc><handNote scope="major">Written throughout in <term>angelicana
- formata</term>.</handNote>
- </handDesc>
-
-
-
Example
-
<handDesc hands="2"><p>The manuscript is written in two
- contemporary hands, otherwise unknown, but clearly those
- of practised scribes. Hand I writes ff. 1r-22v and hand
- II ff. 23 and 24. Some scholars, notably Verner Dahlerup
- and Hreinn Benediktsson, have argued for a third hand on
- f. 24, but the evidence for this is insubstantial.</p>
- </handDesc>
<handDesc>
+ <handNote scope="major">Written throughout in <term>angelicana formata</term>.</handNote>
+</handDesc>
Example
<handDesc hands="2">
+ <p>The manuscript is written in two contemporary hands, otherwise
+ unknown, but clearly those of practised scribes. Hand I writes
+ ff. 1r-22v and hand II ff. 23 and 24. Some scholars, notably
+ Verner Dahlerup and Hreinn Benediktsson, have argued for a third hand
+ on f. 24, but the evidence for this is insubstantial.</p>
+</handDesc>
- <sch:rule context="//tei:handNote/@script">
- <sch:let name="langIdents"
- value="//tei:profileDesc/tei:langUsage/tei:language/@ident"/>
- <sch:assert test="every $i in tokenize(., '\s')
- satisfies $i = $langIdents"> Attribute value(s)
- must match one of the following language codes in
- the <profileDesc>:
- <sch:value-of select="string-join($langIdents,
- ' | ')"/>. </sch:assert>
- </sch:rule>
-
-
-
Datatype
-
1–∞ occurrences ofteidata.name
- separated by
- whitespace
<handNote scope="sole"><p>Written in insular phase II
- half-uncial with interlinear Old English gloss in an
- Anglo-Saxon pointed minuscule.</p>
- </handNote>
-
-
-
Content
- model
-
+
Schema Declaration
+element handDesc { attribute hands { text }, handNote+ }
+<sch:rule context="//tei:handNote/@script">
+<sch:let name="langIdents"
+ value="//tei:profileDesc/tei:langUsage/tei:language/@ident"/>
+<sch:assert test="every $i in tokenize(., '\s') satisfies $i = $langIdents"> Attribute value(s) must match one of the following
+ language codes in the <profileDesc>:
+<sch:value-of select="string-join($langIdents, ' | ')"/>.
+</sch:assert>
+</sch:rule>
Datatype
1–∞ occurrences ofteidata.nameseparated by whitespace
<handNote scope="sole">
+ <p>Written in insular
+ phase II half-uncial with interlinear Old English gloss in an Anglo-Saxon pointed
+ minuscule.</p>
+</handNote>
<head> (heading) contains any type of heading, for example the
- title of a section, or the heading of a list, glossary,
- manuscript description, etc. [4.2.1. Headings and Trailers]
The <head>
- element is used for headings at all levels; software which
- treats (e.g.) chapter headings, section headings, and list
- titles differently must determine the proper processing of a
- <head> element based on
- its structural position. A <head>
- occurring as the first element of a list is the title of
- that list; one occurring as the first element of a <div1> is the title of that
- chapter or section.
-
-
-
Example
-
The most common use for the <head> element is to mark the headings of
- sections. In older writings, the headings or incipits may be rather longer than usual in modern
- works. If a section has an explicit ending as well as a heading,
- it should be marked as a <trailer>, as in this example:
<div1 n="I" type="book"><head>In the name of Christ here begins
- the first book of the ecclesiastical history of Georgius
- Florentinus, known as Gregory, Bishop of Tours.</head><div2 type="section"><head>In the name of Christ here begins
- Book I of the history.</head><p>Proposing as I do ...</p><p>From the Passion of our
- Lord until the death of Saint Martin four hundred and twelve
- years passed.</p>
- <trailer>Here ends
- the first Book, which covers five thousand, five hundred and
- ninety-six years from the beginning of the world down
- to the death of Saint Martin.</trailer></div2>
- </div1>
-
-
-
Example
-
When headings are not inline with the
- running text (see e.g. the heading "Secunda conclusio") they might however be
- encoded as if. The actual placement in the source document can
- be captured with the place
- attribute.
The <head> element is also used
- to mark headings of other units, such as lists:
With
- a few exceptions, connectives are equally useful in all
- kinds of discourse: description, narration, exposition,
- argument. <list rend="bulleted">
- <head>Connectives</head><item>above</item><item>accordingly</item><item>across from</item><item>adjacent to</item><item>again</item><item>
- <!-- ... --></item>
- </list>
-
-
-
Content
- model
-
+}
2.1.86. <head>
<head> (heading) contains any type of heading, for example the title of a section, or the heading of a list, glossary, manuscript description, etc. [4.2.1. Headings and Trailers]
The <head> element is used for headings at all levels; software which treats (e.g.) chapter headings, section headings, and list titles differently must determine the proper processing of a <head> element based on its structural position. A <head> occurring as the first element of a list is the title of that list; one occurring as the first element of a <div1> is the title of that chapter or section.
Example
The most common use for the <head> element is to mark the headings of sections. In older writings, the headings or incipits may be rather longer than usual in modern works. If a section has an explicit ending as well as a heading, it should be marked as a <trailer>, as in this example:
<div1 n="I" type="book">
+ <head>In the name of Christ here begins the first book of the ecclesiastical history of
+ Georgius Florentinus, known as Gregory, Bishop of Tours.</head>
+ <div2 type="section">
+ <head>In the name of Christ here begins Book I of the history.</head>
+ <p>Proposing as I do ...</p>
+ <p>From the Passion of our Lord until the death of Saint Martin four hundred and twelve
+ years passed.</p>
+ <trailer>Here ends the first Book, which covers five thousand, five hundred and ninety-six
+ years from the beginning of the world down to the death of Saint Martin.</trailer>
+ </div2>
+</div1>
Example
When headings are not inline with the running text (see e.g. the heading "Secunda conclusio") they might however be encoded as if. The actual placement in the source document can be captured with the place attribute.
<p>Ownership stamp (xvii cent.) on i recto
- with the arms <heraldry>A
- bull passant within a bordure bezanty, in chief a
- crescent for difference</heraldry> [Cole], crest, and the legend
- <q>Cole Deum</q>.</p>
-
-
-
Content
- model
-
+}
2.1.88. <heraldry>
<heraldry> contains a heraldic formula or phrase, typically found as part of a blazon, coat of arms, etc. [10.3.8. Heraldry]
<p>Ownership stamp (xvii cent.) on i recto with the arms
+<heraldry>A bull passant within a bordure bezanty,
+ in chief a crescent for difference</heraldry> [Cole],
+ crest, and the legend <q>Cole Deum</q>.</p>
<hi rend="gothic">And
- this Indenture further witnesseth</hi> that the said <hi rend="italic">Walter Shandy</hi>, merchant, in consideration of the
- said intended marriage ...
<hi rend="gothic">And this Indenture further witnesseth</hi>
+ that the said <hi rend="italic">Walter Shandy</hi>, merchant,
+ in consideration of the said intended marriage ...
<history><origin><p>Written in Durham during the mid
- twelfth century.</p>
- </origin><provenance><p>Recorded in two medieval
- catalogues of the books belonging to Durham Priory,
- made in 1391 and 1405.</p></provenance><provenance><p>Given to W. Olleyf by William
- Ebchester, Prior (1446-56) and later belonged to Henry
- Dalton, Prior of Holy Island (Lindisfarne) according to
- inscriptions on ff. 4v and 5.</p></provenance><acquisition><p>Presented to Trinity College in 1738 by
- Thomas Gale and his son Roger.</p></acquisition>
- </history>
-
-
-
Content
- model
-
+
Schema Declaration
+element hi { attribute rend { "italic" }, sic*, text }
2.1.90. <history>
<history> groups elements describing the full history of a manuscript, manuscript part, or other object. [10.8. History]
<history>
+ <origin>
+ <p>Written in Durham during the mid twelfth
+ century.</p>
+ </origin>
+ <provenance>
+ <p>Recorded in two medieval
+ catalogues of the books belonging to Durham Priory, made in 1391 and
+ 1405.</p>
+ </provenance>
+ <provenance>
+ <p>Given to W. Olleyf by William Ebchester, Prior (1446-56)
+ and later belonged to Henry Dalton, Prior of Holy Island (Lindisfarne)
+ according to inscriptions on ff. 4v and 5.</p>
+ </provenance>
+ <acquisition>
+ <p>Presented to Trinity College in 1738 by
+ Thomas Gale and his son Roger.</p>
+ </acquisition>
+</history>
International Standard Book
- Number: a 13- or (if assigned prior to 2007)
- 10-digit identifying number assigned by the
- publishing industry to a published book or similar
- item, registered with the International ISBN Agency.
-
ISSN
-
International Standard Serial
- Number: an eight-digit number to uniquely identify
- a serial publication.
-
DOI
-
Digital Object Identifier: a
- unique string of letters and numbers assigned to
- an electronic document.
-
URI
-
Uniform Resource Identifier: a
- string of characters to uniquely identify a
- resource which usually contains indication of the
- means of accessing that resource, the name of its
- host, and its filepath.
-
VIAF
-
A data number in the Virtual
- Internet Authority File assigned to link different
- names in catalogs around the world for the same
- entity.
-
ESTC
-
English Short-Title Catalogue
- number: an identifying number assigned to a
- document in English printed in the British Isles
- or North America before 1801.
-
OCLC
-
OCLC control number (record
- number) for the union catalog record in WorldCat,
- a union catalog for member libraries in the Online
- Computer Library Center global
- cooperative.
<idno> should be used for
- labels which identify an object or concept in a formal
- cataloguing system such as a database or an RDF store, or in
- a distributed system such as the World Wide Web. Some
- suggested values for type on <idno> are ISBN,
- ISSN, DOI, and URI.
In the
- last case, the identifier includes a non-Unicode character which
- is defined elsewhere by means of a <glyph> or
- <char> element referenced here
- as #sym.
-
-
-
Schematron
-
- <sch:rule context="//tei:publicationStmt/tei:idno[@type='URI']/text()">
- <sch:let name="fileNo" value="replace(document-uri(/),
- '.*?(\d{1,5}).xml', '$1')"/> <sch:let name="docURIno"
- value="replace(., '.+?(\d+).+', '$1')"/>
- <sch:let name="msDescIdnoNo"
- value="replace(./following::tei:msDesc/tei:msIdentifier/tei:idno[@type='URI']/text(),
- '.+?(\d+)', '$1')"/>
- <sch:let name="id" value="@xml:id"/>
- <sch:assert test="$fileNo = $docURIno"> The number
- portion of the <idno> element must be the same as the
- URI number in the file name:
- <sch:value-of select="$fileNo"/> </sch:assert>
- <sch:assert test="$docURIno = $msDescIdnoNo"> The
- number portion of this <idno> element must match the
- number portion of the <idno> in
- <publicationStmt>:
- <sch:value-of select="$docURIno"/> </sch:assert>
- <sch:report test="preceding-sibling::element()[@xml:id =
- $id]">This @xml:id is already in use.</sch:report>
- </sch:rule>
International Standard Book Number: a 13- or (if assigned prior to 2007) 10-digit identifying number assigned by the publishing industry to a published book or similar item, registered with the International ISBN Agency.
ISSN
International Standard Serial Number: an eight-digit number to uniquely identify a serial publication.
DOI
Digital Object Identifier: a unique string of letters and numbers assigned to an electronic document.
URI
Uniform Resource Identifier: a string of characters to uniquely identify a resource which usually contains indication of the means of accessing that resource, the name of its host, and its filepath.
VIAF
A data number in the Virtual Internet Authority File assigned to link different names in catalogs around the world for the same entity.
ESTC
English Short-Title Catalogue number: an identifying number assigned to a document in English printed in the British Isles or North America before 1801.
OCLC
OCLC control number (record number) for the union catalog record in WorldCat, a union catalog for member libraries in the Online Computer Library Center global cooperative.
<idno> should be used for labels which identify an object or concept in a formal cataloguing system such as a database or an RDF store, or in a distributed system such as the World Wide Web. Some suggested values for type on <idno> are ISBN, ISSN, DOI, and URI.
In the last case, the identifier includes a non-Unicode character which is defined elsewhere by means of a <glyph> or <char> element referenced here as #sym.
Schematron
+<sch:rule context="//tei:publicationStmt/tei:idno[@type='URI']/text()">
+<sch:let name="fileNo"
+ value="replace(document-uri(/), '.*?(\d{1,5}).xml', '$1')"/>
+<sch:let name="docURIno"
+ value="replace(., '.+?(\d+).+', '$1')"/>
+<sch:let name="msDescIdnoNo"
+ value="replace(./following::tei:msDesc/tei:msIdentifier/tei:idno[@type='URI']/text(),
+ '.+?(\d+)', '$1')"/>
+<sch:let name="id" value="@xml:id"/>
+<sch:assert test="$fileNo = $docURIno"> The number portion of
+ the <idno> element must be the same as the URI number
+ in the file name: <sch:value-of select="$fileNo"/>
+</sch:assert>
+<sch:assert test="$docURIno = $msDescIdnoNo"> The number portion
+ of this <idno> element must match the number portion
+ of the <idno> in <publicationStmt>:
+<sch:value-of select="$docURIno"/>
+</sch:assert>
+<sch:report test="preceding-sibling::element()[@xml:id = $id]">This @xml:id is already in use.</sch:report>
+</sch:rule>
<incipit> contains the incipit of a manuscript or similar
- object item, that is the opening words of the text proper,
- exclusive of any rubric which
- might precede it, of sufficient length to identify the work
- uniquely; such incipits were, in former times, frequently
- used a means of reference to a work, in place of a
- title. [10.6.1. The msItem and msItemStruct Elements]
- <sch:rule context="//tei:incipit/@xml:lang">
- <sch:let name="langIdents"
- value="//tei:profileDesc/tei:langUsage/tei:language/@ident"/>
- <sch:assert test=". = $langIdents">
- Attribute value must match one of the following
- language codes in the <profileDesc>:
- <sch:value-of select="string-join($langIdents,
- ' | ')"/>. </sch:assert>
- </sch:rule>
<incipit>Pater noster qui es in celis</incipit>
- <incipit defective="true">tatem dedit hominibus
- alleluia.</incipit>
- <incipit type="biblical">Ghif ons huden onse
- dagelix broet</incipit>
- <incipit>O ongehoerde
- gewerdighe christi</incipit>
- <incipit type="lemma">Firmiter</incipit>
- <incipit>Ideo dicit
- firmiter quia ordo fidei nostre probari non potest</incipit>
-
-
-
Content
- model
-
+}
2.1.93. <incipit>
<incipit> contains the incipit of a manuscript or similar object item, that is the opening words of the text proper, exclusive of any rubric which might precede it, of sufficient length to identify the work uniquely; such incipits were, in former times, frequently used a means of reference to a work, in place of a title. [10.6.1. The msItem and msItemStruct Elements]
+<sch:rule context="//tei:incipit/@xml:lang">
+<sch:let name="langIdents"
+ value="//tei:profileDesc/tei:langUsage/tei:language/@ident"/>
+<sch:assert test=". = $langIdents"> Attribute value must
+ match one of the following language codes in the
+ <profileDesc>: <sch:value-of select="string-join($langIdents, ' | ')"/>.
+</sch:assert>
+</sch:rule>
<incipit>Pater noster qui es in celis</incipit>
+<incipit defective="true">tatem dedit hominibus alleluia.</incipit>
+<incipit type="biblical">Ghif ons huden onse dagelix broet</incipit>
+<incipit>O ongehoerde gewerdighe christi</incipit>
+<incipit type="lemma">Firmiter</incipit>
+<incipit>Ideo dicit firmiter quia ordo fidei nostre probari non potest</incipit>
<institution> (institution) contains the name of an
- organization such as a university or library, with which a
- manuscript or other object is identified, generally its
- holding institution. [10.4. The Manuscript Identifier]
<institution> contains the name of an organization such as a university or library, with which a manuscript or other object is identified, generally its holding institution. [10.4. The Manuscript Identifier]
<interpretation> (interpretation) describes the scope
- of any analytic or interpretive information added to the
- text in addition to the transcription. [2.3.3. The Editorial Practices Declaration]
<interpretation><p>The part of speech analysis applied
- throughout section 4 was added by hand and has not been
- checked</p>
- </interpretation>
-
-
-
Content
- model
-
+}
2.1.95. <interpretation>
<interpretation> describes the scope of any analytic or interpretive information added to the text in addition to the transcription. [2.3.3. The Editorial Practices Declaration]
May contain simple prose or a sequence
- of chunks.
Whatever string of characters is used to
- label a list item in the copy text may be used as the value
- of the global n attribute, but it
- is not required that numbering be recorded explicitly. In
- ordered lists, the n attribute on
- the <item> element is by
- definition synonymous with the use of the <label> element to record the enumerator of
- the list item. In glossary lists, however, the term being
- defined should be given with the <label> element, not n.
-
-
-
Example
-
<list rend="numbered">
- <head>Here begin the
- chapter headings of Book IV</head><item n="4.1">The
- death of Queen Clotild.</item><item n="4.2">How
- King Lothar wanted to appropriate one third of the Church
- revenues.</item>
- <item n="4.3">The wives and children of
- Lothar.</item><item n="4.4">The Counts of the Bretons.</item><item n="4.5">Saint Gall the Bishop.</item><item n="4.6">The priest Cato.</item><item> ...</item>
- </list>
Whatever string of characters is used to label a list item in the copy text may be used as the value of the global n attribute, but it is not required that numbering be recorded explicitly. In ordered lists, the n attribute on the <item> element is by definition synonymous with the use of the <label> element to record the enumerator of the list item. In glossary lists, however, the term being defined should be given with the <label> element, not n.
Example
<list rend="numbered">
+ <head>Here begin the chapter headings of Book IV</head>
+ <item n="4.1">The death of Queen Clotild.</item>
+ <item n="4.2">How King Lothar wanted to appropriate one third of the Church revenues.</item>
+ <item n="4.3">The wives and children of Lothar.</item>
+ <item n="4.4">The Counts of the Bretons.</item>
+ <item n="4.5">Saint Gall the Bishop.</item>
+ <item n="4.6">The priest Cato.</item>
+ <item> ...</item>
+</list>
identifies the
- controlled vocabulary within which the set of
- keywords concerned is defined, for example by a <taxonomy>
- element, or by some other resource.
Each individual keyword (including
- compound subject headings) should be supplied as a <term> element directly within the <keywords> element.
- An alternative usage, in which each <term>
- appears within an <item> inside a <list> is permitted for backwards
- compatibility, but is deprecated.
If no control list
- exists for the keywords used, then no value should be
- supplied for the scheme
- attribute.
identifies the controlled vocabulary within which the set of keywords concerned is defined, for example by a <taxonomy> element, or by some other resource.
Each individual keyword (including compound subject headings) should be supplied as a <term> element directly within the <keywords> element. An alternative usage, in which each <term> appears within a <item> inside a <list> is permitted for backwards compatibility, but is deprecated.
If no control list exists for the keywords used, then no value should be supplied for the scheme attribute.
<l met="x/x/x/x/x/" real="/xx/x/x/x/">Shall I compare thee to a
- summer's day?</l>
-
-
-
Schematron
-
- <s:report test="ancestor::tei:l[not(.//tei:note//tei:l[.
- = current()])]"> Abstract model violation: Lines may not
- contain lines or lg elements. </s:report>
-
-
-
Content
- model
-
+
Schema Declaration
+element keywords { attribute scheme { text }, list }
<l met="x/x/x/x/x/" real="/xx/x/x/x/">Shall I compare thee to a summer's day?</l>
Schematron
+<s:report test="ancestor::tei:l[not(.//tei:note//tei:l[. = current()])]"> Abstract model violation: Lines may not contain lines or lg elements.
+</s:report>
Labels are commonly used for the headwords
- in glossary lists; note the use of the global xml:lang attribute to set the default language of
- the glossary list to Middle English, and identify the glosses
- and headings as modern English or Latin:
Labels may also be used to record
- explicitly the numbers or letters which mark list items in
- ordered lists, as in this extract from Gibbon's Autobiography. In this usage the <label> element is synonymous with the n attribute on the <item>
- element:
I will add two facts, which have
- seldom occurred in the composition of six, or at least of
- five quartos. <list rend="runon" type="ordered">
- <label>(1)</label><item>My first rough
- manuscript, without any intermediate copy, has been sent to
- the press.</item><label>(2) </label><item>Not a sheet has been
- seen by any human eyes, excepting those of the author and
- the printer: the faults and the merits are exclusively my
- own.</item>
- </list>
-
-
-
Example
-
Labels may also be used for other
- structured list items, as in this extract from the journal of
- Edward Gibbon:
<list type="gloss">
- <label>March
- 1757.</label><item>I wrote some critical
- observations upon Plautus.</item><label>March 8th.</label><item>I wrote a long dissertation upon
- some lines of Virgil.</item><label>June.</label><item>I saw Mademoiselle Curchod — <quote xml:lang="la">Omnia vincit amor, et nos
- cedamus amori.</quote></item><label>August.</label><item>I went to Crassy, and staid two
- days.</item>
- </list>
Note that
- the <label> might also appear within the <item> rather than as its sibling. Though
- syntactically valid, this usage is not recommended TEI
- practice.
-
-
-
Example
-
Labels may also be used to represent a
- label or heading attached to a paragraph or sequence of
- paragraphs not treated as a structural division, or to a group
- of verse lines. Note that, in this case, the <label>
- element appears within the <p> or <lg> element, rather than as a preceding sibling
- of it.
<p>[...] <lb/>& n’entrer en mauuais
- & mal-heu- <lb/>ré meſnage. Or des que le conſente- <lb/>ment des parties y eſt
- le mariage eſt <lb/>
- arreſté, quoy que de faict il ne ſoit <label place="margin">Puiſſance maritale
- entre les Romains.</label><lb/> conſommé. Depuis la conſomma- <lb/>tion du mariage la
- femme eſt ſoubs <lb/> la
- puiſſance du mary, s’il n’eſt eſcla- <lb/>ue ou enfant de famille : car en ce
- <lb/> cas, la femme,
- qui a eſpouſé vn en- <lb/>fant de famille, eſt ſous la
- puiſſance [...]</p>
In this example the text of the label
- appears in the right hand margin of the original source, next to
- the paragraph it describes, but approximately in the middle of
- it. If so desired the type attribute
- may be used to distinguish different categories of label.
-
-
-
Content
- model
-
+}
2.1.99. <label>
<label> contains any label or heading used to identify part of a text, typically but not exclusively in a list or glossary. [3.7. Lists]
Labels are commonly used for the headwords in glossary lists; note the use of the global xml:lang attribute to set the default language of the glossary list to Middle English, and identify the glosses and headings as modern English or Latin:
Labels may also be used to record explicitly the numbers or letters which mark list items in ordered lists, as in this extract from Gibbon's Autobiography. In this usage the <label> element is synonymous with the n attribute on the <item> element:
I will add two facts, which have seldom occurred
+ in the composition of six, or at least of five quartos. <list rend="runon" type="ordered">
+ <label>(1)</label>
+ <item>My first rough manuscript, without any intermediate copy, has been sent to the press.</item>
+ <label>(2) </label>
+ <item>Not a sheet has been seen by any human eyes, excepting those of the author and the
+ printer: the faults and the merits are exclusively my own.</item>
+</list>
Example
Labels may also be used for other structured list items, as in this extract from the journal of Edward Gibbon:
<list type="gloss">
+ <label>March 1757.</label>
+ <item>I wrote some critical observations upon Plautus.</item>
+ <label>March 8th.</label>
+ <item>I wrote a long dissertation upon some lines of Virgil.</item>
+ <label>June.</label>
+ <item>I saw Mademoiselle Curchod — <quote xml:lang="la">Omnia vincit amor, et nos cedamus
+ amori.</quote>
+ </item>
+ <label>August.</label>
+ <item>I went to Crassy, and staid two days.</item>
+</list>
Note that the <label> might also appear within the <item> rather than as its sibling. Though syntactically valid, this usage is not recommended TEI practice.
Example
Labels may also be used to represent a label or heading attached to a paragraph or sequence of paragraphs not treated as a structural division, or to a group of verse lines. Note that, in this case, the <label> element appears within the <p> or <lg> element, rather than as a preceding sibling of it.
<p>[...]
+<lb/>& n’entrer en mauuais & mal-heu-
+<lb/>ré meſnage. Or des que le conſente-
+<lb/>ment des parties y eſt le mariage eſt
+<lb/> arreſté, quoy que de faict il ne ſoit
+<label place="margin">Puiſſance maritale
+ entre les Romains.</label>
+ <lb/> conſommé. Depuis la conſomma-
+<lb/>tion du mariage la femme eſt ſoubs
+<lb/> la puiſſance du mary, s’il n’eſt eſcla-
+<lb/>ue ou enfant de famille : car en ce
+<lb/> cas, la femme, qui a eſpouſé vn en-
+<lb/>fant de famille, eſt ſous la puiſſance
+ [...]</p>
In this example the text of the label appears in the right hand margin of the original source, next to the paragraph it describes, but approximately in the middle of it. If so desired the type attribute may be used to distinguish different categories of label.
(identifier) Supplies a
- language code constructed as defined in BCP
- 47 which is used to identify the language
- documented by this element, and which is
- referenced by the global xml:lang attribute.
-
-
-
Status
-
Required
-
-
-
Schematron
-
- <sch:rule context="//tei:language/@ident">
- <sch:let name="langIdents"
- value="//tei:profileDesc/tei:langUsage/tei:language/@ident"/>
- <sch:assert test=". = $langIdents">
- Attribute value must match one of the following
- language codes in the <profileDesc>:
- <sch:value-of select="string-join($langIdents,
- ' | ')"/>. </sch:assert>
- </sch:rule>
(identifier) Supplies a language code constructed as defined in BCP 47 which is used to identify the language documented by this element, and which is referenced by the global xml:lang attribute.
Status
Required
Schematron
+<sch:rule context="//tei:language/@ident">
+<sch:let name="langIdents"
+ value="//tei:profileDesc/tei:langUsage/tei:language/@ident"/>
+<sch:assert test=". = $langIdents"> Attribute value must
+ match one of the following language codes in the
+ <profileDesc>: <sch:value-of select="string-join($langIdents, ' | ')"/>.
+</sch:assert>
+</sch:rule>
element language
{
- attribute ident { text },
+ attribute ident { text }
+ >>
+ tei:constraintSpec
+ [
+ ident = "ident-on-language"
+ scheme = "schematron"
+ " "
+ " "
+ " Attribute value must match one of the following language codes in the <profileDesc>: "
+ "."
+ ],
attribute usage { text }?,
sic*,
text
-}⚓
-
-
-
-
-
-
2.1.102. <layout>
-
-
-
-
<layout> (layout) describes how text is laid out on the page or
- surface of the object, including information about any
- ruling, pricking, or other evidence of page-preparation
- techniques. [10.7.2. Writing, Decoration, and Other Notations]
(columns) specifies the
- number of columns per page
-
-
-
Status
-
Optional
-
-
-
Datatype
-
1–2 occurrences ofteidata.count
- separated by
- whitespace
-
-
-
Note
-
If a single number is
- given, all pages referenced have this number of
- columns. If two numbers are given, the number of
- columns per page varies between the values
- supplied. Where columns
- is omitted the number is assumed to be 1.
Columns may be
- independent of page orientation or reading
- direction, and a single textual stream may have one or more
- columns.
-
-
-
-
-
-
writtenLines
-
(written
- lines) specifies the number
- of written lines per column
-
-
-
Status
-
Optional
-
-
-
Datatype
-
1–2 occurrences ofteidata.count
- separated by
- whitespace
-
-
-
Note
-
If a single number is
- given, all columns have this number of written
- lines. If two numbers are given, the number of
- written lines per column varies between the values
- supplied.
<layout columns="1" ruledLines="25
- 32">Most pages have between 25 and
- 32 long lines ruled in lead.</layout>
-
-
-
Example
-
<layout columns="2" ruledLines="42"><p>2 columns of 42 lines ruled in ink,
- with central rule between the columns.</p>
- </layout>
-
-
-
Example
-
<layout columns="1
- 2" writtenLines="40 50"><p>Some pages have 2 columns, with central
- rule between the columns; each column with between 40 and
- 50 lines of writing.</p>
- </layout>
-
-
-
Example
-
<layout streams="3" columns="3"/>
- <!-- Further down in document body
- -->
- <div type="page"><ab><pb/> 一二三<cb type="top-stream"/> 一二三<cb type="mid-stream"/> 一二三<cb type="bottom-stream"/>
- <!-- cb here for demo purposes
- --></ab>
- </div>
-
-
-
Content
- model
-
+}
2.1.102. <layout>
<layout> describes how text is laid out on the page or surface of the object, including information about any ruling, pricking, or other evidence of page-preparation techniques. [10.7.2. Writing, Decoration, and Other Notations]
1–2 occurrences ofteidata.countseparated by whitespace
Note
If a single number is given, all pages referenced have this number of columns. If two numbers are given, the number of columns per page varies between the values supplied. Where columns is omitted the number is assumed to be 1.
Columns may be independent of page orientation or reading direction, and a single textual stream may have one or more columns.
writtenLines
specifies the number of written lines per column
Status
Optional
Datatype
1–2 occurrences ofteidata.countseparated by whitespace
Note
If a single number is given, all columns have this number of written lines. If two numbers are given, the number of written lines per column varies between the values supplied.
<layout columns="1" ruledLines="25 32">Most pages have between 25 and 32 long lines ruled in lead.</layout>
Example
<layout columns="2" ruledLines="42">
+ <p>2 columns of 42 lines ruled in ink, with central rule
+ between the columns.</p>
+</layout>
Example
<layout columns="1 2" writtenLines="40 50">
+ <p>Some pages have 2 columns, with central rule
+ between the columns; each column with between 40 and 50 lines of writing.</p>
+</layout>
Example
<layout streams="3" columns="3"/>
+<!-- Further down in document body -->
+<div type="page">
+ <ab>
+ <pb/>
+ 一二三<cb type="top-stream"/>
+ 一二三<cb type="mid-stream"/>
+ 一二三<cb type="bottom-stream"/>
+<!-- cb here for demo purposes -->
+ </ab>
+</div>
<layoutDesc><p>Most pages have between 25 and 32 long
- lines ruled in lead.</p>
- </layoutDesc>
-
-
-
Example
-
<layoutDesc><layout columns="2" ruledLines="42"><p><locus from="f12r" to="f15v"/> 2 columns of 42 lines
- pricked and ruled in ink, with central rule between the
- columns.</p></layout><layout columns="3"><p><locus from="f16"/>Prickings for three columns
- are visible.</p></layout>
- </layoutDesc>
<layoutDesc>
+ <p>Most pages have between 25 and 32 long lines ruled in lead.</p>
+</layoutDesc>
Example
<layoutDesc>
+ <layout columns="2" ruledLines="42">
+ <p>
+ <locus from="f12r" to="f15v"/>
+ 2 columns of 42 lines pricked and ruled in ink, with
+ central rule between the columns.</p>
+ </layout>
+ <layout columns="3">
+ <p>
+ <locus from="f16"/>Prickings for three columns are visible.</p>
+ </layout>
+</layoutDesc>
By convention, <lb>
- elements should appear at the point in the text where a new
- line starts. The n attribute, if
- used, indicates the number or other value associated with
- the text between this point and the next <lb>
- element, typically the sequence number of the line within
- the page, or other appropriate unit. This element is
- intended to be used for marking actual line breaks on a
- manuscript or printed page, at the point where they occur;
- it should not be used to tag structural units such as lines
- of verse (for which the <l> element is available)
- except in circumstances where structural units cannot
- otherwise be marked.
The type
- attribute may be used to characterize the line break in any
- respect. The more specialized attributes break, ed, or edRef should be preferred when the
- intent is to indicate whether or not the line break is
- word-breaking, or to note the source from which it
- derives.
-
-
-
Example
-
This example shows typographical line
- breaks within metrical lines, where they occur at different
- places in different editions:
<l>Of Mans First Disobedience,<lb ed="1674"/> and<lb ed="1667"/> the
- Fruit</l>
- <l>Of that Forbidden
- Tree, whose<lb ed="1667 1674"/>
- mortal tast</l>
- <l>Brought Death into the
- World,<lb ed="1667"/> and
- all<lb ed="1674"/> our woe,</l>
-
-
-
Example
-
This example encodes typographical line
- breaks as a means of preserving the visual appearance of a title
- page. The break attribute is used to
- show that the line break does not (as elsewhere) mark the start
- of a new word.
<titlePart><lb/>With Additions, ne-<lb break="no"/>ver before Printed. </titlePart>
By convention, <lb> elements should appear at the point in the text where a new line starts. The n attribute, if used, indicates the number or other value associated with the text between this point and the next <lb> element, typically the sequence number of the line within the page, or other appropriate unit. This element is intended to be used for marking actual line breaks on a manuscript or printed page, at the point where they occur; it should not be used to tag structural units such as lines of verse (for which the <l> element is available) except in circumstances where structural units cannot otherwise be marked.
The type attribute may be used to characterize the line break in any respect. The more specialized attributes break, ed, or edRef should be preferred when the intent is to indicate whether or not the line break is word-breaking, or to note the source from which it derives.
Example
This example shows typographical line breaks within metrical lines, where they occur at different places in different editions:
<l>Of Mans First Disobedience,<lb ed="1674"/> and<lb ed="1667"/> the Fruit</l>
+<l>Of that Forbidden Tree, whose<lb ed="1667 1674"/> mortal tast</l>
+<l>Brought Death into the World,<lb ed="1667"/> and all<lb ed="1674"/> our woe,</l>
Example
This example encodes typographical line breaks as a means of preserving the visual appearance of a title page. The break attribute is used to show that the line break does not (as elsewhere) mark the start of a new word.
<titlePart>
+ <lb/>With Additions, ne-<lb break="no"/>ver before Printed.
+</titlePart>
contains verse lines or nested line
- groups only, possibly prefixed by a heading.
-
-
-
Example
-
<lg type="free">
- <l>Let me be my own
- fool</l><l>of my own making, the
- sum of it</l>
- </lg>
- <lg type="free"><l>is equivocal.</l><l>One says of the drunken farmer:</l>
- </lg>
- <lg type="free"><l>leave him lay off it. And this is</l><l>the explanation.</l>
- </lg>
-
-
-
Schematron
-
- <sch:assert test="count(descendant::tei:lg|descendant::tei:l|descendant::tei:gap)
- > 0">An lg element must contain at least one child l,
- lg, or gap element.</sch:assert>
-
-
-
Schematron
-
- <s:report test="ancestor::tei:l[not(.//tei:note//tei:lg[.
- = current()])]"> Abstract model violation: Lines may not
- contain line groups. </s:report>
contains verse lines or nested line groups only, possibly prefixed by a heading.
Example
<lg type="free">
+ <l>Let me be my own fool</l>
+ <l>of my own making, the sum of it</l>
+</lg>
+<lg type="free">
+ <l>is equivocal.</l>
+ <l>One says of the drunken farmer:</l>
+</lg>
+<lg type="free">
+ <l>leave him lay off it. And this is</l>
+ <l>the explanation.</l>
+</lg>
Schematron
+<sch:assert test="count(descendant::tei:lg|descendant::tei:l|descendant::tei:gap) >
+ 0">An lg element
+ must contain at least one child l, lg, or gap element.</sch:assert>
Schematron
+<s:report test="ancestor::tei:l[not(.//tei:note//tei:lg[. = current()])]"> Abstract model violation: Lines may not contain line groups.
+</s:report>
A <licence> element should be supplied for each
- licence agreement applicable to the text in question. The
- target attribute may be used to
- reference a full version of the licence. The when, notBefore, notAfter,
- from or to attributes may be used in combination to
- indicate the date or dates of applicability of the
- licence.
A <licence> element should be supplied for each licence agreement applicable to the text in question. The target attribute may be used to reference a full version of the licence. The when, notBefore, notAfter, from or to attributes may be used in combination to indicate the date or dates of applicability of the licence.
May contain an optional heading
- followed by a series of items, or a series of label and item
- pairs, the latter being optionally preceded by one or two
- specialized headings.
-
-
-
Example
-
<list rend="numbered">
- <item>a butcher</item><item>a baker</item><item>a candlestick maker,
- with <list rend="bulleted"><item>rings on his
- fingers</item>
- <item>bells on his
- toes</item></list></item>
- </list>
-
-
-
Example
-
<list type="syllogism" rend="bulleted">
- <item>All Cretans
- are liars.</item><item>Epimenides is a
- Cretan.</item><item>ERGO Epimenides is a
- liar.</item>
- </list>
-
-
-
Example
-
<list type="litany" rend="simple">
- <item>God save us
- from drought.</item>
- <item>God save us
- from pestilence.</item>
- <item>God save us
- from wickedness in high places.</item><item>Praise be to God.</item>
- </list>
-
-
-
Example
-
The following example treats the short
- numbered clauses of Anglo-Saxon legal codes as lists of items.
- The text is from an ordinance of King Athelstan (924–939):
<div1 type="section"><head>Athelstan's Ordinance</head><list rend="numbered"><item n="1">Concerning thieves. First, that no
- thief is to be spared who is caught with the stolen
- goods, [if he is] over twelve years and [if the value of the
- goods is] over eightpence. <list rend="numbered">
- <item n="1.1">And if
- anyone does spare one, he is to pay for the thief with his
- wergild — and the thief is to be no nearer a
- settlement on that account — or to clear himself by
- an oath of that amount.</item><item n="1.2">If,
- however, he [the thief] wishes to defend himself or to
- escape, he is not to be spared [whether younger or
- older than twelve].</item><item n="1.3">If a
- thief is put into prison, he is to be in prison 40 days, and
- he may then be redeemed with 120 shillings; and the
- kindred are to stand surety for him that he will
- desist for ever.</item>
- <item n="1.4">And if
- he steals after that, they are to pay for him with his
- wergild, or to bring him back there.</item><item n="1.5">And if he steals after that, they
- are to pay for him with his wergild, whether to the
- king or to him to whom it rightly belongs; and everyone of
- those who supported him is to pay 120 shillings to
- the king as a fine.</item></list></item><item n="2">Concerning lordless men. And we
- pronounced about these lordless men, from whom no
- justice can be obtained, that one should order their kindred
- to fetch back such a person to justice and to find him
- a lord in public meeting. <list rend="numbered">
- <item n="2.1">And if
- they then will not, or cannot, produce him on that appointed
- day, he is then to be a fugitive afterwards, and he
- who encounters him is to strike him down as a
- thief.</item>
- <item n="2.2">And he
- who harbours him after that, is to pay for him with his
- wergild or to clear himself by an oath of that
- amount.</item>
- </list></item><item n="3">Concerning the refusal of justice.
- The lord who refuses justice and upholds his guilty
- man, so that the king is appealed to, is to repay the value
- of the goods and 120 shillings to the king; and he who
- appeals to the king before he demands justice as often
- as he ought, is to pay the same fine as the other would have
- done, if he had refused him justice. <list rend="numbered"><item n="3.1">And the lord who is an accessory
- to a theft by his slave, and it becomes known about
- him, is to forfeit the slave and be liable to his wergild on
- the first occasionp if he does it more often, he is
- to be liable to pay all that he owns.</item><item n="3.2">And
- likewise any of the king's treasurers or of our reeves, who
- has been an accessory of thieves who have committed
- theft, is to liable to the same.</item></list></item><item n="4">Concerning treachery to a lord. And we
- have pronounced concerning treachery to a lord, that he
- [who is accused] is to forfeit his life if he cannot deny it
- or is afterwards convicted at the three-fold
- ordeal.</item></list>
- </div1>
Note that
- nested lists have been used so the tagging mirrors the structure
- indicated by the two-level numbering of the clauses. The clauses
- could have been treated as a one-level list with irregular
- numbering, if desired.
-
-
-
Example
-
<p>These decrees, most blessed Pope
- Hadrian, we propounded in the public council ... and they
- confirmed them in our hand in your stead with the sign of
- the Holy Cross, and afterwards inscribed with a careful pen
- on the paper of this page, affixing thus the sign of the
- Holy Cross. <list rend="simple">
- <item>I, Eanbald,
- by the grace of God archbishop of the holy church of York,
- have subscribed to the pious and catholic validity of
- this document with the sign of the Holy Cross.</item><item>I, Ælfwold, king of
- the people across the Humber, consenting have subscribed
- with the sign of the Holy Cross.</item><item>I, Tilberht, prelate of the church
- of Hexham, rejoicing have subscribed with the sign of
- the Holy Cross.</item>
- <item>I, Higbald,
- bishop of the church of Lindisfarne, obeying have subscribed
- with the sign of the Holy Cross.</item><item>I, Ethelbert, bishop of Candida
- Casa, suppliant, have subscribed with thef sign of the
- Holy Cross.</item>
- <item>I, Ealdwulf,
- bishop of the church of Mayo, have subscribed with devout
- will.</item><item>I, Æthelwine, bishop,
- have subscribed through delegates.</item><item>I, Sicga, patrician, have subscribed
- with serene mind with the sign of the Holy Cross.</item></list>
- </p>
-
-
-
Schematron
-
- <sch:rule context="tei:list[@type='gloss']">
- <sch:assert test="tei:label">The content of a "gloss"
- list should include a sequence of one or more pairs of a
- label element followed by an item element</sch:assert>
- </sch:rule>
May contain an optional heading followed by a series of items, or a series of label and item pairs, the latter being optionally preceded by one or two specialized headings.
Example
<list rend="numbered">
+ <item>a butcher</item>
+ <item>a baker</item>
+ <item>a candlestick maker, with
+ <list rend="bulleted">
+ <item>rings on his fingers</item>
+ <item>bells on his toes</item>
+ </list>
+ </item>
+</list>
Example
<list type="syllogism" rend="bulleted">
+ <item>All Cretans are liars.</item>
+ <item>Epimenides is a Cretan.</item>
+ <item>ERGO Epimenides is a liar.</item>
+</list>
Example
<list type="litany" rend="simple">
+ <item>God save us from drought.</item>
+ <item>God save us from pestilence.</item>
+ <item>God save us from wickedness in high places.</item>
+ <item>Praise be to God.</item>
+</list>
Example
The following example treats the short numbered clauses of Anglo-Saxon legal codes as lists of items. The text is from an ordinance of King Athelstan (924–939):
<div1 type="section">
+ <head>Athelstan's Ordinance</head>
+ <list rend="numbered">
+ <item n="1">Concerning thieves. First, that no thief is to be spared who is caught with
+ the stolen goods, [if he is] over twelve years and [if the value of the goods is] over
+ eightpence.
+ <list rend="numbered">
+ <item n="1.1">And if anyone does spare one, he is to pay for the thief with his
+ wergild — and the thief is to be no nearer a settlement on that account — or to
+ clear himself by an oath of that amount.</item>
+ <item n="1.2">If, however, he [the thief] wishes to defend himself or to escape, he is
+ not to be spared [whether younger or older than twelve].</item>
+ <item n="1.3">If a thief is put into prison, he is to be in prison 40 days, and he may
+ then be redeemed with 120 shillings; and the kindred are to stand surety for him
+ that he will desist for ever.</item>
+ <item n="1.4">And if he steals after that, they are to pay for him with his wergild,
+ or to bring him back there.</item>
+ <item n="1.5">And if he steals after that, they are to pay for him with his wergild,
+ whether to the king or to him to whom it rightly belongs; and everyone of those who
+ supported him is to pay 120 shillings to the king as a fine.</item>
+ </list>
+ </item>
+ <item n="2">Concerning lordless men. And we pronounced about these lordless men, from whom
+ no justice can be obtained, that one should order their kindred to fetch back such a
+ person to justice and to find him a lord in public meeting.
+ <list rend="numbered">
+ <item n="2.1">And if they then will not, or cannot, produce him on that appointed day,
+ he is then to be a fugitive afterwards, and he who encounters him is to strike him
+ down as a thief.</item>
+ <item n="2.2">And he who harbours him after that, is to pay for him with his wergild
+ or to clear himself by an oath of that amount.</item>
+ </list>
+ </item>
+ <item n="3">Concerning the refusal of justice. The lord who refuses justice and upholds
+ his guilty man, so that the king is appealed to, is to repay the value of the goods and
+ 120 shillings to the king; and he who appeals to the king before he demands justice as
+ often as he ought, is to pay the same fine as the other would have done, if he had
+ refused him justice.
+ <list rend="numbered">
+ <item n="3.1">And the lord who is an accessory to a theft by his slave, and it becomes
+ known about him, is to forfeit the slave and be liable to his wergild on the first
+ occasionp if he does it more often, he is to be liable to pay all that he owns.</item>
+ <item n="3.2">And likewise any of the king's treasurers or of our reeves, who has been
+ an accessory of thieves who have committed theft, is to liable to the same.</item>
+ </list>
+ </item>
+ <item n="4">Concerning treachery to a lord. And we have pronounced concerning treachery to
+ a lord, that he [who is accused] is to forfeit his life if he cannot deny it or is
+ afterwards convicted at the three-fold ordeal.</item>
+ </list>
+</div1>
Note that nested lists have been used so the tagging mirrors the structure indicated by the two-level numbering of the clauses. The clauses could have been treated as a one-level list with irregular numbering, if desired.
Example
<p>These decrees, most blessed Pope Hadrian, we propounded in the public council ... and they
+ confirmed them in our hand in your stead with the sign of the Holy Cross, and afterwards
+ inscribed with a careful pen on the paper of this page, affixing thus the sign of the Holy
+ Cross.
+<list rend="simple">
+ <item>I, Eanbald, by the grace of God archbishop of the holy church of York, have
+ subscribed to the pious and catholic validity of this document with the sign of the Holy
+ Cross.</item>
+ <item>I, Ælfwold, king of the people across the Humber, consenting have subscribed with
+ the sign of the Holy Cross.</item>
+ <item>I, Tilberht, prelate of the church of Hexham, rejoicing have subscribed with the
+ sign of the Holy Cross.</item>
+ <item>I, Higbald, bishop of the church of Lindisfarne, obeying have subscribed with the
+ sign of the Holy Cross.</item>
+ <item>I, Ethelbert, bishop of Candida Casa, suppliant, have subscribed with thef sign of
+ the Holy Cross.</item>
+ <item>I, Ealdwulf, bishop of the church of Mayo, have subscribed with devout will.</item>
+ <item>I, Æthelwine, bishop, have subscribed through delegates.</item>
+ <item>I, Sicga, patrician, have subscribed with serene mind with the sign of the Holy
+ Cross.</item>
+ </list>
+</p>
Schematron
+<sch:rule context="tei:list[@type='gloss']">
+<sch:assert test="tei:label">The content of a "gloss" list should include a sequence of one or more pairs of a label element followed by an item element</sch:assert>
+</sch:rule>
<listBibl><head>Works consulted</head><bibl>Blain, Clements and Grundy: Feminist
- Companion to Literature in English (Yale, 1990) </bibl><biblStruct><analytic><title>The Interesting
- story of the Children in the Wood</title></analytic><monogr><title>The Penny Histories</title><author>Victor E
- Neuberg</author>
- <imprint>
- <publisher>OUP</publisher><date>1968</date></imprint></monogr></biblStruct>
- </listBibl>
<listBibl>
+ <head>Works consulted</head>
+ <bibl>Blain, Clements and Grundy: Feminist Companion to
+ Literature in English (Yale, 1990)
+ </bibl>
+ <biblStruct>
+ <analytic>
+ <title>The Interesting story of the Children in the Wood</title>
+ </analytic>
+ <monogr>
+ <title>The Penny Histories</title>
+ <author>Victor E Neuberg</author>
+ <imprint>
+ <publisher>OUP</publisher>
+ <date>1968</date>
+ </imprint>
+ </monogr>
+ </biblStruct>
+</listBibl>
<listRelation> provides
- information about relationships identified amongst people,
- places, and organizations, either informally as prose or as
- formally expressed relation links. [13.3.2.3. Personal Relationships]
May contain a prose description
- organized as paragraphs, or a sequence of <relation>
- elements.
-
-
-
Example
-
<listPerson><person xml:id="pp1">
- <!-- data about person pp1
- --></person><person xml:id="pp2">
- <!-- data about person pp1
- --></person>
- <!-- more person (pp3, pp4)
- elements here --><listRelation type="personal"><relation name="parent" active="#pp1
- #pp2" passive="#pp3
- #pp4"/><relation name="spouse" mutual="#pp1
- #pp2"/></listRelation><listRelation type="social"><relation name="employer" active="#pp1" passive="#pp3
- #pp5 #pp6 #pp7"/></listRelation>
- </listPerson>
The
- persons with identifiers pp1 and pp2 are the parents of pp3 and
- pp4; they are also married to each other; pp1 is the employer of
- pp3, pp5, pp6, and pp7.
-
-
-
Example
-
<listPerson><person xml:id="en_pp1">
- <!-- data about person en_pp1
- --></person><person xml:id="en_pp2">
- <!-- data about person en_pp2
- --></person>
- <!-- more person (en_pp3, en_pp4)
- elements here -->
- </listPerson>
- <listPlace><place xml:id="en_pl1">
- <!-- data about place en_pl1
- --></place>
- <!-- more place (en_pl2, en_pl3)
- elements here -->
- </listPlace>
- <listRelation><relation name="residence" active="#en_pp1
- #en_pp2" passive="#en_pl1"/>
- </listRelation>
The
- persons with identifiers en_pp1 and en_pp2 live in en_pl1.
-
-
-
Example
-
<listRelation><p>All speakers are members of the Ceruli
- family, born in Naples.</p>
- </listRelation>
<listRelation> provides information about relationships identified amongst people, places, and organizations, either informally as prose or as formally expressed relation links. [13.3.2.3. Personal Relationships]
May contain a prose description organized as paragraphs, or a sequence of <relation> elements.
Example
<listPerson>
+ <person xml:id="pp1">
+<!-- data about person pp1 -->
+ </person>
+ <person xml:id="pp2">
+<!-- data about person pp1 -->
+ </person>
+<!-- more person (pp3, pp4) elements here -->
+ <listRelation type="personal">
+ <relation name="parent"
+ active="#pp1 #pp2" passive="#pp3 #pp4"/>
+ <relation name="spouse"
+ mutual="#pp1 #pp2"/>
+ </listRelation>
+ <listRelation type="social">
+ <relation name="employer" active="#pp1"
+ passive="#pp3 #pp5 #pp6 #pp7"/>
+ </listRelation>
+</listPerson>
The persons with identifiers pp1 and pp2 are the parents of pp3 and pp4; they are also married to each other; pp1 is the employer of pp3, pp5, pp6, and pp7.
Example
<listPerson>
+ <person xml:id="en_pp1">
+<!-- data about person en_pp1 -->
+ </person>
+ <person xml:id="en_pp2">
+<!-- data about person en_pp2 -->
+ </person>
+<!-- more person (en_pp3, en_pp4) elements here -->
+</listPerson>
+<listPlace>
+ <place xml:id="en_pl1">
+<!-- data about place en_pl1 -->
+ </place>
+<!-- more place (en_pl2, en_pl3) elements here -->
+</listPlace>
+<listRelation>
+ <relation name="residence"
+ active="#en_pp1 #en_pp2" passive="#en_pl1"/>
+</listRelation>
The persons with identifiers en_pp1 and en_pp2 live in en_pl1.
Example
<listRelation>
+ <p>All speakers are members of the Ceruli family, born in Naples.</p>
+</listRelation>
<locus> (locus) defines a location within a manuscript, manuscript
- part, or other object typically as a (possibly
- discontinuous) sequence of folio references. [10.3.5. References to Locations within a
- Manuscript]
The target
- attribute should only be used to point to elements that
- contain or indicate a transcription of the locus being
- described, as in the ‘Ben Jonson’
- example.
To associate a <locus> element with a page image or other
- comparable representation, the global facs attribute should be used, as shown in the
- ‘Birds Praise of Love’ example.
- The facs attribute may be used to
- indicate one or more image files, as in that example, or
- alternatively it may point to one or more appropriate XML
- elements, such as the <surface>, <zone>,
- <graphic>, or <binaryObject>
- elements.
When a single page is being cited, use the
- from and to attributes with an identical value. When no
- clear endpoint is provided, the from attribute may be used without to; for example a citation such as
- ‘p. 3ff’ might be encoded
- <locus from="3">p.
- 3ff</locus>.
-
-
-
Example
-
- <!-- within ms description
- --><msItem n="1"><locus target="#F1r
- #F1v #F2r" from="1r" to="2r">ff.
- 1r-2r</locus><author>Ben Jonson</author><title>Ode to himself</title><rubric rend="italics"> An Ode<lb/> to him selfe.</rubric><incipit>Com leaue the
- loathed stage</incipit>
- <explicit>And see
- his chariot triumph ore his wayne.</explicit><bibl><name>Beal</name>, <title>Index 1450-1625</title>, JnB 380</bibl>
- </msItem>
- <!-- within transcription ...
- -->
- <pb xml:id="F1r"/>
- <!-- ... -->
- <pb xml:id="F1v"/>
- <!-- ... -->
- <pb xml:id="F2r"/>
- <!-- ... -->
-
-
-
Example
-
The facs
- attribute is available globally when the transcr module is included in a
- schema. It may be used to point directly to an image file, as in
- the following example:
<locus> defines a location within a manuscript, manuscript part, or other object typically as a (possibly discontinuous) sequence of folio references. [10.3.5. References to Locations within a Manuscript]
The target attribute should only be used to point to elements that contain or indicate a transcription of the locus being described, as in the first example above. To associate a <locus> element with a page image or other comparable representation, the global facs attribute should be used instead, as shown in the second example. Use of the target attribute to indicate an image is strongly deprecated. The facs attribute may be used to indicate one or more image files, as above, or alternatively it may point to one or more appropriate XML elements, such as the <surface>, <zone> element, <graphic>, or <binaryObject> elements.
When a single page is being cited, use the from and to attributes with an identical value. When no clear endpoint is provided, the from attribute may be used without to; for example a citation such as ‘p. 3ff’ might be encoded <biblScope from="3">p. 3ff<biblScope>.
Example
+<!-- within ms description --><msItem n="1">
+ <locus target="#F1r #F1v #F2r" from="1r"
+ to="2r">ff. 1r-2r</locus>
+ <author>Ben Jonson</author>
+ <title>Ode to himself</title>
+ <rubric rend="italics"> An Ode<lb/> to him selfe.</rubric>
+ <incipit>Com leaue the loathed stage</incipit>
+ <explicit>And see his chariot triumph ore his wayne.</explicit>
+ <bibl>
+ <name>Beal</name>, <title>Index 1450-1625</title>, JnB 380</bibl>
+</msItem>
+<!-- within transcription ... -->
+<pb xml:id="F1r"/>
+<!-- ... -->
+<pb xml:id="F1v"/>
+<!-- ... -->
+<pb xml:id="F2r"/>
+<!-- ... -->
Example
The facs attribute is available globally when the transcr module is included in a schema. It may be used to point directly to an image file, as in the following example:
element locus
{
attribute from { text }?,
attribute to { text }?,
( sic* | text | model.gLike | model.hiLike )*
-}⚓
-
-
-
-
-
-
2.1.111. <locusGrp>
-
-
-
-
<locusGrp> (locus
- group) groups a number of locations which
- together form a distinct but discontinuous item within a
- manuscript, manuscript part, or other object. [10.3.5. References to Locations within a
- Manuscript]
(scheme) identifies the
- foliation scheme in terms of which all the
- locations contained by the group are specified by
- pointing to some <foliation> element defining it, or to
- some other equivalent resource.
identifies the foliation scheme in terms of which all the locations contained by the group are specified by pointing to some <foliation> element defining it, or to some other equivalent resource.
Suggested values for the type attribute include exact for exact equivalences, uppercase for uppercase equivalences,
- lowercase for lowercase
- equivalences, and simplified for
- simplified characters. The <g> elements contained by
- this element can point to either another <char> or <glyph>element or contain a character that is
- intended to be the target of this mapping.
Suggested values for the type attribute include exact for exact equivalences, uppercase for uppercase equivalences, lowercase for lowercase equivalences, and simplified for simplified characters. The <g> elements contained by this element can point to either another <char> or <glyph>element or contain a character that is intended to be the target of this mapping.
<material> (material)
- contains a word or phrase describing the
- material of which the object being described is
- composed. [10.3.2. Material and Object Type]
sewing at the head or tail of
- the codex spine to strengthen the binding, often
- decorative
-
slipcase
-
removable protective cover for
- a set of one or more codices
-
support
-
the surface for
- writing
-
tie
-
a ribbon or string used to
- bind or close a codex or rolled scroll
-
-
-
-
Note
-
The sample values
- here are for descriptive bibliography. Other sets
- of sample values might include armrests, legs,
- tabletop, pan, and back for furniture; or wall, floor,
- window, column, ceiling,
- roof, stairs, chimney
- for architecture.
-
-
-
-
-
-
target
-
identifies one
- or more elements to which the metamark
- applies.
-
-
-
Status
-
Optional
-
-
-
Datatype
-
1–∞ occurrences ofteidata.pointer
- separated by
- whitespace
-element material
-{
- attribute function { text }?,
- attribute target { list { + } }?,
- ( locus*, sic*, text )
-}⚓
-
-
-
-
-
-
2.1.114. <measure>
-
-
-
-
<measure> (measure)
- contains a word or phrase referring to some
- quantity of an object or commodity, usually comprising a
- number, a unit, and a commodity name. [3.6.3. Numbers and Measures]
This example references a definition of a
- measurement unit declared in the TEI header:
<measure type="weight"><num>2</num> pounds of flesh </measure>
- <measure type="currency">£10-11-6d</measure>
- <measure type="area" unitRef="#merk">2 <unit>merks</unit> of old extent</measure>
- <!-- In the TEI Header:
- -->
- <encodingDesc><unitDecl><unitDef xml:id="merk" type="area"><label>merk</label><placeName ref="#Scotland"/><desc>A merk was an area of
- land determined variably by its agricultural
- productivity.</desc>
- </unitDef></unitDecl>
- </encodingDesc>
<measure> contains a word or phrase referring to some quantity of an object or commodity, usually comprising a number, a unit, and a commodity name. [3.5.3. Numbers and Measures]
This example references a definition of a measurement unit declared in the TEI header:
<measure type="weight">
+ <num>2</num> pounds of flesh
+</measure>
+<measure type="currency">£10-11-6d</measure>
+<measure type="area" unitRef="#merk">2 <unit>merks</unit> of old extent</measure>
+<!-- In the TEI Header: -->
+<encodingDesc>
+ <unitDecl>
+ <unitDef xml:id="merk" type="area">
+ <label>merk</label>
+ <placeName ref="#Scotland"/>
+ <desc>A merk was an area of land determined variably by its agricultural productivity.</desc>
+ </unitDef>
+ </unitDecl>
+</encodingDesc>
<monogr> (monographic
- level) contains bibliographic
- elements describing an item (e.g. a book or journal)
- published as an independent item (i.e. as a separate
- physical object). [3.12.2.1. Analytic, Monographic, and Series
- Levels]
May contain specialized bibliographic
- elements, in a prescribed order.
The <monogr> element may
- only occur only within a <biblStruct>, where its use is mandatory for
- the description of a monographic-level bibliographic
- item.
-
-
-
Example
-
<biblStruct><analytic><author>Chesnutt, David</author><title>Historical Editions
- in the States</title>
- </analytic><monogr><title level="j">Computers and the Humanities</title><imprint><date when="1991-12">(December, 1991):</date></imprint><biblScope>25.6</biblScope><biblScope unit="page" from="377" to="380">377–380</biblScope></monogr>
- </biblStruct>
-
-
-
Example
-
<biblStruct type="book"><monogr><author><persName><forename>Leo Joachim</forename><surname>Frachtenberg</surname></persName></author><title type="main" level="m">Lower Umpqua Texts</title><imprint><pubPlace>New York</pubPlace><publisher>Columbia
- University Press</publisher><date>1914</date></imprint></monogr><series><title type="main" level="s">Columbia University Contributions
- to Anthropology</title><biblScope unit="volume">4</biblScope></series>
- </biblStruct>
-
-
-
Content
- model
-
+}
2.1.115. <monogr>
<monogr> (monographic level) contains bibliographic elements describing an item (e.g. a book or journal) published as an independent item (i.e. as a separate physical object). [3.11.2.1. Analytic, Monographic, and Series Levels]
May contain specialized bibliographic elements, in a prescribed order.
The <monogr> element may only occur only within a <biblStruct>, where its use is mandatory for the description of a monographic-level bibliographic item.
Example
<biblStruct>
+ <analytic>
+ <author>Chesnutt, David</author>
+ <title>Historical Editions in the States</title>
+ </analytic>
+ <monogr>
+ <title level="j">Computers and the Humanities</title>
+ <imprint>
+ <date when="1991-12">(December, 1991):</date>
+ </imprint>
+ <biblScope>25.6</biblScope>
+ <biblScope unit="page" from="377" to="380">377–380</biblScope>
+ </monogr>
+</biblStruct>
<msContents> (manuscript
- contents) describes the intellectual
- content of a manuscript, manuscript part, or other object
- either as a series of paragraphs or as a series of
- structured manuscript items. [10.6. Intellectual Content]
Unless it contains a simple prose
- description, this element should contain at least one of the
- elements <summary>, <msItem>, or <msItemStruct>.
- This constraint is not currently enforced by the
- schema.
-
-
-
Example
-
<msContents class="#sermons"><p>A collection of Lollard sermons</p>
- </msContents>
-
-
-
Example
-
<msContents><msItem n="1"><locus>fols. 5r-7v</locus><title>An ABC</title><bibl><title>IMEV</title><biblScope>239</biblScope></bibl></msItem><msItem n="2"><locus>fols. 7v-8v</locus><title xml:lang="frm">Lenvoy de Chaucer a
- Scogan</title>
- <bibl><title>IMEV</title><biblScope>3747</biblScope></bibl></msItem><msItem n="3"><locus>fol. 8v</locus><title>Truth</title><bibl><title>IMEV</title><biblScope>809</biblScope></bibl></msItem><msItem n="4"><locus>fols. 8v-10v</locus><title>Birds Praise of
- Love</title><bibl><title>IMEV</title><biblScope>1506</biblScope></bibl></msItem><msItem n="5"><locus>fols. 10v-11v</locus><title xml:lang="la">De amico ad amicam</title><title xml:lang="la">Responcio</title><bibl><title>IMEV</title><biblScope>16 & 19</biblScope></bibl></msItem><msItem n="6"><locus>fols. 14r-126v</locus><title>Troilus and Criseyde</title><note>Bk. 1:71-Bk. 5:1701,
- with additional losses due to mutilation throughout</note></msItem>
- </msContents>
-
-
-
Content
- model
-
+}
2.1.116. <msContents>
<msContents> (manuscript contents) describes the intellectual content of a manuscript, manuscript part, or other object either as a series of paragraphs or as a series of structured manuscript items. [10.6. Intellectual Content]
Unless it contains a simple prose description, this element should contain at least one of the elements <summary>, <msItem>, or <msItemStruct>. This constraint is not currently enforced by the schema.
Example
<msContents class="#sermons">
+ <p>A collection of Lollard sermons</p>
+</msContents>
<msDesc> (manuscript
- description) contains a description
- of a single identifiable manuscript or other text-bearing
- object such as early printed books. [10.1. Overview]
- <sch:rule context="//tei:msDesc/@xml:id">
- <sch:let name="docURIno"
- value="replace(ancestor::tei:fileDesc/tei:publicationStmt/tei:idno[@type='URI']/text(),
- '.+?(\d+).+', '$1')"/>
- <sch:let name="msDescIDno" value="replace(.,
- '.+?(\d+)', '$1')"/>
- <sch:assert test="$msDescIDno = $docURIno">
- The number portion of this @xml:id attribute must
- match the number portion of the <idno> in
- <publicationStmt>:
- <sch:value-of select="$docURIno"/>
- </sch:assert> </sch:rule>
Although the <msDesc> has primarily been designed with a
- view to encoding manuscript descriptions, it may also be
- used for other objects such as early printed books,
- fasicles, epigraphs, or any text-bearing objects that
- require substantial description. If an object is not
- text-bearing or the reasons for describing the object is not
- primarily the textual content, the more general <object> may be more
- suitable.
-
-
-
Example
-
<msDesc><msIdentifier><settlement>Oxford</settlement><repository>Bodleian Library</repository><idno type="Bod">MS Poet. Rawl. D. 169.</idno></msIdentifier><msContents><msItem><author>Geoffrey
- Chaucer</author>
- <title>The
- Canterbury Tales</title>
- </msItem></msContents><physDesc><objectDesc><p>A parchment codex of 136
- folios, measuring approx 28 by 19 inches, and
- containing 24 quires.</p>
- <p>The pages are
- margined and ruled throughout.</p><p>Four hands have been identified in the
- manuscript: the first 44 folios being written in two
- cursive anglicana scripts, while the remainder is for
- the most part in a mixed secretary hand.</p></objectDesc></physDesc>
- </msDesc>
<msDesc> (manuscript description) contains a description of a single identifiable manuscript or other text-bearing object such as early printed books. [10.1. Overview]
+<sch:rule context="//tei:msDesc/@xml:id">
+<sch:let name="docURIno"
+ value="replace(ancestor::tei:fileDesc/tei:publicationStmt/tei:idno[@type='URI']/text(),
+ '.+?(\d+).+', '$1')"/>
+<sch:let name="msDescIDno"
+ value="replace(., '.+?(\d+)', '$1')"/>
+<sch:assert test="$msDescIDno = $docURIno"> The number
+ portion of this @xml:id attribute must match the
+ number portion of the <idno> in
+ <publicationStmt>: <sch:value-of select="$docURIno"/>
+</sch:assert>
+</sch:rule>
Although the <msDesc> has primarily been designed with a view to encoding manuscript descriptions, it may also be used for other objects such as early printed books, fasicles, epigraphs, or any text-bearing objects that require substantial description. If an object is not text-bearing or the reasons for describing the object is not primarily the textual content, the more general <object> may be more suitable.
Example
<msDesc>
+ <msIdentifier>
+ <settlement>Oxford</settlement>
+ <repository>Bodleian Library</repository>
+ <idno type="Bod">MS Poet. Rawl. D. 169.</idno>
+ </msIdentifier>
+ <msContents>
+ <msItem>
+ <author>Geoffrey Chaucer</author>
+ <title>The Canterbury Tales</title>
+ </msItem>
+ </msContents>
+ <physDesc>
+ <objectDesc>
+ <p>A parchment codex of 136 folios, measuring approx
+ 28 by 19 inches, and containing 24 quires.</p>
+ <p>The pages are margined and ruled throughout.</p>
+ <p>Four hands have been identified in the manuscript: the first 44
+ folios being written in two cursive anglicana scripts, while the
+ remainder is for the most part in a mixed secretary hand.</p>
+ </objectDesc>
+ </physDesc>
+</msDesc>
2.1.117. att.global.responsibility.attribute.cert,
att.global.responsibility.attribute.resp,
att.global.source.attribute.source,
- attribute xml:id { text }?,
+ attribute xml:id { text }?
+ >>
+ tei:constraintSpec
+ [
+ ident = "xmlID-on-msDesc"
+ scheme = "schematron"
+ " "
+ " "
+ " "
+ " The number portion of this @xml:id attribute must match the number portion of the <idno> in <publicationStmt>: "
+ ],
(
msIdentifier,
model.headLike*,
@@ -36549,175 +4433,35 @@
2.1.117. ⚓
-
-
-
-
-
-
2.1.118. <msFrag>
-
-
-
-
<msFrag> (manuscript
- fragment) contains information about
- a fragment described in relation to a prior context,
- typically as a description of a virtual reconstruction of a
- manuscript or other object whose fragments were catalogued
- separately [10.11. Manuscript Fragments]
<msFrag> (manuscript fragment) contains information about a fragment described in relation to a prior context, typically as a description of a virtual reconstruction of a manuscript or other object whose fragments were catalogued separately [10.11. Manuscript Fragments]
<msIdentifier> (manuscript
- identifier) contains the information
- required to identify the manuscript or similar object being
- described. [10.4. The Manuscript Identifier]
- <s:report test="not(parent::tei:msPart) and
- (local-name(*[1])='idno' or local-name(*[1])='altIdentifier'
- or normalize-space(.)='')">An msIdentifier must contain
- either a repository or location.</s:report>
-
-
-
Content
- model
-
+}
2.1.119. <msIdentifier>
<msIdentifier> (manuscript identifier) contains the information required to identify the manuscript or similar object being described. [10.4. The Manuscript Identifier]
+<s:report test="not(parent::tei:msPart) and (local-name(*[1])='idno' or local-name(*[1])='altIdentifier'
+ or normalize-space(.)='')">An msIdentifier must contain either a repository or location.</s:report>
<msItem> (manuscript
- item) describes an individual work or
- item within the intellectual content of a manuscript,
- manuscript part, or other object. [10.6.1. The msItem and msItemStruct Elements]
- <sch:rule context="tei:msItem[descendant::tei:msItem[@defective='true']]">
- <sch:assert test="@defective='true'"> This
- <msItem> element must have a @defective
- attribute with the value "true" because its
- contains a descendant <msItem> element
- indicating that it is defective.
- </sch:assert> </sch:rule>
<msItem class="#saga"><locus>ff. 1r-24v</locus><title>Agrip af Noregs konunga sögum</title><incipit>regi oc h<ex>ann</ex> setiho <gap reason="illegible" extent="7"/>sc heim se<ex>m</ex> þio</incipit><explicit>h<ex>on</ex> hev<ex>er</ex><ex>oc</ex>þa buit hesta .ij. aNan viþ fé
- enh<ex>on</ex>o<ex>m</ex> aNan til reiþ<ex>ar</ex></explicit><textLang mainLang="non">Old Norse/Icelandic</textLang>
- </msItem>
-
-
-
Content
- model
-
+}
2.1.120. <msItem>
<msItem> (manuscript item) describes an individual work or item within the intellectual content of a manuscript, manuscript part, or other object. [10.6.1. The msItem and msItemStruct Elements]
+<sch:rule context="tei:msItem[descendant::tei:msItem[@defective='true']]">
+<sch:assert test="@defective='true'"> This
+ <msItem> element must have a @defective
+ attribute with the value "true" because its contains
+ a descendant <msItem> element indicating that
+ it is defective. </sch:assert>
+</sch:rule>
2.1.120. att.global.source.attribute.source,
attribute xml:id { text },
attribute n { text },
- attribute defective { text }?,
+ attribute defective { text }?
+ >>
+ tei:constraintSpec
+ [
+ ident = "defective-on-msItem"
+ scheme = "schematron"
+ " "
+ """ This <msItem> element must have a @defective attribute with the value "true" because its contains a descendant <msItem> element indicating that it is defective."""
+ ],
(
( locus | locusGrp )*,
(
@@ -37308,223 +4619,21 @@
<msItemStruct> (structured
- manuscript item) contains a
- structured description for an individual work or item within
- the intellectual content of a manuscript, manuscript part,
- or other object. [10.6.1. The msItem and msItemStruct Elements]
<msItemStruct> (structured manuscript item) contains a structured description for an individual work or item within the intellectual content of a manuscript, manuscript part, or other object. [10.6.1. The msItem and msItemStruct Elements]
<msName> (alternative
- name) contains any form of
- unstructured alternative name used for a manuscript or other
- object, such as an ‘ocellus nominum’, or nickname.
- [10.4. The Manuscript Identifier]
<msName> (alternative name) contains any form of unstructured alternative name used for a manuscript or other object, such as an ‘ocellus nominum’, or nickname. [10.4. The Manuscript Identifier]
<msPart> (manuscript
- part) contains information about an
- originally distinct manuscript or part of a manuscript,
- which is now part of a composite manuscript. [10.10. Manuscript Parts]
As this last example shows, for
- compatibility reasons the identifier of a manuscript part
- may be supplied as a simple <altIdentifier> rather than using the more
- structured <msIdentifier>
- element. This usage is however deprecated.
<msDesc><msIdentifier><settlement>Amiens</settlement><repository>Bibliothèque Municipale</repository><idno>MS 3</idno><msName>Maurdramnus
- Bible</msName></msIdentifier><msContents><summary xml:lang="lat">Miscellany of various texts;
- Prudentius, Psychomachia; Physiologus de natura
- animantium</summary>
- <textLang mainLang="lat">Latin</textLang></msContents><physDesc><objectDesc form="composite_manuscript"/></physDesc><msPart><msIdentifier><idno>ms. 10066-77 ff.
- 140r-156v</idno>
- </msIdentifier>
- <msContents>
- <summary xml:lang="lat">Physiologus</summary><textLang mainLang="lat">Latin</textLang></msContents></msPart><msPart><msIdentifier><altIdentifier><idno>MS 6</idno></altIdentifier></msIdentifier>
- <!-- other information specific to
- this part here --></msPart>
- <!-- more parts here -->
- </msDesc>
-
-
-
Content
- model
-
+}
2.1.123. <msPart>
<msPart> (manuscript part) contains information about an originally distinct manuscript or part of a manuscript, which is now part of a composite manuscript. [10.10. Manuscript Parts]
As this last example shows, for compatibility reasons the identifier of a manuscript part may be supplied as a simple <altIdentifier> rather than using the more structured <msIdentifier> element. This usage is however deprecated.
Proper nouns referring to people,
- places, and organizations may be tagged instead with <persName>, <placeName>, or
- <orgName>, when the TEI
- module for names and dates is included.
Proper nouns referring to people, places, and organizations may be tagged instead with <persName>, <placeName>, or <orgName>, when the TEI module for names and dates is included.
In the following example, the translator
- has supplied a footnote containing an explanation of the term
- translated as "painterly":
And yet it is not only in the great
- line of Italian renaissance art, but even in the painterly
- <note place="bottom" type="gloss" resp="#MDMH"><term xml:lang="de">Malerisch</term>. This word has, in the German, two
- distinct meanings, one objective, a quality residing in the
- object, the other subjective, a mode of apprehension and
- creation. To avoid confusion, they have been distinguished
- in English as <mentioned>picturesque</mentioned> and <mentioned>painterly</mentioned> respectively.
- </note> style of the
- Dutch genre painters of the seventeenth century that drapery
- has this psychological significance. <!-- elsewhere in the document -->
- <respStmt xml:id="MDMH"><resp>translation from German to
- English</resp><name>Hottinger, Marie
- Donald Mackie</name>
- </respStmt>
For this
- example to be valid, the code MDMH
- must be defined elsewhere, for example by means of a
- responsibility statement in the associated TEI header.
-
-
-
Example
-
The global n
- attribute may be used to supply the symbol or number used to
- mark the note's point of attachment in the source text, as in
- the following example:
Mevorakh b. Saadya's mother, the
- matriarch of the family during the second half of the
- eleventh century, <note n="126" anchored="true"> The
- alleged mention of Judah Nagid's mother in a letter from
- 1071 is, in fact, a reference to Judah's children; cf.
- above, nn. 111 and 54. </note> is well known from Geniza
- documents published by Jacob Mann.
However, if notes
- are numbered in sequence and their numbering can be
- reconstructed automatically by processing software, it may well
- be considered unnecessary to record the note numbers.
In modern texts, notes are usually anchored by means of explicit footnote or endnote symbols. An explicit indication of the phrase or line annotated may however be used instead (e.g. ‘page 218, lines 3–4’). The anchored attribute indicates whether any explicit location is given, whether by symbol or by prose cross-reference. The value true indicates that such an explicit location is indicated in the copy text; the value false indicates that the copy text does not indicate a specific place of attachment for the note. If the specific symbols used in the copy text at the location the note is anchored are to be recorded, use the n attribute.
targetEnd
points to the end of the span to which the note is attached, if the note is not embedded in the text at that point.
This attribute is retained for backwards compatibility; it may be removed at a subsequent release of the Guidelines. The recommended way of pointing to a span of elements is by means of the range function of XPointer, as further described in 16.2.4.6. range().
In the following example, the translator has supplied a footnote containing an explanation of the term translated as "painterly":
And yet it is not only
+ in the great line of Italian renaissance art, but even in the
+ painterly <note place="bottom" type="gloss"
+ resp="#MDMH">
+ <term xml:lang="de">Malerisch</term>. This word has, in the German, two
+ distinct meanings, one objective, a quality residing in the object,
+ the other subjective, a mode of apprehension and creation. To avoid
+ confusion, they have been distinguished in English as
+<mentioned>picturesque</mentioned> and
+<mentioned>painterly</mentioned> respectively.
+</note> style of the
+ Dutch genre painters of the seventeenth century that drapery has this
+ psychological significance.
+
+<!-- elsewhere in the document -->
+<respStmt xml:id="MDMH">
+ <resp>translation from German to English</resp>
+ <name>Hottinger, Marie Donald Mackie</name>
+</respStmt>
For this example to be valid, the code MDMH must be defined elsewhere, for example by means of a responsibility statement in the associated TEI header.
Example
The global n attribute may be used to supply the symbol or number used to mark the note's point of attachment in the source text, as in the following example:
Mevorakh b. Saadya's mother, the matriarch of the
+ family during the second half of the eleventh century, <note n="126" anchored="true"> The
+ alleged mention of Judah Nagid's mother in a letter from 1071 is, in fact, a reference to
+ Judah's children; cf. above, nn. 111 and 54. </note> is well known from Geniza documents
+ published by Jacob Mann.
However, if notes are numbered in sequence and their numbering can be reconstructed automatically by processing software, it may well be considered unnecessary to record the note numbers.
Detailed analyses of quantities and
- units of measure in historical documents may also use the
- feature structure mechanism described in chapter 18. Feature Structures. The <num>
- element is intended for use in simple applications.
-
-
-
Example
-
<p>I reached <num type="cardinal" value="21">twenty-one</num> on my <num type="ordinal" value="21">twenty-first</num> birthday</p>
- <p>Light travels at <num value="3E10">3×10<hi rend="sup">10</hi></num> cm per second.</p>
Detailed analyses of quantities and units of measure in historical documents may also use the feature structure mechanism described in chapter 18. Feature Structures. The <num> element is intended for use in simple applications.
Example
<p>I reached <num type="cardinal" value="21">twenty-one</num> on
+ my <num type="ordinal" value="21">twenty-first</num> birthday</p>
+<p>Light travels at <num value="3E10">3×10<hi rend="sup">10</hi>
+ </num> cm per second.</p>
<objectDesc> (object
- description) contains a description
- of the physical components making up the object which is
- being described. [10.7.1. Object Description]
(form)
- a short project-specific name
- identifying the physical form of the carrier, for
- example as a codex, roll, fragment, partial leaf,
- cutting etc.
<objectDesc form="codex"><supportDesc material="mixed"><p>Early modern <material>parchment</material> and <material>paper</material>.</p></supportDesc><layoutDesc><layout ruledLines="25
- 32"/></layoutDesc>
- </objectDesc>
-
-
-
Schematron
-
- <sch:rule see="https://msdesc.github.io/consolidated-tei-schema/msdesc.html#objectdescBook"
- context="//tei:sourceDesc/tei:msDesc[not(tei:msPart)]">
- <sch:assert test="tei:physDesc/tei:objectDesc[@form]"
- role="warn"> The physical form of the carrier should be
- recorded in the objectDesc element, with a form attribute.
- </sch:assert> </sch:rule>
- <sch:rule context="//tei:sourceDesc/tei:msDesc/tei:msPart">
- <sch:assert test=" tei:physDesc/tei:objectDesc[@form] or
- ancestor::tei:msDesc/tei:physDesc/tei:objectDesc[@form] "
- role="warn"> The physical form of the carrier should be
- recorded in the objectDesc element, with a form attribute,
- unless it has been described for the entire manuscript.
- </sch:assert> </sch:rule>
-
-
-
Content
- model
-
+}
2.1.128. <objectDesc>
<objectDesc> contains a description of the physical components making up the object which is being described. [10.7.1. Object Description]
+<sch:rule see="https://msdesc.github.io/consolidated-tei-schema/msdesc.html#objectdescBook"
+ context="//tei:sourceDesc/tei:msDesc[not(tei:msPart)]">
+<sch:assert test="tei:physDesc/tei:objectDesc[@form]"
+ role="warn"> The physical form of the carrier should be
+ recorded in the objectDesc element, with a form attribute.
+</sch:assert>
+</sch:rule>
+<sch:rule context="//tei:sourceDesc/tei:msDesc/tei:msPart">
+<sch:assert test=" tei:physDesc/tei:objectDesc[@form] or ancestor::tei:msDesc/tei:physDesc/tei:objectDesc[@form]
+ "
+ role="warn"> The
+ physical form of the carrier should be recorded in the
+ objectDesc element, with a form attribute, unless it has
+ been described for the entire manuscript. </sch:assert>
+</sch:rule>
If all that is desired is to call
- attention to the original version in the copy text, <orig> may be used alone:
<l>But this will be a <orig>meere</orig> confusion</l>
- <l>And hardly shall we
- all be <orig>vnderstoode</orig>
- </l>
-
-
-
Example
-
More usually, an <orig> will
- be combined with a regularized form within a <choice>
- element:
<l>But this will be a <choice><orig>meere</orig><reg>mere</reg></choice> confusion</l>
- <l>And hardly shall we
- all be <choice><orig>vnderstoode</orig><reg>understood</reg></choice>
- </l>
If all that is desired is to call attention to the original version in the copy text, <orig> may be used alone:
<l>But this will be a <orig>meere</orig> confusion</l>
+<l>And hardly shall we all be <orig>vnderstoode</orig>
+</l>
Example
More usually, an <orig> will be combined with a regularized form within a <choice> element:
<l>But this will be a <choice>
+ <orig>meere</orig>
+ <reg>mere</reg>
+ </choice> confusion</l>
+<l>And hardly shall we all be <choice>
+ <orig>vnderstoode</orig>
+ <reg>understood</reg>
+ </choice>
+</l>
<origDate> (origin
- date) contains any form of date, used to
- identify the date of origin for a manuscript, manuscript
- part, or other object. [10.3.1. Origination]
<origDate notBefore="-0300" notAfter="-0200">3rd century BCE</origDate>
-
-
-
Schematron
-
- <sch:rule context="//tei:origDate">
- <sch:assert test="@calendar and ((@when or @notBefore or
- @notAfter or @from or @to) or (@when-custom or
- @notBefore-custom or @notAfter-custom or @from-custom or
- @to-custom)) and string-length(normalize-space(string())) gt
- 0" role="error"> The origDate element must have two or
- more attributes - calendar and at least one of the regular
- date attributes (when, notBefore, notAfter, from, and/or to)
- -OR- custom dates (when-custom, notBefore-custom,
- notAfter-custom, from-custom, and/or to-custom) and must
- contain some text describing the date. </sch:assert>
- </sch:rule>
<origDate> (origin date) contains any form of date, used to identify the date of origin for a manuscript, manuscript part, or other object. [10.3.1. Origination]
<origDate notBefore="-0300"
+ notAfter="-0200">3rd century BCE</origDate>
Schematron
+<sch:rule context="//tei:origDate">
+<sch:assert test="@calendar and ((@when or @notBefore or @notAfter or @from or @to)
+ or (@when-custom or @notBefore-custom or @notAfter-custom or @from-custom
+ or @to-custom)) and string-length(normalize-space(string())) gt 0"
+ role="error"> The origDate element must have two or more attributes -
+ calendar and at least one of the regular date attributes
+ (when, notBefore, notAfter, from, and/or to) -OR- custom
+ dates (when-custom, notBefore-custom, notAfter-custom,
+ from-custom, and/or to-custom) and must contain some text
+ describing the date. </sch:assert>
+</sch:rule>
<origPlace> (origin
- place) contains any form of place
- name, used to identify the place of origin for a manuscript,
- manuscript part, or other object. [10.3.1. Origination]
The type
- attribute may be used to distinguish different kinds of
- ‘origin’, for example original place of publication, as
- opposed to original place of printing.
-
-
-
Example
-
<origPlace>Birmingham</origPlace>
-
-
-
Content
- model
-
+}
2.1.132. <origPlace>
<origPlace> (origin place) contains any form of place name, used to identify the place of origin for a manuscript, manuscript part, or other object. [10.3.1. Origination]
The type attribute may be used to distinguish different kinds of ‘origin’, for example original place of publication, as opposed to original place of printing.
<origin> (origin) contains any descriptive or other information
- concerning the origin of a manuscript, manuscript part, or
- other object. [10.8. History]
<origin notBefore="1802" notAfter="1845" evidence="internal" resp="#AMH">Copied in <name type="origPlace">Derby</name>, probably from an
- old Flemish original, between 1802 and 1845, according to
- <persName xml:id="AMH">Anne-Mette Hansen</persName>. </origin>
-
-
-
Content
- model
-
+}
2.1.133. <origin>
<origin> contains any descriptive or other information concerning the origin of a manuscript, manuscript part, or other object. [10.8. History]
<origin notBefore="1802" notAfter="1845"
+ evidence="internal" resp="#AMH">Copied in <name type="origPlace">Derby</name>, probably from an
+ old Flemish original, between 1802 and 1845, according to <persName xml:id="AMH">Anne-Mette Hansen</persName>.
+</origin>
<p>Hallgerd was outside. <q>There is blood on your
- axe,</q> she said.
- <q>What have you
- done?</q>
- </p>
- <p><q>I have now arranged that
- you can be married a second time,</q> replied Thjostolf. </p>
- <p><q>Then you must mean that
- Thorvald is dead,</q> she
- said. </p>
- <p><q>Yes,</q> said Thjostolf. <q>And now you must think
- up some plan for me.</q>
- </p>
-
-
-
Schematron
-
- <s:report test="not(ancestor::tei:floatingText) and
- (ancestor::tei:p or ancestor::tei:ab) and
- not(parent::tei:exemplum |parent::tei:item |parent::tei:note
- |parent::tei:q |parent::tei:quote |parent::tei:remarks
- |parent::tei:said |parent::tei:sp |parent::tei:stage
- |parent::tei:cell |parent::tei:figure )"> Abstract model
- violation: Paragraphs may not occur inside other paragraphs
- or ab elements. </s:report>
-
-
-
Schematron
-
- <s:report test="(ancestor::tei:l or ancestor::tei:lg) and
- not(parent::tei:figure or parent::tei:note or
- ancestor::tei:floatingText)"> Abstract model violation:
- Lines may not contain higher-level structural elements such
- as div, p, or ab, unless p is a child of figure or note, or
- is a descendant of floatingText.
- </s:report>
<p>Hallgerd was outside. <q>There is blood on your axe,</q> she said. <q>What have you
+ done?</q>
+</p>
+<p>
+ <q>I have now arranged that you can be married a second time,</q> replied Thjostolf.
+</p>
+<p>
+ <q>Then you must mean that Thorvald is dead,</q> she said.
+</p>
+<p>
+ <q>Yes,</q> said Thjostolf. <q>And now you must think up some plan for me.</q>
+</p>
Schematron
+<s:report test="not(ancestor::tei:floatingText) and (ancestor::tei:p or ancestor::tei:ab)
+ and not(parent::tei:exemplum |parent::tei:item |parent::tei:note |parent::tei:q
+ |parent::tei:quote |parent::tei:remarks |parent::tei:said |parent::tei:sp
+ |parent::tei:stage |parent::tei:cell |parent::tei:figure )"> Abstract model violation: Paragraphs may not occur inside other paragraphs or ab elements.
+</s:report>
Schematron
+<s:report test="ancestor::tei:l[not(.//tei:note//tei:p[. = current()])]"> Abstract model violation: Lines may not contain higher-level structural elements such as div, p, or ab.
+</s:report>
A <pb> element should appear
- at the start of the page which it identifies. The global
- n attribute indicates the
- number or other value associated with this page. This will
- normally be the page number or signature printed on it,
- since the physical sequence number is implicit in the
- presence of the <pb> element
- itself.
The type attribute
- may be used to characterize the page break in any respect.
- The more specialized attributes break, ed, or edRef should be preferred when the
- intent is to indicate whether or not the page break is
- word-breaking, or to note the source from which it
- derives.
-
-
-
Example
-
Page numbers may vary in different
- editions of a text.
A page break may be associated with a
- facsimile image of the page it introduces by means of the facs attribute
<body><pb n="1" facs="page1.png"/>
- <!-- page1.png contains an image of
- the page; the text it contains is encoded here
- --><p>
- <!-- ... --></p><pb n="2" facs="page2.png"/>
- <!-- similarly, for page 2
- --><p>
- <!-- ... --></p>
- </body>
A <pb> element should appear at the start of the page which it identifies. The global n attribute indicates the number or other value associated with this page. This will normally be the page number or signature printed on it, since the physical sequence number is implicit in the presence of the <pb> element itself.
The type attribute may be used to characterize the page break in any respect. The more specialized attributes break, ed, or edRef should be preferred when the intent is to indicate whether or not the page break is word-breaking, or to note the source from which it derives.
Example
Page numbers may vary in different editions of a text.
<p> ... <pb n="145" ed="ed2"/>
+<!-- Page 145 in edition "ed2" starts here --> ... <pb n="283" ed="ed1"/>
+<!-- Page 283 in edition "ed1" starts here--> ... </p>
Example
A page break may be associated with a facsimile image of the page it introduces by means of the facs attribute
<body>
+ <pb n="1" facs="page1.png"/>
+<!-- page1.png contains an image of the page;
+ the text it contains is encoded here -->
+ <p>
+<!-- ... -->
+ </p>
+ <pb n="2" facs="page2.png"/>
+<!-- similarly, for page 2 -->
+ <p>
+<!-- ... -->
+ </p>
+</body>
<persName> (personal
- name) contains a proper noun or
- proper-noun phrase referring to a person, possibly including
- one or more of the person's forenames, surnames, honorifics,
- added names, etc. [13.2.1. Personal Names]
<persName><forename>Edward</forename><forename>George</forename><surname type="linked">Bulwer-Lytton</surname>, <roleName>Baron Lytton of
- <placeName>Knebworth</placeName></roleName>
- </persName>
-
-
-
Schematron
-
- <sch:rule context="//tei:persName/tei:choice">
- <sch:assert test="((tei:sic and tei:corr) or (tei:abbr
- and tei:expan))"> As child of <persName>,
- <choice> can either be used to correct a mistake in
- the original print volume (using <sic> and
- <corr>) or to indicate an abbreviation and an
- expansion of that abbreviation (using <abbr> and
- <expan>). The <choice> element should not be
- used to mark up a name in different languages.
- </sch:assert> </sch:rule>
-
-
-
Content
- model
-
+}
2.1.136. <persName>
<persName> (personal name) contains a proper noun or proper-noun phrase referring to a person, possibly including one or more of the person's forenames, surnames, honorifics, added names, etc. [13.2.1. Personal Names]
+<sch:rule context="tei:persName/@ref">
+<sch:let name="personIndex"
+ value="doc('https://raw.githubusercontent.com/srophe/syriaca/master/documentation/indexes/persons.xml')"/>
+<sch:let name="personURIs"
+ value="$personIndex//tei:person/@ref"/>
+<sch:let name="error" value="."/>
+<sch:assert test="starts-with(., 'http://syriaca.org/person/') or starts-with(., 'smbl')"> The @ref attribute must begin with either
+ "http://syriaca.org/person/" or with "smbl".
+</sch:assert>
+</sch:rule>
+<sch:rule context="//tei:persName/tei:choice">
+<sch:assert test="((tei:sic and tei:corr) or (tei:abbr and tei:expan))"> As child of <persName>, <choice> can either be
+ used to correct a mistake in the original print volume
+ (using <sic> and <corr>) or to indicate an
+ abbreviation and an expansion of that abbreviation (using
+ <abbr> and <expan>). The <choice> element
+ should not be used to mark up a name in different languages.
+</sch:assert>
+</sch:rule>
element persName
{
att.global.attributes,
att.editLike.attributes,
att.typed.attribute.subtype,
- attribute ref { list { + } }?,
+ attribute ref { list { + } }?
+ >>
+ tei:constraintSpec
+ [
+ ident = "ref-on-persName"
+ scheme = "schematron"
+ " "
+ " "
+ " "
+ " "
+ """ The @ref attribute must begin with either "http://syriaca.org/person/" or with "smbl"."""
+ ],
attribute type { text }?,
( choice*, foreign*, persName?, placeName*, sic*, supplied*, text )
-}⚓
-
-
-
-
-
-
2.1.137. <person>
-
-
-
-
<person> (person) provides information about an identifiable
- individual, for example a participant in a language
- interaction, or a person referred to in a historical
- source. [13.3.2. The Person Element
- 15.2.2. The Participant Description]
Values for this
- attribute may be locally defined by a project,
- using arbitrary keywords such as artist, employer,
- author, relative, or servant, each of which should be
- associated with a definition. Such local
- definitions will typically be provided by a <valList> element in the
- project schema specification.
-
-
-
-
-
-
sex
-
specifies the
- sex of the person.
-
-
-
Status
-
Optional
-
-
-
Datatype
-
1–∞ occurrences ofteidata.sex
- separated by
- whitespace
Values for this
- attribute may be locally defined by a project,
- using arbitrary keywords such as infant, child,
- teen, adult, or senior,
- each of which should be associated with a
- definition. Such local definitions will typically
- be provided by a <valList> element in the project
- schema specification.
May contain either a prose description
- organized as paragraphs, or a sequence of more specific
- demographic elements drawn from the model.personPart
- class.
-
-
-
Example
-
<person sex="F" age="adult">
- <p>Female
- respondent, well-educated, born in Shropshire UK, 12 Jan
- 1950, of unknown occupation. Speaks French fluently.
- Socio-Economic status B2.</p>
- </person>
Values for this attribute may be locally defined by a project, using arbitrary keywords such as artist, employer, author, relative, or servant, each of which should be associated with a definition. Such local definitions will typically be provided by a <valList> element in the project schema specification.
sex
specifies the sex of the person.
Status
Optional
Datatype
1–∞ occurrences ofteidata.sexseparated by whitespace
Values for this attribute may be locally defined by a project, using arbitrary keywords such as infant, child, teen, adult, or senior, each of which should be associated with a definition. Such local definitions will typically be provided by a <valList> element in the project schema specification.
May contain either a prose description organized as paragraphs, or a sequence of more specific demographic elements drawn from the model.personPart class.
Example
<person sex="F" age="adult">
+ <p>Female respondent, well-educated, born in Shropshire UK, 12 Jan 1950, of unknown occupation. Speaks French fluently. Socio-Economic
+ status B2.</p>
+</person>
<physDesc> (physical
- description) contains a full physical
- description of a manuscript, manuscript part, or other
- object optionally subdivided using more specialized elements
- from the model.physDescPart
- class. [10.7. Physical Description]
<physDesc><objectDesc form="codex"><supportDesc material="perg"><support>Parchment.</support><extent>i + 55 leaves <dimensions scope="all" type="leaf" unit="inch"><height>7¼</height><width>5⅜</width></dimensions></extent></supportDesc><layoutDesc><layout columns="2">In double columns.</layout></layoutDesc></objectDesc><handDesc><p>Written in more than one
- hand.</p></handDesc><decoDesc><p>With a few coloured
- capitals.</p></decoDesc>
- </physDesc>
-
-
-
Content
- model
-
+}
2.1.138. <physDesc>
<physDesc> (physical description) contains a full physical description of a manuscript, manuscript part, or other object optionally subdivided using more specialized elements from the model.physDescPart class. [10.7. Physical Description]
- <sch:rule context="//tei:placeName/tei:choice">
- <sch:assert test="((tei:sic and tei:corr) or (tei:abbr
- and tei:expan))"> As child of <persName>,
- <choice> can either be used to correct a mistake in
- the original print volume (using <sic> and
- <corr>) or to indicate an abbreviation and an
- expansion of that abbreviation (using <abbr> and
- <expan>). The <choice> element should not be
- used to mark up a name in different languages.
- </sch:assert> </sch:rule>
-
-
-
Content
- model
-
+}
2.1.140. <placeName>
<placeName> contains an absolute or relative place name. [13.2.3. Place Names]
+<sch:rule context="//tei:text//tei:placeName/@ref">
+<sch:let name="placeIndex"
+ value="doc('https://raw.githubusercontent.com/srophe/syriaca/master/documentation/indexes/places.xml')"/>
+<sch:let name="placeURIs"
+ value="$placeIndex//tei:place/@ref"/>
+<sch:let name="error" value="."/>
+<sch:assert test="starts-with(., 'http://syriaca.org/place/') or starts-with(., 'smbl')"> The @ref attribute must begin with either
+ "http://syriaca.org/person/" or with "smbl".
+</sch:assert>
+</sch:rule>
+<sch:rule context="//tei:placeName/tei:choice">
+<sch:assert test="((tei:sic and tei:corr) or (tei:abbr and tei:expan))"> As child of <persName>, <choice> can either be
+ used to correct a mistake in the original print volume
+ (using <sic> and <corr>) or to indicate an
+ abbreviation and an expansion of that abbreviation (using
+ <abbr> and <expan>). The <choice> element
+ should not be used to mark up a name in different languages.
+</sch:assert>
+</sch:rule>
element placeName
{
att.editLike.attributes,
att.global.attributes,
att.typed.attributes,
- attribute ref { list { + } }?,
+ attribute ref { list { + } }?
+ >>
+ tei:constraintSpec
+ [
+ ident = "ref-on-placeName"
+ scheme = "schematron"
+ " "
+ " "
+ " "
+ " "
+ """ The @ref attribute must begin with either "http://syriaca.org/person/" or with "smbl"."""
+ ],
( choice*, foreign*, placeName*, sic*, supplied*, text )
-}⚓
-
-
-
-
-
-
2.1.141. <postCode>
-
-
-
-
<postCode> (postal
- code) contains a numerical or
- alphanumeric code used as part of a postal address to
- simplify sorting or delivery of mail. [3.6.2. Addresses]
The position and nature of postal codes
- is highly country-specific; the conventions appropriate to
- the country concerned should be used.
-
-
-
Example
-
<postCode>HR1 3LR</postCode>
-
-
-
Example
-
<postCode>60142-7</postCode>
-
-
-
Content
- model
-
+}
2.1.141. <postCode>
<postCode> (postal code) contains a numerical or alphanumeric code used as part of a postal address to simplify sorting or delivery of mail. [3.5.2. Addresses]
<principal> (principal
- researcher) supplies the name of the
- principal researcher responsible for the creation of an
- electronic text. [2.2.1. The Title Statement]
<principal> (principal researcher) supplies the name of the principal researcher responsible for the creation of an electronic text. [2.2.1. The Title Statement]
<profileDesc> (text-profile
- description) provides a detailed
- description of non-bibliographic aspects of a text,
- specifically the languages and sublanguages used, the
- situation in which it was produced, the participants and
- their setting. [2.4. The Profile Description
- 2.1.1. The TEI Header and Its Components]
Although the content model permits it,
- it is rarely meaningful to supply multiple occurrences for
- any of the child elements of <profileDesc> unless these are documenting
- multiple texts.
<profileDesc> (text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting. [2.4. The Profile Description2.1.1. The TEI Header and Its Components]
Although the content model permits it, it is rarely meaningful to supply multiple occurrences for any of the child elements of <profileDesc> unless these are documenting multiple texts.
<provenance> (provenance) contains any descriptive
- or other information concerning a single identifiable
- episode during the history of a manuscript, manuscript part,
- or other object after its creation but before its
- acquisition. [10.8. History]
<provenance>Listed as the property of
- Lawrence Sterne in 1788.</provenance>
- <provenance>Sold at
- Sothebys in 1899.</provenance>
-
-
-
Content
- model
-
+}
2.1.145. <provenance>
<provenance> contains any descriptive or other information concerning a single identifiable episode during the history of a manuscript, manuscript part, or other object after its creation but before its acquisition. [10.8. History]
Where a publication statement contains
- several members of the model.publicationStmtPart.agency or model.publicationStmtPart.detail classes rather
- than one or more paragraphs or anonymous blocks, care should
- be taken to ensure that the repeated elements are presented
- in a meaningful order. It is a conformance requirement that
- elements supplying information about publication place,
- address, identifier, availability, and date be given
- following the name of the publisher, distributor, or
- authority concerned, and preferably in that order.
-
-
-
Example
-
<publicationStmt><publisher>C. Muquardt </publisher><pubPlace>Bruxelles
- & Leipzig</pubPlace><date when="1846"/>
- </publicationStmt>
-
-
-
Example
-
<publicationStmt><publisher>Chadwyck Healey</publisher><pubPlace>Cambridge</pubPlace><availability><p>Available under licence
- only</p></availability><date when="1992">1992</date>
- </publicationStmt>
-
-
-
Example
-
<publicationStmt><publisher>Zea Books</publisher><pubPlace>Lincoln, NE</pubPlace><date>2017</date><availability><p>This is an open access work licensed
- under a Creative Commons Attribution 4.0 International
- license.</p></availability><ptr target="http://digitalcommons.unl.edu/zeabook/55"/>
- </publicationStmt>
Where a publication statement contains several members of the model.publicationStmtPart.agency or model.publicationStmtPart.detail classes rather than one or more paragraphs or anonymous blocks, care should be taken to ensure that the repeated elements are presented in a meaningful order. It is a conformance requirement that elements supplying information about publication place, address, identifier, availability, and date be given following the name of the publisher, distributor, or authority concerned, and preferably in that order.
<publicationStmt>
+ <publisher>Zea Books</publisher>
+ <pubPlace>Lincoln, NE</pubPlace>
+ <date>2017</date>
+ <availability>
+ <p>This is an open access work licensed under a Creative Commons Attribution 4.0 International license.</p>
+ </availability>
+ <ptr target="http://digitalcommons.unl.edu/zeabook/55"/>
+</publicationStmt>
<q>
- (quoted) contains material which is distinguished from the
- surrounding text using quotation marks or a similar method,
- for any one of a variety of reasons including, but not
- limited to: direct speech or thought, technical terms or
- jargon, authorial distance, quotations from elsewhere, and
- passages that are mentioned but not used. [3.3.3. Quotation]
May be used to indicate that a passage
- is distinguished from the surrounding text for reasons
- concerning which no claim is made. When used in this manner,
- <q> may be thought of as syntactic sugar for
- <hi> with a value of rend that indicates the use of such mechanisms
- as quotation marks.
-
-
-
Example
-
It is spelled <q>Tübingen</q> — to enter the letter <q>u</q> with an umlaut hold down the <q>option</q> key and press <q>0 0 f c</q>
-
-
-
Content
- model
-
+}
2.1.150. <q>
<q> (quoted) contains material which is distinguished from the surrounding text using quotation marks or a similar method, for any one of a variety of reasons including, but not limited to: direct speech or thought, technical terms or jargon, authorial distance, quotations from elsewhere, and passages that are mentioned but not used. [3.3.3. Quotation]
May be used to indicate that a passage is distinguished from the surrounding text for reasons concerning which no claim is made. When used in this manner, <q> may be thought of as syntactic sugar for <hi> with a value of rend that indicates the use of such mechanisms as quotation marks.
Example
It is spelled <q>Tübingen</q> — to enter the
+ letter <q>u</q> with an umlaut hold down the <q>option</q> key and press
+<q>0 0 f c</q>
<quote> (quotation)
- contains a phrase or passage attributed by
- the narrator or author to some agency external to the
- text. [3.3.3. Quotation
- 4.3.1. Grouped Texts]
- <sch:rule context="//tei:quote/@xml:lang">
- <sch:let name="langIdents"
- value="//tei:profileDesc/tei:langUsage/tei:language/@ident"/>
- <sch:assert test=". = $langIdents">
- Attribute value must match one of the following
- language codes in the <profileDesc>:
- <sch:value-of select="string-join($langIdents,
- ' | ')"/>. </sch:assert>
- </sch:rule>
If a bibliographic citation is supplied
- for the source of a quotation, the two may be grouped using
- the <cit> element.
-
-
-
Example
-
Lexicography has shown little sign
- of being affected by the work of followers of J.R. Firth,
- probably best summarized in his slogan, <quote>You shall know a
- word by the company it keeps</quote>
- <ref>(Firth, 1957)</ref>
-
-
-
Content
- model
-
+}
2.1.151. <quote>
<quote> (quotation) contains a phrase or passage attributed by the narrator or author to some agency external to the text. [3.3.3. Quotation4.3.1. Grouped Texts]
+<sch:rule context="//tei:quote/@xml:lang">
+<sch:let name="langIdents"
+ value="//tei:profileDesc/tei:langUsage/tei:language/@ident"/>
+<sch:assert test=". = $langIdents"> Attribute value must
+ match one of the following language codes in the
+ <profileDesc>: <sch:value-of select="string-join($langIdents, ' | ')"/>.
+</sch:assert>
+</sch:rule>
If a bibliographic citation is supplied for the source of a quotation, the two may be grouped using the <cit> element.
Example
Lexicography has shown little sign of being affected by the
+ work of followers of J.R. Firth, probably best summarized in his
+ slogan, <quote>You shall know a word by the company it
+ keeps</quote>
+<ref>(Firth, 1957)</ref>
2.1.151. att.global.responsibility.attribute.cert,
att.global.responsibility.attribute.resp,
att.global.source.attribute.source,
- attribute xml:lang { text },
+ attribute xml:lang { text }
+ >>
+ tei:constraintSpec
+ [
+ ident = "xmlLang-on-quote"
+ scheme = "schematron"
+ " "
+ " "
+ " Attribute value must match one of the following language codes in the <profileDesc>: "
+ "."
+ ],
macro.specialPara
-}⚓
-
-
-
-
-
-
2.1.152. <recordHist>
-
-
-
-
<recordHist> (recorded
- history) provides information about
- the source and revision status of the parent manuscript or
- object description itself. [10.9.1. Administrative Information]
<recordHist><source><p>Derived from <ref target="#IMEV">IMEV 123</ref> with additional
- research by P.M.W.Robinson</p></source><change when="1999-06-23"><name>LDB</name> (editor) checked
- examples against DTD version 3.6 </change>
- </recordHist>
-
-
-
Content
- model
-
+}
2.1.152. <recordHist>
<recordHist> (recorded history) provides information about the source and revision status of the parent manuscript or object description itself. [10.9.1. Administrative Information]
+<sch:rule context="//tei:ref/@target[contains(., 'hand')]">
+<sch:let name="handIDs"
+ value="//@xml:id[contains(., 'hand')]"/>
+<sch:let name="IDsToPointers"
+ value="for $i in $handIDs return concat('#', $i)"/>
+<sch:assert test=". = $IDsToPointers"> Attribute value
+ must match one of the following @xml:id attributes:
+<sch:value-of select="string-join($IDsToPointers, ' | ')"/>.
+</sch:assert>
+</sch:rule>
If all that is desired is to call
- attention to the fact that the copy text has been regularized,
- <reg> may be used alone:
<q>Please <reg>knock</reg> if an <reg>answer</reg> is <reg>required</reg>
- </q>
-
-
-
Example
-
It is also possible to identify the
- individual responsible for the regularization, and, using the <choice> and <orig> elements, to provide
- both the original and regularized readings:
<q>Please <choice><reg resp="#LB">knock</reg><orig>cnk</orig></choice> if an <choice><reg>answer</reg><orig>nsr</orig></choice> is <choice><reg>required</reg><orig>reqd</orig></choice>
- </q>
If all that is desired is to call attention to the fact that the copy text has been regularized, <reg> may be used alone:
<q>Please <reg>knock</reg> if an <reg>answer</reg> is <reg>required</reg>
+</q>
Example
It is also possible to identify the individual responsible for the regularization, and, using the <choice> and <orig> elements, to provide both the original and regularized readings:
<q>Please <choice>
+ <reg resp="#LB">knock</reg>
+ <orig>cnk</orig>
+ </choice> if an <choice>
+ <reg>answer</reg>
+ <orig>nsr</orig>
+ </choice> is <choice>
+ <reg>required</reg>
+ <orig>reqd</orig>
+ </choice>
+</q>
<region> (region) contains the name of an administrative unit such
- as a state, province, or county, larger than a settlement,
- but smaller than a country. [13.2.3. Place Names]
<region> contains the name of an administrative unit such as a state, province, or county, larger than a settlement, but smaller than a country. [13.2.3. Place Names]
<relatedItem> contains or
- references some other bibliographic item which is related to
- the present one in some specified manner, for example as a
- constituent or alternative version of it. [3.12.2.7. Related Items]
If the target
- attribute is used to reference the related bibliographic
- item, the element must be empty.
-
-
-
Example
-
<biblStruct><monogr><author>Shirley, James</author><title type="main">The gentlemen of Venice</title><imprint><pubPlace>New York</pubPlace><publisher>Readex
- Microprint</publisher><date>1953</date></imprint><extent>1 microprint card, 23 x 15
- cm.</extent></monogr><series><title>Three centuries of
- drama: English, 1642–1700</title></series><relatedItem type="otherForm"><biblStruct><monogr><author>Shirley, James</author><title type="main">The gentlemen of Venice</title><title type="sub">a tragi-comedie presented at
- the private house in Salisbury Court by Her
- Majesties servants</title><imprint><pubPlace>London</pubPlace><publisher>H. Moseley</publisher><date>1655</date></imprint><extent>78 p.</extent></monogr></biblStruct></relatedItem>
- </biblStruct>
-
-
-
Schematron
-
- <sch:report test="@target and count( child::* ) >
- 0">If the @target attribute on <sch:name/> is used,
- the relatedItem element must be empty</sch:report>
- <sch:assert test="@target or child::*">A relatedItem
- element should have either a 'target' attribute or a child
- element to indicate the related bibliographic
- item</sch:assert>
-
-
-
Content
- model
-
+}
2.1.156. <relatedItem>
<relatedItem> contains or references some other bibliographic item which is related to the present one in some specified manner, for example as a constituent or alternative version of it. [3.11.2.7. Related Items]
If the target attribute is used to reference the related bibliographic item, the element must be empty.
Example
<biblStruct>
+ <monogr>
+ <author>Shirley, James</author>
+ <title type="main">The gentlemen of Venice</title>
+ <imprint>
+ <pubPlace>New York</pubPlace>
+ <publisher>Readex Microprint</publisher>
+ <date>1953</date>
+ </imprint>
+ <extent>1 microprint card, 23 x 15 cm.</extent>
+ </monogr>
+ <series>
+ <title>Three centuries of drama: English, 1642–1700</title>
+ </series>
+ <relatedItem type="otherForm">
+ <biblStruct>
+ <monogr>
+ <author>Shirley, James</author>
+ <title type="main">The gentlemen of Venice</title>
+ <title type="sub">a tragi-comedie presented at the private house in Salisbury
+ Court by Her Majesties servants</title>
+ <imprint>
+ <pubPlace>London</pubPlace>
+ <publisher>H. Moseley</publisher>
+ <date>1655</date>
+ </imprint>
+ <extent>78 p.</extent>
+ </monogr>
+ </biblStruct>
+ </relatedItem>
+</biblStruct>
Schematron
+<sch:report test="@target and count( child::* ) > 0">If the @target attribute on <sch:name/> is used, the
+ relatedItem element must be empty</sch:report>
+<sch:assert test="@target or child::*">A relatedItem element should have either a 'target' attribute
+ or a child element to indicate the related bibliographic item</sch:assert>
<relation> (relationship) describes any kind of
- relationship or linkage amongst a specified group of places,
- events, persons, objects or other items. [13.3.2.3. Personal Relationships]
1–∞ occurrences ofteidata.pointer
- separated by
- whitespace
-
-
-
-
-
-
active
-
identifies the
- ‘active’ participants in a non-mutual
- relationship, or all the participants in a mutual
- one.
-
-
-
Status
-
Optional
-
-
-
Schematron
-
- <sch:rule context="//tei:msDesc/tei:head//tei:relation/@active">
- <sch:let name="msDescURI"
- value="ancestor::tei:msDesc/tei:msIdentifier/tei:idno[@type='URI']/text()"/>
- <sch:assert test=". = $msDescURI"> The value
- of @active must match the <idno> in the
- containing <msDesc>:
- <sch:value-of select="$msDescURI"/>
- </sch:assert> </sch:rule>
- <sch:rule context="//tei:msPart/tei:head//tei:relation/@active">
- <sch:let name="msPartURI"
- value="ancestor::tei:msPart/tei:msIdentifier/tei:idno[@type='URI']/text()"/>
- <sch:assert test=". = $msPartURI"> The value
- of @active must match the <idno> in the
- containing <msPart>:
- <sch:value-of select="$msPartURI"/>
- </sch:assert> </sch:rule>
-
-
-
Datatype
-
1–∞ occurrences ofteidata.pointer
- separated by
- whitespace
-
-
-
-
-
-
mutual
-
supplies a
- list of participants amongst all of whom the
- relationship holds equally.
-
-
-
Status
-
Optional
-
-
-
Datatype
-
1–∞ occurrences ofteidata.pointer
- separated by
- whitespace
-
-
-
-
-
-
name
-
supplies a
- name for the kind of relationship of which this is
- an instance.
Only one of the attributes active and mutual may be supplied; the attribute passive may be supplied only if the
- attribute active is supplied. Not
- all of these constraints can be enforced in all schema
- languages.
This example records a relationship, defined by the SAWS
- ontology, between a passage of text identified by a CTS URN, and
- a variant passage of text in the Perseus Digital Library, and
- assigns the identification of the relationship to a particular
- editor (all using resolvable URIs).
-
-
-
Schematron
-
<s:assert test="@ref
- or @key or @name">One of the attributes 'name', 'ref' or
- 'key' must be supplied</s:assert>
-
-
-
Schematron
-
<!-- Note: this
- constraint is pointless in RELAX NG land, where the
- org=choice works. It is useful in DTD land, where the
- attList/@org has no effect. It looks to me like it is useful
- in W3C XML Schema land, too, which I find suprising, as I
- thought XSD could express a disjuntion like that w/o
- difficulty. (But I may be reading the XSD incorrectly.) —
- Syd, 2018-05-01 --> <s:report test="@active and
- @mutual">Only one of the attributes @active and @mutual
- may be supplied</s:report>
-
-
-
Schematron
-
- <s:report test="@passive and not(@active)">the
- attribute 'passive' may be supplied only if the attribute
- 'active' is supplied</s:report>
-
-
-
Content
- model
-
+}
2.1.157. <relation>
<relation> (relationship) describes any kind of relationship or linkage amongst a specified group of places, events, persons, objects or other items. [13.3.2.3. Personal Relationships]
identifies the ‘active’ participants in a non-mutual relationship, or all the participants in a mutual one.
Status
Optional
Schematron
+<sch:rule context="//tei:msDesc/tei:head//tei:relation/@active">
+<sch:let name="msDescURI"
+ value="ancestor::tei:msDesc/tei:msIdentifier/tei:idno[@type='URI']/text()"/>
+<sch:assert test=". = $msDescURI"> The value of @active
+ must match the <idno> in the containing
+ <msDesc>: <sch:value-of select="$msDescURI"/>
+</sch:assert>
+</sch:rule>
+<sch:rule context="//tei:msPart/tei:head//tei:relation/@active">
+<sch:let name="msPartURI"
+ value="ancestor::tei:msPart/tei:msIdentifier/tei:idno[@type='URI']/text()"/>
+<sch:assert test=". = $msPartURI"> The value of @active
+ must match the <idno> in the containing
+ <msPart>: <sch:value-of select="$msPartURI"/>
+</sch:assert>
+</sch:rule>
Only one of the attributes active and mutual may be supplied; the attribute passive may be supplied only if the attribute active is supplied. Not all of these constraints can be enforced in all schema languages.
This example records a relationship, defined by the SAWS ontology, between a passage of text identified by a CTS URN, and a variant passage of text in the Perseus Digital Library, and assigns the identification of the relationship to a particular editor (all using resolvable URIs).
Schematron
+<s:assert test="@ref or @key or @name">One of the attributes 'name', 'ref' or 'key' must be supplied</s:assert>
Schematron
+
+<!-- Note: this constraint is pointless in RELAX NG land, where the
+ org=choice works. It is useful in DTD land, where the attList/@org
+ has no effect. It looks to me like it is useful in W3C XML Schema
+ land, too, which I find suprising, as I thought XSD could express
+ a disjuntion like that w/o difficulty. (But I may be reading the
+ XSD incorrectly.) — Syd, 2018-05-01 -->
+<s:report test="@active and @mutual">Only one of the attributes @active and @mutual may be supplied</s:report>
Schematron
+<s:report test="@passive and not(@active)">the attribute 'passive' may be supplied only if the attribute 'active' is supplied</s:report>
element relation
{
attribute ref { list { + } },
- ( attribute active { list { + } }? | attribute mutual { list { + } }? ),
+ (
+ attribute active { list { + } }?
+ >>
+ tei:constraintSpec
+ [
+ ident = "active-on-relation"
+ scheme = "schematron"
+ " "
+ " "
+ " The value of @active must match the <idno> in the containing <msDesc>: "
+ " "
+ " "
+ " "
+ " The value of @active must match the <idno> in the containing <msPart>: "
+ ]
+ | attribute mutual { list { + } }?
+ ),
attribute name { text },
attribute passive { list { + } }?,
desc?
-}⚓
-
-
-
-
-
-
2.1.158. <repository>
-
-
-
-
<repository> (repository) contains the name of a
- repository within which manuscripts or other objects are
- stored, possibly forming part of an institution. [10.4. The Manuscript Identifier]
<repository> contains the name of a repository within which manuscripts or other objects are stored, possibly forming part of an institution. [10.4. The Manuscript Identifier]
The attribute ref, inherited from the class att.canonical may be used to
- indicate the kind of responsibility in a normalized form by
- referring directly to a standardized list of responsibility
- types, such as that maintained by a naming authority, for
- example the list maintained at http://www.loc.gov/marc/relators/relacode.html
- for bibliographic usage.
The attribute ref, inherited from the class att.canonical may be used to indicate the kind of responsibility in a normalized form by referring directly to a standardized list of responsibility types, such as that maintained by a naming authority, for example the list maintained at http://www.loc.gov/marc/relators/relacode.html for bibliographic usage.
<respStmt> (statement of
- responsibility) supplies a statement
- of responsibility for the intellectual content of a text,
- edition, recording, or series, where the specialized
- elements for authors, editors, etc. do not suffice or do not
- apply. May also be used to encode information about
- individuals or organizations which have played a role in the
- production or distribution of a bibliographic work.
- [3.12.2.2. Titles, Authors, and Editors
- 2.2.1. The Title Statement
- 2.2.2. The Edition Statement
- 2.2.5. The Series Statement]
<respStmt> (statement of responsibility) supplies a statement of responsibility for the intellectual content of a text, edition, recording, or series, where the specialized elements for authors, editors, etc. do not suffice or do not apply. May also be used to encode information about individuals or organizations which have played a role in the production or distribution of a bibliographic work. [3.11.2.2. Titles, Authors, and Editors2.2.1. The Title Statement2.2.2. The Edition Statement2.2.5. The Series Statement]
If present on this element, the status attribute should indicate the
- current status of the document. The same attribute may
- appear on any <change> to record the
- status at the time of that change. Conventionally <change> elements
- should be given in reverse date order, with the most recent
- change at the start of the list.
If present on this element, the status attribute should indicate the current status of the document. The same attribute may appear on any <change> to record the status at the time of that change. Conventionally <change> elements should be given in reverse date order, with the most recent change at the start of the list.
<rubric> (rubric) contains the text of any rubric or heading attached to a particular
- manuscript item, that is, a string of words through which a
- manuscript or other object signals the beginning of a text
- division, often with an assertion as to its author and
- title, which is in some way set off from the text itself,
- typically in red ink, or by use of different size or type of
- script, or some other such visual device. [10.6.1. The msItem and msItemStruct Elements]
- <sch:rule context="//tei:rubric/@xml:lang">
- <sch:let name="langIdents"
- value="//tei:profileDesc/tei:langUsage/tei:language/@ident"/>
- <sch:assert test=". = $langIdents">
- Attribute value must match one of the following
- language codes in the <profileDesc>:
- <sch:value-of select="string-join($langIdents,
- ' | ')"/>. </sch:assert>
- </sch:rule>
<rubric>Nu koma Skyckiu Rym<ex>ur</ex>.</rubric>
- <rubric>Incipit liber de
- consciencia humana a beatissimo Bernardo editus.</rubric>
- <rubric><locus>16. f. 28v in
- margin: </locus>Dicta
- Cassiodori </rubric>
<rubric> contains the text of any rubric or heading attached to a particular manuscript item, that is, a string of words through which a manuscript or other object signals the beginning of a text division, often with an assertion as to its author and title, which is in some way set off from the text itself, typically in red ink, or by use of different size or type of script, or some other such visual device. [10.6.1. The msItem and msItemStruct Elements]
+<sch:rule context="//tei:rubric/@xml:lang">
+<sch:let name="langIdents"
+ value="//tei:profileDesc/tei:langUsage/tei:language/@ident"/>
+<sch:assert test=". = $langIdents"> Attribute value must
+ match one of the following language codes in the
+ <profileDesc>: <sch:value-of select="string-join($langIdents, ' | ')"/>.
+</sch:assert>
+</sch:rule>
<rubric>Nu koma Skyckiu Rym<ex>ur</ex>.</rubric>
+<rubric>Incipit liber de consciencia humana a beatissimo Bernardo editus.</rubric>
+<rubric>
+ <locus>16. f. 28v in margin: </locus>Dicta Cassiodori
+</rubric>
<seal n="2" type="pendant" subtype="cauda_duplex"><p>The seal of <name>Jens Olufsen</name> in black wax. (<ref>DAS 1061</ref>). Legend: <q>S IOHANNES OLAVI</q>. Parchment tag on
- which is written: <q>Woldorp Iohanne G</q>.</p>
- </seal>
-
-
-
Content
- model
-
+}
2.1.166. <seal>
<seal> contains a description of one seal or similar applied to the object described [10.7.3.2. Seals]
<seal n="2" type="pendant"
+ subtype="cauda_duplex">
+ <p>The seal of <name>Jens Olufsen</name> in black wax.
+ (<ref>DAS 1061</ref>). Legend: <q>S IOHANNES OLAVI</q>.
+ Parchment tag on which is written: <q>Woldorp Iohanne G</q>.</p>
+</seal>
<sealDesc> (seal
- description) describes the seals or
- similar items related to the object described, either as a
- series of paragraphs or as a series of <seal>
- elements. [10.7.3.2. Seals]
<sealDesc><seal type="pendant" contemporary="true">
- <p>Green wax
- vertical oval seal attached at base.</p></seal>
- </sealDesc>
-
-
-
Example
-
<sealDesc><p>Parchment strip for seal in place; seal
- missing.</p>
- </sealDesc>
-
-
-
Content
- model
-
+}
2.1.167. <sealDesc>
<sealDesc> (seal description) describes the seals or similar items related to the object described, either as a series of paragraphs or as a series of <seal> elements. [10.7.3.2. Seals]
<secFol> (second folio)
- marks the word or words taken from a fixed
- point in a codex (typically the beginning of the second
- leaf) in order to provide a unique identifier for it.
- [10.3.7. Catchwords, Signatures, Secundo Folio]
- <sch:assert test="ancestor::tei:msDesc or
- ancestor::tei:egXML">The <sch:name/> element should
- not be used outside of msDesc.</sch:assert>
-
-
-
Content
- model
-
+}
2.1.168. <secFol>
<secFol> (second folio) marks the word or words taken from a fixed point in a codex (typically the beginning of the second leaf) in order to provide a unique identifier for it. [10.3.7. Catchwords, Signatures, Secundo Folio]
The <seg> element may be used
- at the encoder's discretion to mark any segments of the text
- of interest for processing. One use of the element is to
- mark text features for which no appropriate markup is
- otherwise defined. Another use is to provide an identifier
- for some segment which is to be pointed at by some other
- element—i.e. to provide a target, or a part of a target, for
- a <ptr> or other similar element.
-
-
-
Example
-
<seg>When are you leaving?</seg>
- <seg>Tomorrow.</seg>
-
-
-
Example
-
<s><seg rend="caps" type="initial-cap">So father's only</seg> glory was the
- ballfield. </s>
-
-
-
Example
-
<seg type="preamble">
- <seg>Sigmund, <seg type="patronym">the son of Volsung</seg>, was a king in
- Frankish country.</seg>
- <seg>Sinfiotli was
- the eldest of his sons ...</seg><seg>Borghild, Sigmund's wife, had a
- brother ... </seg>
- </seg>
The <seg> element may be used at the encoder's discretion to mark any segments of the text of interest for processing. One use of the element is to mark text features for which no appropriate markup is otherwise defined. Another use is to provide an identifier for some segment which is to be pointed at by some other element—i.e. to provide a target, or a part of a target, for a <ptr> or other similar element.
Example
<seg>When are you leaving?</seg>
+<seg>Tomorrow.</seg>
Example
<s>
+ <seg rend="caps" type="initial-cap">So father's only</seg> glory was the ballfield.
+</s>
Example
<seg type="preamble">
+ <seg>Sigmund, <seg type="patronym">the son of Volsung</seg>, was a king in Frankish country.</seg>
+ <seg>Sinfiotli was the eldest of his sons ...</seg>
+ <seg>Borghild, Sigmund's wife, had a brother ... </seg>
+</seg>
<settlement> (settlement) contains the name of a
- settlement such as a city, town, or village identified as a
- single geo-political or administrative unit. [13.2.3. Place Names]
<settlement> contains the name of a settlement such as a city, town, or village identified as a single geo-political or administrative unit. [13.2.3. Place Names]
for his nose was as sharp as a pen,
- and <sic>a Table</sic> of green
- fields.
-
-
-
Example
-
If all that is desired is to call
- attention to the apparent problem in the copy text, <sic> may be used alone:
I
- don't know, Juan. It's so far in the past now — how <sic>we can</sic> prove or disprove
- anyone's theories?
-
-
-
Example
-
It is also possible, using the <choice> and <corr> elements, to provide a
- corrected reading:
I don't know, Juan. It's so far in
- the past now — how <choice><sic>we can</sic><corr>can we</corr>
- </choice> prove or
- disprove anyone's theories?
-
-
-
Example
-
for his nose was as sharp as a pen,
- and <choice><sic>a Table</sic><corr>a' babbld</corr>
- </choice> of green
- fields.
for his nose was as sharp as
+ a pen, and <sic>a Table</sic> of green fields.
Example
If all that is desired is to call attention to the apparent problem in the copy text, <sic> may be used alone:
I don't know, Juan. It's so far in the past now
+ — how <sic>we can</sic> prove or disprove anyone's theories?
Example
It is also possible, using the <choice> and <corr> elements, to provide a corrected reading:
I don't know, Juan. It's so far in the past now
+ — how <choice>
+ <sic>we can</sic>
+ <corr>can we</corr>
+</choice> prove or disprove anyone's theories?
Example
for his nose was as sharp as
+ a pen, and <choice>
+ <sic>a Table</sic>
+ <corr>a' babbld</corr>
+</choice> of green fields.
<signatures>Quire and leaf signatures in
- letters, [b]-v, and roman numerals; those in quires 10 (1)
- and 17 (s) in red ink and different from others; every third
- quire also signed with red crayon in arabic numerals in the
- center lower margin of the first leaf recto: "2" for quire 4
- (f. 19), "3" for quire 7 (f. 43); "4," barely visible, for
- quire 10 (f. 65), "5," in a later hand, for quire 13 (f.
- 89), "6," in a later hand, for quire 16 (f. 113).</signatures>
-
-
-
Schematron
-
- <sch:assert test="ancestor::tei:msDesc or
- ancestor::tei:egXML">The <sch:name/> element should
- not be used outside of msDesc.</sch:assert>
<signatures>Quire and leaf signatures in letters, [b]-v, and roman
+ numerals; those in quires 10 (1) and 17 (s) in red ink and different
+ from others; every third quire also signed with red crayon in arabic
+ numerals in the center lower margin of the first leaf recto: "2" for
+ quire 4 (f. 19), "3" for quire 7 (f. 43); "4," barely visible, for
+ quire 10 (f. 65), "5," in a later hand, for quire 13 (f. 89), "6," in
+ a later hand, for quire 16 (f. 113).</signatures>
Schematron
+<sch:assert test="ancestor::tei:msDesc or ancestor::tei:egXML">The <sch:name/> element should not be used outside of msDesc.</sch:assert>
<sourceDesc> (source
- description) describes the source(s)
- from which an electronic text was derived or generated,
- typically a bibliographic description in the case of a
- digitized text, or a phrase such as "born digital" for a
- text which has no previous existence. [2.2.7. The Source Description]
<sourceDesc><bibl><title level="a">The Interesting story of the
- Children in the Wood</title>. In <author>Victor E Neuberg</author>, <title>The Penny
- Histories</title>.
- <publisher>OUP</publisher><date>1968</date>. </bibl>
- </sourceDesc>
-
-
-
Example
-
<sourceDesc><p>Born digital: no previous source
- exists.</p>
- </sourceDesc>
<sourceDesc> (source description) describes the source(s) from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as "born digital" for a text which has no previous existence. [2.2.7. The Source Description]
<sourceDesc>
+ <bibl>
+ <title level="a">The Interesting story of the Children in the Wood</title>. In
+ <author>Victor E Neuberg</author>, <title>The Penny Histories</title>.
+ <publisher>OUP</publisher>
+ <date>1968</date>. </bibl>
+</sourceDesc>
Example
<sourceDesc>
+ <p>Born digital: no previous source exists.</p>
+</sourceDesc>
Sponsors give their intellectual
- authority to a project; they are to be distinguished from
- funders (see element <funder>), who provide
- the funding but do not necessarily take intellectual
- responsibility.
-
-
-
Example
-
<sponsor>Association for Computers and the
- Humanities</sponsor>
- <sponsor>Association for
- Computational Linguistics</sponsor>
- <sponsor ref="http://www.allc.org/">Association
- for Literary and Linguistic Computing</sponsor>
Sponsors give their intellectual authority to a project; they are to be distinguished from funders (see element <funder>), who provide the funding but do not necessarily take intellectual responsibility.
Example
<sponsor>Association for Computers and the Humanities</sponsor>
+<sponsor>Association for Computational Linguistics</sponsor>
+<sponsor ref="http://www.allc.org/">Association for Literary and Linguistic Computing</sponsor>
<rubric>Apologyticu TTVLLIANI AC IGNORATIA
- IN XPO IHV<lb/> SI NON
- LICET<lb/> NOBIS
- RO<lb/> manii imperii
- <stamp>Bodleian
- stamp</stamp><lb/>
- </rubric>
<rubric>Apologyticu TTVLLIANI AC IGNORATIA IN XPO IHV<lb/>
+ SI NON LICET<lb/>
+ NOBIS RO<lb/>
+ manii imperii <stamp>Bodleian stamp</stamp>
+ <lb/>
+</rubric>
<street> contains a full
- street address including any name or number identifying a
- building as well as the name of the street or route on which
- it is located. [3.6.2. Addresses]
The order and presentation of house
- names and numbers and street names, etc., may vary
- considerably in different countries. The encoding should
- reflect the order which is appropriate in the country
- concerned.
<street> contains a full street address including any name or number identifying a building as well as the name of the street or route on which it is located. [3.5.2. Addresses]
The order and presentation of house names and numbers and street names, etc., may vary considerably in different countries. The encoding should reflect the order which is appropriate in the country concerned.
<subst> (substitution)
- groups one or more deletions (or surplus
- text) with one or more additions when the combination is to
- be regarded as a single intervention in the text. [11.3.1.5. Substitutions]
... are all included. <del hand="#RG">It is</del>
- <subst><add>T</add><del>t</del>
- </subst>he expressed
-
-
-
-
Example
-
that he and his Sister Miſs D —
- <lb/>who always lived
- with him, wd. be <subst>
- <del>very</del><lb/><add>principally</add>
- </subst> remembered in
- her Will.
- <s:assert test="child::tei:add and (child::tei:del or
- child::tei:surplus)"> <s:name/> must have at least
- one child add and at least one child del or
- surplus</s:assert>
<subst> (substitution) groups one or more deletions with one or more additions when the combination is to be regarded as a single intervention in the text. [11.3.1.5. Substitutions]
... are all included. <del hand="#RG">It is</del>
+<subst>
+ <add>T</add>
+ <del>t</del>
+</subst>he expressed
+
Example
that he and his Sister Miſs D — <lb/>who always lived with him, wd. be <subst>
+ <del>very</del>
+ <lb/>
+ <add>principally</add>
+</subst> remembered in her Will.
+
<summary> contains an overview
- of the available information concerning some aspect of an
- item or object (for example, its intellectual content,
- history, layout, typography etc.) as a complement or
- alternative to the more detailed information carried by more
- specific elements. [10.6. Intellectual Content]
<summary>This item consists of three books
- with a prologue and an epilogue. </summary>
-
-
-
Example
-
<typeDesc><summary>Uses a mixture of Roman and Black
- Letter types.</summary>
- <typeNote>Antiqua
- typeface, showing influence of Jenson's Venetian
- fonts.</typeNote>
- <typeNote>The black
- letter face is a variant of Schwabacher.</typeNote>
- </typeDesc>
<summary> contains an overview of the available information concerning some aspect of an item or object (for example, its intellectual content, history, layout, typography etc.) as a complement or alternative to the more detailed information carried by more specific elements. [10.6. Intellectual Content]
<summary>This item consists of three books with a prologue and an epilogue.
+</summary>
Example
<typeDesc>
+ <summary>Uses a mixture of Roman and Black Letter types.</summary>
+ <typeNote>Antiqua typeface, showing influence of Jenson's Venetian
+ fonts.</typeNote>
+ <typeNote>The black letter face is a variant of Schwabacher.</typeNote>
+</typeDesc>
<supplied> (supplied)
- signifies text supplied by the transcriber
- or editor for any reason; for example because the original
- cannot be read due to physical damage, or because of an
- obvious omission by the author or scribe. [11.3.3.1. Damage, Illegibility, and Supplied Text]
<supplied> signifies text supplied by the transcriber or editor for any reason; for example because the original cannot be read due to physical damage, or because of an obvious omission by the author or scribe. [11.3.3.1. Damage, Illegibility, and Supplied Text]
<support> (support)
- contains a description of the materials etc.
- which make up the physical support for the written part of a
- manuscript or other object. [10.7.1. Object Description]
<objectDesc form="roll"><supportDesc><support> Parchment roll with <material>silk</material> ribbons.
- </support></supportDesc>
- </objectDesc>
-
-
-
Content
- model
-
+}
2.1.182. <support>
<support> contains a description of the materials etc. which make up the physical support for the written part of a manuscript or other object. [10.7.1. Object Description]
<supportDesc> (support
- description) groups elements
- describing the physical support for the written part of a
- manuscript or other object. [10.7.1. Object Description]
<supportDesc><support> Parchment roll with <material>silk</material> ribbons. </support>
- </supportDesc>
-
-
-
Schematron
-
- <sch:rule see="https://msdesc.github.io/consolidated-tei-schema/msdesc.html#supportdesc"
- context="//tei:sourceDesc/tei:msDesc[not(tei:msPart)]">
- <sch:assert test="tei:physDesc/tei:objectDesc/tei:supportDesc[@material]"
- role="warn"> The material (parchment, paper, etc.) of a
- manuscript should be recorded in the supportDesc element,
- with a material attribute. </sch:assert>
- </sch:rule>
- <sch:rule context="//tei:sourceDesc/tei:msDesc/tei:msPart">
- <sch:assert test="
- tei:physDesc/tei:objectDesc/tei:supportDesc[@material] or
- ancestor::tei:msDesc/tei:physDesc/tei:objectDesc/tei:supportDesc[@material]
- " role="warn"> The material (parchment, paper, etc.) of
- each part should be recorded in the supportDesc element,
- with a material attribute, unless it has been described for
- the entire manuscript. </sch:assert>
- </sch:rule>
<supportDesc> (support description) groups elements describing the physical support for the written part of a manuscript or other object. [10.7.1. Object Description]
<supportDesc>
+ <support> Parchment roll with <material>silk</material> ribbons.
+ </support>
+</supportDesc>
Schematron
+<sch:rule see="https://msdesc.github.io/consolidated-tei-schema/msdesc.html#supportdesc"
+ context="//tei:sourceDesc/tei:msDesc[not(tei:msPart)]">
+<sch:assert test="tei:physDesc/tei:objectDesc/tei:supportDesc[@material]"
+ role="warn"> The material (parchment, paper, etc.) of a
+ manuscript should be recorded in the supportDesc element,
+ with a material attribute. </sch:assert>
+</sch:rule>
+<sch:rule context="//tei:sourceDesc/tei:msDesc/tei:msPart">
+<sch:assert test=" tei:physDesc/tei:objectDesc/tei:supportDesc[@material] or ancestor::tei:msDesc/tei:physDesc/tei:objectDesc/tei:supportDesc[@material]
+ "
+ role="warn"> The
+ material (parchment, paper, etc.) of each part should be
+ recorded in the supportDesc element, with a material
+ attribute, unless it has been described for the entire
+ manuscript. </sch:assert>
+</sch:rule>
<surface> defines a written
- surface as a two-dimensional coordinate space, optionally
- grouping one or more graphic representations of that space,
- zones of interest within that space, and transcriptions of
- the writing within them. [11.1. Digital Facsimiles
- 11.2.2. Embedded Transcription]
The <surface> element represents any
- two-dimensional space on some physical surface forming part
- of the source material, such as a piece of paper, a face of
- a monument, a billboard, a scroll, a leaf etc.
The
- coordinate space defined by this element may be thought of
- as a grid lrx - ulx units wide and uly
- - lry units high.
The <surface> element may
- contain graphic representations or transcriptions of written
- zones, or both. The coordinate values used by every <zone> element contained by this element are
- to be understood with reference to the same
- grid.
Where it is useful or meaningful to do so, any
- grouping of multiple <surface> elements may
- be indicated using the <surfaceGrp> element.
<surface> defines a written surface as a two-dimensional coordinate space, optionally grouping one or more graphic representations of that space, zones of interest within that space, and transcriptions of the writing within them. [11.1. Digital Facsimiles11.2.2. Embedded Transcription]
The <surface> element represents any two-dimensional space on some physical surface forming part of the source material, such as a piece of paper, a face of a monument, a billboard, a scroll, a leaf etc.
The coordinate space defined by this element may be thought of as a grid lrx - ulx units wide and uly - lry units high.
The <surface> element may contain graphic representations or transcriptions of written zones, or both. The coordinate values used by every <zone> element contained by this element are to be understood with reference to the same grid.
Where it is useful or meaningful to do so, any grouping of multiple <surface> elements may be indicated using the <surfaceGrp> element.
<surfaceGrp> defines any kind
- of useful grouping of written surfaces, for example the
- recto and verso of a single leaf, which the encoder wishes
- to treat as a single unit. [11.1. Digital Facsimiles]
<surfaceGrp> defines any kind of useful grouping of written surfaces, for example the recto and verso of a single leaf, which the encoder wishes to treat as a single unit. [11.1. Digital Facsimiles]
<surrogates> (surrogates) contains information
- about any representations of the manuscript or other object
- being described which may exist in the holding institution
- or elsewhere. [10.9. Additional Information]
<surrogates><bibl><title type="gmd">diapositive</title><idno>AM 74 a, fol.</idno><date>May 1984</date></bibl><bibl><title type="gmd">b/w prints</title><idno>AM 75 a, fol.</idno><date>1972</date></bibl>
- </surrogates>
-
-
-
Content
- model
-
+}
2.1.187. <surrogates>
<surrogates> contains information about any representations of the manuscript or other object being described which may exist in the holding institution or elsewhere. [10.9. Additional Information]
<taxonomy> (taxonomy)
- defines a typology either implicitly, by
- means of a bibliographic citation, or explicitly by a
- structured taxonomy. [2.3.7. The Classification Declaration]
<taxonomy> defines a typology either implicitly, by means of a bibliographic citation, or explicitly by a structured taxonomy. [2.3.7. The Classification Declaration]
One of the few elements unconditionally
- required in any TEI document.
-
-
-
Example
-
<teiHeader><fileDesc><titleStmt><title>Shakespeare: the first folio (1623)
- in electronic form</title><author>Shakespeare, William
- (1564–1616)</author>
- <respStmt>
- <resp>Originally
- prepared by</resp>
- <name>Trevor
- Howard-Hill</name>
- </respStmt>
- <respStmt>
- <resp>Revised and
- edited by</resp>
- <name>Christine
- Avern-Carr</name>
- </respStmt>
- </titleStmt>
- <publicationStmt>
- <distributor>Oxford Text Archive</distributor><address><addrLine>13 Banbury Road,
- Oxford OX2 6NN, UK</addrLine></address><idno type="OTA">119</idno><availability><p>Freely available on a non-commercial
- basis.</p></availability><date when="1968">1968</date></publicationStmt><sourceDesc><bibl>The first folio of Shakespeare,
- prepared by Charlton Hinman (The Norton Facsimile,
- 1968)</bibl></sourceDesc></fileDesc><encodingDesc><projectDesc><p>Originally prepared for
- use in the production of a series of old-spelling
- concordances in 1968, this text was extensively checked and
- revised for use during the editing of the new Oxford
- Shakespeare (Wells and Taylor, 1989).</p></projectDesc><editorialDecl><correction><p>Turned letters are silently
- corrected.</p>
- </correction>
- <normalization>
- <p>Original
- spelling and typography is retained, except that long s and
- ligatured forms are not encoded.</p></normalization></editorialDecl><refsDecl xml:id="ASLREF"><cRefPattern matchPattern="(\S+) ([^.]+)\.(.*)" replacementPattern="#xpath(//div1[@n='$1']/div2/[@n='$2']//lb[@n='$3'])">
- <p>A reference is
- created by assembling the following, in the reverse order as
- that listed here: <list><item>the <att>n</att> value of the preceding <gi>lb</gi></item><item>a period</item><item>the <att>n</att> value of the ancestor <gi>div2</gi></item><item>a space</item><item>the <att>n</att> value of the parent <gi>div1</gi></item></list></p></cRefPattern></refsDecl></encodingDesc><revisionDesc><list><item><date when="1989-04-12">12 Apr 89</date> Last checked by
- CAC</item><item><date when="1989-03-01">1 Mar 89</date> LB made new
- file</item></list></revisionDesc>
- </teiHeader>
One of the few elements unconditionally required in any TEI document.
Example
<teiHeader>
+ <fileDesc>
+ <titleStmt>
+ <title>Shakespeare: the first folio (1623) in electronic form</title>
+ <author>Shakespeare, William (1564–1616)</author>
+ <respStmt>
+ <resp>Originally prepared by</resp>
+ <name>Trevor Howard-Hill</name>
+ </respStmt>
+ <respStmt>
+ <resp>Revised and edited by</resp>
+ <name>Christine Avern-Carr</name>
+ </respStmt>
+ </titleStmt>
+ <publicationStmt>
+ <distributor>Oxford Text Archive</distributor>
+ <address>
+ <addrLine>13 Banbury Road, Oxford OX2 6NN, UK</addrLine>
+ </address>
+ <idno type="OTA">119</idno>
+ <availability>
+ <p>Freely available on a non-commercial basis.</p>
+ </availability>
+ <date when="1968">1968</date>
+ </publicationStmt>
+ <sourceDesc>
+ <bibl>The first folio of Shakespeare, prepared by Charlton Hinman (The Norton Facsimile,
+ 1968)</bibl>
+ </sourceDesc>
+ </fileDesc>
+ <encodingDesc>
+ <projectDesc>
+ <p>Originally prepared for use in the production of a series of old-spelling
+ concordances in 1968, this text was extensively checked and revised for use during the
+ editing of the new Oxford Shakespeare (Wells and Taylor, 1989).</p>
+ </projectDesc>
+ <editorialDecl>
+ <correction>
+ <p>Turned letters are silently corrected.</p>
+ </correction>
+ <normalization>
+ <p>Original spelling and typography is retained, except that long s and ligatured
+ forms are not encoded.</p>
+ </normalization>
+ </editorialDecl>
+ <refsDecl xml:id="ASLREF">
+ <cRefPattern matchPattern="(\S+) ([^.]+)\.(.*)"
+ replacementPattern="#xpath(//div1[@n='$1']/div2/[@n='$2']//lb[@n='$3'])">
+ <p>A reference is created by assembling the following, in the reverse order as that
+ listed here: <list>
+ <item>the <att>n</att> value of the preceding <gi>lb</gi>
+ </item>
+ <item>a period</item>
+ <item>the <att>n</att> value of the ancestor <gi>div2</gi>
+ </item>
+ <item>a space</item>
+ <item>the <att>n</att> value of the parent <gi>div1</gi>
+ </item>
+ </list>
+ </p>
+ </cRefPattern>
+ </refsDecl>
+ </encodingDesc>
+ <revisionDesc>
+ <list>
+ <item>
+ <date when="1989-04-12">12 Apr 89</date> Last checked by CAC</item>
+ <item>
+ <date when="1989-03-01">1 Mar 89</date> LB made new file</item>
+ </list>
+ </revisionDesc>
+</teiHeader>
When this element appears within an
- <index> element, it is
- understood to supply the form under which an index entry is
- to be made for that location. Elsewhere, it is understood
- simply to indicate that its content is to be regarded as a
- technical or specialised term. It may be associated with a
- <gloss> element by means
- of its ref attribute; alternatively
- a <gloss> element may point to
- a <term> element by means of its target attribute.
In formal
- terminological work, there is frequently discussion over
- whether terms must be atomic or may include multi-word
- lexical items, symbolic designations, or phraseological
- units. The <term> element may be
- used to mark any of these. No position is taken on the
- philosophical issue of what a term can be; the looser
- definition simply allows the <term>
- element to be used by practitioners of any
- persuasion.
As with other members of the att.canonical class,
- instances of this element occuring in a text may be
- associated with a canonical definition, either by means of a
- URI (using the ref attribute), or
- by means of some system-specific code value (using the key attribute). Because the mutually
- exclusive target and cRef attributes overlap with the
- function of the ref attribute, they
- are deprecated and may be removed at a subsequent
- release.
-
-
-
Example
-
A computational device that infers
- structure from grammatical strings of words is known as a
- <term>parser</term>, and much of the
- history of NLP over the last 20 years has been occupied with
- the design of parsers.
-
-
-
Example
-
We may define <term xml:id="TDPV1" rend="sc">discoursal point of view</term> as <gloss target="#TDPV1">the relationship,
- expressed through discourse structure, between the implied
- author or some other addresser, and the fiction.</gloss>
-
-
-
Example
-
We may define <term ref="#TDPV2" rend="sc">discoursal point of view</term> as <gloss xml:id="TDPV2">the relationship, expressed
- through discourse structure, between the implied author or
- some other addresser, and the fiction.</gloss>
-
-
-
Example
-
We discuss Leech's concept of <term ref="myGlossary.xml#TDPV2" rend="sc">discoursal point of view</term> below.
When this element appears within an <index> element, it is understood to supply the form under which an index entry is to be made for that location. Elsewhere, it is understood simply to indicate that its content is to be regarded as a technical or specialised term. It may be associated with a <gloss> element by means of its ref attribute; alternatively a <gloss> element may point to a <term> element by means of its target attribute.
In formal terminological work, there is frequently discussion over whether terms must be atomic or may include multi-word lexical items, symbolic designations, or phraseological units. The <term> element may be used to mark any of these. No position is taken on the philosophical issue of what a term can be; the looser definition simply allows the <term> element to be used by practitioners of any persuasion.
As with other members of the att.canonical class, instances of this element occuring in a text may be associated with a canonical definition, either by means of a URI (using the ref attribute), or by means of some system-specific code value (using the key attribute). Because the mutually exclusive target and cRef attributes overlap with the function of the ref attribute, they are deprecated and may be removed at a subsequent release.
Example
A computational device that infers structure
+ from grammatical strings of words is known as a <term>parser</term>, and much of the history
+ of NLP over the last 20 years has been occupied with the design of parsers.
Example
We may define <term xml:id="TDPV1" rend="sc">discoursal point of view</term> as
+<gloss target="#TDPV1">the relationship, expressed
+ through discourse structure, between the implied author or some other addresser, and the
+ fiction.</gloss>
Example
We may define <term ref="#TDPV2" rend="sc">discoursal point of view</term> as
+<gloss xml:id="TDPV2">the relationship, expressed
+ through discourse structure, between the implied author or some other addresser, and the
+ fiction.</gloss>
Example
We discuss Leech's concept of <term ref="myGlossary.xml#TDPV2" rend="sc">discoursal point of view</term> below.
<text> (text) contains a single text of any kind, whether
- unitary or composite, for example a poem or drama, a
- collection of essays, a novel, a dictionary, or a corpus
- sample. [4. Default Text Structure
- 15.1. Varieties of Composite Text]
This element should not be used to
- represent a text which is inserted at an arbitrary point
- within the structure of another, for example as in an
- embedded or quoted narrative; the <floatingText> is provided for this
- purpose.
-
-
-
Example
-
<text><front><docTitle><titlePart>Autumn Haze</titlePart></docTitle></front><body><l>Is it a dragonfly or a
- maple leaf</l><l>That settles softly down
- upon the water?</l>
- </body>
- </text>
-
-
-
Example
-
The body of a text may be replaced by a
- group of nested texts, as in the following schematic:
<text><front>
- <!-- front matter for the whole
- group --></front><group><text>
- <!-- first text -->
- </text><text>
- <!-- second text -->
- </text></group>
- </text>
This element should not be used to represent a text which is inserted at an arbitrary point within the structure of another, for example as in an embedded or quoted narrative; the <floatingText> is provided for this purpose.
Example
<text>
+ <front>
+ <docTitle>
+ <titlePart>Autumn Haze</titlePart>
+ </docTitle>
+ </front>
+ <body>
+ <l>Is it a dragonfly or a maple leaf</l>
+ <l>That settles softly down upon the water?</l>
+ </body>
+</text>
Example
The body of a text may be replaced by a group of nested texts, as in the following schematic:
<text>
+ <front>
+<!-- front matter for the whole group -->
+ </front>
+ <group>
+ <text>
+<!-- first text -->
+ </text>
+ <text>
+<!-- second text -->
+ </text>
+ </group>
+</text>
<textClass> (text
- classification) groups information
- which describes the nature or topic of a text in terms of a
- standard classification scheme, thesaurus, etc. [2.4.3. The Text Classification]
<taxonomy><category xml:id="acprose"><catDesc>Academic prose</catDesc></category>
- <!-- other categories here
- -->
- </taxonomy>
- <!-- ... -->
- <textClass><catRef target="#acprose"/><classCode scheme="http://www.udcc.org">001.9</classCode><keywords scheme="http://authorities.loc.gov">
- <list><item>End of the world</item><item>History -
- philosophy</item>
- </list></keywords>
- </textClass>
-
-
-
Content
- model
-
+}
2.1.193. <textClass>
<textClass> (text classification) groups information which describes the nature or topic of a text in terms of a standard classification scheme, thesaurus, etc. [2.4.3. The Text Classification]
(main
- language) supplies a code
- which identifies the chief language used in the
- bibliographic work.
-
-
-
Status
-
Required
-
-
-
Schematron
-
- <sch:rule context="//tei:textLang/@mainLang">
- <sch:let name="langIdents"
- value="//tei:profileDesc/tei:langUsage/tei:language/@ident"/>
- <sch:assert test=". = $langIdents">
- Attribute value must match one of the following
- language codes in the <profileDesc>:
- <sch:value-of select="string-join($langIdents,
- ' | ')"/>. </sch:assert>
- </sch:rule>
This element should not be used to
- document the languages or writing systems used for the
- bibliographic or manuscript description itself: as for all
- other TEI elements, such information should be provided by
- means of the global xml:lang
- attribute attached to the element containing the
- description.
In all cases, languages should be
- identified by means of a standardized ‘language tag’
- generated according to BCP 47.
- Additional documentation for the language may be provided by
- a <language> element in
- the TEI header.
-
-
-
Example
-
<textLang mainLang="en" otherLangs="la"> Predominantly in English with
- Latin glosses</textLang>
-
-
-
Schematron
-
- <sch:rule context="//tei:msItem">
- <sch:assert test=" tei:textLang or
- ancestor::tei:msContents/tei:textLang or
- ancestor::tei:msItem/tei:textLang or ( tei:msItem and (every
- $i in tei:msItem satisfies
- $i/descendant-or-self::tei:textLang) ) " role="warn">
- The language of each item should be recorded in a textLang
- element, unless it has been described for the entire
- manuscript or part. Use 'und' for undetermined or 'zxx' if
- there is no linguistic content. </sch:assert>
- </sch:rule> <sch:rule context="//tei:textLang">
- <sch:assert test="@mainLang and
- string-length(normalize-space(string())) gt 0"
- role="error"> The predominant language must be recorded
- in using a code in a mainLang attribute (and an otherLang
- attribute if there are other languages) and described as
- text within the textLang element. </sch:assert>
- </sch:rule>
(main language) supplies a code which identifies the chief language used in the bibliographic work.
Status
Required
Schematron
+<sch:rule context="//tei:textLang/@mainLang">
+<sch:let name="langIdents"
+ value="//tei:profileDesc/tei:langUsage/tei:language/@ident"/>
+<sch:assert test=". = $langIdents"> Attribute value must
+ match one of the following language codes in the
+ <profileDesc>: <sch:value-of select="string-join($langIdents, ' | ')"/>.
+</sch:assert>
+</sch:rule>
This element should not be used to document the languages or writing systems used for the bibliographic or manuscript description itself: as for all other TEI elements, such information should be provided by means of the global xml:lang attribute attached to the element containing the description.
In all cases, languages should be identified by means of a standardized ‘language tag’ generated according to BCP 47. Additional documentation for the language may be provided by a <language> element in the TEI header.
Example
<textLang mainLang="en" otherLangs="la"> Predominantly in English with Latin
+ glosses</textLang>
Schematron
+<sch:rule context="//tei:msItem">
+<sch:assert test=" tei:textLang or ancestor::tei:msContents/tei:textLang or ancestor::tei:msItem/tei:textLang
+ or ( tei:msItem and (every $i in tei:msItem satisfies $i/descendant-or-self::tei:textLang)
+ ) "
+ role="warn"> The
+ language of each item should be recorded in a textLang
+ element, unless it has been described for the entire
+ manuscript or part. Use 'und' for undetermined or 'zxx' if
+ there is no linguistic content. </sch:assert>
+</sch:rule>
+<sch:rule context="//tei:textLang">
+<sch:assert test="@mainLang and string-length(normalize-space(string())) gt 0"
+ role="error"> The predominant language must be recorded in
+ using a code in a mainLang attribute (and an otherLang
+ attribute if there are other languages) and described as
+ text within the textLang element. </sch:assert>
+</sch:rule>
element textLang
{
- attribute mainLang { text },
+ attribute mainLang { text }
+ >>
+ tei:constraintSpec
+ [
+ ident = "mainLang-on-textLang"
+ scheme = "schematron"
+ " "
+ " "
+ " Attribute value must match one of the following language codes in the <profileDesc>: "
+ "."
+ ],
attribute otherLangs { list { * } }?,
sic*,
text
-}⚓
- <sch:rule context="//tei:title/@xml:lang">
- <sch:let name="langIdents"
- value="//tei:profileDesc/tei:langUsage/tei:language/@ident"/>
- <sch:assert test=". = $langIdents">
- Attribute value must match one of the following
- language codes in the <profileDesc>:
- <sch:value-of select="string-join($langIdents,
- ' | ')"/>. </sch:assert>
- </sch:rule>
(alternate) alternate title, often in another
- language, by which the work is also
- known
-
short
-
abbreviated form of
- title
-
desc
-
(descriptive) descriptive paraphrase of the work
- functioning as a title
-
-
-
-
Note
-
This attribute is
- provided for convenience in analysing titles and
- processing them according to their type; where
- such specialized processing is not necessary,
- there is no need for such analysis, and the entire
- title, including subtitles and any parallel
- titles, may be enclosed within a single <title>
- element.
-
-
-
-
-
-
ref
-
(reference) provides an
- explicit means of locating a full definition or
- identity for the entity being named by means of
- one or more URIs.
- <sch:rule context="//tei:title/@ref">
- <sch:assert test="matches(.,
- 'http://syriaca.org/work/\d{1,5}$')"> The value
- of @ref must be a Syriaca.org work URI,
- "http://syriaca.org/work/" followed by 1-5 digits.
- Please confirm that this URI matches the correct
- work record. </sch:assert>
- </sch:rule>
-
-
-
Datatype
-
1–∞ occurrences ofteidata.pointer
- separated by
- whitespace
-
-
-
-
-
-
level
-
indicates the
- bibliographic level for a title, that is, whether
- it identifies an article, book, journal, series,
- or unpublished material.
(analytic) the title applies to an analytic item,
- such as an article, poem, or other work published
- as part of a larger item.
-
m
-
(monographic) the title applies to a monograph such as
- a book or other item considered to be a distinct
- publication, including single volumes of
- multi-volume works
-
j
-
(journal) the title applies to any serial or
- periodical publication such as a journal,
- magazine, or newspaper
-
s
-
(series) the title applies to a series of
- otherwise distinct publications such as a
- collection
-
u
-
(unpublished) the title applies to any unpublished
- material (including theses and dissertations
- unless published by a commercial
- press)
-
-
-
-
Note
-
The level of a title
- is sometimes implied by its context: for example,
- a title appearing directly within an <analytic>
- element is ipso facto
- of level ‘a’, and one
- appearing within a <series> element of level ‘s’. For this reason, the level attribute is not required
- in contexts where its value can be unambiguously
- inferred. Where it is supplied in such contexts,
- its value should not contradict the value implied
- by its parent element.
The attributes key and ref, inherited
- from the class att.canonical may be used to indicate the
- canonical form for the title; the former, by supplying (for
- example) the identifier of a record in some external library
- system; the latter by pointing to an XML element somewhere
- containing the canonical form of the title.
-
-
-
Example
-
<title>Information Technology and the
- Research Process: Proceedings of a conference held at
- Cranfield Institute of Technology, UK, 18–21 July 1989</title>
-
-
-
Example
-
<title>Hardy's Tess of the D'Urbervilles:
- a machine readable edition</title>
-
-
-
Example
-
<title type="full"><title type="main">Synthèse</title><title type="sub">an international journal for
- epistemology, methodology and history of science</title>
- </title>
-
-
-
Schematron
-
- <sch:rule context="tei:msItem/tei:title">
- <sch:assert test="@xml:lang"> This <title>
- element must have an @xml:lang attribute.
- </sch:assert> </sch:rule>
+<sch:rule context="//tei:title/@xml:lang">
+<sch:let name="langIdents"
+ value="//tei:profileDesc/tei:langUsage/tei:language/@ident"/>
+<sch:assert test=". = $langIdents"> Attribute value must
+ match one of the following language codes in the
+ <profileDesc>: <sch:value-of select="string-join($langIdents, ' | ')"/>.
+</sch:assert>
+</sch:rule>
(alternate) alternate title, often in another language, by which the work is also known
short
abbreviated form of title
desc
(descriptive) descriptive paraphrase of the work functioning as a title
Note
This attribute is provided for convenience in analysing titles and processing them according to their type; where such specialized processing is not necessary, there is no need for such analysis, and the entire title, including subtitles and any parallel titles, may be enclosed within a single <title> element.
ref
(reference) provides an explicit means of locating a full definition or identity for the entity being named by means of one or more URIs.
+<sch:rule context="//tei:title/@ref">
+<sch:assert test="matches(., 'http://syriaca.org/work/\d{1,5}$')"> The value of @ref must be a Syriaca.org work URI,
+ "http://syriaca.org/work/" followed by 1-5 digits.
+ Please confirm that this URI matches the correct
+ work record. </sch:assert>
+</sch:rule>
(analytic) the title applies to an analytic item, such as an article, poem, or other work published as part of a larger item.
m
(monographic) the title applies to a monograph such as a book or other item considered to be a distinct publication, including single volumes of multi-volume works
j
(journal) the title applies to any serial or periodical publication such as a journal, magazine, or newspaper
s
(series) the title applies to a series of otherwise distinct publications such as a collection
u
(unpublished) the title applies to any unpublished material (including theses and dissertations unless published by a commercial press)
Note
The level of a title is sometimes implied by its context: for example, a title appearing directly within an <analytic> element is ipso facto of level ‘a’, and one appearing within a <series> element of level ‘s’. For this reason, the level attribute is not required in contexts where its value can be unambiguously inferred. Where it is supplied in such contexts, its value should not contradict the value implied by its parent element.
The attributes key and ref, inherited from the class att.canonical may be used to indicate the canonical form for the title; the former, by supplying (for example) the identifier of a record in some external library system; the latter by pointing to an XML element somewhere containing the canonical form of the title.
Example
<title>Information Technology and the Research Process: Proceedings of
+ a conference held at Cranfield Institute of Technology, UK,
+ 18–21 July 1989</title>
Example
<title>Hardy's Tess of the D'Urbervilles: a machine readable
+ edition</title>
Example
<title type="full">
+ <title type="main">Synthèse</title>
+ <title type="sub">an international journal for
+ epistemology, methodology and history of
+ science</title>
+</title>
Schematron
+<sch:rule context="tei:msItem/tei:title">
+<sch:assert test="@xml:lang"> This <title> element must
+ have an @xml:lang attribute. </sch:assert>
+</sch:rule>
2.1.195. att.global.responsibility.attribute.cert,
att.global.source.attribute.source,
att.typed.attribute.subtype,
- attribute xml:lang { text }?,
+ attribute xml:lang { text }?
+ >>
+ tei:constraintSpec
+ [
+ ident = "xmlLang-on-title"
+ scheme = "schematron"
+ " "
+ " "
+ " Attribute value must match one of the following language codes in the <profileDesc>: "
+ "."
+ ],
attribute resp { list { + } }?,
attribute type { text }?,
- attribute ref { list { + } }?,
+ attribute ref { list { + } }?
+ >>
+ tei:constraintSpec
+ [
+ ident = "ref-on-title"
+ scheme = "schematron"
+ " "
+ """ The value of @ref must be a Syriaca.org work URI, "http://syriaca.org/work/" followed by 1-5 digits. Please confirm that this URI matches the correct work record."""
+ ],
attribute level { "a" | "m" | "j" | "s" | "u" }?,
( choice*, foreign*, locus*, quote*, sic*, supplied*, text )
-}⚓
<titleStmt><title>Capgrave's Life of St. John
- Norbert: a machine-readable transcription</title><respStmt><resp>compiled by</resp><name>P.J. Lucas</name></respStmt>
- </titleStmt>
<titleStmt>
+ <title>Capgrave's Life of St. John Norbert: a machine-readable transcription</title>
+ <respStmt>
+ <resp>compiled by</resp>
+ <name>P.J. Lucas</name>
+ </respStmt>
+</titleStmt>
<typeDesc> (typeface
- description) contains a description
- of the typefaces or other aspects of the printing of an
- incunable or other printed source. [10.7.2.1. Writing]
<typeDesc><p>Uses an unidentified black letter font,
- probably from the 15th century</p>
- </typeDesc>
-
-
-
Example
-
<typeDesc><summary>Contains a mixture of blackletter
- and Roman (antiqua) typefaces</summary><typeNote xml:id="Frak1">Blackletter face, showing
- similarities to those produced in Wuerzburg after
- 1470.</typeNote>
- <typeNote xml:id="Rom1">Roman
- face of Venetian origins.</typeNote>
- </typeDesc>
<typeDesc>
+ <p>Uses an unidentified black letter font, probably from the
+ 15th century</p>
+</typeDesc>
Example
<typeDesc>
+ <summary>Contains a mixture of blackletter and Roman (antiqua) typefaces</summary>
+ <typeNote xml:id="Frak1">Blackletter face, showing
+ similarities to those produced in Wuerzburg after 1470.</typeNote>
+ <typeNote xml:id="Rom1">Roman face of Venetian origins.</typeNote>
+</typeDesc>
<typeNote> (typographic
- note) describes a particular font or
- other significant typographic feature distinguished within
- the description of a printed resource. [10.7.2. Writing, Decoration, and Other Notations]
The same element is used for all cases
- of uncertainty in the transcription of element content,
- whether for written or spoken material. For other aspects of
- certainty, uncertainty, and reliability of tagging and
- transcription, see chapter 21. Certainty, Precision, and
- Responsibility.
The same element is used for all cases of uncertainty in the transcription of element content, whether for written or spoken material. For other aspects of certainty, uncertainty, and reliability of tagging and transcription, see chapter 21. Certainty, Precision, and Responsibility.
<width> (width) contains a measurement of an object along the axis
- parallel to its bottom, e.g. perpendicular to the spine of a
- book or codex. [10.3.4. Dimensions]
If used to specify the depth of a non
- text-bearing portion of some object, for example a monument,
- this element conventionally refers to the axis facing the
- observer, and perpendicular to that indicated by the ‘depth’
- axis.
<width> contains a measurement of an object along the axis parallel to its bottom, e.g. perpendicular to the spine of a book or codex. [10.3.4. Dimensions]
If used to specify the depth of a non text-bearing portion of some object, for example a monument, this element conventionally refers to the axis facing the observer, and perpendicular to that indicated by the ‘depth’ axis.
indicates the
- amount by which this zone has been rotated
- clockwise, with respect to the normal orientation
- of the parent <surface> element as implied by the
- dimensions given in the <msDesc> element or by the coordinates
- of the <surface>
- itself. The orientation is expressed in arc
- degrees.
The position of every zone for a given
- surface is always defined by reference to the coordinate
- system defined for that surface.
A graphic element
- contained by a zone represents the whole of the
- zone.
A zone may be of any shape. The attribute points may be used to define a
- polygonal zone, using the coordinate system defined by its
- parent surface.
A zone is always a closed polygon.
- Repeating the initial coordinate at the end of the sequence
- is optional. To encode an unclosed path, use the <path> element.
This
- example defines a zone which has been defined as larger than its
- parent surface in order to match the dimensions of the graphic
- it contains.
indicates the amount by which this zone has been rotated clockwise, with respect to the normal orientation of the parent <surface> element as implied by the dimensions given in the <msDesc> element or by the coordinates of the <surface> itself. The orientation is expressed in arc degrees.
The position of every zone for a given surface is always defined by reference to the coordinate system defined for that surface.
A graphic element contained by a zone represents the whole of the zone.
A zone may be of any shape. The attribute points may be used to define a polygonal zone, using the coordinate system defined by its parent surface.
A zone is always a closed polygon. Repeating the initial coordinate at the end of the sequence is optional. To encode an unclosed path, use the <path> element.
model.emphLikegroups phrase-level
- elements which are typographically distinct and to which a
- specific function can be attributed. [3.3. Highlighting and Quotation]
model.hiLikegroups phrase-level
- elements which are typographically distinct but to which no
- specific function can be attributed. [3.3. Highlighting and Quotation]
model.limitedPhrasegroups
- phrase-level elements excluding those elements primarily
- intended for transcription of existing sources. [1.3. The TEI Class System]
model.measureLikegroups elements
- which denote a number, a quantity, a measurement, or similar
- piece of text that conveys some numerical meaning.
- [3.6.3. Numbers and Measures]
model.pPart.editorialgroups
- phrase-level elements for simple editorial interventions
- that may be useful both in transcribing and in
- authoring. [3.5. Simple Editorial Changes]
model.pPart.transcriptionalgroups
- phrase-level elements used for editorial transcription of
- pre-existing source materials. [3.5. Simple Editorial Changes]
model.persStateLikegroups elements
- describing changeable characteristics of a person which have
- a definite duration, for example occupation, residence, or
- name.
This class of elements can occur within
- paragraphs, list items, lines of verse, etc.
-
-
-
-
-
-
2.2.46. model.phrase.xml
-
-
-
-
model.phrase.xmlgroups phrase-level
- elements used to encode XML constructs such as element
- names, attribute names, and attribute values [22. Documentation Elements]
model.respLikegroups elements which
- are used to indicate intellectual or other significant
- responsibility, for example within a bibliographic
- element.
The principles on which segmentation is
- carried out, and any special codes or attribute values used,
- should be defined explicitly in the <segmentation> element of the <encodingDesc>
- within the associated TEI header.
-
-
-
-
-
-
2.2.55. model.teiHeaderPart
-
-
-
-
model.teiHeaderPartgroups high
- level elements which may appear more than once in a TEI
- header.
model.titlepagePartgroups elements
- which can occur as direct constituents of a title page, such
- as <docTitle>, <docAuthor>, <docImprint>, or <epigraph>. [4.6. Title Pages]
att.breakingprovides attributes to
- indicate whether or not the element concerned is considered
- to mark the end of an orthographic token in the same way as
- whitespace. [3.11.3. Milestone Elements]
indicates
- whether or not the element bearing this attribute
- should be considered to mark the end of an
- orthographic token in the same way as
- whitespace.
the element bearing this
- attribute is considered to mark the end of any
- adjacent orthographic token irrespective of the
- presence of any adjacent whitespace
-
no
-
the element bearing this
- attribute is considered not to mark the end of any
- adjacent orthographic token irrespective of the
- presence of any adjacent whitespace
-
maybe
-
the encoding does not take any
- position on this issue.
-
-
-
-
In the following lines from the Dream of the Rood, linebreaks
- occur in the middle of the words lāðost and reord-berendum.
(canonical
- reference) specifies the
- destination of the pointer by supplying a
- canonical reference expressed using the scheme
- defined in a <refsDecl> element in the TEI
- header
The value of cRef should be constructed so
- that when the algorithm for the resolution of
- canonical references (described in section 16.2.5. Canonical References) is applied to
- it the result is a valid URI reference to the
- intended target.
The <refsDecl> to use may be indicated
- with the decls
- attribute.
Currently these Guidelines only
- provide for a single canonical reference to be
- encoded on any given <ptr> element.
-
-
-
-
-
-
-
-
-
-
-
-
2.3.3. att.canonical
-
-
-
-
att.canonicalprovides attributes
- that can be used to associate a representation such as a
- name or title with canonical information about the object
- being named or referenced. [13.1.1. Linking Names and Their Referents]
The value must point
- directly to one or more XML elements or other
- resources by means of one or more URIs, separated
- by whitespace. If more than one is supplied the
- implication is that the name identifies several
- distinct entities.
-
-
-
-
-
-
-
-
-
-
-
-
2.3.4. att.citing
-
-
-
-
att.citingprovides attributes for
- specifying the specific part of a bibliographic item being
- cited. [1.3.1. Attribute Classes]
identifies a
- two dimensional area by means of a series of pairs
- of numbers, each of which gives the x,y
- coordinates of a point on a line enclosing the
- area.
-
-
-
Status
-
Optional
-
-
-
Datatype
-
3–∞ occurrences ofteidata.point
- separated by
- whitespace
-
-
-
-
-
-
-
-
-
-
-
-
2.3.6. att.datable
-
-
-
-
att.datableprovides attributes for
- normalization of elements that contain dates, times, or
- datable events. [3.6.4. Dates and Times
- 13.4. Dates]
indicates one
- or more systems or calendars to which the date
- represented by the content of this element
- belongs.
-
-
-
Status
-
Optional
-
-
-
Datatype
-
1–∞ occurrences ofteidata.pointer
- separated by
- whitespace
-
-
-
Schematron
-
- <sch:rule context="tei:*[@calendar]">
- <sch:assert test="string-length(.) gt 0">
- @calendar indicates one or more systems or
- calendars to which the date represented by the
- content of this element belongs, but this
- <sch:name/> element has no textual
- content.</sch:assert>
- </sch:rule>
-
-
-
He was born on <date calendar="#gregorian">Feb. 22, 1732</date> (<date calendar="#julian" when="1732-02-22">Feb. 11, 1731/32,
- O.S.</date>).
-
-
-
-
He was born on <date calendar="#gregorian #julian" when="1732-02-22">Feb. 22, 1732 (Feb.
- 11, 1731/32, O.S.)</date>.
-
-
-
Note
-
Note that the calendar attribute (unlike
- datingMethod defined in
- att.datable.custom) defines the calendar
- system of the date in the original material
- defined by the parent element, not the
- calendar to which the date is normalized.
-
-
-
-
-
-
period
-
supplies
- pointers to one or more definitions of named
- periods of time (typically <category>s or <calendar>s) within which the
- datable item is understood to have
- occurred.
-
-
-
Status
-
Optional
-
-
-
Datatype
-
1–∞ occurrences ofteidata.pointer
- separated by
- whitespace
-
-
-
-
-
-
-
-
-
Note
-
This ‘superclass’ provides attributes
- that can be used to provide normalized values of temporal
- information. By default, the attributes from the att.datable.w3c class are
- provided. If the module for names & dates is loaded,
- this class also provides attributes from the att.datable.iso and att.datable.custom classes.
- In general, the possible values of attributes restricted to
- the W3C datatypes form a subset of those values available
- via the ISO 8601 standard. However, the greater
- expressiveness of the ISO datatypes may not be needed, and
- there exists much greater software support for the W3C
- datatypes.
-
-
-
-
-
-
2.3.7. att.datable.custom
-
-
-
-
att.datable.customprovides
- attributes for normalization of elements that contain
- datable events to a custom dating system (i.e. other than
- the Gregorian used by W3 and ISO). [13.4. Dates]
supplies the
- value of a date or time in some custom standard
- form.
-
-
-
Status
-
Optional
-
-
-
Datatype
-
1–∞ occurrences ofteidata.word
- separated by
- whitespace
-
-
-
The following are examples of
- custom date or time formats that are not
- valid ISO or W3C format normalizations, normalized
- to a different dating system
<p>Alhazen died in Cairo on the
- <date when="1040-03-06" when-custom="431-06-12"> 12th day of Jumada
- t-Tania, 430 AH </date>.</p>
- <p>The current
- world will end at the <date when="2012-12-21" when-custom="13.0.0.0.0">end of B'ak'tun
- 13</date>.</p>
- <p>The Battle
- of Meggidu (<date when-custom="Thutmose_III:23">23rd year of
- reign of Thutmose III</date>).</p>
- <p>Esidorus
- bixit in pace annos LXX plus minus sub <date when-custom="Ind:4-10-11">die XI mensis
- Octobris indictione IIII</date>
- </p>
Not
- all custom date formulations will have Gregorian
- equivalents.The when-custom attribute and other custom
- dating are not constrained to a datatype by the
- TEI, but individual projects are recommended to
- regularize and document their dating formats.
-
-
-
-
-
-
notBefore-custom
-
specifies the
- earliest possible date for the event in some
- custom standard form.
-
-
-
Status
-
Optional
-
-
-
Datatype
-
1–∞ occurrences ofteidata.word
- separated by
- whitespace
-
-
-
-
-
-
notAfter-custom
-
specifies the
- latest possible date for the event in some custom
- standard form.
-
-
-
Status
-
Optional
-
-
-
Datatype
-
1–∞ occurrences ofteidata.word
- separated by
- whitespace
-
-
-
-
-
-
from-custom
-
indicates the
- starting point of the period in some custom
- standard form.
-
-
-
Status
-
Optional
-
-
-
Datatype
-
1–∞ occurrences ofteidata.word
- separated by
- whitespace
-
-
-
<event xml:id="FIRE1" datingMethod="#julian" from-custom="1666-09-02" to-custom="1666-09-05"><head>The Great Fire
- of London</head><p>The Great Fire of London burned
- through a large part of the city of
- London.</p>
- </event>
-
-
-
-
-
-
to-custom
-
indicates the
- ending point of the period in some custom standard
- form.
-
-
-
Status
-
Optional
-
-
-
Datatype
-
1–∞ occurrences ofteidata.word
- separated by
- whitespace
-
-
-
-
-
-
datingPoint
-
supplies a
- pointer to some location defining a named point in
- time with reference to which the datable item is
- understood to have occurred
Contayning the Originall,
- Antiquity, Increaſe, Moderne eſtate, and
- deſcription of that Citie, written in the yeare
- <date when-custom="1598" calendar="#julian" datingMethod="#julian">1598</date>. by Iohn Stow
- Citizen of London.
In this example, the calendar attribute points to a
- <calendar> element
- for the Julian calendar, specifying that the text
- content of the <date> element is a Julian date, and
- the datingMethod
- attribute also points to the Julian calendar to
- indicate that the content of the when-custom attribute value is Julian
- too.
In
- this example, a date is given in a Mediaeval text
- measured "from the creation of the world", which
- is normalised (in when)
- to the Gregorian date, but is also normalized (in
- when-custom) to a
- machine-actionable, numeric version of the date
- from the Creation.
-
-
-
Note
-
Note that the datingMethod attribute (unlike
- calendar defined in att.datable) defines
- the calendar or dating system to which the date
- described by the parent element is normalized
- (i.e. in the when-custom
- or other X-custom
- attributes), not the calendar of the
- original date in the element.
-
-
-
-
-
-
-
-
-
-
-
-
2.3.8. att.datable.iso
-
-
-
-
att.datable.isoprovides attributes
- for normalization of elements that contain datable events
- using the ISO 8601 standard. [3.6.4. Dates and Times
- 13.4. Dates]
The following are examples of ISO
- date, time, and date & time formats that are
- not valid W3C format normalizations.
<date when-iso="1996-09-24T07:25+00">Sept. 24th,
- 1996 at 3:25 in the morning</date>
- <date when-iso="1996-09-24T03:25-04">Sept. 24th,
- 1996 at 3:25 in the morning</date>
- <time when-iso="1999-01-04T20:42-05">4 Jan 1999
- at 8:42 pm</time>
- <time when-iso="1999-W01-1T20,70-05">4 Jan 1999
- at 8:42 pm</time>
- <date when-iso="2006-05-18T10:03">a few minutes
- after ten in the morning on Thu 18 May</date>
- <time when-iso="03:00">3
- A.M.</time>
- <time when-iso="14">around
- two</time>
- <time when-iso="15,5">half
- past three</time>
All of the examples of
- the when attribute in the
- att.datable.w3c
- class are also valid with respect to this
- attribute.
-
-
-
He likes to be punctual. I
- said <q><time when-iso="12">around noon</time>
- </q>, and he
- showed up at <time when-iso="12:00:00">12 O'clock</time> on the
- dot.
The second occurence of <time> could have been encoded with
- the when attribute, as
- 12:00:00 is a valid time
- with respect to the W3C XML
- Schema Part 2: Datatypes Second Edition
- specification. The first occurence could not.
-
-
-
-
-
-
notBefore-iso
-
specifies the
- earliest possible date for the event in standard
- form, e.g. yyyy-mm-dd.
The value of these attributes should be
- a normalized representation of the date, time, or combined
- date & time intended, in any of the standard formats
- specified by ISO 8601, using the Gregorian calendar.
If both when-iso and
- dur-iso are specified, the
- values should be interpreted as indicating a span of time by
- its starting time (or date) and duration. That is,
- <date when-iso="2007-06-01" dur-iso="P8D"/>
-
indicates the same time period as
- <date when-iso="2007-06-01/P8D"/>
-
In providing a ‘regularized’ form, no claim
- is made that the form in the source text is incorrect; the
- regularized form is simply that chosen as the main form for
- purposes of unifying variant forms under a single
- heading.
-
-
-
-
-
-
2.3.9. att.datable.w3c
-
-
-
-
att.datable.w3cprovides attributes
- for normalization of elements that contain datable events
- conforming to the W3C XML Schema Part
- 2: Datatypes Second Edition. [3.6.4. Dates and Times
- 13.4. Dates]
Examples of W3C date, time, and
- date & time formats.
<p><date when="1945-10-24">24 Oct 45</date><date when="1996-09-24T07:25:00Z">September
- 24th, 1996 at 3:25 in the morning</date><time when="1999-01-04T20:42:00-05:00">Jan 4
- 1999 at 8 pm</time><time when="14:12:38">fourteen twelve and 38
- seconds</time>
- <date when="1962-10">October of 1962</date><date when="--06-12">June 12th</date><date when="---01">the first of the
- month</date>
- <date when="--08">August</date><date when="2006">MMVI</date><date when="0056">AD 56</date><date when="-0056">56 BC</date>
- </p>
-
-
-
This list begins in the
- year 1632, more precisely on Trinity Sunday, i.e.
- the Sunday after Pentecost, in that year the <date calendar="#julian" when="1632-06-06">27th of May (old
- style)</date>.
- <sch:rule context="//*[not(self::tei:locus or
- self::tei:biblScope or self::tei:citedRange)] [(@notBefore
- and @notAfter) or (@from and @to)]"> <sch:let name="f"
- value="(@notBefore,@from)[1]"/> <sch:let name="t"
- value="(@notAfter,@to)[1]"/>
- <sch:let name="bothdates" value="$f castable as xs:date
- and $t castable as xs:date"/>
- <sch:let name="bothyears" value="$f castable as
- xs:integer and $t castable as xs:integer"/>
- <sch:let name="fd" value="if ($bothdates) then
- xs:date($f) else ()"/> <sch:let name="td" value="if
- ($bothdates) then xs:date($t) else ()"/>
- <sch:let name="fy" value="if ($bothyears) then
- xs:integer($f) else ()"/> <sch:let name="ty"
- value="if ($bothyears) then xs:integer($t) else ()"/>
- <sch:report test="($bothdates and $fd gt $td) or
- ($bothyears and $fy gt $ty)" role="error"> The date
- range
- <sch:value-of select="$f"/>–<sch:value-of select="$t"/>
- in <sch:value-of select="name(.)"/> is not valid.
- </sch:report> </sch:rule>
-
-
-
Schematron
-
- <sch:rule context="tei:*[@when]">
- <sch:report test="@notBefore|@notAfter|@from|@to"
- role="nonfatal">The @when attribute cannot be used with
- any other att.datable.w3c attributes.</sch:report>
- </sch:rule>
-
-
-
Schematron
-
- <sch:rule context="tei:*[@from]">
- <sch:report test="@notBefore" role="nonfatal">The
- @from and @notBefore attributes cannot be used
- together.</sch:report> </sch:rule>
-
-
-
Schematron
-
- <sch:rule context="tei:*[@to]">
- <sch:report test="@notAfter" role="nonfatal">The @to
- and @notAfter attributes cannot be used
- together.</sch:report> </sch:rule>
-
-
-
Example
-
<date from="1863-05-28" to="1863-06-01">28 May through 1 June
- 1863</date>
-
-
-
Note
-
The value of these attributes should be
- a normalized representation of the date, time, or combined
- date & time intended, in any of the standard formats
- specified by XML Schema Part 2:
- Datatypes Second Edition, using the Gregorian
- calendar.
The most commonly-encountered format for the
- date portion of a temporal attribute is
- yyyy-mm-dd, but yyyy,
- --mm, ---dd,
- yyyy-mm, or --mm-dd may also
- be used. For the time part, the form hh:mm:ss
- is used.
Note that this format does not currently
- permit use of the value 0000 to
- represent the year 1 BCE; instead the value -0001 should be used.
-
-
-
-
-
-
2.3.10. att.datcat
-
-
-
-
att.datcatprovides attributes that
- are used to align XML elements or attributes with the
- appropriate Data Categories (DCs) defined by the ISO
- 12620:2009 standard and stored in the Web repository called
- ISOCat at http://www.isocat.org/. [9.5.2. Lexical View
- 18.3. Other Atomic Feature Values]
contains a PID
- (persistent identifier) that aligns the given
- element with the appropriate Data Category (or
- categories) in ISOcat.
-
-
-
Status
-
Optional
-
-
-
Datatype
-
1–∞ occurrences ofteidata.pointer
- separated by
- whitespace
-
-
-
-
-
-
valueDatcat
-
contains a PID
- (persistent identifier) that aligns the content of
- the given element or the value of the given
- attribute with the appropriate simple Data
- Category (or categories) in ISOcat.
-
-
-
Status
-
Optional
-
-
-
Datatype
-
1–∞ occurrences ofteidata.pointer
- separated by
- whitespace
-
-
-
-
-
-
-
-
-
Example
-
In this example dcr:datcat relates the feature name to the data
- category "partOfSpeech" and dcr:valueDatcat the feature value to the data
- category "commonNoun". Both these data categories reside in the
- ISOcat DCR at www.isocat.org, which is the DCR used by ISO TC37 and
- hosted by its registration authority, the MPI for
- Psycholinguistics in Nijmegen.
ISO 12620:2009 is a standard describing
- the data model and procedures for a Data Category Registry
- (DCR). Data categories are defined as elementary descriptors
- in a linguistic structure. In the DCR data model each data
- category gets assigned a unique Peristent IDentifier (PID),
- i.e., an URI. Linguistic resources or preferably their
- schemas that make use of data categories from a DCR should
- refer to them using this PID. For XML-based resources, like
- TEI documents, ISO 12620:2009 normative Annex A gives a
- small Data Category Reference XML vocabulary (also available
- online at http://www.isocat.org/12620/),
- which provides two attributes, dcr:datcat and dcr:valueDatcat.
-
-
-
-
-
-
2.3.11. att.declarable
-
-
-
-
att.declarableprovides attributes
- for those elements in the TEI header which may be
- independently selected by means of the special purpose decls attribute. [15.3. Associating Contextual Information with a
- Text]
This element is selected if
- its parent is selected
-
false
-
This element can only be
- selected explicitly, unless it is the only one of
- its kind, in which case it is selected if its
- parent is selected.[Default]
-
-
-
-
-
-
-
-
-
-
Note
-
The rules governing the association of
- declarable elements with individual parts of a TEI text are
- fully defined in chapter 15.3. Associating Contextual Information with a
- Text. Only one element of a particular type may have
- a default attribute with a value of
- true.
-
-
-
-
-
-
2.3.12. att.declaring
-
-
-
-
att.declaringprovides attributes
- for elements which may be independently associated with a
- particular declarable element within the header, thus
- overriding the inherited default for that element.
- [15.3. Associating Contextual Information with a
- Text]
identifies one
- or more declarable
- elements within the header, which are
- understood to apply to the element bearing this
- attribute and its content.
-
-
-
Status
-
Optional
-
-
-
Datatype
-
1–∞ occurrences ofteidata.pointer
- separated by
- whitespace
The members of this attribute class are
- typically used to represent any kind of editorial
- intervention in a text, for example a correction or
- interpretation, or to date or localize manuscripts
- etc.
Each pointer on the source (if present) corresponding to a witness
- or witness group should reference a bibliographic citation
- such as a <witness>, <msDesc>, or <bibl> element, or another external
- bibliographic citation, documenting the source
- concerned.
-
-
-
-
-
-
2.3.17. att.edition
-
-
-
-
att.editionprovides attributes
- identifying the source edition from which some encoded
- feature derives.
(edition) supplies a sigil
- or other arbitrary identifier for the source
- edition in which the associated feature (for
- example, a page, column, or line break) occurs at
- this point in the text.
-
-
-
Status
-
Optional
-
-
-
Datatype
-
1–∞ occurrences ofteidata.word
- separated by
- whitespace
-
-
-
-
-
-
edRef
-
(edition
- reference) provides a
- pointer to the source edition in which the
- associated feature (for example, a page, column,
- or line break) occurs at this point in the
- text.
-
-
-
Status
-
Optional
-
-
-
Datatype
-
1–∞ occurrences ofteidata.pointer
- separated by
- whitespace
-
-
-
-
-
-
-
-
-
Example
-
<l>Of Mans First Disobedience,<lb ed="1674"/> and<lb ed="1667"/> the
- Fruit</l>
- <l>Of that Forbidden
- Tree, whose<lb ed="1667 1674"/>
- mortal tast</l>
- <l>Brought Death into the
- World,<lb ed="1667"/> and
- all<lb ed="1674"/> our woe,</l>
-
-
-
Example
-
<listBibl><bibl xml:id="stapledon1937"><author>Olaf Stapledon</author>, <title>Starmaker</title>, <publisher>Methuen</publisher>, <date>1937</date></bibl><bibl xml:id="stapledon1968"><author>Olaf Stapledon</author>, <title>Starmaker</title>, <publisher>Dover</publisher>, <date>1968</date></bibl>
- </listBibl>
- <!-- ... -->
- <p>Looking into the
- future aeons from the supreme moment of the cosmos, I saw
- the populations still with all their strength maintaining
- the<pb n="411" edRef="#stapledon1968"/>essentials of
- their ancient culture, still living their personal lives in
- zest and endless novelty of action, … I saw myself still
- preserving, though with increasing difficulty, my lucid
- con-<pb n="291" edRef="#stapledon1937"/>sciousness;</p>
-
-
-
-
-
-
2.3.18. att.fragmentable
-
-
-
-
att.fragmentableprovides attributes
- for representing fragmentation of a structural element,
- typically as a consequence of some overlapping
- hierarchy.
specifies
- whether or not its parent element is fragmented in
- some way, typically by some other overlapping
- structure: for example a speech which is divided
- between two or more verse stanzas, a paragraph
- which is split across a page division, a verse
- line which is divided between two
- speakers.
The value of this
- attribute is always understood to be a single
- token, even if it contains space or other
- punctuation characters, and need not be composed
- of numbers only. It is typically used to specify
- the numbering of chapters, sections, list items,
- etc.; it may also be used in the specification of
- a standard reference system for the text.
-
-
-
-
-
-
xml:lang
-
(language) indicates the
- language of the element content using a ‘tag’
- generated according to BCP 47.
<p> … The consequences of this rapid
- depopulation were the loss of the last <foreign xml:lang="rap">ariki</foreign> or chief (Routledge
- 1920:205,210) and their connections to ancestral
- territorial organization.</p>
-
-
-
Note
-
The xml:lang value will be inherited from the
- immediately enclosing element, or from its parent,
- and so on up the document hierarchy. It is
- generally good practice to specify xml:lang at the highest
- appropriate level, noticing that a different
- default may be needed for the <teiHeader> from that needed for the
- associated resource element or elements, and that
- a single TEI document may contain texts in many
- languages.
Only attributes with free text
- values (rare in these guidelines) will be in the
- scope of xml:lang.
The
- value used must conform with BCP 47. If the value
- is a private use code (i.e., starts with x- or contains -x-), a <language> element with a matching
- value for its ident
- attribute should be supplied in the TEI header to
- document this value. Such documentation may also
- optionally be supplied for non-private-use codes,
- though these must remain consistent with their
- (IETF)Internet Engineering Task
- Force definitions.
-
-
-
-
-
-
xml:base
-
provides a
- base URI reference with which applications can
- resolve relative URI references into absolute URI
- references.
signals that the application's
- default white-space processing modes are
- acceptable
-
preserve
-
indicates the intent that
- applications preserve all white space
-
-
-
-
Note
-
The XML specification provides further guidance
- on the use of this attribute. Note that many
- parsers may not handle xml:space
- correctly.
-
-
-
-
-
-
-
-
-
-
-
-
2.3.20. att.global.change
-
-
-
-
att.global.changeprovides
- attributes allowing its member elements to specify one or
- more states or revision campaigns with which they are
- associated.
points to one
- or more <change> elements
- documenting a state or revision campaign to which
- the element bearing this attribute and its
- children have been assigned by the
- encoder.
-
-
-
Status
-
Optional
-
-
-
Datatype
-
1–∞ occurrences ofteidata.pointer
- separated by
- whitespace
-
-
-
-
-
-
-
-
-
-
-
-
2.3.21. att.global.facs
-
-
-
-
att.global.facsprovides attributes
- used to express correspondence between an element and all or
- part of a facsimile image or surface. [11.1. Digital Facsimiles]
(corresponds) points to
- elements that correspond to the current element in
- some way.
-
-
-
Status
-
Optional
-
-
-
Datatype
-
1–∞ occurrences ofteidata.pointer
- separated by
- whitespace
-
-
-
<group><text xml:id="t1-g1-t1" xml:lang="mi"><body xml:id="t1-g1-t1-body1"><div type="chapter"><head>He
- Whakamaramatanga mo te Ture Hoko, Riihi hoki, i
- nga Whenua Maori, 1876.</head><p>…</p></div></body></text><text xml:id="t1-g1-t2" xml:lang="en"><body xml:id="t1-g1-t2-body1" corresp="#t1-g1-t1-body1"><div type="chapter"><head>An Act to
- regulate the Sale, Letting, and Disposal of Native
- Lands, 1876.</head><p>…</p></div></body></text>
- </group>
In this example a
- <group> contains two
- <text>s, each
- containing the same document in a different
- language. The correspondence is indicated using
- corresp. The language is
- indicated using xml:lang,
- whose value is inherited; both the tag with the
- corresp and the tag
- pointed to by the corresp
- inherit the value from their immediate
- parent.
-
-
-
- <!-- In a placeography
- called "places.xml" --><place xml:id="LOND1" corresp="people.xml#LOND2
- people.xml#GENI1"><placeName>London</placeName><desc>The city of
- London...</desc>
- </place>
- <!-- In a literary
- personography called "people.xml" -->
- <person xml:id="LOND2" corresp="places.xml#LOND1
- #GENI1"><persName type="lit">London</persName><note><p>Allegorical character
- representing the city of <placeName ref="places.xml#LOND1">London</placeName>.</p></note>
- </person>
- <person xml:id="GENI1" corresp="places.xml#LOND1
- #LOND2"><persName type="lit">London’s Genius</persName><note><p>Personification of
- London’s genius. Appears as an allegorical
- character in mayoral shows. </p></note>
- </person>
In this example, a <place> element
- containing information about the city of London is
- linked with two <person> elements in a literary
- personography. This correspondence represents a
- slightly looser relationship than the one in the
- preceding example; there is no sense in which an
- allegorical character could be substituted for the
- physical city, or vice versa, but there is
- obviously a correspondence between them.
-
-
-
-
-
-
synch
-
(synchronous) points to
- elements that are synchronous with the current
- element.
-
-
-
Status
-
Optional
-
-
-
Datatype
-
1–∞ occurrences ofteidata.pointer
- separated by
- whitespace
-
-
-
-
-
-
sameAs
-
points to an
- element that is the same as the current
- element.
It is recommended
- that the element indicated be of the same type as
- the element bearing this attribute.
-
-
-
-
-
-
exclude
-
points to
- elements that are in exclusive alternation with
- the current element.
-
-
-
Status
-
Optional
-
-
-
Datatype
-
1–∞ occurrences ofteidata.pointer
- separated by
- whitespace
-
-
-
-
-
-
select
-
selects one or
- more alternants; if one alternant is selected, the
- ambiguity or uncertainty is marked as resolved. If
- more than one alternant is selected, the degree of
- ambiguity or uncertainty is marked as reduced by
- the number of alternants not selected.
-
-
-
Status
-
Optional
-
-
-
Datatype
-
1–∞ occurrences ofteidata.pointer
- separated by
- whitespace
-
-
-
Note
-
This attribute should
- be placed on an element which is superordinate to
- all of the alternants from which the selection is
- being made.
-
-
-
-
-
-
-
-
-
-
-
-
2.3.23. att.global.rendition
-
-
-
-
att.global.renditionprovides
- rendering attributes common to all elements in the TEI
- encoding scheme. [1.3.1.1.3. Rendition Indicators]
(rendition) indicates how
- the element in question was rendered or presented
- in the source text.
-
-
-
Status
-
Optional
-
-
-
Datatype
-
1–∞ occurrences ofteidata.word
- separated by
- whitespace
-
-
-
<head rend="align(center) case(allcaps)">
- <lb/>To The
- <lb/>Duchesse
- <lb/>of <lb/>Newcastle, <lb/>On Her <lb/><hi rend="case(mixed)">New
- Blazing-World</hi>. </head>
-
-
-
Note
-
These Guidelines make
- no binding recommendations for the values of the
- rend attribute; the
- characteristics of visual presentation vary too
- much from text to text and the decision to record
- or ignore individual characteristics varies too
- much from project to project. Some potentially
- useful conventions are noted from time to time at
- appropriate points in the Guidelines. The values
- of the rend attribute are
- a set of sequence-indeterminate individual tokens
- separated by whitespace.
-
-
-
-
-
-
style
-
contains an
- expression in some formal style definition
- language which defines the rendering or
- presentation used for this element in the source
- text
<head style="text-align: center; font-variant:
- small-caps"><lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, <lb/>On Her <lb/><hi style="font-variant: normal">New
- Blazing-World</hi>. </head>
-
-
-
Note
-
Unlike the attribute
- values of rend, which
- uses whitespace as a separator, the style attribute may contain
- whitespace. This attribute is intended for
- recording inline stylistic information concerning
- the source, not any particular output.
The
- formal language in which values for this attribute
- are expressed may be specified using the <styleDefDecl> element in
- the TEI header.
If style and rendition are both present on an element,
- then style overrides or
- complements rendition.
- style should not be used
- in conjunction with rend,
- because the latter does not employ a formal style
- definition language.
-
-
-
-
-
-
rendition
-
points to a
- description of the rendering or presentation used
- for this element in the source text.
-
-
-
Status
-
Optional
-
-
-
Datatype
-
1–∞ occurrences ofteidata.pointer
- separated by
- whitespace
The rendition attribute is used in a very
- similar way to the class
- attribute defined for XHTML but with the important
- distinction that its function is to describe the
- appearance of the source text, not necessarily to
- determine how that text should be presented on
- screen or paper.
If rendition is used to refer to a style
- definition in a formal language like CSS, it is
- recommended that it not be used in conjunction
- with rend. Where both
- rendition and rend are supplied, the latter
- is understood to override or complement the
- former.
Each URI provided should indicate a
- <rendition> element
- defining the intended rendition in terms of some
- appropriate style language, as indicated by the
- scheme
- attribute.
(responsible
- party) indicates the agency
- responsible for the intervention or
- interpretation, for example an editor or
- transcriber.
-
-
-
Status
-
Optional
-
-
-
Datatype
-
1–∞ occurrences ofteidata.pointer
- separated by
- whitespace
-
-
-
Note
-
To reduce the
- ambiguity of a resp
- pointing directly to a person or organization, we
- recommend that resp be
- used to point not to an agent (<person> or <org>) but to a <respStmt>, <author>, <editor> or similar element which
- clarifies the exact role played by the agent.
- Pointing to multiple <respStmt>s allows the encoder to
- specify clearly each of the roles played in part
- of a TEI file (creating, transcribing, encoding,
- editing, proofing etc.).
-
-
-
-
-
-
-
-
-
Example
-
Blessed are the <choice><sic>cheesemakers</sic><corr resp="#editor" cert="high">peacemakers</corr>
- </choice>: for they shall
- be called the children of God.
specifies the
- source from which some aspect of this element is
- drawn.
-
-
-
Status
-
Optional
-
-
-
Datatype
-
1–∞ occurrences ofteidata.pointer
- separated by
- whitespace
-
-
-
Note
-
The source attribute points to an external
- source. When used on elements describing schema
- components such as <schemaSpec> or <moduleRef> it identifies the source
- from which declarations for the components of the
- object being defined may be obtained.
On
- other elements it provides a pointer to the
- bibliographical source from which a quotation or
- citation is drawn.
In either case, the
- location may be provided using any form of URI,
- for example an absolute URI, a relative URI, or
- private scheme URI that is expanded to an absolute
- URI as documented in a <prefixDef>.
If more than one
- location is specified, the default assumption is
- that the required source should be obtained by
- combining the resources indicated.
-
-
-
-
-
-
-
-
-
Example
-
<p>
- <!-- ... --> As Willard
- McCarty (<bibl xml:id="mcc_2012">2012, p.2</bibl>) tells us, <quote source="#mcc_2012">‘Collaboration’ is a
- problematic and should be a contested term.</quote>
- <!-- ... -->
- </p>
-
-
-
Example
-
<p>
- <!-- ... --><quote source="#chicago_15_ed">Grammatical
- theories are in flux, and the more we learn, the less we
- seem to know.</quote>
- <!-- ... -->
- </p>
- <!-- ... -->
- <bibl xml:id="chicago_15_ed"><title level="m">The Chicago Manual of Style</title>, <edition>15th edition</edition>. <pubPlace>Chicago</pubPlace>: <publisher>University of
- Chicago Press</publisher>
- (<date>2003</date>), <biblScope unit="page">p.147</biblScope>. </bibl>
-
-
-
Example
-
- <elementRef key="p" source="tei:2.0.1"/>
-
Include in the schema an element named <p> available from
- the TEI P5 2.0.1 release.
-
-
-
Example
-
- <schemaSpec ident="myODD" source="mycompiledODD.xml">
- <!-- further declarations
- specifying the components required -->
- </schemaSpec>
-
Create a schema using components taken from the file mycompiledODD.xml.
-
-
-
-
-
-
2.3.26. att.handFeatures
-
-
-
-
att.handFeaturesprovides attributes
- describing aspects of the hand in which a manuscript is
- written. [11.3.2.1. Document Hands]
points to a
- full description of the scribe concerned,
- typically supplied by a <person> element elsewhere in the
- description.
-
-
-
Status
-
Optional
-
-
-
Datatype
-
1–∞ occurrences ofteidata.pointer
- separated by
- whitespace
-
-
-
-
-
-
script
-
characterizes
- the particular script or writing style used by
- this hand, for example secretary, copperplate, Chancery, Italian, etc.
-
-
-
Status
-
Optional
-
-
-
Datatype
-
1–∞ occurrences ofteidata.name
- separated by
- whitespace
-
-
-
-
-
-
scriptRef
-
points to a
- full description of the script or writing style
- used by this hand, typically supplied by a <scriptNote>
- element elsewhere in the description.
-
-
-
Status
-
Optional
-
-
-
Datatype
-
1–∞ occurrences ofteidata.pointer
- separated by
- whitespace
-
-
-
-
-
-
medium
-
describes the
- tint or type of ink, e.g. brown, or other writing medium, e.g. pencil
This attribute class provides an
- attribute for describing a computer resource, typically
- available over the internet, using a value taken from a
- standard taxonomy. At present only a single taxonomy is
- supported, the Multipurpose Internet Mail Extensions (MIME)
- Media Type system. This typology of media types is defined
- by the Internet Engineering Task Force in RFC 2046.
- The list
- of types is maintained by the Internet Assigned
- Numbers Authority (IANA). The mimeType attribute must have a value taken from
- this list.
-
-
-
-
-
-
2.3.28. att.media
-
-
-
-
att.mediaprovides attributes for
- specifying display and related properties of external
- media.
identifies the
- text types or classifications applicable to this
- item by pointing to other elements or resources
- defining the classification concerned.
-
-
-
Status
-
Optional
-
-
-
Datatype
-
1–∞ occurrences ofteidata.pointer
- separated by
- whitespace
-
-
-
-
-
-
-
-
-
-
-
-
2.3.30. att.msExcerpt
-
-
-
-
att.msExcerpt (manuscript
- excerpt) provides attributes used to
- describe excerpts from a manuscript placed in a description
- thereof. [10.6. Intellectual Content]
In the case of an incipit, indicates
- whether the incipit as given is defective, i.e. the first
- words of the text as preserved, as opposed to the first
- words of the work itself. In the case of an explicit,
- indicates whether the explicit as given is defective, i.e.
- the final words of the text as preserved, as opposed to what
- the closing words would have been had the text of the work
- been whole.
may be used to
- specify further information about the entity
- referenced by this name in the form of a set of
- whitespace-separated values, for example the
- occupation of a person, or the status of a
- place.
(reference to
- the canonical name) provides a means of locating the canonical form
- (nym) of the names
- associated with the object named by the element
- bearing it.
-
-
-
Status
-
Optional
-
-
-
Datatype
-
1–∞ occurrences ofteidata.pointer
- separated by
- whitespace
-
-
-
Note
-
The value must point
- directly to one or more XML elements by means of
- one or more URIs, separated by whitespace. If more
- than one is supplied, the implication is that the
- name is associated with several distinct canonical
- names.
-
-
-
-
-
-
-
-
-
-
-
-
2.3.32. att.notated
-
-
-
-
att.notatedprovides attributes to
- indicate any specialised notation used for element
- content.
att.personal (attributes for
- components of names usually, but not necessarily, personal
- names) common attributes for those
- elements which form part of a name usually, but not
- necessarily, a personal name. [13.2.1. Personal Names]
to the right, e.g. to the
- right of a vertical line of text, or to the right
- of a figure
-
below
-
below the line
-
left
-
to the left, e.g. to the left
- of a vertical line of text, or to the left of a
- figure
-
end
-
at the end of e.g. chapter or
- volume.
-
inline
-
within the body of the
- text.
-
inspace
-
in a predefined space, for
- example left by an earlier scribe.
-
-
-
-
<add place="margin">[An addition written in
- the margin]</add>
- <add place="bottom
- opposite">[An addition written at
- the foot of the current page and also on the
- facing page]</add>
- <sch:rule context="tei:*[not(self::tei:schemaSpec)][@targetLang]">
- <sch:assert test="@target">@targetLang
- should only be used on <sch:name/> if
- @target is specified.</sch:assert>
- </sch:rule>
In the example
- above, the <linkGrp>
- combines pointers at parallel fragments of the
- Universal Declaration of
- Human Rights: one of them is in Polish, the
- other in Swahili.
-
-
-
Note
-
The value must
- conform to BCP 47. If the value is a private use
- code (i.e., starts with x- or contains -x-), a <language> element with a matching
- value for its ident
- attribute should be supplied in the TEI header to
- document this value. Such documentation may also
- optionally be supplied for non-private-use codes,
- though these must remain consistent with their
- (IETF)Internet Engineering Task
- Force definitions.
-
-
-
-
-
-
target
-
specifies the
- destination of the reference by supplying one or
- more URI References
-
-
-
Status
-
Optional
-
-
-
Datatype
-
1–∞ occurrences ofteidata.pointer
- separated by
- whitespace
-
-
-
Note
-
One or more
- syntactically valid URI references, separated by
- whitespace. Because whitespace is used to separate
- URIs, no whitespace is permitted inside a single
- URI. If a whitespace character is required in a
- URI, it should be escaped with the normal
- mechanism, e.g.
- TEI%20Consortium.
-
-
-
-
-
-
evaluate
-
(evaluate) specifies the
- intended meaning when the target of a pointer is
- itself a pointer.
if the element pointed to is
- itself a pointer, then the target of that pointer
- will be taken, and so on, until an element is
- found which is not a pointer.
-
one
-
if the element pointed to is
- itself a pointer, then its target (whether a
- pointer or not) is taken as the target of this
- pointer.
-
none
-
no further evaluation of
- targets is carried out beyond that needed to find
- the element specified in the pointer's
- target.
-
-
-
-
Note
-
If no value is given,
- the application program is responsible for
- deciding (possibly on the basis of user input) how
- far to trace a chain of pointers.
-
-
-
-
-
-
-
-
-
-
-
-
2.3.36. att.ranging
-
-
-
-
att.rangingprovides attributes for
- describing numerical ranges.
specifies the
- degree of statistical confidence (between zero and
- one) that a value falls within the range specified
- by min and max, or the proportion of
- observed values that fall within that
- range.
- <sch:rule context="//*[(@atLeast and @atMost) or (@min
- and @max)]"> <sch:let name="f"
- value="(@atLeast,@min)[1]"/>
- <sch:let name="t" value="(@atMost,@max)[1]"/>
- <sch:let name="bothnumbers" value="$f castable as
- xs:float and $t castable as xs:float"/>
- <sch:let name="fv" value="if ($bothnumbers) then
- xs:float($f) else ()"/> <sch:let name="tv" value="if
- ($bothnumbers) then xs:float($t) else ()"/>
- <sch:report test="$bothnumbers and $fv gt $tv"
- role="warn"> The numerical range
- <sch:value-of select="$f"/>–<sch:value-of select="$t"/>
- in <sch:value-of select="name(.)"/> may not be valid.
- </sch:report> </sch:rule>
-
-
-
Example
-
The MS. was lost in transmission by
- mail from <del rend="overstrike">
- <gap reason="illegible" extent="one or
- two letters" atLeast="1" atMost="2" unit="chars"/>
- </del> Philadelphia to
- the Graphic office, New York.
-
-
-
-
-
-
2.3.37. att.resourced
-
-
-
-
att.resourcedprovides attributes by
- which a resource (such as an externally held media file) may
- be located.
Attribute values will
- often vary depending on the type of element to
- which they are attached. For example, a <cl>, may take values such
- as coordinate, subject, adverbial etc. For a <phr>, such values as
- subject, predicate etc. may be more appropriate.
- Such constraints will typically be implemented by
- a project-defined customization.
-
-
-
-
-
-
-
-
-
-
-
-
2.3.39. att.sortable
-
-
-
-
att.sortableprovides attributes for
- elements in lists or groups that are sortable, but whose
- sorting key cannot be derived mechanically from the element
- content. [9.1. Dictionary Body and Overall Structure]
David's other principal
- backer, Josiah ha-Kohen <index indexName="NAMES"><term sortKey="Azarya_Josiah_Kohen">Josiah
- ha-Kohen b. Azarya</term>
- </index> b.
- Azarya, son of one of the last gaons of Sura was
- David's own first cousin.
-
-
-
Note
-
The sort key is used
- to determine the sequence and grouping of entries
- in an index. It provides a sequence of characters
- which, when sorted with the other values, will
- produced the desired order; specifics of sort key
- construction are
- application-dependent
Dictionary order often
- differs from the collation sequence of
- machine-readable character sets; in
- English-language dictionaries, an entry for 4-H will often appear
- alphabetized under ‘fourh’,
- and McCoy may be
- alphabetized under ‘maccoy’, while A1, A4, and
- A5 may all appear
- in numeric order ‘alphabetized’ between ‘a-’ and ‘AA’. The sort key is required if the
- orthography of the dictionary entry does not
- suffice to determine its location.
The
- @spanTo attribute must point to an element
- following the current element
- <sch:rule context="tei:*[@spanTo]">
- <sch:assert test="id(substring(@spanTo,2)) and
- following::*[@xml:id=substring(current()/@spanTo,2)]">The
- element indicated by @spanTo
- (<sch:value-of select="@spanTo"/>) must
- follow the current element <sch:name/>
- </sch:assert> </sch:rule>
-
-
-
-
-
-
-
-
-
Note
-
The span is defined as running in
- document order from the start of the content of the pointing
- element to the end of the content of the element pointed to
- by the spanTo attribute (if any).
- If no value is supplied for the attribute, the assumption is
- that the span is coextensive with the pointing element. If
- no content is present, the assumption is that the starting
- point of the span is immediately following the element
- itself.
-
-
-
-
-
-
2.3.41. att.transcriptional
-
-
-
-
att.transcriptionalprovides
- attributes specific to elements encoding authorial or
- scribal intervention in a text when transcribing manuscript
- or similar sources. [11.3.1.4. Additions and Deletions]
indicates the
- effect of the intervention, for example in the
- case of a deletion, strikeouts which include too
- much or too little text, or in the case of an
- addition, an insertion which duplicates some of
- the text already present.
all of the text indicated as
- an addition duplicates some text that is in the
- original, whether the duplication is word-for-word
- or less exact.
-
duplicate-partial
-
part of the text indicated as
- an addition duplicates some text that is in the
- original
-
excessStart
-
some text at the beginning of
- the deletion is marked as deleted even though it
- clearly should not be deleted.
-
excessEnd
-
some text at the end of the
- deletion is marked as deleted even though it
- clearly should not be deleted.
-
shortStart
-
some text at the beginning of
- the deletion is not marked as deleted even though
- it clearly should be.
-
shortEnd
-
some text at the end of the
- deletion is not marked as deleted even though it
- clearly should be.
-
partial
-
some text in the deletion is
- not marked as deleted even though it clearly
- should be.
-
unremarkable
-
the deletion is not
- faulty.[Default]
-
-
-
-
Note
-
Status information on
- each deletion is needed rather rarely except in
- critical editions from authorial manuscripts;
- status information on additions is even less
- common.
Marking a deletion or addition as
- faulty is inescapably an interpretive act; the
- usual test applied in practice is the linguistic
- acceptability of the text with and without the
- letters or words in question.
-
-
-
-
-
-
cause
-
documents the
- presumed cause for the intervention.
<div type="verse"><head>Night in Tarras</head><lg type="stanza"><l>At evening tramping on the hot
- white road</l>
- <l>…</l></lg><lg type="stanza"><l>A wind sprang up from nowhere as
- the sky</l>
- <l>…</l></lg>
- </div>
-
-
-
Note
-
The type attribute is present on a number of
- elements, not all of which are members of att.typed, usually
- because these elements restrict the possible
- values for the attribute in a specific
- way.
-
-
-
-
-
-
subtype
-
(subtype) provides a
- sub-categorization of the element, if
- needed
The subtype attribute may be used to provide
- any sub-classification for the element additional
- to that provided by its type attribute.
-
-
-
-
-
-
-
-
-
Schematron
-
- <sch:rule context="tei:*[@subtype]">
- <sch:assert test="@type">The <sch:name/> element
- should not be categorized in detail with @subtype unless
- also categorized in general with @type</sch:assert>
- </sch:rule>
-
-
-
Note
-
When appropriate, values from an
- established typology should be used. Alternatively a
- typology may be defined in the associated TEI header. If
- values are to be taken from a project-specific list, this
- should be defined using the <valList> element in the project-specific
- schema description, as described in 23.3.1.3. Modification of Attribute and Attribute Value
- Lists .
-
-
-
-
-
-
2.3.43. att.written
-
-
-
-
att.writtenprovides attributes to
- indicate the hand in which the content of an element was
- written in the source being transcribed. [1.3.1. Attribute Classes]
macro.limitedContent (paragraph
- content) defines the content of prose
- elements that are not used for transcription of extant
- materials. [1.3. The TEI Class System]
model.emphLikegroups phrase-level elements which are typographically distinct and to which a specific function can be attributed. [3.3. Highlighting and Quotation]
model.hiLikegroups phrase-level elements which are typographically distinct but to which no specific function can be attributed. [3.3. Highlighting and Quotation]
model.limitedPhrasegroups phrase-level elements excluding those elements primarily intended for transcription of existing sources. [1.3. The TEI Class System]
model.measureLikegroups elements which denote a number, a quantity, a measurement, or similar piece of text that conveys some numerical meaning. [3.5.3. Numbers and Measures]
model.pPart.editorialgroups phrase-level elements for simple editorial interventions that may be useful both in transcribing and in authoring. [3.4. Simple Editorial Changes]
model.pPart.transcriptionalgroups phrase-level elements used for editorial transcription of pre-existing source materials. [3.4. Simple Editorial Changes]
model.persStateLikegroups elements describing changeable characteristics of a person which have a definite duration, for example occupation, residence, or name.
This class of elements can occur within paragraphs, list items, lines of verse, etc.
2.2.45. model.phrase.xml
model.phrase.xmlgroups phrase-level elements used to encode XML constructs such as element names, attribute names, and attribute values [22. Documentation Elements]
The principles on which segmentation is carried out, and any special codes or attribute values used, should be defined explicitly in the <segmentation> element of the <encodingDesc> within the associated TEI header.
2.2.55. model.teiHeaderPart
model.teiHeaderPartgroups high level elements which may appear more than once in a TEI header.
model.titlepagePartgroups elements which can occur as direct constituents of a title page, such as <docTitle>, <docAuthor>, <docImprint>, or <epigraph>. [4.6. Title Pages]
att.breakingprovides an attribute to indicate whether or not the element concerned is considered to mark the end of an orthographic token in the same way as whitespace. [3.10.3. Milestone Elements]
indicates whether or not the element bearing this attribute should be considered to mark the end of an orthographic token in the same way as whitespace.
the element bearing this attribute is considered to mark the end of any adjacent orthographic token irrespective of the presence of any adjacent whitespace
no
the element bearing this attribute is considered not to mark the end of any adjacent orthographic token irrespective of the presence of any adjacent whitespace
maybe
the encoding does not take any position on this issue.
In the following lines from the Dream of the Rood, linebreaks occur in the middle of the words lāðost and reord-berendum.
(canonical reference) specifies the destination of the pointer by supplying a canonical reference expressed using the scheme defined in a <refsDecl> element in the TEI header
The value of cRef should be constructed so that when the algorithm for the resolution of canonical references (described in section 16.2.5. Canonical References) is applied to it the result is a valid URI reference to the intended target.
The <refsDecl> to use may be indicated with the decls attribute.
Currently these Guidelines only provide for a single canonical reference to be encoded on any given <ptr> element.
2.3.3. att.canonical
att.canonicalprovides attributes which can be used to associate a representation such as a name or title with canonical information about the object being named or referenced. [13.1.1. Linking Names and Their Referents]
The value must point directly to one or more XML elements or other resources by means of one or more URIs, separated by whitespace. If more than one is supplied the implication is that the name identifies several distinct entities.
2.3.4. att.citing
att.citingprovides attributes for specifying the specific part of a bibliographic item being cited. [1.3.1. Attribute Classes]
identifies a two dimensional area by means of a series of pairs of numbers, each of which gives the x,y coordinates of a point on a line enclosing the area.
Status
Optional
Datatype
3–∞ occurrences ofteidata.pointseparated by whitespace
+<sch:rule context="tei:*[@calendar]">
+<sch:assert test="string-length(.) gt 0"> @calendar indicates the system or calendar to
+ which the date represented by the content of this element belongs, but this
+<sch:name/> element has no textual content.</sch:assert>
+</sch:rule>
He was born on <date calendar="#gregorian">Feb. 22, 1732</date> (<date calendar="#julian"
+ when="1732-02-22"> Feb. 11, 1731/32,
+ O.S.</date>).
Note
Note that the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized.
period
supplies a pointer to some location defining a named period of time within which the datable item is understood to have occurred.
This ‘superclass’ provides attributes that can be used to provide normalized values of temporal information. By default, the attributes from the att.datable.w3c class are provided. If the module for names & dates is loaded, this class also provides attributes from the att.datable.iso and att.datable.custom classes. In general, the possible values of attributes restricted to the W3C datatypes form a subset of those values available via the ISO 8601 standard. However, the greater expressiveness of the ISO datatypes may not be needed, and there exists much greater software support for the W3C datatypes.
2.3.7. att.datable.custom
att.datable.customprovides attributes for normalization of elements that contain datable events to a custom dating system (i.e. other than the Gregorian used by W3 and ISO). [13.3.7. Dates and Times]
supplies the value of a date or time in some custom standard form.
Status
Optional
Datatype
1–∞ occurrences ofteidata.wordseparated by whitespace
The following are examples of custom date or time formats that are not valid ISO or W3C format normalizations, normalized to a different dating system
<p>Alhazen died in Cairo on the
+<date when="1040-03-06"
+ when-custom="431-06-12"> 12th day of Jumada t-Tania, 430 AH
+ </date>.</p>
+<p>The current world will end at the
+<date when="2012-12-21"
+ when-custom="13.0.0.0.0">end of B'ak'tun 13</date>.</p>
+<p>The Battle of Meggidu
+ (<date when-custom="Thutmose_III:23">23rd year of reign of Thutmose III</date>).</p>
+<p>Esidorus bixit in pace annos LXX plus minus sub
+<date when-custom="Ind:4-10-11">die XI mensis Octobris indictione IIII</date>
+</p>
Not all custom date formulations will have Gregorian equivalents.The when-custom attribute and other custom dating are not constrained to a datatype by the TEI, but individual projects are recommended to regularize and document their dating formats.
notBefore-custom
specifies the earliest possible date for the event in some custom standard form.
Status
Optional
Datatype
1–∞ occurrences ofteidata.wordseparated by whitespace
notAfter-custom
specifies the latest possible date for the event in some custom standard form.
Status
Optional
Datatype
1–∞ occurrences ofteidata.wordseparated by whitespace
from-custom
indicates the starting point of the period in some custom standard form.
Status
Optional
Datatype
1–∞ occurrences ofteidata.wordseparated by whitespace
<event xml:id="FIRE1"
+ datingMethod="#julian"
+ from-custom="1666-09-02"
+ to-custom="1666-09-05">
+ <head>The Great Fire of London</head>
+ <p>The Great Fire of London burned through a large part
+ of the city of London.</p>
+</event>
to-custom
indicates the ending point of the period in some custom standard form.
Status
Optional
Datatype
1–∞ occurrences ofteidata.wordseparated by whitespace
datingPoint
supplies a pointer to some location defining a named point in time with reference to which the datable item is understood to have occurred
Contayning the Originall, Antiquity, Increaſe, Moderne
+ eſtate, and deſcription of that Citie, written in the yeare
+<date when-custom="1598"
+ calendar="#julian"
+ datingMethod="#julian">1598</date>. by Iohn Stow
+ Citizen of London.
In this example, the calendar attribute points to a <calendar> element for the Julian calendar, specifying that the text content of the <date> element is a Julian date, and the datingMethod attribute also points to the Julian calendar to indicate that the content of the when-custom attribute value is Julian too.
In this example, a date is given in a Mediaeval text measured "from the creation of the world", which is normalised (in when) to the Gregorian date, but is also normalized (in when-custom) to a machine-actionable, numeric version of the date from the Creation.
Note
Note that the datingMethod attribute (unlike calendar defined in att.datable) defines the calendar or dating system to which the date described by the parent element is normalized (i.e. in the when-custom or other X-custom attributes), not the calendar of the original date in the element.
The following are examples of ISO date, time, and date & time formats that are not valid W3C format normalizations.
<date when-iso="1996-09-24T07:25+00">Sept. 24th, 1996 at 3:25 in the morning</date>
+<date when-iso="1996-09-24T03:25-04">Sept. 24th, 1996 at 3:25 in the morning</date>
+<time when-iso="1999-01-04T20:42-05">4 Jan 1999 at 8:42 pm</time>
+<time when-iso="1999-W01-1T20,70-05">4 Jan 1999 at 8:42 pm</time>
+<date when-iso="2006-05-18T10:03">a few minutes after ten in the morning on Thu 18 May</date>
+<time when-iso="03:00">3 A.M.</time>
+<time when-iso="14">around two</time>
+<time when-iso="15,5">half past three</time>
All of the examples of the when attribute in the att.datable.w3c class are also valid with respect to this attribute.
He likes to be punctual. I said <q>
+ <time when-iso="12">around noon</time>
+</q>, and he showed up at <time when-iso="12:00:00">12 O'clock</time> on the dot.
The second occurence of <time> could have been encoded with the when attribute, as 12:00:00 is a valid time with respect to the W3C XML Schema Part 2: Datatypes Second Edition specification. The first occurence could not.
notBefore-iso
specifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd.
The value of these attributes should be a normalized representation of the date, time, or combined date & time intended, in any of the standard formats specified by ISO 8601, using the Gregorian calendar.
If both when-iso and dur-iso are specified, the values should be interpreted as indicating a span of time by its starting time (or date) and duration. That is,
<date when-iso="2007-06-01" dur-iso="P8D"/>
indicates the same time period as
<date when-iso="2007-06-01/P8D"/>
In providing a ‘regularized’ form, no claim is made that the form in the source text is incorrect; the regularized form is simply that chosen as the main form for purposes of unifying variant forms under a single heading.
2.3.9. att.datable.w3c
att.datable.w3cprovides attributes for normalization of elements that contain datable events conforming to the W3C XML Schema Part 2: Datatypes Second Edition. [3.5.4. Dates and Times13.3.7. Dates and Times]
Examples of W3C date, time, and date & time formats.
<p>
+ <date when="1945-10-24">24 Oct 45</date>
+ <date when="1996-09-24T07:25:00Z">September 24th, 1996 at 3:25 in the morning</date>
+ <time when="1999-01-04T20:42:00-05:00">Jan 4 1999 at 8 pm</time>
+ <time when="14:12:38">fourteen twelve and 38 seconds</time>
+ <date when="1962-10">October of 1962</date>
+ <date when="--06-12">June 12th</date>
+ <date when="---01">the first of the month</date>
+ <date when="--08">August</date>
+ <date when="2006">MMVI</date>
+ <date when="0056">AD 56</date>
+ <date when="-0056">56 BC</date>
+</p>
This list begins in
+ the year 1632, more precisely on Trinity Sunday, i.e. the Sunday after
+ Pentecost, in that year the
+<date calendar="#julian"
+ when="1632-06-06">27th of May (old style)</date>.
+<sch:rule context="//*[not(self::tei:locus or self::tei:biblScope or self::tei:citedRange)]
+ [(@notBefore and @notAfter) or (@from and @to)]">
+<sch:let name="f"
+ value="(@notBefore,@from)[1]"/>
+<sch:let name="t"
+ value="(@notAfter,@to)[1]"/>
+<sch:let name="bothdates"
+ value="$f castable as xs:date and $t castable as xs:date"/>
+<sch:let name="bothyears"
+ value="$f castable as xs:integer and $t castable as xs:integer"/>
+<sch:let name="fd"
+ value="if ($bothdates) then xs:date($f) else ()"/>
+<sch:let name="td"
+ value="if ($bothdates) then xs:date($t) else ()"/>
+<sch:let name="fy"
+ value="if ($bothyears) then xs:integer($f) else ()"/>
+<sch:let name="ty"
+ value="if ($bothyears) then xs:integer($t) else ()"/>
+<sch:report test="($bothdates and $fd gt $td) or ($bothyears and $fy gt $ty)"
+ role="error"> The date range <sch:value-of select="$f"/>–<sch:value-of select="$t"/> in <sch:value-of select="name(.)"/> is not valid. </sch:report>
+</sch:rule>
Schematron
+<sch:rule context="tei:*[@when]">
+<sch:report test="@notBefore|@notAfter|@from|@to"
+ role="nonfatal">The @when attribute cannot be used with any other att.datable.w3c attributes.</sch:report>
+</sch:rule>
Schematron
+<sch:rule context="tei:*[@from]">
+<sch:report test="@notBefore"
+ role="nonfatal">The @from and @notBefore attributes cannot be used together.</sch:report>
+</sch:rule>
Schematron
+<sch:rule context="tei:*[@to]">
+<sch:report test="@notAfter"
+ role="nonfatal">The @to and @notAfter attributes cannot be used together.</sch:report>
+</sch:rule>
Example
<date from="1863-05-28" to="1863-06-01">28 May through 1 June 1863</date>
Note
The value of these attributes should be a normalized representation of the date, time, or combined date & time intended, in any of the standard formats specified by XML Schema Part 2: Datatypes Second Edition, using the Gregorian calendar.
The most commonly-encountered format for the date portion of a temporal attribute is yyyy-mm-dd, but yyyy, --mm, ---dd, yyyy-mm, or --mm-dd may also be used. For the time part, the form hh:mm:ss is used.
Note that this format does not currently permit use of the value 0000 to represent the year 1 BCE; instead the value -0001 should be used.
2.3.10. att.datcat
att.datcatprovides the dcr:datacat and dcr:ValueDatacat attributes which are used to align XML elements or attributes with the appropriate Data Categories (DCs) defined by the ISO 12620:2009 standard and stored in the Web repository called ISOCat at http://www.isocat.org/. [9.5.2. Lexical View18.3. Other Atomic Feature Values]
contains a PID (persistent identifier) that aligns the content of the given element or the value of the given attribute with the appropriate simple Data Category (or categories) in ISOcat.
In this example dcr:datcat relates the feature name to the data category "partOfSpeech" and dcr:valueDatcat the feature value to the data category "commonNoun". Both these data categories reside in the ISOcat DCR at www.isocat.org, which is the DCR used by ISO TC37 and hosted by its registration authority, the MPI for Psycholinguistics in Nijmegen.
ISO 12620:2009 is a standard describing the data model and procedures for a Data Category Registry (DCR). Data categories are defined as elementary descriptors in a linguistic structure. In the DCR data model each data category gets assigned a unique Peristent IDentifier (PID), i.e., an URI. Linguistic resources or preferably their schemas that make use of data categories from a DCR should refer to them using this PID. For XML-based resources, like TEI documents, ISO 12620:2009 normative Annex A gives a small Data Category Reference XML vocabulary (also available online at http://www.isocat.org/12620/), which provides two attributes, dcr:datcat and dcr:valueDatcat.
2.3.11. att.declarable
att.declarableprovides attributes for those elements in the TEI header which may be independently selected by means of the special purpose decls attribute. [15.3. Associating Contextual Information with a Text]
This element is selected if its parent is selected
false
This element can only be selected explicitly, unless it is the only one of its kind, in which case it is selected if its parent is selected.[Default]
Note
The rules governing the association of declarable elements with individual parts of a TEI text are fully defined in chapter 15.3. Associating Contextual Information with a Text. Only one element of a particular type may have a default attribute with a value of true.
2.3.12. att.declaring
att.declaringprovides attributes for elements which may be independently associated with a particular declarable element within the header, thus overriding the inherited default for that element. [15.3. Associating Contextual Information with a Text]
The members of this attribute class are typically used to represent any kind of editorial intervention in a text, for example a correction or interpretation, or to date or localize manuscripts etc.
Each pointer on the source (if present) corresponding to a witness or witness group should reference a bibliographic citation such as a <witness>, <msDesc>, or <bibl> element, or another external bibliographic citation, documenting the source concerned.
2.3.17. att.edition
att.editionprovides attributes identifying the source edition from which some encoded feature derives.
(edition) supplies a sigil or other arbitrary identifier for the source edition in which the associated feature (for example, a page, column, or line break) occurs at this point in the text.
Status
Optional
Datatype
1–∞ occurrences ofteidata.wordseparated by whitespace
edRef
(edition reference) provides a pointer to the source edition in which the associated feature (for example, a page, column, or line break) occurs at this point in the text.
<l>Of Mans First Disobedience,<lb ed="1674"/> and<lb ed="1667"/> the Fruit</l>
+<l>Of that Forbidden Tree, whose<lb ed="1667 1674"/> mortal tast</l>
+<l>Brought Death into the World,<lb ed="1667"/> and all<lb ed="1674"/> our woe,</l>
Example
<listBibl>
+ <bibl xml:id="stapledon1937">
+ <author>Olaf Stapledon</author>,
+ <title>Starmaker</title>, <publisher>Methuen</publisher>, <date>1937</date>
+ </bibl>
+ <bibl xml:id="stapledon1968">
+ <author>Olaf Stapledon</author>,
+ <title>Starmaker</title>, <publisher>Dover</publisher>, <date>1968</date>
+ </bibl>
+</listBibl>
+<!-- ... -->
+<p>Looking into the future aeons from the supreme moment of
+ the cosmos, I saw the populations still with all their
+ strength maintaining the<pb n="411" edRef="#stapledon1968"/>essentials of their ancient culture,
+ still living their personal lives in zest and endless
+ novelty of action, … I saw myself still
+ preserving, though with increasing difficulty, my lucid
+ con-<pb n="291" edRef="#stapledon1937"/>sciousness;</p>
2.3.18. att.fragmentable
att.fragmentableprovides an attribute for representing fragmentation of a structural element, typically as a consequence of some overlapping hierarchy.
specifies whether or not its parent element is fragmented in some way, typically by some other overlapping structure: for example a speech which is divided between two or more verse stanzas, a paragraph which is split across a page division, a verse line which is divided between two speakers.
The value of this attribute is always understood to be a single token, even if it contains space or other punctuation characters, and need not be composed of numbers only. It is typically used to specify the numbering of chapters, sections, list items, etc.; it may also be used in the specification of a standard reference system for the text.
xml:lang
(language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
<p> … The consequences of
+ this rapid depopulation were the loss of the last
+<foreign xml:lang="rap">ariki</foreign> or chief
+ (Routledge 1920:205,210) and their connections to
+ ancestral territorial organization.</p>
Note
The xml:lang value will be inherited from the immediately enclosing element, or from its parent, and so on up the document hierarchy. It is generally good practice to specify xml:lang at the highest appropriate level, noticing that a different default may be needed for the <teiHeader> from that needed for the associated resource element or elements, and that a single TEI document may contain texts in many languages.
The value used must conform with BCP 47. If the value is a private use code (i.e., starts with x- or contains -x-), a <language> element with a matching value for its ident attribute should be supplied in the TEI header to document this value. Such documentation may also optionally be supplied for non-private-use codes, though these must remain consistent with their (IETF)Internet Engineering Task Force definitions.
xml:base
provides a base URI reference with which applications can resolve relative URI references into absolute URI references.
signals that the application's default white-space processing modes are acceptable
preserve
indicates the intent that applications preserve all white space
Note
The XML specification provides further guidance on the use of this attribute. Note that many parsers may not handle xml:space correctly.
2.3.20. att.global.change
att.global.changesupplies the change attribute, allowing its member elements to specify one or more states or revision campaigns with which they are associated.
points to one or more <change> elements documenting a state or revision campaign to which the element bearing this attribute and its children have been assigned by the encoder.
att.global.facsprovides an attribute used to express correspondence between an element containing transcribed text and all or part of an image representing that text. [11.1. Digital Facsimiles]
<group>
+ <text xml:id="t1-g1-t1"
+ xml:lang="mi">
+ <body xml:id="t1-g1-t1-body1">
+ <div type="chapter">
+ <head>He Whakamaramatanga mo te Ture Hoko, Riihi hoki, i nga Whenua Maori, 1876.</head>
+ <p>…</p>
+ </div>
+ </body>
+ </text>
+ <text xml:id="t1-g1-t2"
+ xml:lang="en">
+ <body xml:id="t1-g1-t2-body1"
+ corresp="#t1-g1-t1-body1">
+ <div type="chapter">
+ <head>An Act to regulate the Sale, Letting, and Disposal of Native Lands, 1876.</head>
+ <p>…</p>
+ </div>
+ </body>
+ </text>
+</group>
In this example a <group> contains two <text>s, each containing the same document in a different language. The correspondence is indicated using corresp. The language is indicated using xml:lang, whose value is inherited; both the tag with the corresp and the tag pointed to by the corresp inherit the value from their immediate parent.
+<!-- In a placeography called "places.xml" --><place xml:id="LOND1"
+ corresp="people.xml#LOND2 people.xml#GENI1">
+ <placeName>London</placeName>
+ <desc>The city of London...</desc>
+</place>
+<!-- In a literary personography called "people.xml" -->
+<person xml:id="LOND2"
+ corresp="places.xml#LOND1 #GENI1">
+ <persName type="lit">London</persName>
+ <note>
+ <p>Allegorical character representing the city of <placeName ref="places.xml#LOND1">London</placeName>.</p>
+ </note>
+</person>
+<person xml:id="GENI1"
+ corresp="places.xml#LOND1 #LOND2">
+ <persName type="lit">London’s Genius</persName>
+ <note>
+ <p>Personification of London’s genius. Appears as an
+ allegorical character in mayoral shows.
+ </p>
+ </note>
+</person>
In this example, a <place> element containing information about the city of London is linked with two <person> elements in a literary personography. This correspondence represents a slightly looser relationship than the one in the preceding example; there is no sense in which an allegorical character could be substituted for the physical city, or vice versa, but there is obviously a correspondence between them.
synch
(synchronous) points to elements that are synchronous with the current element.
selects one or more alternants; if one alternant is selected, the ambiguity or uncertainty is marked as resolved. If more than one alternant is selected, the degree of ambiguity or uncertainty is marked as reduced by the number of alternants not selected.
(rendition) indicates how the element in question was rendered or presented in the source text.
Status
Optional
Datatype
1–∞ occurrences ofteidata.wordseparated by whitespace
<head rend="align(center) case(allcaps)">
+ <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle,
+<lb/>On Her <lb/>
+ <hi rend="case(mixed)">New Blazing-World</hi>.
+</head>
Note
These Guidelines make no binding recommendations for the values of the rend attribute; the characteristics of visual presentation vary too much from text to text and the decision to record or ignore individual characteristics varies too much from project to project. Some potentially useful conventions are noted from time to time at appropriate points in the Guidelines. The values of the rend attribute are a set of sequence-indeterminate individual tokens separated by whitespace.
style
contains an expression in some formal style definition language which defines the rendering or presentation used for this element in the source text
<head style="text-align: center; font-variant: small-caps">
+ <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, <lb/>On Her
+<lb/>
+ <hi style="font-variant: normal">New Blazing-World</hi>.
+</head>
Note
Unlike the attribute values of rend, which uses whitespace as a separator, the style attribute may contain whitespace. This attribute is intended for recording inline stylistic information concerning the source, not any particular output.
The formal language in which values for this attribute are expressed may be specified using the <styleDefDecl> element in the TEI header.
If style and rendition are both present on an element, then style overrides or complements rendition. style should not be used in conjunction with rend, because the latter does not employ a formal style definition language.
rendition
points to a description of the rendering or presentation used for this element in the source text.
The rendition attribute is used in a very similar way to the class attribute defined for XHTML but with the important distinction that its function is to describe the appearance of the source text, not necessarily to determine how that text should be presented on screen or paper.
If rendition is used to refer to a style definition in a formal language like CSS, it is recommended that it not be used in conjunction with rend. Where both rendition and rend are supplied, the latter is understood to override or complement the former.
Each URI provided should indicate a <rendition> element defining the intended rendition in terms of some appropriate style language, as indicated by the scheme attribute.
To reduce the ambiguity of a resp pointing directly to a person or organization, we recommend that resp be used to point not to an agent (<person> or <org>) but to a <respStmt>, <author>, <editor> or similar element which clarifies the exact role played by the agent. Pointing to multiple <respStmt>s allows the encoder to specify clearly each of the roles played in part of a TEI file (creating, transcribing, encoding, editing, proofing etc.).
Example
Blessed are the
+<choice>
+ <sic>cheesemakers</sic>
+ <corr resp="#editor" cert="high">peacemakers</corr>
+</choice>: for they shall be called the children of God.
The source attribute points to an external source. When used on elements describing schema components such as <schemaSpec> or <moduleRef> it identifies the source from which declarations for the components of the object being defined may be obtained.
On other elements it provides a pointer to the bibliographical source from which a quotation or citation is drawn.
In either case, the location may be provided using any form of URI, for example an absolute URI, a relative URI, or private scheme URI that is expanded to an absolute URI as documented in a <prefixDef>.
If more than one location is specified, the default assumption is that the required source should be obtained by combining the resources indicated.
Example
<p>
+<!-- ... --> As Willard McCarty (<bibl xml:id="mcc_2012">2012, p.2</bibl>) tells us, <quote source="#mcc_2012">‘Collaboration’ is a problematic and should be a contested
+ term.</quote>
+<!-- ... -->
+</p>
Example
<p>
+<!-- ... -->
+ <quote source="#chicago_15_ed">Grammatical theories are in flux, and the more we learn, the
+ less we seem to know.</quote>
+<!-- ... -->
+</p>
+<!-- ... -->
+<bibl xml:id="chicago_15_ed">
+ <title level="m">The Chicago Manual of Style</title>,
+<edition>15th edition</edition>. <pubPlace>Chicago</pubPlace>: <publisher>University of
+ Chicago Press</publisher> (<date>2003</date>), <biblScope unit="page">p.147</biblScope>.
+
+</bibl>
Example
<elementRef key="p" source="tei:2.0.1"/>
Include in the schema an element named <p> available from the TEI P5 2.0.1 release.
Example
<schemaSpec ident="myODD"
+ source="mycompiledODD.xml">
+<!-- further declarations specifying the components required -->
+</schemaSpec>
Create a schema using components taken from the file mycompiledODD.xml.
2.3.26. att.handFeatures
att.handFeaturesprovides attributes describing aspects of the hand in which a manuscript is written. [11.3.2.1. Document Hands]
characterizes the particular script or writing style used by this hand, for example secretary, copperplate, Chancery, Italian, etc.
Status
Optional
Datatype
1–∞ occurrences ofteidata.nameseparated by whitespace
scriptRef
points to a full description of the script or writing style used by this hand, typically supplied by a <scriptNote> element elsewhere in the description.
This attribute class provides an attribute for describing a computer resource, typically available over the internet, using a value taken from a standard taxonomy. At present only a single taxonomy is supported, the Multipurpose Internet Mail Extensions (MIME) Media Type system. This typology of media types is defined by the Internet Engineering Task Force in RFC 2046. The list of types is maintained by the Internet Assigned Numbers Authority (IANA). The mimeType attribute must have a value taken from this list.
2.3.28. att.media
att.mediaprovides attributes for specifying display and related properties of external media.
att.msExcerpt (manuscript excerpt) provides attributes used to describe excerpts from a manuscript placed in a description thereof. [10.6. Intellectual Content]
In the case of an incipit, indicates whether the incipit as given is defective, i.e. the first words of the text as preserved, as opposed to the first words of the work itself. In the case of an explicit, indicates whether the explicit as given is defective, i.e. the final words of the text as preserved, as opposed to what the closing words would have been had the text of the work been whole.
may be used to specify further information about the entity referenced by this name in the form of a set of whitespace-separated values, for example the occupation of a person, or the status of a place.
(reference to the canonical name) provides a means of locating the canonical form (nym) of the names associated with the object named by the element bearing it.
The value must point directly to one or more XML elements by means of one or more URIs, separated by whitespace. If more than one is supplied, the implication is that the name is associated with several distinct canonical names.
2.3.32. att.notated
att.notatedprovides an attribute to indicate any specialised notation used for element content.
att.personal (attributes for components of names usually, but not necessarily, personal names) common attributes for those elements which form part of a name usually, but not necessarily, a personal name. [13.2.1. Personal Names]
in a predefined space, for example left by an earlier scribe.
<add place="margin">[An addition written in the margin]</add>
+<add place="bottom opposite">[An addition written at the
+ foot of the current page and also on the facing page]</add>
+<sch:rule context="tei:*[not(self::tei:schemaSpec)][@targetLang]">
+<sch:assert test="@target">@targetLang should only be used on <sch:name/> if @target is specified.</sch:assert>
+</sch:rule>
In the example above, the <linkGrp> combines pointers at parallel fragments of the Universal Declaration of Human Rights: one of them is in Polish, the other in Swahili.
Note
The value must conform to BCP 47. If the value is a private use code (i.e., starts with x- or contains -x-), a <language> element with a matching value for its ident attribute should be supplied in the TEI header to document this value. Such documentation may also optionally be supplied for non-private-use codes, though these must remain consistent with their (IETF)Internet Engineering Task Force definitions.
target
specifies the destination of the reference by supplying one or more URI References
One or more syntactically valid URI references, separated by whitespace. Because whitespace is used to separate URIs, no whitespace is permitted inside a single URI. If a whitespace character is required in a URI, it should be escaped with the normal mechanism, e.g. TEI%20Consortium.
evaluate
specifies the intended meaning when the target of a pointer is itself a pointer.
if the element pointed to is itself a pointer, then the target of that pointer will be taken, and so on, until an element is found which is not a pointer.
one
if the element pointed to is itself a pointer, then its target (whether a pointer or not) is taken as the target of this pointer.
none
no further evaluation of targets is carried out beyond that needed to find the element specified in the pointer's target.
Note
If no value is given, the application program is responsible for deciding (possibly on the basis of user input) how far to trace a chain of pointers.
2.3.36. att.ranging
att.rangingprovides attributes for describing numerical ranges.
specifies the degree of statistical confidence (between zero and one) that a value falls within the range specified by min and max, or the proportion of observed values that fall within that range.
+<sch:rule context="//*[(@atLeast and @atMost) or (@min and @max)]">
+<sch:let name="f"
+ value="(@atLeast,@min)[1]"/>
+<sch:let name="t" value="(@atMost,@max)[1]"/>
+<sch:let name="bothnumbers"
+ value="$f castable as xs:float and $t castable as xs:float"/>
+<sch:let name="fv"
+ value="if ($bothnumbers) then xs:float($f) else ()"/>
+<sch:let name="tv"
+ value="if ($bothnumbers) then xs:float($t) else ()"/>
+<sch:report test="$bothnumbers and $fv gt $tv"
+ role="warn"> The
+ numerical range <sch:value-of select="$f"/>–<sch:value-of select="$t"/> in <sch:value-of select="name(.)"/> may
+ not be valid. </sch:report>
+</sch:rule>
Example
The MS. was lost in transmission by mail from <del rend="overstrike">
+ <gap reason="illegible"
+ extent="one or two letters" atLeast="1" atMost="2" unit="chars"/>
+</del> Philadelphia to the Graphic office, New York.
+
2.3.37. att.resourced
att.resourcedprovides attributes by which a resource (such as an externally held media file) may be located.
Attribute values will often vary depending on the type of element to which they are attached. For example, a <cl>, may take values such as coordinate, subject, adverbial etc. For a <phr>, such values as subject, predicate etc. may be more appropriate. Such constraints will typically be implemented by a project-defined customization.
2.3.39. att.sortable
att.sortableprovides attributes for elements in lists or groups that are sortable, but whose sorting key cannot be derived mechanically from the element content. [9.1. Dictionary Body and Overall Structure]
David's other principal backer, Josiah
+ ha-Kohen <index indexName="NAMES">
+ <term sortKey="Azarya_Josiah_Kohen">Josiah ha-Kohen b. Azarya</term>
+</index> b. Azarya, son of one of the last gaons of Sura was David's own first
+ cousin.
Note
The sort key is used to determine the sequence and grouping of entries in an index. It provides a sequence of characters which, when sorted with the other values, will produced the desired order; specifics of sort key construction are application-dependent
Dictionary order often differs from the collation sequence of machine-readable character sets; in English-language dictionaries, an entry for 4-H will often appear alphabetized under ‘fourh’, and McCoy may be alphabetized under ‘maccoy’, while A1, A4, and A5 may all appear in numeric order ‘alphabetized’ between ‘a-’ and ‘AA’. The sort key is required if the orthography of the dictionary entry does not suffice to determine its location.
The @spanTo attribute must point to an element following the current element
+<sch:rule context="tei:*[@spanTo]">
+<sch:assert test="id(substring(@spanTo,2)) and following::*[@xml:id=substring(current()/@spanTo,2)]">The element indicated by @spanTo (<sch:value-of select="@spanTo"/>) must follow the current element <sch:name/>
+</sch:assert>
+</sch:rule>
Note
The span is defined as running in document order from the start of the content of the pointing element to the end of the content of the element pointed to by the spanTo attribute (if any). If no value is supplied for the attribute, the assumption is that the span is coextensive with the pointing element. If no content is present, the assumption is that the starting point of the span is immediately following the element itself.
2.3.41. att.transcriptional
att.transcriptionalprovides attributes specific to elements encoding authorial or scribal intervention in a text when transcribing manuscript or similar sources. [11.3.1.4. Additions and Deletions]
indicates the effect of the intervention, for example in the case of a deletion, strikeouts which include too much or too little text, or in the case of an addition, an insertion which duplicates some of the text already present.
all of the text indicated as an addition duplicates some text that is in the original, whether the duplication is word-for-word or less exact.
duplicate-partial
part of the text indicated as an addition duplicates some text that is in the original
excessStart
some text at the beginning of the deletion is marked as deleted even though it clearly should not be deleted.
excessEnd
some text at the end of the deletion is marked as deleted even though it clearly should not be deleted.
shortStart
some text at the beginning of the deletion is not marked as deleted even though it clearly should be.
shortEnd
some text at the end of the deletion is not marked as deleted even though it clearly should be.
partial
some text in the deletion is not marked as deleted even though it clearly should be.
unremarkable
the deletion is not faulty.[Default]
Note
Status information on each deletion is needed rather rarely except in critical editions from authorial manuscripts; status information on additions is even less common.
Marking a deletion or addition as faulty is inescapably an interpretive act; the usual test applied in practice is the linguistic acceptability of the text with and without the letters or words in question.
cause
documents the presumed cause for the intervention.
<div type="verse">
+ <head>Night in Tarras</head>
+ <lg type="stanza">
+ <l>At evening tramping on the hot white road</l>
+ <l>…</l>
+ </lg>
+ <lg type="stanza">
+ <l>A wind sprang up from nowhere as the sky</l>
+ <l>…</l>
+ </lg>
+</div>
Note
The type attribute is present on a number of elements, not all of which are members of att.typed, usually because these elements restrict the possible values for the attribute in a specific way.
subtype
provides a sub-categorization of the element, if needed
The subtype attribute may be used to provide any sub-classification for the element additional to that provided by its type attribute.
Schematron
+<sch:rule context="tei:*[@subtype]">
+<sch:assert test="@type">The <sch:name/> element should not be categorized in detail with @subtype unless also categorized in general with @type</sch:assert>
+</sch:rule>
Note
When appropriate, values from an established typology should be used. Alternatively a typology may be defined in the associated TEI header. If values are to be taken from a project-specific list, this should be defined using the <valList> element in the project-specific schema description, as described in 23.3.1.3. Modification of Attribute and Attribute Value Lists .
2.3.43. att.written
att.writtenprovides an attribute to indicate the hand in which the content of an element was written in the source being transcribed. [1.3.1. Attribute Classes]
macro.limitedContent (paragraph content) defines the content of prose elements that are not used for transcription of extant materials. [1.3. The TEI Class System]
macro.phraseSeq.limited (limited
- phrase sequence) defines a sequence
- of character data and those phrase-level elements that are
- not typically used for transcribing extant documents.
- [1.4.1. Standard Content Models]
macro.phraseSeq.limited (limited phrase sequence) defines a sequence of character data and those phrase-level elements that are not typically used for transcribing extant documents. [1.4.1. Standard Content Models]
macro.specialPara ('special' paragraph content) defines the content model of elements such as
- notes or list items, which either contain a series of
- component-level elements or else have the same structure as
- a paragraph, containing a series of phrase-level and
- inter-level elements. [1.3. The TEI Class System]
macro.specialPara ('special' paragraph content) defines the content model of elements such as notes or list items, which either contain a series of component-level elements or else have the same structure as a paragraph, containing a series of phrase-level and inter-level elements. [1.3. The TEI Class System]
Certainty may be expressed by one of
- the predefined symbolic values high, medium, or low. The value unknown should be used in cases where the
- encoder does not wish to assert an opinion about the
- matter.
-
-
-
-
-
-
2.5.2. teidata.count
-
-
-
-
teidata.countdefines the range of attribute values used for a
- non-negative integer value used as a count.
Certainty may be expressed by one of the predefined symbolic values high, medium, or low. The value unknown should be used in cases where the encoder does not wish to assert an opinion about the matter.
2.5.2. teidata.count
teidata.countdefines the range of attribute values used for a non-negative integer value used as a count.
<time dur-iso="PT0,75H">three-quarters of an hour</time>
-
-
-
Example
-
<date dur-iso="P1,5D">a day
- and a half</date>
-
-
-
Example
-
<date dur-iso="P14D">a
- fortnight</date>
-
-
-
Example
-
<time dur-iso="PT0.02S">20
- ms</time>
-
-
-
Note
-
A duration is expressed as a sequence
- of number-letter pairs, preceded by the letter P; the letter
- gives the unit and may be Y (year), M (month), D (day), H
- (hour), M (minute), or S (second), in that order. The
- numbers are all unsigned integers, except for the last,
- which may have a decimal component (using either
- . or , as the decimal point;
- the latter is preferred). If any number is 0, then that number-letter pair
- may be omitted. If any of the H (hour), M (minute), or S
- (second) number-letter pairs are present, then the separator
- T must precede the first ‘time’
- number-letter pair.
For complete details, see ISO 8601
- Data elements and interchange
- formats — Information interchange — Representation of
- dates and times.
-
-
-
-
-
-
2.5.4. teidata.duration.w3c
-
-
-
-
teidata.duration.w3cdefines the
- range of attribute values available for representation of a
- duration in time using W3C datatypes.
<time dur-iso="PT0,75H">three-quarters of an hour</time>
Example
<date dur-iso="P1,5D">a day and a half</date>
Example
<date dur-iso="P14D">a fortnight</date>
Example
<time dur-iso="PT0.02S">20 ms</time>
Note
A duration is expressed as a sequence of number-letter pairs, preceded by the letter P; the letter gives the unit and may be Y (year), M (month), D (day), H (hour), M (minute), or S (second), in that order. The numbers are all unsigned integers, except for the last, which may have a decimal component (using either . or , as the decimal point; the latter is preferred). If any number is 0, then that number-letter pair may be omitted. If any of the H (hour), M (minute), or S (second) number-letter pairs are present, then the separator T must precede the first ‘time’ number-letter pair.
For complete details, see ISO 8601 Data elements and interchange formats — Information interchange — Representation of dates and times.
2.5.4. teidata.duration.w3c
teidata.duration.w3cdefines the range of attribute values available for representation of a duration in time using W3C datatypes.
A duration is expressed as a sequence
- of number-letter pairs, preceded by the letter P; the letter
- gives the unit and may be Y (year), M (month), D (day), H
- (hour), M (minute), or S (second), in that order. The
- numbers are all unsigned integers, except for the
- S number, which may have a decimal
- component (using . as the decimal point). If
- any number is 0, then that
- number-letter pair may be omitted. If any of the H (hour), M
- (minute), or S (second) number-letter pairs are present,
- then the separator T must precede the first
- ‘time’ number-letter pair.
A duration is expressed as a sequence of number-letter pairs, preceded by the letter P; the letter gives the unit and may be Y (year), M (month), D (day), H (hour), M (minute), or S (second), in that order. The numbers are all unsigned integers, except for the S number, which may have a decimal component (using . as the decimal point). If any number is 0, then that number-letter pair may be omitted. If any of the H (hour), M (minute), or S (second) number-letter pairs are present, then the separator T must precede the first ‘time’ number-letter pair.
Attributes using this datatype must
- contain a single ‘word’ which contains only letters, digits,
- punctuation characters, or symbols: thus it cannot include
- whitespace.
Typically, the list of documented
- possibilities will be provided (or exemplified) by a value
- list in the associated attribute specification, expressed
- with a <valList>
- element.
-
-
-
-
-
-
2.5.6. teidata.language
-
-
-
-
teidata.languagedefines the range of attribute values used to
- identify a particular combination of human language and
- writing system. [6.1. Language Identification]
Attributes using this datatype must contain a single ‘word’ which contains only letters, digits, punctuation characters, or symbols: thus it cannot include whitespace.
Typically, the list of documented possibilities will be provided (or exemplified) by a value list in the associated attribute specification, expressed with a <valList> element.
2.5.6. teidata.language
teidata.languagedefines the range of attribute values used to identify a particular combination of human language and writing system. [6.1. Language Identification]
The values for this attribute are
- language ‘tags’ as defined in BCP 47.
- Currently BCP 47 comprises RFC 5646 and RFC 4647; over time,
- other IETF documents may succeed these as the best current
- practice.
A ‘language tag’, per BCP 47, is assembled
- from a sequence of components or subtags separated by the hyphen character (-, U+002D). The tag is made of
- the following subtags, in the following order. Every subtag
- except the first is optional. If present, each occurs only
- once, except the fourth and fifth components (variant and
- extension), which are repeatable.
-
language
-
The IANA-registered code for the language. This is
- almost always the same as the ISO 639 2-letter language
- code if there is one. The list of available registered
- language subtags can be found at http://www.iana.org/assignments/language-subtag-registry.
- It is recommended that this code be written in lower
- case.
-
script
-
The ISO 15924 code for the script. These codes consist
- of 4 letters, and it is recommended they be written with
- an initial capital, the other three letters in lower
- case. The canonical list of codes is maintained by the
- Unicode Consortium, and is available at http://unicode.org/iso15924/iso15924-codes.html.
- The IETF recommends this code be omitted unless it is
- necessary to make a distinction you need.
-
region
-
Either an ISO 3166 country code or a UN M.49 region code
- that is registered with IANA (not all such codes are
- registered, e.g. UN codes for economic groupings or
- codes for countries for which there is already an ISO
- 3166 2-letter code are not registered). The former
- consist of 2 letters, and it is recommended they be
- written in upper case; the list of codes can be searched
- or browsed at https://www.iso.org/obp/ui/#search/code/.
- The latter consist of 3 digits; the list of codes can be
- found at http://unstats.un.org/unsd/methods/m49/m49.htm.
-
variant
-
An IANA-registered variation. These codes are used to indicate additional,
- well-recognized variations that define a language or
- its dialects that are not covered by other available
- subtags.
-
extension
-
An extension has the format of a single letter followed
- by a hyphen followed by additional subtags. These exist
- to allow for future extension to BCP 47, but as of this
- writing no such extensions are in use.
-
private use
-
An extension that uses the initial subtag of the single
- letter x (i.e., starts
- with x-) has no meaning except as
- negotiated among the parties involved. These should be
- used with great care, since they interfere with the
- interoperability that use of RFC 4646 is intended to
- promote. In order for a document that makes use of these
- subtags to be TEI-conformant, a corresponding <language>
- element must be present in the TEI header.
-
There are two exceptions to the above format. First,
- there are language tags in the IANA registry that do not match the above syntax,
- but are present because they have been ‘grandfathered’ from
- previous specifications.
Second, an entire language
- tag can consist of only a private use subtag. These tags
- start with x-, and do not need to follow any
- further rules established by the IETF and endorsed by these
- Guidelines. Like all language tags that make use of private
- use subtags, the language in question must be documented in
- a corresponding <language> element in
- the TEI header.
Examples include
-
sn
-
Shona
-
zh-TW
-
Taiwanese
-
zh-Hant-HK
-
Chinese written in traditional script as used in Hong
- Kong
-
en-SL
-
English as spoken in Sierra Leone
-
pl
-
Polish
-
es-MX
-
Spanish as spoken in Mexico
-
es-419
-
Spanish as spoken in Latin America
-
The W3C Internationalization Activity has published a
- useful introduction to BCP 47, Language tags in HTML and XML.
-
-
-
-
-
-
2.5.7. teidata.name
-
-
-
-
teidata.namedefines the range of attribute values expressed as
- an XML Name.
The values for this attribute are language ‘tags’ as defined in BCP 47. Currently BCP 47 comprises RFC 5646 and RFC 4647; over time, other IETF documents may succeed these as the best current practice.
A ‘language tag’, per BCP 47, is assembled from a sequence of components or subtags separated by the hyphen character (-, U+002D). The tag is made of the following subtags, in the following order. Every subtag except the first is optional. If present, each occurs only once, except the fourth and fifth components (variant and extension), which are repeatable.
language
The IANA-registered code for the language. This is almost always the same as the ISO 639 2-letter language code if there is one. The list of available registered language subtags can be found at http://www.iana.org/assignments/language-subtag-registry. It is recommended that this code be written in lower case.
script
The ISO 15924 code for the script. These codes consist of 4 letters, and it is recommended they be written with an initial capital, the other three letters in lower case. The canonical list of codes is maintained by the Unicode Consortium, and is available at http://unicode.org/iso15924/iso15924-codes.html. The IETF recommends this code be omitted unless it is necessary to make a distinction you need.
region
Either an ISO 3166 country code or a UN M.49 region code that is registered with IANA (not all such codes are registered, e.g. UN codes for economic groupings or codes for countries for which there is already an ISO 3166 2-letter code are not registered). The former consist of 2 letters, and it is recommended they be written in upper case; the list of codes can be searched or browsed at https://www.iso.org/obp/ui/#search/code/. The latter consist of 3 digits; the list of codes can be found at http://unstats.un.org/unsd/methods/m49/m49.htm.
variant
An IANA-registered variation. These codes are used to indicate additional, well-recognized variations that define a language or its dialects that are not covered by other available subtags.
extension
An extension has the format of a single letter followed by a hyphen followed by additional subtags. These exist to allow for future extension to BCP 47, but as of this writing no such extensions are in use.
private use
An extension that uses the initial subtag of the single letter x (i.e., starts with x-) has no meaning except as negotiated among the parties involved. These should be used with great care, since they interfere with the interoperability that use of RFC 4646 is intended to promote. In order for a document that makes use of these subtags to be TEI-conformant, a corresponding <language> element must be present in the TEI header.
There are two exceptions to the above format. First, there are language tags in the IANA registry that do not match the above syntax, but are present because they have been ‘grandfathered’ from previous specifications.
Second, an entire language tag can consist of only a private use subtag. These tags start with x-, and do not need to follow any further rules established by the IETF and endorsed by these Guidelines. Like all language tags that make use of private use subtags, the language in question must be documented in a corresponding <language> element in the TEI header.
Examples include
sn
Shona
zh-TW
Taiwanese
zh-Hant-HK
Chinese written in traditional script as used in Hong Kong
Attributes using this datatype must
- contain a single word which follows the rules defining a
- legal XML name (see http://www.w3.org/TR/REC-xml/#dt-name):
- for example they cannot include whitespace or begin with
- digits.
-
-
-
-
-
-
2.5.8. teidata.namespace
-
-
-
-
teidata.namespacedefines the range of attribute values used to
- indicate XML namespaces as defined by the W3C Namespaces in XML Technical
- Recommendation.
Attributes using this datatype must contain a single word which follows the rules defining a legal XML name (see http://www.w3.org/TR/REC-xml/#dt-name): for example they cannot include whitespace or begin with digits.
2.5.8. teidata.namespace
teidata.namespacedefines the range of attribute values used to indicate XML namespaces as defined by the W3C Namespaces in XML Technical Recommendation.
Any numeric value, represented as a
- decimal number, in floating point format, or as a
- ratio.
To represent a floating point number, expressed
- in scientific notation, ‘E notation’, a variant of
- ‘exponential notation’, may be used. In this format, the
- value is expressed as two numbers separated by the letter E.
- The first number, the significand (sometimes called the
- mantissa) is given in decimal format, while the second is an
- integer. The value is obtained by multiplying the mantissa
- by 10 the number of times indicated by the integer. Thus the
- value represented in decimal notation as 1000.0 might be
- represented in scientific notation as 10E3.
A value
- expressed as a ratio is represented by two integer values
- separated by a solidus (/) character. Thus, the value
- represented in decimal notation as 0.5 might be represented
- as a ratio by the string 1/2.
-
-
-
-
-
-
2.5.10. teidata.outputMeasurement
-
-
-
-
teidata.outputMeasurementdefines a
- range of values for use in specifying the size of an object
- that is intended for display.
Any numeric value, represented as a decimal number, in floating point format, or as a ratio.
To represent a floating point number, expressed in scientific notation, ‘E notation’, a variant of ‘exponential notation’, may be used. In this format, the value is expressed as two numbers separated by the letter E. The first number, the significand (sometimes called the mantissa) is given in decimal format, while the second is an integer. The value is obtained by multiplying the mantissa by 10 the number of times indicated by the integer. Thus the value represented in decimal notation as 1000.0 might be represented in scientific notation as 10E3.
A value expressed as a ratio is represented by two integer values separated by a solidus (/) character. Thus, the value represented in decimal notation as 0.5 might be represented as a ratio by the string 1/2.
2.5.10. teidata.outputMeasurement
teidata.outputMeasurementdefines a range of values for use in specifying the size of an object that is intended for display.
<figure><head>The TEI Logo</head><figDesc>Stylized yellow angle brackets
- with the letters <mentioned>TEI</mentioned> in between and <mentioned>text encoding
- initiative</mentioned> underneath, all on a white
- background.</figDesc>
- <graphic height="600px" width="600px" url="http://www.tei-c.org/logos/TEI-600.jpg"/>
- </figure>
-
-
-
Note
-
These values map directly onto the
- values used by XSL-FO and CSS. For definitions of the units
- see those specifications; at the time of this writing the
- most complete list is in the CSS3 working draft.
-
-
-
-
-
-
2.5.11. teidata.pattern
-
-
-
-
teidata.patterndefines attribute values which are expressed as a
- regular expression.
<figure>
+ <head>The TEI Logo</head>
+ <figDesc>Stylized yellow angle brackets with the letters <mentioned>TEI</mentioned> in
+ between and <mentioned>text encoding initiative</mentioned> underneath, all on a white
+ background.</figDesc>
+ <graphic height="600px" width="600px"
+ url="http://www.tei-c.org/logos/TEI-600.jpg"/>
+</figure>
Note
These values map directly onto the values used by XSL-FO and CSS. For definitions of the units see those specifications; at the time of this writing the most complete list is in the CSS3 working draft.
2.5.11. teidata.pattern
teidata.patterndefines attribute values which are expressed as a regular expression.
A regular expression, often called a
- pattern, is an expression
- that describes a set of strings. They are usually used
- to give a concise description of a set, without having
- to list all elements. For example, the set containing
- the three strings Handel,
- Händel, and Haendel can be described by
- the pattern H(ä|ae?)ndel (or alternatively,
- it is said that the pattern H(ä|ae?)ndel
- matches each of the three
- strings)
This TEI datatype is mapped to the XSD token datatype,
- and may therefore contain any string of characters. However,
- it is recommended that the value used conform to the
- particular flavour of regular expression syntax supported by
- XSD Schema.
-
-
-
-
-
-
2.5.12. teidata.point
-
-
-
-
teidata.pointdefines the data type used to express a point in
- cartesian space.
A regular expression, often called a pattern, is an expression that describes a set of strings. They are usually used to give a concise description of a set, without having to list all elements. For example, the set containing the three strings Handel, Händel, and Haendel can be described by the pattern H(ä|ae?)ndel (or alternatively, it is said that the pattern H(ä|ae?)ndelmatches each of the three strings)
This TEI datatype is mapped to the XSD token datatype, and may therefore contain any string of characters. However, it is recommended that the value used conform to the particular flavour of regular expression syntax supported by XSD Schema.
2.5.12. teidata.point
teidata.pointdefines the data type used to express a point in cartesian space.
A point is defined by two numeric
- values, which should be expressed as decimal numbers.
- Neither number can end in a decimal point. E.g., both 0.0,84.2 and 0,84 are allowed, but 0.,84. is not.
-
-
-
-
-
-
2.5.13. teidata.pointer
-
-
-
-
teidata.pointerdefines the range of attribute values used to
- provide a single URI, absolute or relative, pointing to some
- other resource, either within the current document or
- elsewhere.
A point is defined by two numeric values, which should be expressed as decimal numbers. Neither number can end in a decimal point. E.g., both 0.0,84.2 and 0,84 are allowed, but 0.,84. is not.
2.5.13. teidata.pointer
teidata.pointerdefines the range of attribute values used to provide a single URI, absolute or relative, pointing to some other resource, either within the current document or elsewhere.
The range of syntactically valid values
- is defined by RFC 3986
- Uniform Resource Identifier (URI):
- Generic Syntax. Note that the values themselves
- are encoded using RFC 3987
- Internationalized Resource
- Identifiers (IRIs) mapping to URIs. For example,
- https://secure.wikimedia.org/wikipedia/en/wiki/%
- is encoded as
- https://secure.wikimedia.org/wikipedia/en/wiki/%25
- while http://موقع.وزارة-الاتصالات.مصر/ is
- encoded as
- http://xn--4gbrim.xn----rmckbbajlc6dj7bxne2c.xn--wgbh1c/
-
-
-
-
-
-
2.5.14. teidata.probCert
-
-
-
-
teidata.probCertdefines a range of attribute values which can be
- expressed either as a numeric probability or as a coded
- certainty value.
The range of syntactically valid values is defined by RFC 3986Uniform Resource Identifier (URI): Generic Syntax. Note that the values themselves are encoded using RFC 3987Internationalized Resource Identifiers (IRIs) mapping to URIs. For example, https://secure.wikimedia.org/wikipedia/en/wiki/% is encoded as https://secure.wikimedia.org/wikipedia/en/wiki/%25 while http://موقع.وزارة-الاتصالات.مصر/ is encoded as http://xn--4gbrim.xn----rmckbbajlc6dj7bxne2c.xn--wgbh1c/
2.5.14. teidata.probCert
teidata.probCertdefines a range of attribute values which can be expressed either as a numeric probability or as a coded certainty value.
teidata.temporal.isodefines the
- range of attribute values expressing a temporal expression
- such as a date, a time, or a combination of them, that
- conform to the international standard Data elements and interchange formats – Information
- interchange – Representation of dates and
- times.
teidata.temporal.isodefines the range of attribute values expressing a temporal expression such as a date, a time, or a combination of them, that conform to the international standard Data elements and interchange formats – Information interchange – Representation of dates and times.
If it is likely that the value used is
- to be compared with another, then a time zone indicator
- should always be included, and only the dateTime
- representation should be used.
For all representations
- for which ISO 8601 describes both a basic and an extended
- format, these Guidelines recommend use of the extended
- format.
While ISO 8601 permits the use of both
- 00:00 and 24:00 to represent
- midnight, these Guidelines strongly recommend against the
- use of 24:00.
-
-
-
-
-
-
2.5.19. teidata.temporal.w3c
-
-
-
-
teidata.temporal.w3cdefines the
- range of attribute values expressing a temporal expression
- such as a date, a time, or a combination of them, that
- conform to the W3C XML Schema Part 2:
- Datatypes Second Edition
- specification.
If it is likely that the value used is to be compared with another, then a time zone indicator should always be included, and only the dateTime representation should be used.
For all representations for which ISO 8601 describes both a basic and an extended format, these Guidelines recommend use of the extended format.
While ISO 8601 permits the use of both 00:00 and 24:00 to represent midnight, these Guidelines strongly recommend against the use of 24:00.
2.5.19. teidata.temporal.w3c
teidata.temporal.w3cdefines the range of attribute values expressing a temporal expression such as a date, a time, or a combination of them, that conform to the W3C XML Schema Part 2: Datatypes Second Edition specification.
If it is likely that the value used is
- to be compared with another, then a time zone indicator
- should always be included, and only the dateTime
- representation should be used.
-
-
-
-
-
-
2.5.20. teidata.temporal.working
-
-
-
-
teidata.temporal.workingdefines the
- range of values, conforming to the W3C XML Schema Part 2: Datatypes Second Edition
- specification, expressing a date or a date and a time within
- the working life of the document.
If it is likely that the value used is
- to be compared with another, then a time zone indicator
- should always be included, and only the dateTime
- representation should be used.
The earliest time
- expressable with this datatype is 01 January 1970 (the Unix
- Epoch), which could be written as either 1970-01-01 or
- 1970-01-01T00:00:00Z.
-
-
-
-
-
-
2.5.21. teidata.text
-
-
-
-
teidata.textdefines the range of attribute values used to
- express some kind of identifying string as a single sequence
- of Unicode characters possibly including
- whitespace.
If it is likely that the value used is to be compared with another, then a time zone indicator should always be included, and only the dateTime representation should be used.
2.5.20. teidata.text
teidata.textdefines the range of attribute values used to express some kind of identifying string as a single sequence of Unicode characters possibly including whitespace.
The possible values of this datatype
- are 1 or true, or 0 or false.
This datatype applies
- only for cases where uncertainty is inappropriate; if the
- attribute concerned may have a value other than true or
- false, e.g. unknown, or inapplicable, it should have the
- extended version of this datatype: teidata.xTruthValue.
-
-
-
-
-
-
2.5.23. teidata.unboundedInt
-
-
-
-
teidata.unboundedIntdefines an
- attribute value which can be either any non-negative integer
- or the string "unbounded".
The possible values of this datatype are 1 or true, or 0 or false.
This datatype applies only for cases where uncertainty is inappropriate; if the attribute concerned may have a value other than true or false, e.g. unknown, or inapplicable, it should have the extended version of this datatype: data.xTruthValue.
2.5.22. teidata.unboundedInt
teidata.unboundedIntdefines an attribute value which can be either any non-negative integer or the string "unbounded".
The value of this attribute follows the
- pattern specified by the Unicode consortium for its version
- number (http://unicode.org/versions/). A
- version number contains digits and fullstop characters only.
- The first number supplied identifies the major version
- number. A second and third number, for minor and sub-minor
- version numbers, may also be supplied.
-
-
-
-
-
-
2.5.25. teidata.versionNumber
-
-
-
-
teidata.versionNumberdefines the
- range of attribute values used for version
- numbers.
The value of this attribute follows the pattern specified by the Unicode consortium for its version number (http://unicode.org/versions/). A version number contains digits and fullstop characters only. The first number supplied identifies the major version number. A second and third number, for minor and sub-minor version numbers, may also be supplied.
2.5.24. teidata.versionNumber
teidata.versionNumberdefines the range of attribute values used for version numbers.
Attributes using this datatype must
- contain a single ‘word’ which contains only letters, digits,
- punctuation characters, or symbols: thus it cannot include
- whitespace.
-
-
-
-
-
-
2.5.27. teidata.xTruthValue
-
-
-
-
teidata.xTruthValue (extended truth
- value) defines the range of attribute
- values used to express a truth value which may be
- unknown.
Attributes using this datatype must contain a single ‘word’ which contains only letters, digits, punctuation characters, or symbols: thus it cannot include whitespace.
2.5.26. teidata.xTruthValue
teidata.xTruthValue (extended truth value) defines the range of attribute values used to express a truth value which may be unknown.
Any XPath expression using the syntax
- defined in 6.2..
When writing programs that evaluate
- XPath expressions, programmers should be mindful of the
- possibility of malicious code injection attacks. For further
- information about XPath injection attacks, see the article at OWASP.
-
-
-
-
-
-
\ No newline at end of file
diff --git a/documentation/schema/Syriacamsdesc.odd b/documentation/schema/Syriacamsdesc.odd
index fbe7002..716700a 100644
--- a/documentation/schema/Syriacamsdesc.odd
+++ b/documentation/schema/Syriacamsdesc.odd
@@ -1952,25 +1952,141 @@
-->
- The Heading [UNDER REVISION]
+ The Heading
+ SMBL has used the head element to provide summary
+ information about the manuscript or manuscript part.
An auto-generated paragraph describing the masnucript contents has been
- inserted into the head section of each file.
+ inserted into the head element as a note with a
+ type attribute whose value is contents-note.
+ This note provides the title(s) of the first five top-level msItem elements.
+ Their values are copied from the title element of each item; final elipsis
+ indicates that there are more than five top-level manuscript items. Finally, the
+ total number of msItem elements, including descendant manuscript items,
+ is included in the note.
+
+
See the following example, from https://bl.syriac.uk/ms/1023:
+
+ This manuscript contains: Severus. The Hymns of Severus, etc., here only 159 (ܩܢܛ) in number.;
+ Supplicatory hymns of every kind, arranged according to the eight tones.; Cantus ad Magnificat, arranged according to the eight tones.;
+ Additional hymns, arranged according to the eight tones.; Additional.; ...
+ In total, including sub-sections, this manuscript contains 26 items.
+
+
+
For composite manuscripts, the contents note will instead direct the reader to
+ the individual parts for a summary of the contents.
+
Following the contents note, the head element may have a number of
+ listRelation elements.
+ SMBL has recorded the genre classification provided in Wright's Catalogue
+ in a listRelation element with type whose value is Wright-BL-Taxonomy.
+ The taxonomy is recorded in a child relation element given a name attribute of dcterms:type
+ and a ref attribute of http://purl.org/dc/terms/type. The manuscript or part URI
+ is given as the value of the active attribute. A corresponding xml:id attribute value from the
+ category in the taxonomy element is referenced as the value of the passive attribute.
+ Finally, the human-readable label from the same category element is used as a text node of the relation's child
+ desc element.
+
+
An example of Wright's taxonomy encoded in the head element:
+
+
+
+
+ Choral Books
+
+
+
+
+
For composite manuscripts, which contain one or more msPart elements,
+ the manuscript record as well as each individual part will have a listRelation
+ element defining the part-to-whole relationships between the composite manuscript and its parts.
+
The listRelation element has been given a type attribute with the values
+ composite-to-parts or part-to-composite. A child desc element
+ provides a human-readable explanation of the list of relations. It is followed by a series of
+ relation elements that define the part-to-whole or whole-to-part relationships.
+
The relation element includes active and passive
+ attributes whose values are the SMBL URIs for the composite manuscript and the specific manuscript part.
+ Each element also includes a name attribute and ref attribute
+ that define the relationship. The active, passive, and ref attributes can be
+ understood as a triple, so in the example below one migh read:
+ https://bl.syriac.uk/ms/100 has-unspecified-codicological-part https://bl.syriac.uk/ms/101.
+ Finally, a child desc element provides a human-readable label consisting of
+ the shelfmark, and folios if applicable, of the composite or part referenced in the passive attribute.
+
+ SMBL has used the following values for the name and ref attributes for
+ composite-to-parts type listRelation elements:
+
The following example from https://bl.syriac.uk/ms/100
+ shows the use of a listRelation element for relating composites and their parts:
+
+
+ This composite manuscript consists of 3 distinct parts:
+
+ Add. 14,438, foll. 1–49
+
+
+ Add. 14,438, foll. 50–52
+
+
+ Add. 14,438, foll. 53–101
+
+
+
+
+ SMBL has used the following values for the name and ref attributes for
+ part-to-composite type listRelation elements:
+
The following example from https://bl.syriac.uk/ms/101
+ shows a full head element for a manuscript part.
+
+
- This manuscript contains: Philoxenus
- of Mabūg. The discourses of Philoxenus of Mabūg on Christian
- life and character. In total, including sub-sections, this
- manuscript contains 9 items.
+ This manuscript contains:
+ The book of Deuteronomy, according to the Peshitta version. In total, including sub-sections,
+ this manuscript contains 1 item.
-
- Individual Authors
+
+ Old Testament
+
+
+
+ This unit is a part of a composite manuscript:
+
+ Add. 14,438
-
+
Notes for Review Editors (2024)
Please ignore any errors in the head element and its summary.
@@ -1978,6 +2094,11 @@
section is provided for the convenience of the editors undertaking a
revision of the data in 2024 and will be deleted from the final
documentation.
+
Divergences from Consolidated Schema:
+ SMBL has used the head element differently than the Consolidated schema
+ and has not provided a summary title or origin place and date information. Instead, we have used
+ dedicated note and listRelation elements to record summary information about the
+ manuscript and part records.
- Didymus of Alexandria. Fol.
+ Didymus of Alexandria. Fol.
24 b.
- Dionysius the Areopagite:
Dionysius the Areopagite: epistle to Timothy , fol.
19 b; to Titus , fol. 27 b.
- Epiphanius:
the
+ Epiphanius: the
Ancoratus. Fol. 26
a.
- Ephraim: foll. 21
+ Ephraim: foll. 21
a, 25 a, 30 a, 31
b; ܥܠ ܣܒܐ
@@ -3388,7 +3572,7 @@
-->
- Filiation [UNDER REVISION]
+ Filiation
In one test case we have used the filiation element to
encode information that Wright provides about the relationship
of one manuscript to other surviving manuscripts in terms of
@@ -3410,6 +3594,9 @@
In the future, we may chose to convert other references
to this usage of filiation.
+
Notes for Review Editors (2024)
+
Please ignore instances of this element, and for now instead encode any information about the relationships
+ between manuscripts in terms of their contents using a note element.
@@ -4440,8 +4627,87 @@
- Hand Description [UNDER REVISION]
-
Further documentation will be added here.
+ Hand Description
+
Each distinct hand and/or script in the codicological unit has been
+ described in a separate handNote element in the
+ handDesc element. The handDesc element itself
+ has an attribute hands which has been used to record the
+ number of hands identified, including both those involved in the
+ original production of the unit and those contributing later additions.
+
Each handNote element must have an xml:id attribute.
+
The scope attribute can be used to indicate the extent of
+ the hand's appearance in the manuscript. Its values can be one
+ of:
+
+
+ sole
+
+
+ major
+
+
+ minor
+
+
+
The script attribute provides a
+ classification of the script. Oftentimes, only the broadest
+ classification is possible.
SMBL has used a combination
+ of an ISO 639 Language Code with an optional ISO 15924 script code to encode a hand's script information. The script can take multiple, space-separated script values
+
The accepted script values are:
+
+ arUnspecified Arabic script
+ ar-SyrcSyro-Arabic garshunography in unspecified Syriac script
+ ar-SyrnSyro-Arabic garshunography in East Syriac script
+ copUnspecified Coptic script
+ deUnspecified German script
+ enUnspecified English script
+ frUnspecified French script
+ grcUnspecified Greek script
+ heUnspecified Hebrew script
+ hyUnspecified Armenian script
+ itUnspecified Italian script
+ laUnspecified Latin script
+ qhy-x-cpasChristian Palestinian Aramaic script
+ syrUnspecified Syriac script
+ syr-ArabArabo-Syriac garshunography in unspecified Arabic script
+ syr-SyreEstrangela script
+ syr-SyrjWest Syriac script
+ syr-SyrnEast Syriac script
+ syr-x-syrmMelkite Syriac script
+ trUnspecified Turkish script
+ tr-SyrcSyro-Turkish garshunography in unspecified Syriac script
+ xclUnspecified Classical Armenian script
+ undUndetermined
+ mulMultiple scripts
+
+
Each handNote should contain a medium attribute describing
+ the tint or type of ink used by the hand, if known.
+ Typically this will be "unknown" unless Wright provides information about the ink,
+ as in this modifed example from https://bl.syriac.uk/ms/25
+
+
+ This volume is written throughout in a beautiful Edessene character, and dated A. Gr. 723, A.D. 412. The colophon is written with green paint, and the doxology with yellow.
+
+
+
A handNote may contain references to folios,
+ optionally tagged with a locus element;
+ composition dates, or paleographic estimates, tagged with date elements;
+ or the name of the scribe(s), tagged with persName elements.
+
Divergences from Consolidated Schema:
+ SMBL has included in the calculation of the
+ hands attribute, in handDesc,
+ both the hands involved in the original production of the manuscript,
+ and those responsible for later additions.
+ SMBL has not made use of the sameAs attribute
+ for cross-referencing the occurence of a given hand across two codicological units.
+ SMBL employs a different set of values for the script attribute
+ to better fit the scope of the British Library collection. Likewise, we have not used
+ the execution attribute, as there is no standard classification for Syriac manuscripts.
+ Nor have we used the term element for further classifying
+ script or punctation characteristics. Wright's description, when present,
+ of the execution and punctuation have been recorded but left untagged.
- Decoration Description [UNDER REVISION]
-
Further documentation will be added here.
+ Decoration Description
+ SMBL has used decoNote elements within the decoDesc
+ to record information about decorative features in a manuscript. Each decoNote element
+ may have a locus element, which records the folio location(s) on which the decorative
+ elements appear using from, and optionally to, attributes. A prose
+ text node records Wright's description of the decorative feature, with the exception of rubrication
+ where a text node was omitted if Wright does not provide additional details.
+
Each decoNote element has a type attribute.
+
SMBL uses a subset of the Fihrist vocabulary, with one addition ornamentation which
+ refers to any sort of undifferentiated ornamentation. The allowed values are as follows:
+
+ border
+ diagram
+ illustration
+ initial
+ marginal
+ mixed
+ ornamentation
+ rubrication
+ vignette
+
+
Multiple instances of decoration have been recorded in separate decoNote elements,
+ as in the following example from https://bl.syriac.uk/ms/122:
+
+
+
+
+ Ornamented capitals in the Ammonian sections and Eusebian canons.
+
+
+ Ornamentation at the top of fol. 14b.
+
+
+ The figure of a fish on the lower margin of fol. 14b.
+
+
+
+
+
Optionally,
SMBL has employed a subtype attribute to incorporate
+ the decoration vocabulary of the Hill Museum and Manuscripts Library.
+
The following terms derive from the vHMML Features List,
+ employed by the Hill Museum and Manuscript Library:
+
+
+
+ SMBL Subtype Value
+ vHMML Feature Term
+ vHMML Scope notes
+
+
+ hmml:border
+ Border(s), Decorative
+ A continuous decorative design which creates a frame around part or all of a page
+
+
+ hmml:canon-table
+ Canon table(s)
+ A Gospel concordance system devised in the fourth century by Eusebius of Caesarea, in which Gospel passages are numbered in the text (generally in the margins) and correspond to tables, arranged in columnar form, indicating the concordance of passages among the Gospels
+
+
+ hmm:chart
+ Chart(s)
+ Use for display of information arranged in graphic form other than a table
+
+
+ hmml:coat-of-arms
+ Coat(s) of arms
+
+
+
+ hmml:anthropomorphic
+ Decoration, Anthropomorphic
+ Decoration which incorporates all or part of the human body
+
+
+ hmml:architectural
+ Decoration, Architectural
+
+
+
+ hmml:calligraphic
+ Decoration, Calligraphic
+ Do not apply if it is 'plain' writing within a decorative element.
+
+
+ hmml:full-page
+ Decoration, Full-page
+
+
+
+ hmml:geometric
+ Decoration, Geometric
+
+
+
+ hmml:vegetative
+ Decoration, Vegetative
+ Decoration which incorporates plant forms
+
+
+ hmml:zoomorphic
+ Decoration, Zoomorphic
+ Decoration which incorporates animal forms
+
+
+ hmml:diagram
+ Diagram(s)
+ Representation of information graphically, excluding tables
+
+
+ hmml:drawing
+ Drawing(s)
+ Use for pen & ink drawings; some may have color. May or may not be Illustration(s) to the text.
+
+
+ hmml:drollery
+ Drolleries
+ Amusing figures, often of a grotesque character
+
+
+ hmml:engraving
+ Engraving(s)
+ A print taken from an engraved plate
+
+
+ hmml:genealogical-table
+ Genealogical table(s)
+
+
+
+ hmml:headpiece
+ Headpiece(s)
+ Decoration at the head of a book title/chapter/division. USE: particularly for Armenian, Islamic, Persian, and Western manuscripts
+
+
+ hmml:illumination
+ Illumination
+ Use of colors, especially gold or silver, for decoration
+
+
+ hmml:illustration
+ Illustration(s)
+ Use for printed works. For manuscripts, may be used in conjunction with Drawing(s) if appropriate
+
+
+ hmml:decorated-initial
+ Initial(s), Decorated
+ An initial composed of non-figural, non-zoomorphic decorative elements
+
+
+ hmml:historiated-initial
+ Initial(s), Historiated
+ A letter containing an identifiable scene or figures, sometimes relating to the text
+
+
+ hmml:zoomorphic-initial
+ Initial(s), Zoomorphic
+ An initial partly or wholly composed of animal forms
+
+
+ hmml:map
+ Map(s)
+
+
+
+ hmml:marginalia
+ Marginalia
+ Notes on the text written in the margins
+
+
+ hmml:miniature
+ Miniature(s)
+ A color illustration, not part of the decorative element. The term is from the Latin word 'miniare' (to color with red), and does not refer their size, which can be full-page. For pen & ink drawings in manuscripts, see Drawing(s) and Illustration(s)
+
+
+ hmml:music
+ Music
+
+
+
+ hmml:photograph
+ Photograph(s)
+
+
+
+ hmml:plan
+ Plan(s)
+
+
+
+ hmml:portrait
+ Portrait(s)
+
+
+
+ hmml:printer-device
+ Printer's device(s)
+
+
+
+ hmml:seal
+ Seal(s)
+
+
+
+ hmml:table
+ Table(s)
+ Use for display of information, typically in rectangular form, arranged in rows and/or columns. Do not use for Canon tables or for tables of contents
+
+
+ hmml:volvelle
+ Volvelle(s)
+ Wheel chart constructed with rotating parts of one or more layers attacted to a page/leaf. For examples, see: https://medievalbooks.nl/tag/volvelle for manuscripts, http://collation.folger.edu/2012/12/volvelles for early printed ones, and http://volvellery.tumblr.com/ for 20th century examples.
+
+
+ hmml:woodcut
+ Woodcut(s)
+ A print taken from an inked wood block with a raised design
+
+
+
+
The use of terms from the vHMML Features List allow greater specification,
+ as in this example from https://bl.syriac.uk/ms/122:
+
+
+
+ On fol. 1 b there is a rude drawing of an antelope.
+
+
+
+
Divergences from Consolidated Schema:
+ SMBL has not ordered decoNote elements according to any particular hierarchy.
+ SMBL has likewise not employed the primary, hierarchical list of values for the type attribute.
+ Instead, we have employed a subset of the Fihrist typology, with the addition of the generic ornamentation value.
+ The following terms from the Fihrist typology have been excluded due to being outside the scope of the SMBL project:
+
+ frieze
+ map
+ miniature
+ paratext
+ secondary
+ tooling
+ unspecified
+
+
+
Given the scope of descriptions provided by Wright,
SMBL does not employ persName elements
+ for artist names; nor have we included additional structure in the decoNote elements, instead providing the prose
+ description from Wright. Finally, SMBL has not employed the term element for classifying subjects of the decorations.
+