Welcome to the encoding guidelines for the second edition of A New Handbook of Syriac Literature (hereafter NHSL). NHSL a born-digital TEI-encoded reference work for the study of Syriac literature. The first volume, Bibliotheca Hagiographica Syriaca Electronica, was published by Syriaca.org in 2016 using a simple TEI schema to describe a single genre (hagiography). Past TEI-encoding practice has focused on describing specific manuscripts or creating editions of works. By contrast, the NHSL seeks to describe abstract or conceptual works (including unpublished ones) and to relate them to people, places, and other works, as well as to the manuscripts, editions, and translations that embody them. Two key features of this encoding model include using <bibl> for description of works and fully leveraging source for scholarly citations. These guidelines describe the methodology used to create TEI XML files for encoding Syriac literary data according to the schema implemented by Syriaca.org. We have chosen to use the TEI guidelines because they allow a high level of detail, citation of sources, and flexibility for representing prose data. We anticipate that this schema can be easily adapted for other historical corpora of texts and we invite comments and suggestions for improvement.
These guidelines reuse and adapt material published published by the Text Encoding Initiative Consortium as TEI: Guidelines for Electronic Text Encoding and Interchange in the P5 release, Version 4.11.0. Last updated on 18th February 2026, revision 358d2e48e. The TEI guidelines are reused here under the terms of the Creative Commons Attribution 3.0 Unported License.
The present document is also an update to previous documentation published by Syriaca.org. An initial schema and documentation for the first edition of A New Handbook of Syriac Literature was designed in 2016 by Nathan P. Gibson Jeanne-Nicole Mellon Saint-Laurent, David A. Michelson, Winona Salesky, and Daniel L. Schwartz. Portions of the earlier documentation have been reused below under the terms of the Creative Commons Attribution 4.0 International license. The current document represents guidelines for the second edition of A New Handbook of Syriac Literature.
In addition, prose and examples have been reused from the following sources:
Many of the work records in NHSL incorporate data from Ugo Zanetti and Claude Detienne, Bibliotheca Hagiographica Syriaca (unpublished database). That database was incorporated into NHSL by permission under the terms of the Creative Commons Attribution 3.0 Unported License. The database design of Bibliotheca Hagiographica Syriaca helped shape the data model for NHSL.
A New Handbook of Syriac Literature (NHSL) was conceived as part of a larger project to produce reference works (authority files) for the field of Syriac studies. The Syriaca.org data model is designed around identifying and describing seven core conceptual entities relevant to historical research:
http://syriaca.org/place/78)http://syriaca.org/person/13)http://syriaca.org/work/567)http://syriaca.org/cbss/M8NJIL53)For each of the above entities, Syriaca.org's primary goal is to publish ‘authority files’, e.g. reference works which establish a unique identifier for each person, place, primary source text, bibliographic citation, keyword, manuscript, and material artifact relevant to the field of Syriac studies. The format of the identifier is a URI, a technical specification which is described in more detail below; see Assigning Work URIs (Uniform Resource Identifiers). 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, NHSL has entries for more than 15 different hagiographic texts which are accounts of ‘The Forty Martyrs of Sebaste’. Accordingly, all Syriaca.org URIs are unique—each identifying only one conceptual entity. Thus, every different version of the passion of the ‘The Forty Martyrs of Sebaste’ 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.
NHSL is the Syriaca.org publication dedicated to
describing works of literature and is responsible for assinging URIs to
individual texts and textual traditions in the Syriaca.org data model.
Descriptions of literary works in NHSL can also
refer to URIs for any of the seven entities, thus a NHSL record for a particular work may define that text in
relation to other works, as well as to persons, modern bibliography, etc. In
each instance, these relationships will be encoded in the NSHL record as references to Syriaca.org URIs.
Taken as a whole, the entire Syriaca.org dataset of linked URIs forms a
"knowledge graph" or a map of relationships between URIs from the seven core
entitites. In the example of Ephrem the Syrian
(http://syriaca.org/person/13) and his work Hymns on Nisibis
(http://syriaca.org/work/8737) the relationship between
these two entities is part of the Syriaca.org knowledge graph.
NHSL is a reference work published by Syriaca.org to identify and describe texts which exist in Syriac or are relevant to Syriac studies. In library science terms, NHSL is a ‘title authority file’. The concept of a distinct work is the distinguishing criterion for each entry in NHSL. Each record in NHSL represents a unique conceptual entity, a single work that can be disambiguated from other works. The purpose of each record (and thus each XML file) is to provide information which describes the work identified with that record.
We have adopted the concept of a ‘work’ from two standards developed within the field of library science. These standards are the ‘Functional Requirements for Bibliographic Records (FRBR)’ and the ‘International Federation of Library Associations and Institutions Library Reference Model (IFLA LRM)’. The IFLA LRM was issued in 2024 and was developed out of the earlier FRBR model (published in 1998). NHSL was developed using the FRBR standard and updated for the second edition of NHSL to also comply with the IFLA LRM (as published in Pat Riva, Patrick Le Bœuf, Maja Žumer, IFLA Library Reference Model: A Conceptual Model for Bibliographic Information [International Federation of Library Associations and Institutions, August 2017, as emmended and corrected through December 2021, issued July 2024], https://repository.ifla.org/handle/20.500.14598/40.2).
The IFLA LRM defines a ‘work’ as ‘the intellectual or artistic content of a distinct creation’. For our purposes we limit ‘works’ to ‘literary works’ by which we mean all Syriac ‘texts’ (e.g., creative works which take written form, as opposed to visual art).
Each Work in NHSL is assigned a unique indentifier. Because ancient and medieval works often did not have titles, this unique indentifier is the essential element of every NHSL record. Both users and the database itself rely on this identifier to disambiguate work entries.
The format of identifier used in NHSL is that
of a URI (Uniform Resource Identifier), a technical standard established
by the World Wide Web
Consortium (W3C). In NHSL, the URIs
have the following format: http://syriaca.org/work/{\d+}
(where {\d+} signifies a unique string of digits). For
example, the work by Ephrem the Syrian Hymns on
Nisibis is assigned the following URI:
http://syriaca.org/work/8737. 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) that can be
used as a web address leading to a file which provides a definition of
the entity associated with the URI.
Or in simple terms, NHSL assigns the unique
URI http://syriaca.org/work/8737 as an ID number for the
concept of the Hymns on Nisibis, but that
URI is also a working URL which will load the NHSL record describing the Hymns on
Nisibis (see http://syriaca.org/work/8737).
In each NHSL record, this URI is encoded in an <idno> element in the <body> of the XML document. For a discussion of how to endcode the assigned URI as an <idno> element, see the documentation section below on Identifiers (<indo>) .
In terms of including works in NHSL, the editors interpret the scope of Syriac ‘literary works’ in a maximal rather than restrictive sense. NHSL does not intend the adjective ‘literary’ to be a limiting qualifier based on quality. For our purposes, all registers of Syriac texts from poetry to legal documents are ‘literary works’. In practical terms, we define a Syriac text as any item that one might want to identify in a list of contents in a manuscript catalog or refer to in a historical study. This definition encompasses all textual items which might historically have been transmitted from one manuscript to another but leaves some ambiguity with regards to marginalia, colophons, or ink tests which might or might not be considered ‘works’. The NHSL model allows these items to be described as ‘literary works’ should an editor make the case that they should be considered a such.
In addition, the NHSL model also includes ‘works’ which are hypothetical, mythological or ahistorical, or no longer extant. For example, there is an NHSL entry for the Philoxenian version of the New Testament (http://syriaca.org/work/10536) even though that work is only extant in fragments and indeed the existence of a Philoxenian translation may only be hypothetical for some books of the New Testament. In the same way, it would be possible to have an NHSL entry for ‘works’ whose existence is ahistorical but whose conceptual existence is mentioned in other works, for example the Syriaca dialogue poem of the Cherub and the Thief mentions a letter by written by Christ. Although this letter is a literary fiction, it could be given a URI in NHSL if an editor determined it would be useful for research into the theme of letters in Syriac poetry or a similar research purpose.
Bibliographic citation is an essential and required element for every entry in NHSL.
The intellectual contribution and purpose of NHSL is to establish URIs to compile and connect data from previous scholarship on the topic of Syriac Studies. Accordingly, our editorial policy assumes that our records will be primarily composed of information cited from primary and secondary sources, particularly earlier reference works in the field such as the Bibliotheca Hagiographica Syriaca (BHS), the Bibliotheca Hagiographica Orientalis (BHO), critical editions, and manuscript catalogues. As a reference work, NHSL is not intended as a venue for the first publication of original research. In general, our default editorial position will be to accept scholarly consensus and the results of existing scholarship as published. It is not within the scope of NHSL to systematically review and correct past scholarship in the field. Nevertheless, authors of NHSL records should not knowingly reproduce errors in previous scholarship.
When considering the TEI XML schema created for NHSL, it is essential to note that we have customized these guidelines specifically for use in digitally encoding litrary data related to the field of Syriac studies. Due to this specialized use, these guidelines do not include all possible TEI XML features which might be employed for historical or literary data in general. Moreover, because the main language of NHSL is English, these guidelines assume that each file will designate English as its main language.
We have written the guidelines below with the assumption that the resulting XML files for NHSL will be displayed using the custom Gaddel App developed by Syriaca.org and The Digital Lab at Vanderbilt University. For a more detailed discussion of the data model and architecture of Syriaca.org, readers are encouraged to consult the following technical publication: David A. Michelson, “Using Linked Open Data to Model Cultural Heritage Information: The Research Questions and Data Structures of the Syriaca.org Knowledge Graph,” in Linked Open Data for the Ancient Mediterranean: Structures, Practices, Prospects, edited by Sarah E. Bond, Paul Dilley, and Ryan Horne, ISAW Papers 20 (2021), http://hdl.handle.net/2333.1/69p8d8cc.
This section describes encoding conventions which can be employed with a number of different elements. In particular these conventions are used with the following elements, unless otherwise specified:
The language of an element's textual contents, such as that of a title, should be explicitly recorded using an xml:lang attribute. The contents of this attribute should be an ISO 639 Language code. Syriaca.org employs the two-character ISO 639-1 codes where possible, e.g. ‘en’ rather than ‘eng’. If no two-character code is available, use a three-character code from ISO 639-2 or ISO639-3. For textual contents in the Syriac language, Syriaca's convention is to use ‘syr’ rather than ‘syc’ to avoid confusion over distinguishing "Classical Syriac". For more on language code usage, see Syriaca.org Documentation: Language and Script Identifiers.
Explict tagging of language codes using xml:lang attributes is required on the following elements: <desc>, <foreign>, and <note>. This is also required on many <author> and <editor> elements.
| Code | Language |
|---|---|
| la | Latin |
| de | German |
| grc | Ancient Greek |
| gez | Geʽez |
| sog | Sogdian |
| ar | Arabic |
| hy | Armenian |
| ka | Georgian |
| sog | Soghdian |
| cu | Old Church Slavonic |
| cop | Coptic |
| gez | Ethiopic |
| syr-pal | Christian Palestinian Aramaic |
| ar-Syrc | Arabic in Syriac script (Garshuni) |
| ar-syr | Karshuni |
| de | German |
| fr | French |
| en | English |
| it | Italian |
| pt | Portugese |
| ru | Russian |
| nl | Dutch |
| ar | Arabic |
| es | Spanish |
| tr | Turkish |
Dates for manuscripts use the standard notBefore and notAfter attributes for date ranges, or when for exact dates. Dates must be expressed in ISO 8601 format (four-digit year, with leading zeroes for dates before CE 1000).
The values of these temporal attributes must be expressed as a date following
the ISO 8601
Date and Time format, that is YYYY-MM-DD, i.e. the year
followed by month followed by day. In most cases, however, only the year can
or should be included, e.g. ‘1014’. For dates prior
to the year 1000, leading zeroes must be supplied to ensure a four-digit
year, e.g. ‘0751’, ‘0010’,
‘0004’. Positive year values express dates in the
Common Era (CE); for earlier dates, use a negative year value: ‘-0450’ corresponds to 450 BCE (this practice
corresponds to the W3C standard XML Schema Part 2:
Datatypes Second Edition.
For more information on the use of dates within Syriaca.org, including guidelines for approximating date ranges for imprecise or uncertain ranges, see the Syriaca.org Dating Conventions document.
When encoding child elements nested within the main <bibl> element, NHSL records are required to cite their sources using either the source or resp attributes. A <quote> element always requires a source attribute. Either source or resp is required on <note> elements throughout the document unless that element has a child <quote> element. Either is also required when the following elements are part of the main work <bibl> for the record: <author>, <date>, <editor>, or <title>. Either may also appear on <bibl> and <relation> elements.
Whenever possible, the editorial policy of NHSL is that all information in a record should have citations to bibliographic references found in the Comprehensive Bibliography on Syriac Studies. Citations should be made using source as described below in Inserting Bibliographic Citations (source). In rare cases, editors of NHSL may provide attribution information not sourced to a primary or secondary source using the resp attribute as described below; see Asserting Information without a Source (resp). The use of source and resp are mutually exclusive. Editors should use resp only when it is not possible to use source.
Use of the source attribute is a method for pointing to a bibliographic item found in the ‘Bibliography Related to the Work’ section of the XML document. Before using source, editors must first encode an entry for the bibliographic item using the <bibl> element and a assign it an ID as described in the documentation section ‘Bibliography Related to the Work’ (<bibl>).
bib1-9,
bib1-24, and bib1-26.The addition of multiple citations for the same piece of information is, in general, not necessary or even recommended. When it occurs in NHSL it is often the result of the bulk importing of data. As an editorial practice for individual authors, a single source is all that is required (and recommended) for most information. When multiple sources are listed in a single source attribute, they should be sorted in ascending order based on the second numeric value in the xml:id, as demonstrated in the example above (-1, -2, -6, -23, etc.).
Direct quotations are indicated in NHSL according to two different methods: transcription using <title> and quotation using <quote>.
Transcriptions of name variants should be collected and encoded in <title> elements as a direct child of the main <bibl> element. These <title> elements must include a citation (using source) and their contents are be defintion interpreted to be verbatim quotations, with no further markup needed. See the discussion above concerning Inserting Bibliographic Citations (source). For more on supplying title variants in NHSL entries, see below under title (<title>)
In all other instances, direct quotations should be encoded by use of the <quote> element. The opening and closing of the <quote> element should mark the start and conclusion of the quotation. There is no need to use quotation marks in addition to the <quote> element. Quotation marks will be auto-generated and added to the HTML view of the record. All <quote> elements must include a citation (using source) following the method described above concerning Inserting Bibliographic Citations (source).
As discussed above in the section The Seven Core Entities of the Syriaca.org Data Model, one of the distinctive features ofNHSL is its integration with the Syriaca.org knowledge graph through the use of URIs to identify and link persons, places, literary works, and bibliography. For each of these entity types, Syriaca.org has published an ‘authority file’ which assigns a URI or Uniform Resource Identifier to every unique entry. Besides NHSL (the title authority file), these authority files include The Syriac Biographical Dictionary, The Syriac Gazetteer, and the Comprehensive Bibliography on Syriac Studies.
In NHSL, it is possible to link to Syriaca.org URIs within the following descriptive elements: <desc>, <note>, or <quote>. Use of Syriaca.org URIs to identify prose allusions to persons, places, works, etc. is strongly encouraged whenever possible. It should be noted that the use of Syriaca.org URIs in these sections is for descriptive purposes (i.e. relating the subject of the NHSL record to other places, persons, etc.). The inclusion of URIs in these cases does NOT assign a URI to the work record. For that separate function, see the section below: Identifiers (<indo>).
References to persons can appear in <desc>, <quote>, or <note> elements. In these cases, these persons should be linked to Syriaca.org URIs.
http://syriaca.org/work/928) is identified
based on its relationship to two persons: Because the URI and not the personal name serves as the identifier, it is not necessary to use a ‘preferred form’ of the personal name. If the allusion is a quotation, the encoder should leave the wording as found in the original.
Person URIs should be attached only to direct references to persons. When a personal name occurs as part of a title of a work (e.g. The Homilies of John Chrysostom) or as part of a place name (e.g. ‘The Convent of Mar Isaac’), these entities should be treated as works or places respectively. In these cases the prose is marked with a <title> or <placeName> element instead and the personal name must not be tagged nor person URIs attached.
References to places can appear in <desc>, <quote>, or <note> elements. In these cases, these places should be linked to Syriaca.org URIs.
When descriptive prose in a NHSL record refers to a place that has a Syriaca.org URI, the mention of the place should be tagged using the <placeName> element and linked to a URI.
Places URIs should be attached only to direct references to places. When a personal name occurs as part of a title of a work (e.g. The Chronicle of Edessa) or as part of a personal name (e.g. Jacob of Edessa), these entities should be treated as works or persons respectively. In these cases the prose is marked with a <title> or <persName> instead and the geographic epithet must not be tagged nor place URIs attached.
References to texts or literary works can appear in <desc>, <quote>, or <note> elements. In these cases, these works should be linked to Syriaca.org URIs.
When a NHSL record refers to a literary work that has a Syriaca.org URI, the title or mention of the work should be tagged using the <title> element and linked to the URI using the ref attribute.
Work URIs should be attached only to direct references to works. When the
title of a work occurs as part of a personal name (e.g. Author of The Macarian Homilies) or in a yet
unidentified case where a work title might occur as part of a place
name, these entities should be treated as persons or places
respectively. In these cases the prose is marked with a <persName> or a <placeName> instead and the work
title must not be tagged nor work URIs attached. It is also useful to
distinguish between a ‘work’ and a ‘bibliographic item’. The former is an abstract
concept (The Chronicle of Edessa, URI: http://syriaca.org/work/8559), while a
bibliographic item refers to a specific instance of a publication (e.g.
Guidi's 1902 edition of the The Chronicle of
Edessa, URI: http://syriaca.org/cbss/63ZKDBEH).
The encoding feature below has not yet been implemented but is planned for the future.
This section describes the TEI XML structure of each NHSL work record, following the order in which elements appear in the document.
Every NHSL record begins with the <TEI> root element, which must include the namespace declarations and an xml:lang attribute with the value ‘en’, reflecting that the primary language of record data is English.
The <TEI> root element must always contain exactly two child elements: <teiHeader> and <text>.
The <teiHeader> element contains metadata about the record itself: who created it, what it describes, what license covers it, and what series it belongs to. The structure of the <teiHeader> in NHSL records is as follows:
The <titleStmt> records the title of the record (which mirrors the work's primary English headword title), the institutional sponsors and funders, and the editors and contributors. The <title> in the <titleStmt> gives both an English form and a Syriac form separated by an em dash, enclosed in a <foreign> element:
The <editor> element must carry a role attribute (either ‘creator’ or
‘contributor’) and a ref attribute pointing to the Syriaca.org editor URI. Editor
URIs take the form
http://syriaca.org/documentation/editors.xml#[initials].
New contributors should contact the Syriaca editors to obtain an editor
URI.
The <publicationStmt> records
the publishing authority, the URI of this TEI file (formed by appending
/tei to the work URI), the license, and the date the
record was created:
When a record incorporates data from a third-party source under a specific license (such as the Bibliotheca Hagiographica Syriaca), an additional <p> element within <licence> notes the copyrighted material and its license terms.
Each NHSL record belongs to the overarching series and to one or more sub-series. Each membership is recorded in a separate <seriesStmt> element. Every record must include at minimum the top-level NHSL series statement. Additional <seriesStmt> elements record membership in thematic sub-series such as A Guide to the Bible in Syriac or the Bibliotheca Hagiographica Syriaca Electronica:
The <revisionDesc> element records the editorial history of the record. It must carry a status attribute indicating the current state of the record. Permitted values include ‘draft’, ‘uncorrected-draft’, and ‘published’. Within <revisionDesc>, each editorial action is recorded in a <change> element, listed in reverse chronological order (most recent first). Each <change> element must have who (the editor URI of the person making the change) and when (an ISO 8601 datetime) attributes. The text of the <change> element should begin with one of the following terms: ‘CREATED’ (used only for the initial creation of the record), ‘ADDED’, or ‘CHANGED’:
The intellectual content of each NHSL record is
contained in the <text> element, which holds a <body> element
containing a single <bibl> element. The XPath to the main
data element is therefore /TEI/text/body/bibl. The overall
structure is as follows:
The primary container for all data about a literary work is the <bibl> element. This usage adapts the TEI <bibl> element — normally used for bibliographic references — to serve as the top-level element which contains the work description. As a short hand, this <bibl> element may be described as the ‘top-level <bibl>’ or ‘body/bibl’ or ‘main <bibl>’. This use of <bibl> reflects the strongly bibliographic character of NHSL records, which describe works primarily in terms of their titles, editions, manuscripts, and scholarly literature, rather than providing discursive prose descriptions.
The <bibl> element can contain the following child elements in the order listed, some of which are required:
The <bibl> element can carry two classificatory attributes: type and ana. These attributes are used internally in the data model to classify and group types of works within NHSL.
body/bibl/@type)The type attribute on the top-level <bibl> distinguishes between the two fundamental kinds of work record used in NHSL. Its value must be one of the following:
syriaca:LiteraryTradition — this
category is used to identify the literary tradition that
encompasses all of the multiple versions, translations, or
adaptations of a work. The URI assigned to a literary tradition
is used to link together individual conceptual works. For
example, the Genesis literary
tradition URI (http://syriaca.org/work/9628) refers collectively to
the various Syriac translations such as the Peshitta Genesis and Syriac translations of
Genesis from the Greek
Septuagint. Because of their abstract nature, literarytradition
records do not carry incipits or explicits and do not cite
specific manuscripts. They serve primarily as organizing nodes
in the knowledge graph, linking specific conceptual works to a
common tradition.lawd:ConceptualWork — this category of
record is used for a more specific conceptual work that can be
identified by concrete textual and material evidence (incipits,
manuscripts, editions, etc.). This is the most common record
type in NHSL records. The Peshitta
version of Genesis (http://syriaca.org/work/1) is an example of a
conceptual work record because it is a constituent work within a
literarary tradition.It should be noted that the relationship between these two types in the NHSL data model is not symmetrical. Specifically, not every conceptual work record is contained as a constituent part of a literary tradition. This fact is merely due to editorial convenience. NHSL only has literary tradition records for works in which there are multiple recensions or translations which need differentiation. Technically, any conceptual work could be considered as a consituent part of a literary tradition whose parts are n=1. Since such a proliferation of literarry tradition records would serve little use, they have been excluded. A second point to note is that while some conceptual works could be further divided into constituent recensions, as an editorial rule we have only implemented a single literary tradition which contains all conceptual works (rather than a hierarchical tree of recensions or works).
The ana attribute on <bibl> supplies a thematic classification used to divide work records into the thematic sub-volumes of NHSL. Permitted values include:
#syriaca-biblical — the work is a
version, commentary on, or liturgical adaptation of a biblical
text#syriaca-hagiographic — the work is a
hagiographic text, such as a saint's life, martyrdom account, or
commemoration#syriaca-scientific — the work is a
philosophical or scientific workTitles are essential for identifying and disambiguating individual literary works. Every record must include at least one <title> element, and may have any additional number of <title> elements. The text node of this element should contain a title by which the literary work is or was known. Name variants may be recorded for any language, and that language should be recorded as described in the Recording Language Information (xml:lang) section. Each record must have at least one title in English or English transliteration indicated as the headword. Multiple titles attested in manuscripts or in scholarly use may be collected, each recorded in their own <title> element.
name\d+-\d+. The first digits derive from the numerical
portion of the Syriaca URI for the literary work, and the latter is a
sequential integer: Finally, as seen in the preceding example, all <title> elements must indicate the source of the name form as detailed in the Inserting Citations section of these Guidelines.
Titles may be further classified using a type attribute. This practice is optional. Only the following values are permitted:
/TEI/titleStmt/title element: For creators other than authors, the role attribute must be used to further specify the peron's contribution. Currently allowed values include: ‘scribe’ and ‘translator’.
Attribution of creators may also be included even in cases of dubious, disputed, or pseudopigraphic attribution. The ana attribute can be used for this purpose, in which case the following values should be used: ‘attributed’, ‘disputed’, and ‘pseudo’.
This element is required. A record must have at least one <idno> indicating a Syriaca.org URI. Records belonging to more than one Syriaca.org publication, must have an <idno> for each publication. A record may have any number of additional <idno> elements.
http://syriaca.org/work/{\d+}. Other <idno>
elements with type attributes of ‘URI’ may be included to connect the NHSL record with related concepts in other databases, such as Virtual
International Authority File, or WikiData. A work record may include additional <idno> elements identifying it according to standard schemas or in standard reference works. These <idno> elements must have a type attribute value of ‘number’. Their subtype attribute specifies the reference work or identifier schema to which the refrence number belongs. The sources in the following table are currently permitted:
| subtype | Reference Work |
| Bekker | Bekker Number (assigned to the works of Aristotle) |
| BHO | Bibliotheca Hagiographica Orientalis |
| BHS | Bibliotheca Hagiographica Syriaca |
| CPG | Clavis Patrum Graecorum |
| Fichtner | Fichtner Number (assigned to the Corpus Galenicum) |
| Kühn | Kühn Pagination (assigned to the Corpus Galenicum) |
| Takahashi | Number from Takahashi, Barhebraeus: A Bio-Bibliography, (2013). |
The primary language of the work's text is recorded using a <textLang> element with a mainLang attribute whose value is an ISO 639 Language code. See Recording Language Information (xml:lang), above for more general information about using these language codes. For the overwhelming majority of NHSL records, the attribute value will be ‘syr’, for Syriac. This is the case even for literary works originally composed in languages other than Syriac, given the linguistic scope of NHSL.
Only one <textLang> element is allowed. If a work is substantially bilingual or multilingual, additional languages may be recorded in the otherLangs attribute as a space-separated list of ISO 639 Language codes.
Each work record contains one or more <noteGrp> elements that help to disambiguate this work from other similar works. These note groups include record abstracts; descriptive and discursive notes about the work; and excerpts from the work.
The general structure of a <noteGrp> element is as follows. Each <noteGrp> element must have a type attribute and a child <desc> element. The available type attribute values are: ‘abstract’, ‘contents’, ‘disambiguation’, ‘excerpts’, ‘explicit’, ‘incipit’, ‘prologue’, ‘scope’, and ‘versions’. In each case, the <noteGrp> requires a child <desc> element with a text node containing a capitalized version of this type attribute.
One or more child <note> elements may be included in a <noteGrp> element. These <note> elements must have a type attribute whose value corresponds to that of its parent <noteGrp> element. The language of the note must be recorded as described in Recording Language Information (xml:lang) above. The contents of the <note> element should be sourced as described in the guidelines on Inserting Citations. If the contents are a direct quotation from the source, however, a child <quote> element should be included, and that element sourced per the above guidelines.
noteGrp type="abstract")An English-language abstract is required for every record. A record may have any number of additional abstracts as <note> elements. Additionally, individual sub-volumes of NHSL may have their own, distinct abstracts.
The abstract is a short description in prose describing the literary work. The purpose of the abstract is to help users of NHSL to easily disambiguate search results and quickly identify the work for which they are searching.
Abstracts must also have a corresp attribute that contains one or more space-separated URIs that correspond to the <idno> element in the <seriesStmt> elements. These URIs identify NHSL and its sub-volumes, such as the Bibliotheca Hagiographica Syriaca Electronica. If there are multiple abstracts, only one can reference a given series URI, and every series URI must be referenced by one of the abstracts. While some abstracts in NHSL may contain an xml:id, this is legacy data and should be ignored. It is not necessary to assign an xml:id to the abstracts.
noteGrp type="scope", "versions", "content", or
"disambiguation")noteGrp
type="prologue", "incipit", "excerpt", or
"explicit")NHSL uses the <relation> element (which must appear inside a single <listRelation> element) to record relations between a literary work record and other entities in the Syriaca.org Knowledge Graph. The <relation> element must have a ref attribute with one of the following values: "skos:broader", "dcterms:isPartOf", "syriaca:commemorates" or "syriaca:different-from". The use cases for each of these values are described below. The relation is expressed using active and passive attributes, which contain the Syriaca entity URIs for the related entities. Finally, <relation> elements must be sourced as described in Inserting Bibliographic Citations, though they commonly take a resp attribute as described in Asserting Information without a Source.
skos:broader)The relationship between a constituent work and its conceptually broader literary tradition (cf. Literary Traditions and Constituent Works, above, for a discussion of these concepts) is expressed using a ref attribute with the value of ‘skos:broader’. The active URI is the conceptual work, i.e. the current record, and the passive URI is the literary tradition record:
This relation should always placed on the one or more records whose top-level <bibl> element includes a type attribute value of ‘lawd:ConceptualWork’, rather than the broader literary tradition record (which has a type value of ‘syriaca:LiteraryTradition’). In other words, multiple constituent work records may point to the single broader literary tradition reccord.
dcterms:isPartOf)desc/label may specify the ordering of the work within
the larger collection. In the following example, Genesis is related to
the Pentateuch as its first book: The <label> element within the <desc> element records the ordering of the work within its parent. This <label> element must have the type attribute value of ‘order’. It may also take a subtype attribute whose value indicates the unit of ordering (e.g., ‘book’, ‘part’, etc.). An n attribute records the work's sequence within the larger work. The <label> element's text node should record this information in a human-readable format.
syriaca:commemorates)Subjects who are commemorated by hagiographic works are related via a <relation> element with a ref attribute value of ‘syriaca:commemorates’. The active attribute must take the Syriaca.org URI of the commemorating work, i.e. the current record. The passive attribute's value must be the Syriaca.org person, or in rare cases place, URI of the entity commemorated by the work. The child <desc> element should include Syriaca.org's English-language headword for the commemorated entity:
syriaca:different-from)The bibliographic information related to the work is organized into sections describing editions, manuscripts, modern translations, ancient versions, and secondary sources. These classifications are derived from the IFLA LRM entities ‘expression’, ‘manifestation’, and ‘item’. For example, editions and manuscripts contain particular ‘expressions’ and ‘manifestations’ of the work. Translations and versions are ‘expressions’ that are different from the Syriac language ‘expression’ of the work. Each of these expressions" and ‘manifestations’ are identified through particular bibliographic ‘items’ for which a publication citation, manuscript shelmark, or other bibliographic information is provided. Each section is encoded as a separate <listBibl> element with a type attribute identifying the category. These sections are each <listBibl> element begins with a <head> element providing the category label, followed by a <desc> element describing the scope of the bibliography, followed by the individual <bibl> elements for each item. Users of NHSL should note that these bibliographic sections are not necessarily exhaustive. NHSL is published as part of the Syriaca.org linked data graph, so there may be other bibliography related to each literary work which can be found through the Comprehensive Bibliographty on Syriac Studies.
bib\d+-\d+. The first digits derive from the
numerical portion of the Syriaca URI for the literary work, and the
latter is a sequential integer: Nota bene: The xml:id numbers should be created and assigned in sequetial order (for example if ‘bib567-2’ already exists in file 567.xml, then the next bibliographic item should be assigned ‘bib567-3’). Although the xml:id for <bibl> elements are created and assigned sequentially, their occurence in the document need not be sequential. Once an xml:id has been assigned to a bibliographic item, that xml:id should never be renumbered or changed as doing so may break references to it. If an editor wishes to insert a new <bibl> between existing items, for example between ‘bib567-2’ and ‘bib567-3’, it is acceptable to assign that new item whatever number is next available (such as ‘bib567-4’) even if the numbers become out of sequence according to the order of occurance in the document.
listBibl type="editions")Published editions of Syriac texts offer some of the most comprehensive descriptions of distinct literary works, especially if the published text is a critical edition with apparatus. Accordingly, at the time of composition NHSL entries should try to cite all printed editions of the work (including diplomatic and eclectic editions). Because of the constant publication of new scholarship, however, readers should not assume that the list of editions is complete in any given record (a prewritten <desc> element is provided with a note to this effect).
The listBibl type="editions" section records the citations
for editions of the work. Each edition is encoded as a separate <bibl> element with type="lawd:Edition".
Each <bibl> must be assigned a unique xml:id as documented above. Because Syriaca.org manages the
publication information for all citations of modern publications in a
separate reference work, The
Comprehensive Bibliography on Syriac Studies (CBSS),
it is not necessary to include the full citation in the <bibl> element. Instead, the first step in adding a
citation for an edition into a work record in NSHL is to identify the corresponding entry in CBSS.
Users can search the bibliography at https://syriaca.org/cbss/search.html. Once the item to be cited
is located, editors should note the URI for the bibliographic item. This
URI will have the format
http://syriaca.org/cbss/[A-Z0-9]{8}$ (where
"[A-Z0-9]{8}$" signifies a unique string of 8 uppercase
alphanumeric characters). For example, the URI for J.B. Segal, Edessa, ‘The Blessed City’ (Oxford: Clarendon
Press, 1970) is http://syriaca.org/cbss/FQCVBMNS. If the
desired bibliographic item is not found in CBSS, editors should request the creation of an entry in
CBSS.
Once the editor has identified the CBSS URI, they may proceed to encoding the edition citation in NSHL. The <bibl> element must include a title (<title>) and a pointer (<ptr>) to the URI of the CBSS bibliographic URI, and one or more <citedRange> elements specifying the location within the edition where the text appears.
Nota bene: The contents of the <title> are for reference purposes within the XML document only. When the XML file is converted for publication online, the GADDEL app will use the CBSS URI to look up the full publication information in CBSS and insert it into the record. Special care should be taken to include the <citedRange> because that information is unique and cannot be inserted based on the CBSS URI.
The following additional information should be encoded using attribute values within the <bibl> or its descendants. NSHL records are required to cite their sources using either the source or resp attributes as described above. If the information about an edition is derived from another source (such as Zanetti and Detienne, Bibliotheca Hagiographica Syriaca) then that other source should be cited using source. If the edition itself has been consulted directly by the Syriaca.org editor, then an resp should be used with the value ‘http://syriaca.org’ to indicate that the editors of NSHL are responsible for the inclusion of the citation. (This practice avoids creating a circular citation back to the edition itself). Other information encoded as attributes includes unit on <citedRange> and xml:lang on <title> as described above.
Here is an example of an edition citation from work record http://syriaca.org/work/567:
relation
type="mssWitnesses" ref="dcterms:source")As an optional note, within an edition's <bibl> entry, a
nested <listRelation> may be
used to record the manuscript(s) consulted as the base text(s) for
that edition. This relationship is expressed using a <relation> with type="mssWitnesses" and
ref="dcterms:source". The active attribute refers to the xml:id of the edition
entry (with the # prefix); the passive attribute gives the xml:id of the manuscript
entry (with the # prefix) found in the manuscripts
section of the same record. A <desc> provides a human-readable
shelfmark in the following the format described below (see Manuscripts:
listBibl
type="manuscripts")Manuscript witnesses are essential sources for the study of Syriac texts. If possible, NHSL entries should cite at least one manuscript witness as an attestation of the work. If desired, editors may list multiple manuscripts. Given the current state of cataloging of Syriac manuscripts, however, readers should not assume that the list of manuscripts is complete in any given record (a prewritten <desc> element is provided with a note to this effect).
The listBibl type="manuscripts" section records the
manuscript citations. Each manuscript entry is a <bibl> element with
type="syriaca:Manuscript". Each <bibl> must be
assigned a unique xml:id as documented above. A
manuscript entry should include one or more <label> elements
providing a human-readable identification of the manuscript (library,
collection, shelfmark). Multiple <label> elements can be used if the
manuscript has been known by multiple shelfmarks or names. The numeric
portion of the label should be contained in a child element <idno>. The <bibl> element may also include an
optional <ptr> element linking to manuscript records in external
online catalogs. Whenever possible, the <bibl> element
should also contain a <biblScope> specifying the
folios where the work appears and a <date> indicating the date of the
manuscript.
The following additional information should be encoded using attribute values within the <bibl> or its descendants. NSHL records are required to cite their sources using either the source or resp attributes as described above. If the information about a manuscript is derived from another source (such as Zanetti and Detienne, Bibliotheca Hagiographica Syriaca) then that other source should be cited using source. If the manuscript itself has been consulted directly by the Syriaca.org editor, then an resp should be used with the value ‘http://syriaca.org’ to indicate that the editors of NSHL are responsible for the inclusion of the citation. (This practice avoids creating a circular citation back to the manuscript itself). Other information encoded as attributes includes unit on <biblScope> and xml:lang on <label> or <title> as described above.
http://syriaca.org/work/567 : The <label> element will usually contain an <idno> child with a pair of type/subtype values as indicated in the table below:
| <label> | type | subtype |
| Vatican Apostolic Library | shelfmark | BAV |
| London, British Library | shelfmark | BL |
| Florence, The Laurentian Library | shelfmark | BML |
| Paris, Bibliothèque nationale | shelfmark | BNF |
| Berlin, Staatsbibliothek zu Berlin | shelfmark | Berlin |
| Cambridge, University Library | shelfmark | Cambridge |
| Manchester, The University of Manchester, Crawford Collection | shelfmark | Crawford |
| P. Haddad and J. Isaac, Catalogue of the Syriac Manuscripts in Iraq | catalog-number | Haddad-Issac |
| J. Rendell Harris Number | number | Harris |
| Hill Museum and Manuscript Library | project-number | HMML |
| Peshitta Institute Leiden Manuscript Siglum | number | Leiden |
| Birmingham, Selly Oak College Library, Mingana Collection | shelfmark | Mingana |
| Rosen and Forshall, Catalogus...Pars Prima | catalog-number | Rosen |
| Homs, Syriac Orthodox Church, Archdiocese of Homs | shelfmark | SOAH |
| Sachau, Königliche Bibliothek, Berlin: Kurzes Verzeichniss | catalog-number | Sachau |
| Sinai, St. Catherine's Monastery | shelfmark | Sinai |
| Yale University, Beinecke Library | shelfmark | Yale |
If this table does not contain the subtype value needed for your work, please choose appropriate subtype and type values. The schema will give a yellow "warning" message that will inform the editors that there is something in the document that requires their attention.
listBibl
type="modernTranslations")The listBibl type="modernTranslations" section records
modern translations of the work into contemporary languages. This
section is optional, but editors are encouraged to cite modern
translations if possible. As in other instances, readers should not
assume that the list of translations is complete in any given record (a
prewritten <desc> element is provided with a note to this effect).
Each translation is encoded as a <bibl> element with
type="syriaca:ModernTranslation". Each <bibl> must be assigned a unique xml:id as documented above. In addition, each <bibl> must contain a title (<title>) and a
pointer (<ptr>) to the URI of a CBSS bibliographic URI, and one or
more <citedRange> elements
specifying the location within the publication where the translation
appears. In this regard, the citations of modern translations follows
the same workflow and conventions as the citation of editions described
above (i.e. relying upon the full citations found in The
Comprehensive Bibliography on Syriac Studies [CBSS]).
In addition, it is also possible to cite the existence of an unpublished
modern translation directly from a manuscript rather than a print
publication. In such cases, the editor should format the <bibl> following the guidelines above for the type
bibl type="syriaca:Manuscript".
Nota bene: When a <ptr> is used to refer to CBSS, the contents of the <title> are for reference purposes within the XML document only. When the XML file is converted for publication online, the GADDEL app will use the CBSS URI to look up the full publication information in CBSS and insert it into the record. Special care should be taken to include the <citedRange> because that information is unique and cannot be inserted based on the CBSS URI.
The following additional information should be encoded using attribute values within the <bibl> or its descendants. NSHL records are required to cite their sources using either the source or resp attributes as described above. If the information about an modern translation is derived from another source (such as Zanetti and Detienne, Bibliotheca Hagiographica Syriaca) then that other source should be cited using source. If the translation itself has been consulted directly by the Syriaca.org editor, then an resp should be used with the value ‘http://syriaca.org’ to indicate that the editors of NSHL are responsible for the inclusion of the citation. (This practice avoids creating a circular citation back to the translation itself). Other information encoded as attributes includes unit on <citedRange> as described above.
For modern translations and ancient versions, there is an additional element (<textLang>) which is used to indicate the language of the translation or version. (Nota bene: this usage is distinct from the use of xml:lang on <title> where the purpose is to indicate the language of the title. Thus in the example below from the Corpus Scriptorum Christianorum Orientalium, the title is in Latin but the translation itself is in German.)
Here is an example of a modern translation citation:
relation type="translationSource"
ref="dcterms:source")As an optional note, within an modern translation's <bibl> entry, a nested <listRelation> may be used to record the edition(s)
or manuscript(s) used as the base text(s) for that translation. This
relationship is expressed using a <relation> with type="translationSource"
and ref="dcterms:source". The active attribute refers to the xml:id of the translation
entry (with the # prefix); the passive attribute gives the xml:id of the edition or
manuscript entry (with the # prefix) found in the
manuscripts section of the same record. A <desc> provides
a human-readable <label> or <title>:
listBibl type="ancientVersions")This section records the existence of pre-modern versions of the work in languages other than Syriac. Such versions can include pre-modern translations of a Syriac work into another language (for example a work translated into Armenian from Syriac) or the original language versions of works translated into Syriac in Antiquity or the Middle Ages (for example a work translated from Greek into Syriac). In addition, editors may use this section to note the existence of other related ancient versions which have comparative value (for example, if a Greek text was translated into both Syriac and Latin, the Latin version could be noted here or if a Syriac text was translated into Greek and then from Greek into Slavonic, the Slavonic text could be cited here). Examples include Greek, Latin, Armenian, Coptic, Arabic, and Ethiopic versions of texts also attested in Syriac. While this section is optional, editors are encouraged to note the existence of such versions due to their value for establishing the literary history of a work, its transmission across linguistic communities, and its relationships to other textual traditions.
Nota bene: Ancient versions are distinguished by chronological
era from modern scholarly translations, which are recorded separately in
listBibl type="modernTranslations" (see Modern Translations).
The listBibl type="ancientVersions" section records
citations for ancient versions of the work. Each version is encoded as a
separate <bibl> element with type="lawd:Expression",
reflecting the IFLA LRM model that that an ancient version in a
different language constitutes a distinct expression of the
same work. Each <bibl> must be assigned a unique
xml:id following the pattern described
above. As in other instances, readers should not assume that the list of
ancient versions is complete in any given record (a prewritten <desc> element is provided with a note to this
effect).
As with modern translations, NHSL manages
citation information for ancient versions through the Comprehensive Bibliography on Syriac Studies
(CBSS). Editors should first locate the publication
which they wish to cite in CBSS and record
its URI in a <ptr> element. A <title> element should be included
for reference within the XML document; the Gaddel app will use the CBSS
URI to retrieve and display the full publication information. Unlike in
the citations of editions modern translations above, these citations
need to be to an edition of the ancient version. In many cases, the
citation may be to a reference work such as the Clavis patrum graecorum which attests the existence of
ancient versions. In addition, it is also possible to cite the existence
of an ancient version directly from a manuscript rather than a print
publication. In such cases, the editor should format the <bibl> following the guidelines above for the type
bibl type="syriaca:Manuscript".
As in the case of modern translations, the ancient versions use the <textLang> element as a child of <bibl> with a mainLang attribute to record the language of the version. If possible, one or more <citedRange> elements should specify the location within the cited publication where information about the version appears.
If the information about an ancient version is derived from a secondary
source (such as Zanetti and Detienne, Bibliotheca
Hagiographica Syriaca), that source should be cited using
source on the <bibl> element. If
the editor has consulted the version directly, a resp attribute with the value
http://syriaca.org should be used instead to avoid a
circular citation.
Here is an example of an ancient version citation:
listBibl
type="secondaryLiterature")The listBibl type="secondaryLiterature" section serves two
distinct purposes in NHSL records. First,
editors may use it to list a small number of the most notable scholarly
secondary literature about the work. Since items in CBSS can also be linked within CBSS to NHSL, this section
should not be used to create a comprehensive bibliography (as a reminder
to readers, a prewritten <desc> element is provided with a
note to this effect in the record). Second — and equally important —
this secondary literature sections functions as place where editors may
include the citation for any other bibliographic items they wish to
refer to using the source attribute if these
citations have not already been included in the editions, manuscripts,
modern translations, or ancient versions sections.
Each secondary literature entry is encoded as a <bibl> element with
type="lawd:Citation". Each entry must have an xml:id following the pattern documented above. At
minimum, a secondary literature entry must include a <title> for
reference, a <ptr> pointing to the item's CBSS URI, and a <citedRange> element specifying
the exact location within that work to which the citation refers. Two
examples are as follows:
This dual role of the listBibl type="secondaryLiterature"
section means that it will typically include the principal reference
work from which the record data was derived (such as the relevant BHS entry, or an edition catalogue), as well
as additional secondary scholarship as sources elsewhere in the record.
The order of entries within this section does not reflect the order of
citation; rather, entries are numbered sequentially according to when
they were added to the record.
| <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 16.1. Varieties of Composite Text] | |||||||||
| Module | textstructure — NHSL TEI P5 Schema Customization | ||||||||
| Attributes | Attributes att.global (@xml:id,
@n, @xml:lang) (att.global.analytic (@ana)) (att.global.change (@change)) (att.global.linking (@corresp)) (att.global.rendition (@rend)) (att.global.responsibility (@resp)) (att.global.source (@source))
|
||||||||
| Contained by |
textstructure:
TEI
|
||||||||
| May contain | |||||||||
| Note | As with all elements in the TEI scheme (except <egXML>) this element is in the TEI namespace (see 5.7.2. Namespaces). Thus, when it is used as the outermost element of a TEI document, it is necessary to specify the TEI namespace on it. This is customarily achieved by including http://www.tei-c.org/ns/1.0 as the value of the XML namespace declaration (xmlns), without indicating a prefix, and then not using a prefix on TEI elements in the rest of the document. For example: <TEI version="4.8.1" xml:lang="it" xmlns="http://www.tei-c.org/ns/1.0">. |
||||||||
| 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
namespace.</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> |
||||||||
| Content model |
<content>
<sequence minOccurs="1" maxOccurs="1">
<elementRef key="teiHeader"/>
<alternate minOccurs="1" maxOccurs="1">
<sequence minOccurs="1" maxOccurs="1">
<classRef key="model.resource"
minOccurs="1" maxOccurs="unbounded"/>
<elementRef key="TEI" minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
<elementRef key="TEI" minOccurs="1"
maxOccurs="unbounded"/>
</alternate>
</sequence>
</content>
⚓ |
||||||||
| Schema Declaration |
element TEI
{
tei_att.global.attributes,
attribute version { text }?,
( tei_teiHeader, ( ( tei_model.resource+, tei_TEI* ) | tei_TEI+ ) )
}⚓ |
||||||||
| <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] | |
| Module | core — NHSL TEI P5 Schema Customization |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.analytic (@ana)) (att.global.change (@change)) (att.global.linking (@corresp)) (att.global.rendition (@rend)) (att.global.responsibility (@resp)) (att.global.source (@source)) att.datable (@srophe:computed-start, @srophe:computed-end) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) att.naming (@role) (att.canonical (@ref)) |
| Contained by |
core:
bibl
|
| May contain | |
| Note | The <author> element may contain either a <persName> element or text. |
| Example | |
| Schematron |
<sch:rule context="tei:body/child::tei:bibl/child::tei:author/@ana">
<sch:assert test=". = 'attributed' or . = 'disputed' or .
= 'pseudo'"> In this context, the acceptable @ana
attributes are "attributed", "disputed", or "pseudo".
</sch:assert> </sch:rule> |
| Schematron |
<sch:rule context="tei:body/child::tei:bibl/child::tei:author">
<sch:report test="tei:persName"> This <author>
element allows only a text node with an English name or a
<foreign> element with a non-English name.
</sch:report> <sch:assert test="@xml:lang"> This
<author> element requires an @xml:lang attribute.
</sch:assert> <sch:assert test="@source or
@resp"> The <author> element for the main work
<bibl> must have either a @source attribute or a @resp
attribute. </sch:assert>
<sch:assert test="matches(@ref,
concat('http://syriaca.org/person/', '\d+'))"
role="error"> This <author> element must take a
@ref attribute with a Syriaca.org person URI which reqires
the form 'http://syriaca.org/person/{\d+}' (where {\d+} is a
number). </sch:assert> </sch:rule> |
| Content model |
<content>
<sequence minOccurs="1" maxOccurs="1">
<elementRef key="persName" minOccurs="0"
maxOccurs="1"/>
<elementRef key="foreign" minOccurs="0"
maxOccurs="1"/>
<textNode/>
</sequence>
</content>
⚓ |
| Schema Declaration |
element author
{
tei_att.global.attributes,
tei_att.datable.attributes,
tei_att.naming.attributes,
( tei_persName?, tei_foreign?, text )
}⚓ |
| <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.] | |
| Module | header — NHSL TEI P5 Schema Customization |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.analytic (@ana)) (att.global.change (@change)) (att.global.linking (@corresp)) (att.global.rendition (@rend)) (att.global.responsibility (@resp)) (att.global.source (@source)) |
| Contained by |
header:
publicationStmt
|
| May contain | Character data only |
| Note | The identification of Syriaca.org as the responsible entity is accomplished by an <authority> element. |
| Example | <authority>Syriaca.org: The Syriac
Reference Portal</authority> |
| Schematron |
<sch:rule context="//tei:publicationStmt/tei:authority">
<sch:assert test="matches(., 'Syriaca.org: The Syriac
Reference Portal')"> The <authority> element should
contain the text: "Syriaca.org: The Syriac Reference
Portal." </sch:assert> </sch:rule> |
| Content model |
<content>
<textNode/>
</content>
⚓ |
| Schema Declaration |
element authority { tei_att.global.attributes, text }⚓ |
| <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.] | |||||||||
| Module | header — NHSL TEI P5 Schema Customization | ||||||||
| Attributes | Attributes att.global (@xml:id,
@n, @xml:lang) (att.global.analytic (@ana)) (att.global.change (@change)) (att.global.linking (@corresp)) (att.global.rendition (@rend)) (att.global.responsibility (@resp)) (att.global.source (@source))
|
||||||||
| Contained by |
header:
publicationStmt
|
||||||||
| May contain |
header:
licence
character data
|
||||||||
| Note | A consistent format should be adopted |
||||||||
| Example | <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> |
||||||||
| Schematron |
<sch:pattern is-a="declarable">
<sch:param name="tde" value="tei:availability"/>
</sch:pattern> |
||||||||
| Content model |
<content>
<sequence minOccurs="1" maxOccurs="1">
<elementRef key="licence" minOccurs="1"/>
<textNode/>
</sequence>
</content>
⚓ |
||||||||
| Schema Declaration |
element availability
{
tei_att.global.attributes,
attribute status { "free" | "unknown" | "restricted" }?,
( tei_licence, text )
}⚓ |
||||||||
| <bibl> (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 16.3.2. Declarable Elements] | |||||||||||||||
| Module | core — NHSL TEI P5 Schema Customization | ||||||||||||||
| Attributes | Attributesatt.global
(@xml:id, @n, @xml:lang) att.global.change (@change) att.global.linking (@corresp) att.global.rendition
(@rend) att.global.responsibility (@resp) att.global.source (@source) att.typed (type, @subtype)
|
||||||||||||||
| Contained by | |||||||||||||||
| May contain | |||||||||||||||
| Note | 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:body//tei:listBibl[@type='manuscripts']/tei:bibl">
<sch:assert test="tei:label"> A manuscript
<bibl> element must have a child <label>
element. </sch:assert>
<sch:assert test="@type='syriaca:Manuscript'"> This
<bibl> element requires a @type attribute with the
value "syriaca:Manuscript". </sch:assert>
<sch:report test="@ana"> The @ana attribute is not
allowed here. </sch:report> </sch:rule>
<sch:rule context="tei:body//tei:listBibl[@type='ancientVersions']/tei:bibl">
<sch:assert test="tei:label or tei:ptr"> An ancient
versions <bibl> element must have eith a child
<label> element or a child <ptr< element.
</sch:assert>
<sch:assert test="@type='syriaca:AncientVersion'">
This <bibl> element requires a @type attribute with
the value "syriaca:AncientVersion". </sch:assert>
<sch:report test="@ana"> The @ana attribute is not
allowed here. </sch:report> </sch:rule>
<sch:rule context="tei:body//tei:listBibl[@type='editions']/tei:bibl">
<sch:assert test="@type='lawd:Edition'"> This
<bibl> element requires a @type attribute with the
value "lawd:Edition". </sch:assert>
<sch:assert test="tei:ptr"> An edition <bibl>
element must have a child <ptr> element.
</sch:assert> </sch:rule>
<sch:rule context="tei:body//tei:listBibl[@type='modernTranslations']/tei:bibl">
<sch:assert test="@type='syriaca:ModernTranslation'">
This <bibl> element requires a @type attribute with
the value "syriaca:ModernTranslation". </sch:assert>
<sch:assert test="tei:ptr or tei:label"> A modern
translation <bibl> element must have either a child
<ptr> element or a child <label> element. The
<label> element should only be used in the rare
instance where the modern translation is contained in a
manuscript. </sch:assert> </sch:rule>
<sch:rule context="tei:body//tei:listBibl[@type='secondaryLiterature']/tei:bibl">
<sch:assert test="@type='lawd:Citation'"> This
<bibl> element requires a @type attribute with the
value "lawd:Citation". </sch:assert>
<sch:assert test="tei:ptr"> A secondary literature
<bibl> element must have a child <ptr> element.
</sch:assert> </sch:rule>
<sch:rule context="tei:body/child::tei:bibl">
<sch:assert test="tei:title and tei:idno and
tei:listBibl"> Every work-level <bibl> element must
have as child elements at least <title>, <idno>,
and <listBibl>. </sch:assert>
<sch:report test="tei:label"> <label> not
allowed here. The work <bibl> does not take a child
<label> element. </sch:report>
<sch:report test="tei:ptr"> <ptr> not allowed
here. </sch:report>
<sch:report test="tei:citedRange"> <citedRange>
not allowed here. </sch:report>
<sch:report test="tei:biblScope"> <biblScope>
not allowed here. </sch:report>
<sch:report test="tei:note"> <note> not allowed
here. Notes under a work <bibl> must be encoded in a
<noteGrp> element. </sch:report>
<sch:assert test="@xml:id"> The main work <bibl>
must have an @xml:id. </sch:assert> </sch:rule>
<sch:rule context="tei:body/child::tei:bibl/@xml:id">
<sch:let name="docURIno"
value="replace(//tei:publicationStmt/tei:idno[@type='URI'][not(@type='deprecated')]/text(),
'.+?(\d+).+', '$1')"/>
<sch:let name="id" value="@xml:id"/>
<sch:assert test="matches(., concat('work-',
$docURIno))"> The required @xml:id must be
'work-<sch:value-of select="$docURIno"/>.
</sch:assert> </sch:rule>
<sch:rule context="tei:body//tei:listBibl//tei:bibl">
<sch:let name="docURIno"
value="replace(//tei:publicationStmt/tei:idno[@type='URI'][not(@type='deprecated')]/text(),
'.+?(\d+).+', '$1')"/>
<sch:let name="id" value="@xml:id"/>
<sch:assert test="matches(./@xml:id, concat('bib',
$docURIno, '-', '\d+$'))"> The required @xml:id must be
'bib<sch:value-of select="$docURIno"/>-{\d+}' (where
{\d+} is a number). </sch:assert>
<sch:report test="preceding-sibling::element()[@xml:id =
$id]">This @xml:id is already in use.</sch:report>
<sch:report test="tei:noteGrp"> Notes encoded inside a
<listBibl> cannot appear inside a <noteGrp>
element. </sch:report>
<sch:report test="tei:listBibl"> Bibliography encoded
inside a <listBibl> cannot appear inside a
<listBibl> element. </sch:report>
<sch:report test="tei:idno"> In this context, a
<idno> element must appear as the child of a
<label> element. </sch:report>
</sch:rule> |
||||||||||||||
| Schematron |
<sch:rule context="tei:body/child::tei:bibl[contains(@ana,
'#syriaca-hagiographic')]">
<sch:assert test="//tei:seriesStmt/tei:title =
'Bibliotheca Hagiographica Syriaca Electronica'"> This
work record must include a <seriesStmt> indicating
that it is part of the volume "Bibliotheca Hagiographica
Syriaca Electronica". </sch:assert>
<sch:assert test="//tei:seriesStmt/tei:title = 'Gateway
to the Syriac Saints'"> This work record must include a
<seriesStmt> indicating that it is part of the series
"Gateway to the Syriac Saints". </sch:assert>
</sch:rule>
<sch:rule context="tei:TEI[//tei:seriesStmt/tei:title =
'Gateway to the Syriac
Saints']//tei:body/child::tei:bibl">
<sch:assert test="contains(@ana,
'#syriaca-hagiographic')"> A work <bibl> that is
part of the series "Gateway to the Syriac Saints" must have
an @ana attribute with the value "#syriaca-hagiographic".
</sch:assert> </sch:rule>
<sch:rule context="tei:TEI[//tei:seriesStmt/tei:title =
'Bibliotheca Hagiographica Syriaca
Electronica']//tei:body/child::tei:bibl">
<sch:assert test="contains(@ana,
'#syriaca-hagiographic')"> A work <bibl> that is
part of the series "Bibliotheca Hagiographica Syriaca
Electronica" must have an @ana attribute with the value
"#syriaca-hagiographic". </sch:assert>
</sch:rule> |
||||||||||||||
| Schematron |
<sch:rule context="tei:body/child::tei:bibl[contains(@ana,
'#syriaca-biblical')]">
<sch:assert test="//tei:seriesStmt/tei:title = 'A Guide
to the Bible in Syriac'"> This work record must include a
<seriesStmt> indicating that it is part of the volume
"A Guide to the Bible in Syriac". </sch:assert>
</sch:rule>
<sch:rule context="tei:TEI[//tei:seriesStmt/tei:title =
'A Guide to the Bible in
Syriac']//tei:body/child::tei:bibl">
<sch:assert test="contains(@ana,
'#syriaca-biblical')"> A work <bibl> that is part
of the series "A Guide to the Bible in Syriac" must have an
@ana attribute with the value "#syriaca-biblical".
</sch:assert> </sch:rule> |
||||||||||||||
| Schematron |
<sch:rule context="tei:body/child::tei:bibl[contains(@ana,
'#syriaca-scientific')]">
<sch:assert test="//tei:seriesStmt/tei:title = 'Syriac
Scientific and Philosophical Literature'"> This work
record must include a <seriesStmt> indicating that it
is part of the volume "Syriac Scientific and Philosophical
Literature". </sch:assert> </sch:rule>
<sch:rule context="tei:TEI[//tei:seriesStmt/tei:title =
'Syriac Scientific and Philosophical
Literature']//tei:body/child::tei:bibl">
<sch:assert test="contains(@ana,
'#syriaca-scientific')"> A work <bibl> that is part
of the series "Syriac Scientific and Philosophical
Literature" must have an @ana attribute with the value
"#syriaca-scientific". </sch:assert>
</sch:rule> |
||||||||||||||
| Schematron |
<sch:rule context="tei:bibl//tei:bibl">
<sch:report test="tei:listBibl"> This <bibl>
element cannot take a child <listBibl>.
</sch:report> </sch:rule> |
||||||||||||||
| Schematron |
<sch:rule context="//tei:text//tei:desc//tei:bibl |
//tei:text//tei:note//tei:bibl">
<sch:assert test="@type='MS'"> Must be @type='MS'. If
not a mss, use <title>. </sch:assert>
<sch:assert test="tei:ptr/@target"> This <bibl>
must have a <ptr> element with @target attribute.
</sch:assert> </sch:rule>
<sch:rule context="//tei:text//tei:desc//tei:bibl/tei:ptr/@target
| //tei:text//tei:note//tei:bibl/tei:ptr/@target">
<sch:assert test="matches(.,
concat('http://syriaca.org/manuscript/', '\d+$'))"> This
@target attribute must point to a Syriaca.org manuscript URI
taking the form "http://syriaca.org/manuscript/{\d+$}} where
{\d+$} is a number. </sch:assert>
</sch:rule> |
||||||||||||||
| Schematron |
<sch:rule context="//tei:text//tei:bibl[tei:ptr/@target[not(contains(.,
'syriaca.org'))]]"> <sch:assert test="tei:title/text()
= tei:ptr/@target">This <bibl> must have a child
<title> element that equals the value of the @target
attribute on the sibling <ptr>
element.</sch:assert> </sch:rule> |
||||||||||||||
| Schematron |
<sch:pattern is-a="declarable">
<sch:param name="tde" value="tei:bibl"/>
</sch:pattern> |
||||||||||||||
| Content model |
<content>
<sequence minOccurs="1" maxOccurs="1">
<elementRef key="title" minOccurs="0"
maxOccurs="unbounded"/>
<elementRef key="author" minOccurs="0"
maxOccurs="unbounded"/>
<elementRef key="editor" minOccurs="0"
maxOccurs="unbounded"/>
<elementRef key="idno" minOccurs="0"
maxOccurs="unbounded"/>
<elementRef key="label" minOccurs="0"
maxOccurs="unbounded"/>
<elementRef key="ptr" minOccurs="0"
maxOccurs="unbounded"/>
<elementRef key="citedRange"
minOccurs="0" maxOccurs="unbounded"/>
<elementRef key="biblScope" minOccurs="0"
maxOccurs="unbounded"/>
<elementRef key="textLang" minOccurs="0"
maxOccurs="unbounded"/>
<elementRef key="date" minOccurs="0"
maxOccurs="unbounded"/>
<elementRef key="noteGrp" minOccurs="0"
maxOccurs="unbounded"/>
<elementRef key="note" minOccurs="0"
maxOccurs="unbounded"/>
<elementRef key="listRelation"
minOccurs="0" maxOccurs="unbounded"/>
<elementRef key="listBibl" minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
</content>
⚓ |
||||||||||||||
| Schema Declaration |
element bibl
{
tei_att.global.attribute.xmlid,
tei_att.global.attribute.n,
tei_att.global.attribute.xmllang,
tei_att.global.change.attribute.change,
tei_att.global.linking.attribute.corresp,
tei_att.global.rendition.attribute.rend,
tei_att.global.responsibility.attribute.resp,
tei_att.global.source.attribute.source,
tei_att.typed.attribute.subtype,
attribute ana { list { + } }?,
attribute type
{
"lawd:Citation"
| "lawd:Edition"
| "lawd:ConceptualWork"
| "lawd:Edition"
| "syriaca:AncientVersion"
| "syriaca:DigitalCatalog"
| "syriaca:LiteraryTradition"
| "syriaca:Manuscript"
| "syriaca:ModernTranslation"
| "syriaca:PrintCatalog"
}?,
(
tei_title*,
tei_author*,
tei_editor*,
tei_idno*,
tei_label*,
tei_ptr*,
tei_citedRange*,
tei_biblScope*,
tei_textLang*,
tei_date*,
tei_noteGrp*,
tei_note*,
tei_listRelation*,
tei_listBibl*
)
}⚓ |
||||||||||||||
| <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] | |||||||||||
| Module | core — NHSL TEI P5 Schema Customization | ||||||||||
| Attributes | Attributes att.global (@xml:id,
@n, @xml:lang) (att.global.analytic (@ana)) (att.global.change (@change)) (att.global.linking (@corresp)) (att.global.rendition (@rend)) (att.global.responsibility (@resp)) (att.global.source (@source)) att.citing (unit, @from, @to)
|
||||||||||
| Contained by |
core:
bibl
header:
seriesStmt
|
||||||||||
| May contain | |||||||||||
| Note | 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
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. |
||||||||||
| Example | <biblScope>pp 12–34</biblScope>
<biblScope unit="page" from="12" to="34"/>
<biblScope unit="volume">II</biblScope>
<biblScope unit="page">12</biblScope> |
||||||||||
| Content model |
<content>
<sequence minOccurs="1" maxOccurs="1">
<textNode/>
<elementRef key="idno" minOccurs="0"
maxOccurs="unbounded"/>
<elementRef key="title" minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
</content>
⚓ |
||||||||||
| Schema Declaration |
element biblScope
{
tei_att.global.attributes,
tei_att.citing.attribute.from,
tei_att.citing.attribute.to,
attribute unit { "cah" | "fol" | "p" | "vol" },
( text, tei_idno*, tei_title* )
}⚓ |
||||||||||
| <body> (text body) contains the whole body of a single unitary text, excluding any front or back matter. [4. Default Text Structure] | |
| Module | textstructure — NHSL TEI P5 Schema Customization |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.analytic (@ana)) (att.global.change (@change)) (att.global.linking (@corresp)) (att.global.rendition (@rend)) (att.global.responsibility (@resp)) (att.global.source (@source)) |
| Contained by |
textstructure:
text
|
| May contain |
core:
bibl
|
| Example | <body> <l>Nu scylun hergan hefaenricaes uard</l> <l>metudæs maecti end his modgidanc</l> <l>uerc uuldurfadur sue he uundra
gihuaes</l> <l>eci dryctin or
astelidæ</l> <l>he aerist scop aelda
barnum</l> <l>heben til hrofe haleg
scepen.</l> <l>tha middungeard
moncynnæs uard</l> <l>eci dryctin æfter
tiadæ</l> <l>firum foldu frea
allmectig</l> <trailer>primo cantauit
Cædmon istud carmen.</trailer>
</body> |
| Content model |
<content>
<elementRef key="bibl" minOccurs="1"
maxOccurs="1"/>
</content>
⚓ |
| Schema Declaration |
element body { tei_att.global.attributes, tei_bibl }⚓ |
| <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] | |
| Module | header — NHSL TEI P5 Schema Customization |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.analytic (@ana)) (att.global.change (@change)) (att.global.linking (@corresp)) (att.global.rendition (@rend)) (att.global.responsibility (@resp)) (att.global.source (@source)) |
| Contained by |
header:
category
|
| May contain |
core:
ref
character data
|
| Note | The <catDesc> contains a brief prose description of the category’s purpose. |
| Example | <classDecl> <taxonomy> <category xml:id="syriaca-headword"> <catDesc>The name used by
Syriaca.org for document titles, citation, and
disambiguation. These names have been created according to
the Syriac.org guidelines for headwords: <ref target="http://syriaca.org/documentation/headwords.html">http://syriaca.org/documentation/headwords.html</ref>.</catDesc> </category> </taxonomy>
</classDecl> |
| Content model |
<content>
<sequence minOccurs="1" maxOccurs="1">
<textNode/>
<elementRef key="ref" minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
</content>
⚓ |
| Schema Declaration |
element catDesc { tei_att.global.attributes, ( text, tei_ref* ) }⚓ |
| <category> (category) contains an individual descriptive category, possibly nested within a superordinate category, within a user-defined taxonomy. [2.3.7. The Classification Declaration] | |
| Module | header — NHSL TEI P5 Schema Customization |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.analytic (@ana)) (att.global.change (@change)) (att.global.linking (@corresp)) (att.global.rendition (@rend)) (att.global.responsibility (@resp)) (att.global.source (@source)) |
| Contained by |
header:
taxonomy
|
| May contain |
header:
catDesc
|
| Note | The <category> has an xml:id attribute whose value is the tag. Within the <category> element is a <catDesc> element which contains a brief prose description of the category’s purpose. |
| Example | <classDecl> <taxonomy> <category xml:id="syriaca-headword"> <catDesc>The name used by
Syriaca.org for document titles, citation, and
disambiguation. These names have been created according to
the Syriac.org guidelines for headwords: <ref target="http://syriaca.org/documentation/headwords.html">http://syriaca.org/documentation/headwords.html</ref>.</catDesc> </category> </taxonomy>
</classDecl> |
| Content model |
<content>
<elementRef key="catDesc" minOccurs="1"/>
</content>
⚓ |
| Schema Declaration |
element category { tei_att.global.attributes, tei_catDesc }⚓ |
| <change> (change) documents a change or set of changes made during the production of a source document, or during the revision of an electronic file. [2.6. The Revision Description 2.4.1. Creation 12.7. Identifying Changes and Revisions] | |||||||||||||||||||||||||
| Module | header — NHSL TEI P5 Schema Customization | ||||||||||||||||||||||||
| Attributes | Attributes att.typed (@type, @subtype) att.global
(n, @xml:id, @xml:lang)
att.global.analytic (@ana)
att.global.change (@change) att.global.linking (@corresp)
att.global.rendition
(@rend) att.global.responsibility (@resp) att.global.source (@source) att.datable
(@srophe:computed-start, @srophe:computed-end) att.datable.custom
(@when-custom, @notBefore-custom, @notAfter-custom,
@from-custom, @to-custom, @datingPoint, @datingMethod) att.datable.w3c (when, @notBefore, @notAfter,
@from, @to)
|
||||||||||||||||||||||||
| Contained by |
header:
revisionDesc
|
||||||||||||||||||||||||
| May contain |
core:
ref
character data
|
||||||||||||||||||||||||
| Note | The <change> element takes attributes when and who which indicate the date of the change and the person who made the change. The value of when is a date in "yyyy-mm-dd" format, whereas who will have the value of an xml:id attribute from "http://syriaca.org/documentation/editors.xml" - the list of editors. An optional n attribute whose value is a version number can indicate that this change advanced the version number (given in the <editionStmt> within the <fileDesc> element). The contents of the <change> element describe the revision that was made. |
||||||||||||||||||||||||
| Example | <revisionDesc> <change when="2013-04-15" who="http://syriaca.org/documentation/editors.xml#ngibson" n="1.1"> ADDED:
Pleiades coordinates</change> <change when="2013-04-01" who="http://syriaca.org/documentation/editors.xml#dmichelson">
FIXED: Ufra to Urfa</change> <change when="2013-03-16" who="http://syriaca.org/documentation/editors.xml#tcarlson" n="1.0"> ADDED:
teiHeader/revisionDesc</change> <change when="2013-03-15" who="http://syriaca.org/documentation/editors.xml#tcarlson">
ADDED: teiHeader</change> <change when="2013-03-01" who="http://syriaca.org/documentation/editors.xml#tcarlson" n="0.1">
CREATED: place</change>
</revisionDesc> |
||||||||||||||||||||||||
| Schematron |
<sch:rule context="//tei:revisionDesc//tei:change/@who">
<sch:let name="edsDoc"
value="doc('https://raw.githubusercontent.com/srophe/gaddel/master/documentation/editors.xml')"/>
<sch:let name="eds"
value="$edsDoc//tei:text/tei:body/tei:listPerson/tei:person/@xml:id"/>
<sch:let name="refValues" value="for $i in $eds return
concat('http://syriaca.org/documentation/editors.xml#',
$i)"/> <sch:assert test="every $i in tokenize(., ' ')
satisfies $i = $refValues"> Acceptable values for the
@who attribute on a <change> element inside the
<revisionDesc> include:
<sch:value-of select="string-join($refValues, ' |
')"/>. </sch:assert> </sch:rule> |
||||||||||||||||||||||||
| Schematron |
<sch:rule context="//tei:change/@xml:id">
<sch:let name="docURIno"
value="replace(//tei:publicationStmt/tei:idno[@type='URI'][not(@type='deprecated')]/text(),
'.+?(\d+).+', '$1')"/> <sch:assert test="matches(.,
concat('change', $docURIno, '-', '\d+$'))"> The required
@xml:id must be
'change<sch:value-of select="$docURIno"/>-{\d+$}'
(where {\d+$} is a number). </sch:assert>
<sch:report test="preceding-sibling::element()[@xml:id =
.]">This @xml:id is already in use.</sch:report>
</sch:rule> |
||||||||||||||||||||||||
| Content model |
<content>
<sequence minOccurs="1" maxOccurs="1">
<textNode/>
<elementRef key="ref" minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
</content>
⚓ |
||||||||||||||||||||||||
| Schema Declaration |
element change
{
tei_att.global.attribute.xmlid,
tei_att.global.attribute.xmllang,
tei_att.global.analytic.attribute.ana,
tei_att.global.change.attribute.change,
tei_att.global.linking.attribute.corresp,
tei_att.global.rendition.attribute.rend,
tei_att.global.responsibility.attribute.resp,
tei_att.global.source.attribute.source,
tei_att.datable.attribute.srophecomputed-start,
tei_att.datable.attribute.srophecomputed-end,
tei_att.datable.custom.attribute.when-custom,
tei_att.datable.custom.attribute.notBefore-custom,
tei_att.datable.custom.attribute.notAfter-custom,
tei_att.datable.custom.attribute.from-custom,
tei_att.datable.custom.attribute.to-custom,
tei_att.datable.custom.attribute.datingPoint,
tei_att.datable.custom.attribute.datingMethod,
tei_att.datable.w3c.attribute.notBefore,
tei_att.datable.w3c.attribute.notAfter,
tei_att.datable.w3c.attribute.from,
tei_att.datable.w3c.attribute.to,
tei_att.typed.attributes,
attribute n { text }?,
attribute who { list { + } },
attribute when { text },
( text, tei_ref* )
}⚓ |
||||||||||||||||||||||||
| <citedRange> (cited range) defines the range of cited content, often represented by pages or other units. [3.12.2.5. Scopes and Ranges in Bibliographic Citations] | |||||||||||
| Module | core — NHSL TEI P5 Schema Customization | ||||||||||
| Attributes | Attributes att.global (@xml:id,
@n, @xml:lang) (att.global.analytic (@ana)) (att.global.change (@change)) (att.global.linking (@corresp)) (att.global.rendition (@rend)) (att.global.responsibility (@resp)) (att.global.source (@source)) att.pointing (@target)
att.citing (unit, @from,
@to)
|
||||||||||
| Contained by |
core:
bibl
|
||||||||||
| May contain |
core:
foreign
character data
|
||||||||||
| Note | The <citedRange> is used to indicate the portion of a text is being cited in a bibliographic reference. It requires a unit attribute with one of the following values: col, entry, fol, line, map, part, p, section, and vol. |
||||||||||
| Example | <citedRange>pp 12–13</citedRange>
<citedRange unit="page" from="12" to="13"/>
<citedRange unit="volume">II</citedRange>
<citedRange unit="page">12</citedRange> |
||||||||||
| Example | <bibl> <ptr target="#mueller01"/>, <citedRange target="http://example.com/mueller3.xml#page4">vol.
3, pp. 4-5</citedRange>
</bibl> |
||||||||||
| Content model |
<content>
<sequence minOccurs="1" maxOccurs="1">
<textNode/>
<elementRef key="foreign" minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
</content>
⚓ |
||||||||||
| Schema Declaration |
element citedRange
{
tei_att.global.attributes,
tei_att.citing.attribute.from,
tei_att.citing.attribute.to,
tei_att.pointing.attributes,
attribute unit
{
"book"
| "chapter"
| "col"
| "entry"
| "fig"
| "fol"
| "line"
| "map"
| "note"
| "part"
| "p"
| "section"
| "URL"
| "verse"
| "vol"
},
( text, tei_foreign* )
}⚓ |
||||||||||
| <classDecl> (classification declarations) contains one or more taxonomies defining any classificatory codes used elsewhere in the text. [2.3.7. The Classification Declaration 2.3. The Encoding Description] | |
| Module | header — NHSL TEI P5 Schema Customization |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.analytic (@ana)) (att.global.change (@change)) (att.global.linking (@corresp)) (att.global.rendition (@rend)) (att.global.responsibility (@resp)) (att.global.source (@source)) |
| Contained by |
header:
encodingDesc
|
| May contain |
header:
taxonomy
|
| Note | The <classDecl> contains one or more taxonomies defining any classificatory codes used elsewhere in the text. There are various tags which Syriaca.org uses to mark elements for a variety of purposes. Syriaca.org’s preferred name forms are tagged with "syriaca-headword", for example. |
| Example | <classDecl> <taxonomy> <category xml:id="syriaca-headword"> <catDesc>The name used by
Syriaca.org for document titles, citation, and
disambiguation. These names have been created according to
the Syriac.org guidelines for headwords: <ref target="http://syriaca.org/documentation/headwords.html">http://syriaca.org/documentation/headwords.html</ref>.</catDesc> </category> </taxonomy>
</classDecl> |
| Content model |
<content>
<elementRef key="taxonomy" minOccurs="1"
maxOccurs="1"/>
</content>
⚓ |
| Schema Declaration |
element classDecl { tei_att.global.attributes, tei_taxonomy }⚓ |
| <date> (date) contains a date in any format. [3.6.4. Dates and Times 2.2.4. Publication, Distribution, Licensing, etc. 2.6. The Revision Description 3.12.2.4. Imprint, Size of a Document, and Reprint Information 16.2.3. The Setting Description 14.4. Dates] | |||||||||||||||||||||||||||||||
| Module | core — NHSL TEI P5 Schema Customization | ||||||||||||||||||||||||||||||
| Attributes | Attributes att.calendarSystem (@calendar) att.global
(xml:id, n, @xml:lang) att.global.responsibility (@resp) att.global.source (@source) att.datable
(@srophe:computed-start, @srophe:computed-end) att.datable.custom
(@when-custom, @notBefore-custom, @notAfter-custom,
@from-custom, @to-custom, @datingPoint, @datingMethod) att.datable.w3c (notBefore, notAfter, @when, @from, @to)
att.typed (type,
@subtype)
|
||||||||||||||||||||||||||||||
| Contained by |
header:
publicationStmt
|
||||||||||||||||||||||||||||||
| May contain | Character data only | ||||||||||||||||||||||||||||||
| Note | A <date> elment includes both a machine-readable version (using attributes like when, notBefore, notAfter) and a human-readable version as text in the element content. See the Syriaca.org documentation for editorial conventions regarding dates. |
||||||||||||||||||||||||||||||
| Example | <date notBefore="1240" notAfter="1286" type="original-composition">mid-late 13th
century</date> |
||||||||||||||||||||||||||||||
| Schematron |
<sch:rule context="tei:body/child::tei:bibl/child::tei:date">
<sch:assert test="@source or @resp"> The <date>
element for the main work <bibl> must have either a
@source attribute or a @resp attribute. </sch:assert>
</sch:rule> |
||||||||||||||||||||||||||||||
| Content model |
<content>
<textNode/>
</content>
⚓ |
||||||||||||||||||||||||||||||
| Schema Declaration |
element date
{
tei_att.global.attribute.xmllang,
tei_att.global.responsibility.attribute.resp,
tei_att.global.source.attribute.source,
tei_att.calendarSystem.attributes,
tei_att.datable.attribute.srophecomputed-start,
tei_att.datable.attribute.srophecomputed-end,
tei_att.datable.custom.attribute.when-custom,
tei_att.datable.custom.attribute.notBefore-custom,
tei_att.datable.custom.attribute.notAfter-custom,
tei_att.datable.custom.attribute.from-custom,
tei_att.datable.custom.attribute.to-custom,
tei_att.datable.custom.attribute.datingPoint,
tei_att.datable.custom.attribute.datingMethod,
tei_att.datable.w3c.attribute.when,
tei_att.datable.w3c.attribute.from,
tei_att.datable.w3c.attribute.to,
tei_att.typed.attribute.subtype,
attribute notBefore { text }?,
attribute notAfter { text }?,
attribute type { "original-composition" | "revision" | "translation" }?,
text
}⚓ |
||||||||||||||||||||||||||||||
| <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. [23.4.1. Description of Components] | |||||||||||||||||
| Module | core — NHSL TEI P5 Schema Customization | ||||||||||||||||
| Attributes | Attributesatt.global.linking (@corresp) att.global.responsibility (@resp) att.global.source (@source)
|
||||||||||||||||
| Contained by | |||||||||||||||||
| May contain | |||||||||||||||||
| Note | 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. <place xml:id="KERG2"> <placeName>Kerguelen Islands</placeName>
<!-- ... --> <terrain> <desc>antarctic tundra</desc> </terrain>
<!-- ... -->
</place> |
||||||||||||||||
| Schematron |
<sch:rule context="tei:noteGrp[@type='abstract']/tei:desc">
<sch:assert test=". = 'Abstract'">Text node must be
"Abstract".</sch:assert> </sch:rule>
<sch:rule context="tei:noteGrp[@type='contents']/tei:desc">
<sch:assert test=". = 'Contents'">Text node must be
"Contents".</sch:assert> </sch:rule>
<sch:rule context="tei:noteGrp[@type='disambiguation']/tei:desc">
<sch:assert test=". = 'Disambiguation'">Text node must
be "Disambiguation".</sch:assert> </sch:rule>
<sch:rule context="tei:noteGrp[@type='excerpts']/tei:desc">
<sch:assert test=". = 'Excerpts'">Text node must be
"Excerpt".</sch:assert> </sch:rule>
<sch:rule context="tei:noteGrp[@type='explicit']/tei:desc">
<sch:assert test=". = 'Explicit'">Text node must be
"Explicit".</sch:assert> </sch:rule>
<sch:rule context="tei:noteGrp[@type='incipit']/tei:desc">
<sch:assert test=". = 'Incipit'">Text node must be
"Incipit".</sch:assert> </sch:rule>
<sch:rule context="tei:noteGrp[@type='prologue']/tei:desc">
<sch:assert test=". = 'Prologue'">Text node must be
"Prologue".</sch:assert> </sch:rule>
<sch:rule context="tei:noteGrp[@type='scope']/tei:desc">
<sch:assert test=". = 'Scope'">Text node must be
"Scope".</sch:assert> </sch:rule>
<sch:rule context="tei:noteGrp[@type='versions']/tei:desc">
<sch:assert test=". = 'Ancient Versions'">Text node
must be "Versions".</sch:assert>
</sch:rule> |
||||||||||||||||
| Schematron |
<sch:rule context="//tei:body//tei:desc">
<sch:assert test="./@xml:lang"> All <desc>
elements must have an @xml:lang attribute.
</sch:assert> </sch:rule> |
||||||||||||||||
| Schematron |
<sch:rule context="tei:desc[@type='abstract']">
<sch:let name="series"
value="ancestor::tei:TEI//tei:seriesStmt/tei:idno[@type='URI']"/>
<sch:let name="abstractLangPairs" value="for $i in
parent::element()/tei:desc[@type='abstract']/tokenize(@corresp,
' ') return concat($i, '-', @xml:lang)"/>
<sch:assert test="every $i in tokenize(@corresp, ' ')
satisfies $i = $series"> Values allowed on @corresp:
<sch:value-of select="string-join($series, '; ')"/>.
</sch:assert>
<sch:assert test="count($abstractLangPairs) eq
count(distinct-values($abstractLangPairs))"> A series
(see individual values of @corresp) may have only one
abstract per language (see @xml:lang). </sch:assert>
</sch:rule> |
||||||||||||||||
| Schematron |
<sch:rule context="tei:desc[@type='abstract'][@xml:lang='en']">
<sch:let name="series"
value="ancestor::tei:TEI//tei:seriesStmt/tei:idno[@type='URI']"/>
<sch:let name="corresps"
value="parent::*/tei:desc[@xml:lang='en']/@corresp/tokenize(.,
'\s')"/> <sch:assert test="every $i in $series
satisfies $i = $corresps"> Each abstract must be
associated with a series. As such, each of the following
must appear once as a value on the @corresp attribute of an
abstract: <sch:value-of select="string-join($series, ';
')"/>. </sch:assert> </sch:rule> |
||||||||||||||||
| Schematron |
<sch:rule context="tei:event/tei:desc">
<sch:report test="@resp or @source">Documentation
using @resp or @source should go on the parent <event>
element.</sch:report> </sch:rule>
<sch:rule context="tei:state/tei:desc">
<sch:report test="@resp or @source">Documentation
using @resp or @source should go on the parent <state>
element.</sch:report> </sch:rule> |
||||||||||||||||
| 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> |
||||||||||||||||
| Content model |
<content>
<sequence minOccurs="1" maxOccurs="1">
<textNode/>
<elementRef key="label" minOccurs="0"
maxOccurs="1"/>
<elementRef key="persName" minOccurs="0"
maxOccurs="1"/>
<elementRef key="placeName" minOccurs="0"
maxOccurs="1"/>
<elementRef key="ref" minOccurs="0"
maxOccurs="1"/>
<elementRef key="title" minOccurs="0"
maxOccurs="1"/>
</sequence>
</content>
⚓ |
||||||||||||||||
| Schema Declaration |
element desc
{
tei_att.global.linking.attribute.corresp,
tei_att.global.responsibility.attribute.resp,
tei_att.global.source.attribute.source,
attribute xml:lang
{
"ar"
| "ar-Syrc"
| "ar-Syre"
| "ar-Syrj"
| "ar-Syrn"
| "cop"
| "cu"
| "de"
| "de-x-baumstrk"
| "fr-x-zanetti"
| "el"
| "en"
| "en-x-gedsh"
| "en-x-lah"
| "en-x-srp1"
| "es"
| "fr"
| "fr-x-bhs"
| "fr-x-fiey"
| "gez"
| "grc"
| "he"
| "hy"
| "it"
| "ka"
| "la"
| "mal"
| "mal-Syrc"
| "mal-Syre"
| "mal-Syrj"
| "mal-Syrn"
| "nl"
| "pl"
| "pt"
| "ru"
| "syr"
| "syr-Syre"
| "syr-Syrj"
| "syr-Syrn"
| "syr-pal"
| "syr-x-syrm"
| "sog"
| "tr"
}?,
attribute type { "abstract" | "note" }?,
( text, tei_label?, tei_persName?, tei_placeName?, tei_ref?, tei_title? )
}⚓ |
||||||||||||||||
| <edition> (edition) describes the particularities of one edition of a text. [2.2.2. The Edition Statement] | |||||||||
| Module | header — NHSL TEI P5 Schema Customization | ||||||||
| Attributes | Attributesatt.global
(n, @xml:id, @xml:lang)
att.global.analytic (@ana)
att.global.change (@change) att.global.linking (@corresp)
att.global.rendition
(@rend) att.global.responsibility (@resp) att.global.source (@source)
|
||||||||
| Contained by |
header:
editionStmt
|
||||||||
| May contain | Empty element | ||||||||
| Example | <edition>First edition <date>Oct 1990</date>
</edition>
<edition n="S2">Students' edition</edition> |
||||||||
| Content model |
<content>
<empty/>
</content>
⚓ |
||||||||
| Schema Declaration |
element edition
{
tei_att.global.attribute.xmlid,
tei_att.global.attribute.xmllang,
tei_att.global.analytic.attribute.ana,
tei_att.global.change.attribute.change,
tei_att.global.linking.attribute.corresp,
tei_att.global.rendition.attribute.rend,
tei_att.global.responsibility.attribute.resp,
tei_att.global.source.attribute.source,
attribute n { text },
empty
}⚓ |
||||||||
| <editionStmt> (edition statement) groups information relating to one edition of a text. [2.2.2. The Edition Statement 2.2. The File Description] | |
| Module | header — NHSL TEI P5 Schema Customization |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.analytic (@ana)) (att.global.change (@change)) (att.global.linking (@corresp)) (att.global.rendition (@rend)) (att.global.responsibility (@resp)) (att.global.source (@source)) |
| Contained by |
header:
fileDesc
|
| May contain |
header:
edition
|
| Note | The <editionStmt> allows the specification of an edition or version number. When a TEI file is first published online, that edition should be "1.0". Subsequent revisions may bump the revision number, either by a whole new version (i.e. to "2.0") or by a minor version (i.e. to "1.1"). |
| Example | <editionStmt> <edition n="1.0"/>
</editionStmt> |
| Content model |
<content>
<elementRef key="edition" minOccurs="1"
maxOccurs="1"/>
</content>
⚓ |
| Schema Declaration |
element editionStmt { tei_att.global.attributes, tei_edition }⚓ |
| <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] | |||||||||||||||||||||||||||||
| Module | core — NHSL TEI P5 Schema Customization | ||||||||||||||||||||||||||||
| Attributes | Attributes
|
||||||||||||||||||||||||||||
| Contained by |
core:
bibl
header:
seriesStmt
titleStmt
|
||||||||||||||||||||||||||||
| May contain | |||||||||||||||||||||||||||||
| Note | The <editor> element is used in three places in the Srophé App. In the <teiHeader> the editors of the document appear inside the <titleStmt> element while inside the <seriesStmt> the editors responsible for a series that the document might be a part of are listed. In the text of files, the <editor> element is used inside of <bibl> elements to indicated editors of works sited. |
||||||||||||||||||||||||||||
| Example | <editor ref="http://syriaca.org/person/239" role="http://syriaca.org/documentation/author-editor-roles.xml#translator">
<persName xml:lang="en">Gregorius Bar Hebraeus</persName> — <persName xml:lang="syr">ܓܪܝܓܘܪܝܘܣ ܒܪ ܥܒܪܝܐ</persName>
</editor> |
||||||||||||||||||||||||||||
| Example | <editor role="creator" ref="http://syriaca.org/documentation/editors.xml#tcarlson">Thomas
A. Carlson</editor> |
||||||||||||||||||||||||||||
| Example | <bibl xml:id="bib18-9">
<title xml:lang="en">The Sixth Book of the Select
Letters of Severus, Patriarch of Antioch in the Syriac
Version of Athanasius of Nisibis</title> <title type="sub">Translation, I.1 - II.3</title> <author> <persName ref="http://syriaca.org/person/51">Severus
of Antioch</persName>
</author> <editor> <persName ref="http://syriaca.org/person/403">E.
W. Brooks</persName>
</editor> <ptr target="http://syriaca.org/bibl/668"/>
<citedRange unit="p">151</citedRange>
</bibl> |
||||||||||||||||||||||||||||
| Example | <titleStmt> <title level="a" xml:lang="en">Telneshe — <foreign xml:lang="syr">ܬܠܢܫܐ</foreign> </title> ... <editor role="code-author" ref="http://syriaca.org/documentation/editors.xml#tcarlson">Thomas
A. Carlson</editor>
<editor role="content-author"
ref="http://syriaca.org/documentation/editors.xml#dboero">Dina
Boero</editor> <respStmt> <resp>Initial XML by</resp> <name ref="http://syriaca.org/documentation/editors.xml#tcarlson">Thomas
A. Carlson</name>
</respStmt> <respStmt> <resp>Data submission
by</resp> <name ref="http://syriaca.org/documentation/editors.xml#dboero">Dina
Boero</name> </respStmt> <respStmt> <resp>Data submission
review by</resp> <name ref="http://syriaca.org/documentation/editors.xml#pforness">Philip
Forness</name>
</respStmt>
</titleStmt> |
||||||||||||||||||||||||||||
| Example | <seriesStmt> <title level="s" xml:lang="en">The Syriac Gazetteer</title> <editor role="general" ref="http://syriaca.org/documentation/editors.xml#dmichelson">
<persName>David A.
Michelson</persName>,
<date from="2014">2014-present</date>.</editor> <editor role="general" ref="http://syriaca.org/documentation/editors.xml#wpotter">
<persName>William
L. Potter</persName>,
<date from="2020">2020-present</date>.</editor> <editor role="technical" ref="http://syriaca.org/documentation/editors.xml#dschwartz">
<persName>Daniel L.
Schwartz</persName>,
<date from="2019">2019-present</date>.</editor> <editor role="past-general" ref="http://syriaca.org/documentation/editors.xml#tcarlson">
<persName>Thomas A.
Carlson</persName>,
<date from="2014" to="2018">2014-2018</date> </editor> <idno type="URI">http://syriaca.org/geo</idno>
</seriesStmt> |
||||||||||||||||||||||||||||
| Schematron |
<sch:rule context="tei:body/child::tei:bibl/child::tei:editor/@ana">
<sch:assert test=". = 'attributed' or . = 'disputed' or .
= 'pseudo'"> In this context, the acceptable @ana
attribute values are "attributed", "disputed", or "pseudo".
</sch:assert> </sch:rule> |
||||||||||||||||||||||||||||
| Schematron |
<sch:rule context="tei:body/child::tei:bibl/child::tei:editor">
<sch:report test="tei:persName"> This <author>
element allows only a text node with an English name or a
<foreign> element with a non-English name.
</sch:report> <sch:assert test="@xml:lang"> This
<editor> element requires an @xml:lang attribute.
</sch:assert> <sch:assert test="@source or
@resp"> The <editor> element for the main work
<bibl> must have either a @source attribute or a @resp
attribute. </sch:assert>
<sch:assert test="matches(@ref,
concat('http://syriaca.org/person/', '\d+'))"> This
<editor> element must take a @ref attribute with a
Syriaca.org person URI which reqires the form
'http://syriaca.org/person/{\d+}' (where {\d+} is a number).
</sch:assert> </sch:rule>
<sch:rule context="tei:body/child::tei:bibl/child::tei:editor/@role">
<sch:assert test=". = 'scribe' or . = 'translator'">
The only @role values allowed on this <editor> element
are "scribe" or "translator". </sch:assert>
</sch:rule> |
||||||||||||||||||||||||||||
| Schematron |
<sch:rule context="//tei:teiHeader//tei:editor">
<sch:assert test="./@role">A @role attribute is
required on the <editor> element inside
<teiHeader>.</sch:assert> </sch:rule>
<sch:rule context="//tei:teiHeader//tei:titleStmt//tei:editor/@role">
<sch:assert test=". = 'creator' or . = 'code-author' or .
= 'content-author' or . = 'contributor'"> The acceptable
attribute values for @role on the <editor> element
inside the <titleStmt> are: creator, code-author,
content-author, or contributor. </sch:assert>
</sch:rule>
<sch:rule context="//tei:teiHeader//tei:seriesStmt//tei:editor/@role">
<sch:assert test=". = 'associate' or . = 'general' or . =
'technical' or . = 'past-associate' or . = 'past-general' or
. = 'past-technical'"> The acceptable attribute values
for @role on the <editor> element inside the
<seriesStmt> are: associate, general, technical,
past-associate, past-general, or past-technical.
</sch:assert> </sch:rule>
<sch:rule context="//tei:body//tei:editor/@role">
<sch:assert test=". = 'editor' or . = 'general' or . =
'scribe' or . = 'translator'"> The acceptable attribute
values for @role on the <editor> element inside the
<body> are: editor, general, scribe, or translator.
</sch:assert> </sch:rule> |
||||||||||||||||||||||||||||
| Schematron |
<sch:rule context="//tei:teiHeader//tei:seriesStmt//tei:editor[contains(@role,
'past')]"> <sch:assert test="tei:date">An
<editor> element with a "past" @role attribute must
contain a <date> element.</sch:assert>
</sch:rule> |
||||||||||||||||||||||||||||
| Schematron |
<sch:rule context="//tei:teiHeader//tei:editor">
<sch:assert test="./@ref">A @ref attribute is required
on the <editor> element inside
<teiHeader>.</sch:assert> </sch:rule>
<sch:rule context="//tei:teiHeader//tei:editor/@ref">
<sch:let name="edsDoc"
value="doc('https://raw.githubusercontent.com/srophe/gaddel/master/documentation/editors.xml')"/>
<sch:let name="eds"
value="$edsDoc//tei:text/tei:body/tei:listPerson/tei:person/@xml:id"/>
<sch:let name="refValues" value="for $i in $eds return
concat('http://syriaca.org/documentation/editors.xml#',
$i)"/> <sch:assert test="every $i in . satisfies $i =
$refValues"> Acceptable values for the @ref attribute on
an <editor> element inside the <teiHeader>
include: <sch:value-of select="string-join($refValues, '
| ')"/>. </sch:assert> </sch:rule> |
||||||||||||||||||||||||||||
| Content model |
<content>
<sequence minOccurs="1" maxOccurs="1">
<elementRef key="date" minOccurs="0"
maxOccurs="1"/>
<elementRef key="persName" minOccurs="0"
maxOccurs="1"/>
<elementRef key="foreign" minOccurs="0"
maxOccurs="1"/>
<textNode/>
</sequence>
</content>
⚓ |
||||||||||||||||||||||||||||
| Schema Declaration |
element editor
{
attribute source { list { + } }?,
attribute role
{
list
{
(
"associate"
| "code-author"
| "content-author"
| "contributor"
| "creator"
| "editor"
| "general"
| "past-associate"
| "past-general"
| "past-technical"
| "scribe"
| "technical"
| "translator"
)+
}
}?,
attribute ref { text }?,
( tei_date?, tei_persName?, tei_foreign?, text )
}⚓ |
||||||||||||||||||||||||||||
| <editorialDecl> (editorial practice declaration) provides details of editorial principles and practices applied during the encoding of a text. [2.3.3. The Editorial Practices Declaration 2.3. The Encoding Description 16.3.2. Declarable Elements] | |
| Module | header — NHSL TEI P5 Schema Customization |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.analytic (@ana)) (att.global.change (@change)) (att.global.linking (@corresp)) (att.global.rendition (@rend)) (att.global.responsibility (@resp)) (att.global.source (@source)) |
| Contained by |
header:
encodingDesc
|
| May contain |
core:
p
header:
interpretation
|
| Note | The first element within an <encodingDesc> is the <editorialDecl>, which indicates editorial decisions regarding how the source documents were handled. An <editorialDecl> cannot directly contain prose, so a prose description of each editorial decision should be wrapped in a <p> element. References to particular bibliographic entries can have their Syriaca.org URIs wrapped in an <idno> for specificity. The first <p> element should contain a pointer to the Syriaca.org documentation. |
| Example | <encodingDesc> <editorialDecl> <p>This record created following the
Syriaca.org guidelines. Documentation available at:
<ref target="http://syriaca.org/documentation">
http://syriaca.org/documentation</ref>.</p> <p>The capitalization of names from GEDSH
(<idno type="URI">http://syriaca.org/bibl/1</idno>) was normalized
(i.e. names in ALL-CAPS were replaced by Proper-noun
capitalization).</p>
<p>The unchanging
parts of alternate names from Barsoum (<idno type="URI">http://syriaca.org/bibl/2</idno>, <idno type="URI">http://syriaca.org/bibl/3</idno>, or <idno type="URI">http://syriaca.org/bibl/4</idno>) have been supplied
to each alternate.</p>
<p>Names from the
English translation of Barsoum (<idno type="URI">http://syriaca.org/bibl/4</idno>) were put in
sentence word order rather than fronting a dictionary
headword. Any commas in the Barsoum name in English were
removed.</p> <p>The <gi>state</gi> element of
@type="existence" indicates the period for which this
place was in use as a place of its indicated type (e.g. an
inhabited settlement, a functioning monastery or
church, an administrative province). Natural features
always in existence have no <gi>state</gi> element of
@type="existence".</p> ... </editorialDecl> ... </encodingDesc> |
| Schematron |
<sch:pattern is-a="declarable">
<sch:param name="tde" value="tei:editorialDecl"/>
</sch:pattern> |
| Content model |
<content>
<sequence minOccurs="1" maxOccurs="1">
<elementRef key="interpretation"
maxOccurs="unbounded"/>
<elementRef key="p" maxOccurs="unbounded"/>
</sequence>
</content>
⚓ |
| Schema Declaration |
element editorialDecl
{
tei_att.global.attributes,
( tei_interpretation+, tei_p+ )
}⚓ |
| <encodingDesc> (encoding description) documents the relationship between an electronic text and the source or sources from which it was derived. [2.3. The Encoding Description 2.1.1. The TEI Header and Its Components] | |
| Module | header — NHSL TEI P5 Schema Customization |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.analytic (@ana)) (att.global.change (@change)) (att.global.linking (@corresp)) (att.global.rendition (@rend)) (att.global.responsibility (@resp)) (att.global.source (@source)) |
| Contained by |
header:
teiHeader
|
| May contain |
header:
classDecl
editorialDecl
|
| Note | The <encodingDesc> element of the <teiHeader> is used for indicating aspects of the process of encoding the text. Even data are "born digital," they nevertheless have certain editorial decisions regarding how they have used data derived from print resources, and certain tags available for use in our srophe:tags attribute. Those sorts of details are encoded here. |
| Example | <encodingDesc> <editorialDecl> <p>This record has been created following
the Syriaca.org editorial guidelines. Documentation is
available at: <ref target="http://syriaca.org/documentation">http://syriaca.org/documentation</ref>. <title>The Syriac
Gazetteer</title>
was encoded using both the general editorial guidelines
for all publications of Syriaca.org and an encoding
schema specific to <title>The Syriac Gazetteer</title>.</p> <p>Approximate dates
described in terms of centuries or partial centuries have
been interpreted into quantitative values as documented
in the Syriaca.org guidelines for normalization of
dates. See <ref target="http://syriaca.org/documentation/dates.html">Syriaca.org
Guidelines for Approximate Dates</ref>.</p> <p>The <gi>state</gi> element of @type="existence"
indicates the period for which this place was in use as
a place of its indicated type (e.g. an inhabited
settlement, a functioning monastery or church, an
administrative province). While it is possible to
indicate a source for this date, this date is usually
based on the estimate of the editors and provided as an aid
to searching. As a practice, attested dates for a place
based on historical sources have instead been encoded
more precisely using <gi>event</gi> of @type="attestation". Natural
features which have always existed have no date on the <gi>state</gi> element of
@type="existence" since they are are presumed to have always
existed throughout recorded history.</p> <p>In some cases, maps from
print publications have been used as the basis for
coordinate data in <title>The Syriac Gazetteer</title>. In two instances,
the editors of such print maps provided the digital
coordinate data used to prepare the print maps.
Specifically, coordinates which are attributed to <title>The Gorgias
Encyclopedic Dictionary of the Syriac Heritage</title> (<ref target="http://syriaca.org/bibl/1">http://syriaca.org/bibl/1</ref>) or to <title>The Syriac
World</title> (<ref target="http://syriaca.org/bibl/PUTG99V4">http://syriaca.org/bibl/PUTG99V4</ref>) were extracted from
the KML files used to create the print maps for those
volumes. Because only the print maps were published,
the citation for these coordinates refers to the print
source. The editors of the <title>The Syriac Gazetteer</title> are grateful to
the editors of <title>The Gorgias Encyclopedic Dictionary
of the Syriac Heritage</title> and <title>The Syriac World</title> for providing
these coordinate files.</p> <p>The editors have silently normalized
data from other sources in some cases. The primary
instances are listed below.</p> <p>The capitalization of names from <title>The Gorgias
Encyclopedic Dictionary of the Syriac Heritage</title> (<ref target="http://syriaca.org/bibl/1">http://syriaca.org/bibl/1</ref>) was normalized
silently (i.e. names in ALL-CAPS were replaced by
Proper-noun capitalization).</p> <p>The unchanging parts of alternate names
from the editions and translations of Barsoum, <title>The Scattered
Pearls: A History of Syriac Literature and
Sciences</title>
(<ref target="http://syriaca.org/bibl/2">http://syriaca.org/bibl/2</ref>, <ref target="http://syriaca.org/bibl/3">http://syriaca.org/bibl/3</ref>, or <ref target="http://syriaca.org/bibl/4">http://syriaca.org/bibl/4</ref>) have been supplied
silently.</p> <p>Names from the English
translation of Barsoum, <title>The Scattered Pearls: A
History of Syriac Literature and Sciences</title> (<ref target="http://syriaca.org/bibl/4">http://syriaca.org/bibl/4</ref>) were silently
transformed into sentence word order rather than the
headword alphabetization used by Barsoum. Commas were
silently removed.</p>
</editorialDecl>
<classDecl> <taxonomy> <category xml:id="syriaca-headword"> <catDesc>The name used by
Syriaca.org for document titles, citation, and
disambiguation. These names have been created according to
the Syriac.org guidelines for headwords: <ref target="http://syriaca.org/documentation/headwords.html">http://syriaca.org/documentation/headwords.html</ref>.</catDesc> </category> </taxonomy> </classDecl>
</encodingDesc> |
| Example | <encodingDesc> <editorialDecl> <p>This record has been created following
the Syriaca.org editorial guidelines. Documentation is
available at: <ref target="http://syriaca.org/documentation">http://syriaca.org/documentation</ref>. <title>The Syriac
Gazetteer</title>
was encoded using both the general editorial guidelines
for all publications of Syriaca.org and an encoding
schema specific to <title>The Syriac Gazetteer</title>.</p> <p>Approximate dates
described in terms of centuries or partial centuries have
been interpreted into quantitative values as documented
in the Syriaca.org guidelines for normalization of
dates. See <ref target="http://syriaca.org/documentation/dates.html">Syriaca.org
Guidelines for Approximate Dates</ref>.</p> <p>The <gi>state</gi> element of @type="existence"
indicates the period for which this place was in use as
a place of its indicated type (e.g. an inhabited
settlement, a functioning monastery or church, an
administrative province). While it is possible to
indicate a source for this date, this date is usually
based on the estimate of the editors and provided as an aid
to searching. As a practice, attested dates for a place
based on historical sources have instead been encoded
more precisely using <gi>event</gi> of @type="attestation". Natural
features which have always existed have no date on the <gi>state</gi> element of
@type="existence" since they are are presumed to have always
existed throughout recorded history.</p> <p>In some cases, maps from
print publications have been used as the basis for
coordinate data in <title>The Syriac Gazetteer</title>. In two instances,
the editors of such print maps provided the digital
coordinate data used to prepare the print maps.
Specifically, coordinates which are attributed to <title>The Gorgias
Encyclopedic Dictionary of the Syriac Heritage</title> (<ref target="http://syriaca.org/bibl/1">http://syriaca.org/bibl/1</ref>) or to <title>The Syriac
World</title> (<ref target="http://syriaca.org/bibl/PUTG99V4">http://syriaca.org/bibl/PUTG99V4</ref>) were extracted from
the KML files used to create the print maps for those
volumes. Because only the print maps were published,
the citation for these coordinates refers to the print
source. The editors of the <title>The Syriac Gazetteer</title> are grateful to
the editors of <title>The Gorgias Encyclopedic Dictionary
of the Syriac Heritage</title> and <title>The Syriac World</title> for providing
these coordinate files.</p> <p>The editors have silently normalized
data from other sources in some cases. The primary
instances are listed below.</p> <p>The capitalization of names from <title>The Gorgias
Encyclopedic Dictionary of the Syriac Heritage</title> (<ref target="http://syriaca.org/bibl/1">http://syriaca.org/bibl/1</ref>) was normalized
silently (i.e. names in ALL-CAPS were replaced by
Proper-noun capitalization).</p> <p>The unchanging parts of alternate names
from the editions and translations of Barsoum, <title>The Scattered
Pearls: A History of Syriac Literature and
Sciences</title>
(<ref target="http://syriaca.org/bibl/2">http://syriaca.org/bibl/2</ref>, <ref target="http://syriaca.org/bibl/3">http://syriaca.org/bibl/3</ref>, or <ref target="http://syriaca.org/bibl/4">http://syriaca.org/bibl/4</ref>) have been supplied
silently.</p> <p>Names from the English
translation of Barsoum, <title>The Scattered Pearls: A
History of Syriac Literature and Sciences</title> (<ref target="http://syriaca.org/bibl/4">http://syriaca.org/bibl/4</ref>) were silently
transformed into sentence word order rather than the
headword alphabetization used by Barsoum. Commas were
silently removed.</p>
</editorialDecl> ...
</encodingDesc> |
| Content model |
<content>
<sequence minOccurs="1" maxOccurs="1">
<elementRef key="editorialDecl"/>
<elementRef key="classDecl"/>
</sequence>
</content>
⚓ |
| Schema Declaration |
element encodingDesc
{
tei_att.global.attributes,
( tei_editorialDecl, tei_classDecl )
}⚓ |
| <fileDesc> (file description) contains a full bibliographic description of an electronic file. [2.2. The File Description 2.1.1. The TEI Header and Its Components] | |
| Module | header — NHSL TEI P5 Schema Customization |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.analytic (@ana)) (att.global.change (@change)) (att.global.linking (@corresp)) (att.global.rendition (@rend)) (att.global.responsibility (@resp)) (att.global.source (@source)) |
| Contained by |
header:
teiHeader
|
| May contain | |
| Note | Each <fileDesc> element contains (in order) a <titleStmt>, an <editionStmt>, a <publicationStmt>, an optional <seriesStmt>, and a <sourceDesc>. |
| 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> |
| Content model |
<content>
<sequence minOccurs="1" maxOccurs="1">
<elementRef key="titleStmt" minOccurs="1"
maxOccurs="1"/>
<elementRef key="editionStmt"
minOccurs="1" maxOccurs="1"/>
<elementRef key="publicationStmt"
minOccurs="1" maxOccurs="1"/>
<elementRef key="seriesStmt"
minOccurs="0" maxOccurs="unbounded"/>
<elementRef key="sourceDesc"
minOccurs="1" maxOccurs="1"/>
</sequence>
</content>
⚓ |
| Schema Declaration |
element fileDesc
{
tei_att.global.attributes,
(
tei_titleStmt,
tei_editionStmt,
tei_publicationStmt,
tei_seriesStmt*,
tei_sourceDesc
)
}⚓ |
| <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] | |||||||||||
| Module | core — NHSL TEI P5 Schema Customization | ||||||||||
| Attributes | Attributesatt.global
(xml:lang, @xml:id, @n)
att.global.analytic (@ana)
att.global.change (@change) att.global.linking (@corresp)
att.global.rendition
(@rend) att.global.responsibility (@resp) att.global.source (@source)
|
||||||||||
| Contained by |
core:
author
citedRange
editor
quote
title
|
||||||||||
| May contain | Character data only | ||||||||||
| Note | 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>? |
||||||||||
| Content model |
<content>
<textNode/>
</content>
⚓ |
||||||||||
| Schema Declaration |
element foreign
{
tei_att.global.attribute.xmlid,
tei_att.global.attribute.n,
tei_att.global.analytic.attribute.ana,
tei_att.global.change.attribute.change,
tei_att.global.linking.attribute.corresp,
tei_att.global.rendition.attribute.rend,
tei_att.global.responsibility.attribute.resp,
tei_att.global.source.attribute.source,
attribute xml:lang
{
"ar"
| "ar-Syrc"
| "ar-Syre"
| "ar-Syrj"
| "ar-Syrn"
| "cop"
| "cu"
| "de"
| "de-x-baumstrk"
| "fr-x-zanetti"
| "el"
| "en"
| "en-x-gedsh"
| "en-x-lah"
| "en-x-srp1"
| "es"
| "fr"
| "fr-x-bhs"
| "fr-x-fiey"
| "gez"
| "grc"
| "he"
| "hy"
| "it"
| "ka"
| "la"
| "mal"
| "mal-Syrc"
| "mal-Syre"
| "mal-Syrj"
| "mal-Syrn"
| "nl"
| "pl"
| "pt"
| "ru"
| "syr"
| "syr-Syre"
| "syr-Syrj"
| "syr-Syrn"
| "syr-pal"
| "syr-x-syrm"
| "sog"
| "tr"
},
text
}⚓ |
||||||||||
| <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] | |
| Module | header — NHSL TEI P5 Schema Customization |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.analytic (@ana)) (att.global.change (@change)) (att.global.linking (@corresp)) (att.global.rendition (@rend)) (att.global.responsibility (@resp)) (att.global.source (@source)) |
| Contained by |
header:
titleStmt
|
| May contain | Character data only |
| Note | Next within the <titleStmt> the funding bodies are identified by use of the <funder> element. If multiple funding bodies are relevant, then each one gets a separate <funder> element, which are simply listed. |
| Example | <titleStmt> ... <funder>The National Endowment for the
Humanities</funder>
<funder>The
International Balzan Prize Foundation</funder> ... </titleStmt> |
| Content model |
<content>
<textNode/>
</content>
⚓ |
| Schema Declaration |
element funder { tei_att.global.attributes, text }⚓ |
| <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] | |
| Module | core — NHSL TEI P5 Schema Customization |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.analytic (@ana)) (att.global.change (@change)) (att.global.linking (@corresp)) (att.global.rendition (@rend)) (att.global.responsibility (@resp)) (att.global.source (@source)) att.cmc (@generatedBy) att.placement (@place) att.typed (@type, @subtype) att.written (@hand) |
| Contained by |
core:
listBibl
|
| May contain | Character data only |
| Note | 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. <div type="subsection"> <head place="margin">Secunda conclusio</head> <p> <lb n="1251"/>
<hi rend="large">Potencia: habitus: et
actus: recipiunt speciem ab obiectis<supplied>.</supplied> </hi> <lb n="1252"/>Probatur sic. Omne importans
necessariam habitudinem ad proprium [...] </p>
</div> |
| Example | 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> |
| Schematron |
<sch:rule context="tei:listBibl[@type='editions']/tei:head">
<sch:assert test=". = 'Editions'">Text node must be
"Editions".</sch:assert> </sch:rule>
<sch:rule context="tei:listBibl[@type='manuscripts']/tei:head">
<sch:assert test=". = 'Manuscripts'">Text node must be
"Manuscripts".</sch:assert> </sch:rule>
<sch:rule context="tei:listBibl[@type='modernTranslations']/tei:head">
<sch:assert test=". = 'Modern Translations'">Text node
must be "Modern Translations".</sch:assert>
</sch:rule>
<sch:rule context="tei:listBibl[@type='ancientVersions']/tei:head">
<sch:assert test=". = 'Ancient Versions'">Text node
must be "Ancient Version".</sch:assert>
</sch:rule>
<sch:rule context="tei:listBibl[@type='secondaryLiterature']/tei:head">
<sch:assert test=". = 'Secondary Literature'">Text
node must be "Secondary Literature".</sch:assert>
</sch:rule> |
| Content model |
<content>
<textNode/>
</content>
⚓ |
| Schema Declaration |
element head
{
tei_att.global.attributes,
tei_att.cmc.attributes,
tei_att.placement.attributes,
tei_att.typed.attributes,
tei_att.written.attributes,
text
}⚓ |
| <idno> (identifier) supplies any form of identifier used to identify some object, such as a bibliographic item, a person, a title, an organization, etc. in a standardized way. [14.3.1. Basic Principles 2.2.4. Publication, Distribution, Licensing, etc. 2.2.5. The Series Statement 3.12.2.4. Imprint, Size of a Document, and Reprint Information] | |||||||||||||||||||
| Module | header — NHSL TEI P5 Schema Customization | ||||||||||||||||||
| Attributes | Attributes att.global (@xml:id,
@n, @xml:lang) (att.global.analytic (@ana)) (att.global.change (@change)) (att.global.linking (@corresp)) (att.global.rendition (@rend)) (att.global.responsibility (@resp)) (att.global.source (@source))
|
||||||||||||||||||
| Contained by |
header:
publicationStmt
seriesStmt
|
||||||||||||||||||
| May contain | Character data only | ||||||||||||||||||
| Note | <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. |
||||||||||||||||||
| Example | <idno type="ISBN">978-1-906964-22-1</idno>
<idno type="ISSN">0143-3385</idno>
<idno type="DOI">10.1000/123</idno>
<idno type="URI">http://www.worldcat.org/oclc/185922478</idno>
<idno type="URI">http://authority.nzetc.org/463/</idno>
<idno type="LT">Thomason Tract E.537(17)</idno>
<idno type="Wing">C695</idno>
<idno type="oldCat"> <g ref="#sym"/>345
</idno> 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:body/child::tei:bibl/child::tei:idno[@type='number']/@subtype">
<sch:assert test=". = ('Bekker', 'BHO', 'BHS', 'CPG',
'Fichtner', 'Kühn', 'Takahashi')"> The only acceptable
values for @subtype on a work <idno> with
@type="number" are "Bekker", "BHO", "BHS", "CPG",
"Fichtner", "Kühn", and "Takahashi". </sch:assert>
</sch:rule>
<sch:rule context="tei:listBibl[@type='manuscripts']/tei:bibl/tei:label/tei:idno/@subtype"
role="warning"> <sch:assert test=". = ('BAV', 'BL',
'BML', 'BNF', 'Berlin', 'Cambridge', 'Crawford',
'Haddad-Isaac', 'Harris', 'HMML', 'Leiden', 'Mingana',
'Rosen', 'SOAH', 'Sachau', 'Sinai', 'Yale')"> In the
context of manuscripts, this @subtype value may only be
"BAV" (for the Vatican Apostolic Library), "BML" (for The
Laurentian Library), "Berlin", "Cambridge", "Crawford",
"Haddad-Isaac", "Harris", "HMML", "Leiden", "Mingana",
"Rosen", "SOAH", "Sachau", or "Yale". If none of these
options is correct, please write in an appropriate value and
the warning message will prompt editors to ensure that it is
the correct value. </sch:assert>
</sch:rule> |
||||||||||||||||||
| 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="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:report test="preceding-sibling::element()[@xml:id =
$id]">This @xml:id is already in use.</sch:report>
</sch:rule> |
||||||||||||||||||
| Schematron |
<sch:rule context="//tei:idno[@type='deprecated']">
<sch:assert test="@change"> An <idno> element
with a @type attribute of "deprecation" must have a @change
attribute. </sch:assert> </sch:rule>
<sch:rule context="//tei:idno[not(@type='deprecated')]">
<sch:report test="@change"> Only an <idno>
element with a @type attribute of "deprecation" may have a
@change attribute. </sch:report>
</sch:rule> |
||||||||||||||||||
| Content model |
<content>
<textNode/>
</content>
⚓ |
||||||||||||||||||
| Schema Declaration |
element idno
{
tei_att.global.attributes,
attribute type { text },
attribute subtype
{
"BAV"
| "Bekker"
| "Berlin"
| "BHS"
| "BHO"
| "BL"
| "BML"
| "BNF"
| "Cambridge"
| "CPG"
| "Crawford"
| "Fichtner"
| "Haddad-Isaac"
| "Harris"
| "Kühn"
| "Leiden"
| "Mingana"
| "Rosen"
| "Takashi"
| "Sachau"
| "SOAH"
| "Sinai"
| "Yale"
}?,
text
}⚓ |
||||||||||||||||||
| <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] | |
| Module | header — NHSL TEI P5 Schema Customization |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.analytic (@ana)) (att.global.change (@change)) (att.global.linking (@corresp)) (att.global.rendition (@rend)) (att.global.responsibility (@resp)) (att.global.source (@source)) |
| Contained by |
header:
editorialDecl
|
| May contain |
core:
p
|
| Example | <interpretation> <p>The part of speech analysis applied
throughout section 4 was added by hand and has not been
checked</p>
</interpretation> |
| Schematron |
<sch:pattern is-a="declarable">
<sch:param name="tde" value="tei:interpretation"/>
</sch:pattern> |
| Content model |
<content>
<elementRef key="p"/>
</content>
⚓ |
| Schema Declaration |
element interpretation { tei_att.global.attributes, tei_p }⚓ |
| <label> (label) contains any label or heading used to identify part of a text, typically but not exclusively in a list or glossary. [3.8. Lists] | |||||||||||||||||
| Module | core — NHSL TEI P5 Schema Customization | ||||||||||||||||
| Attributes | Attributes att.global (@xml:id,
@n, @xml:lang) (att.global.analytic (@ana)) (att.global.change (@change)) (att.global.linking (@corresp)) (att.global.rendition (@rend)) (att.global.responsibility (@resp)) (att.global.source (@source))
|
||||||||||||||||
| Contained by | |||||||||||||||||
| May contain | |||||||||||||||||
| Example | 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: <list type="gloss" xml:lang="enm"> <head xml:lang="en">Vocabulary</head> <headLabel xml:lang="en">Middle English</headLabel> <headItem xml:lang="en">New English</headItem> <label>nu</label> <item xml:lang="en">now</item> <label>lhude</label> <item xml:lang="en">loudly</item> <label>bloweth</label> <item xml:lang="en">blooms</item> <label>med</label> <item xml:lang="en">meadow</item> <label>wude</label> <item xml:lang="en">wood</item> <label>awe</label> <item xml:lang="en">ewe</item> <label>lhouth</label> <item xml:lang="en">lows</item> <label>sterteth</label> <item xml:lang="en">bounds, frisks (cf. <cit> <ref>Chaucer, K.T.644</ref> <quote>a courser, <term>sterting</term>as the fyr</quote> </cit> </item> <label>verteth</label> <item xml:lang="la">pedit</item> <label>murie</label> <item xml:lang="en">merrily</item> <label>swik</label> <item xml:lang="en">cease</item> <label>naver</label> <item xml:lang="en">never</item>
</list> |
||||||||||||||||
| Example | 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
numbered"> <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. |
||||||||||||||||
| Schematron |
<sch:rule context="tei:label[not(ancestor::tei:relation)]">
<sch:report test="tei:ptr"> A <ptr> child of
<label> should only be used when <label> is the
descendant of <relation>. </sch:report>
</sch:rule> |
||||||||||||||||
| Schematron |
<sch:rule context="tei:listBibl[@type='manuscripts']/bibl/label[idno/@subtype='BAV']">
<sch:assert test="starts-with(., 'Vatican Apostolic
Library')"> This text should begin "The Vatican Apostolic
Library". </sch:assert> </sch:rule>
<sch:rule context="tei:listBibl[@type='manuscripts']/bibl/label[idno/@subtype='BL']">
<sch:assert test="starts-with(., 'London, British
Library')"> This text should begin "London, British
Library". </sch:assert> </sch:rule>
<sch:rule context="tei:listBibl[@type='manuscripts']/bibl/label[idno/@subtype='BML']">
<sch:assert test="starts-with(., 'Florence, The
Laurentian Library')"> This text should begin "Florence,
The Laurentian Library". </sch:assert>
</sch:rule>
<sch:rule context="tei:listBibl[@type='manuscripts']/bibl/label[idno/@subtype='BNF']">
<sch:assert test="starts-with(., 'Paris, Bibliothèque
nationale')"> This text should begin "Paris, Bibliothèque
nationale". </sch:assert> </sch:rule>
<sch:rule context="tei:listBibl[@type='manuscripts']/bibl/label[idno/@subtype='Berlin']">
<sch:assert test="starts-with(., 'Berlin,
Staatsbibliothek zu Berlin')"> This text should begin
"Berlin, Staatsbibliothek zu Berlin". </sch:assert>
</sch:rule>
<sch:rule context="tei:listBibl[@type='manuscripts']/bibl/label[idno/@subtype='Cambridge']">
<sch:assert test="starts-with(., 'Cambridge, University
Library')"> This text should begin "Cambridge, University
Library". </sch:assert> </sch:rule>
<sch:rule context="tei:listBibl[@type='manuscripts']/bibl/label[idno/@subtype='Crawford']">
<sch:assert test="starts-with(., 'Manchester, The
University of Manchester, Crawford Collection')"> This
text should begin "Manchester, The University of Manchester,
Crawford Collection". </sch:assert> </sch:rule>
<sch:rule context="tei:listBibl[@type='manuscripts']/bibl/label[idno/@subtype='Haddad-Issac']">
<sch:assert test="starts-with(., 'P. Haddad and J.
Isaac')"> This text should begin "P. Haddad and J.
Isaac". </sch:assert> </sch:rule>
<sch:rule context="tei:listBibl[@type='manuscripts']/bibl/label[idno/@subtype='Harris']">
<sch:assert test="starts-with(., 'J. Rendell Harris
Number')"> This text should begin "J. Rendell Harris
Number". </sch:assert> </sch:rule>
<sch:rule context="tei:listBibl[@type='manuscripts']/bibl/label[idno/@subtype='HMML']">
<sch:assert test="starts-with(., 'Hill Museum and
Manuscript Library')"> This text should begin "Hill
Museum and Manuscript Library". </sch:assert>
</sch:rule>
<sch:rule context="tei:listBibl[@type='manuscripts']/bibl/label[idno/@subtype='Leiden']">
<sch:assert test="starts-with(., 'Peshitta Institute
Leiden Manuscript Siglum')"> This text should begin
"Peshitta Institute Leiden Manuscript Siglum".
</sch:assert> </sch:rule>
<sch:rule context="tei:listBibl[@type='manuscripts']/bibl/label[idno/@subtype='Mingana']">
<sch:assert test="starts-with(., 'Birmingham, Selly Oak
College Library, Mingana Collection')"> This text should
begin "Birmingham, Selly Oak College Library, Mingana
Collection". </sch:assert> </sch:rule>
<sch:rule context="tei:listBibl[@type='manuscripts']/bibl/label[idno/@subtype='Rosen']">
<sch:assert test="starts-with(., 'Rosen and
Forshall')"> This text should begin "Rosen and Forshall".
</sch:assert> </sch:rule>
<sch:rule context="tei:listBibl[@type='manuscripts']/bibl/label[idno/@subtype='SOAH']">
<sch:assert test="starts-with(., 'Homs, Syriac Orthodox
Church, Archdiocese of Homs')"> This text should begin
"Homs, Syriac Orthodox Church, Archdiocese of Homs".
</sch:assert> </sch:rule>
<sch:rule context="tei:listBibl[@type='manuscripts']/bibl/label[idno/@subtype='Sachau']">
<sch:assert test="starts-with(., 'Sachau')"> This text
should begin "Sachau". </sch:assert> </sch:rule>
<sch:rule context="tei:listBibl[@type='manuscripts']/bibl/label[idno/@subtype='Sinai']">
<sch:assert test="starts-with(., "Sinai, St. Catherine's
Monastery")"> This text should begin "Sinai, St.
Catherine's Monastery". </sch:assert>
</sch:rule>
<sch:rule context="tei:listBibl[@type='manuscripts']/bibl/label[idno/@subtype='Yale']">
<sch:assert test="starts-with(., 'Yale University,
Beinecke Library')"> This text should begin "Yale
University, Beinecke Library". </sch:assert>
</sch:rule> |
||||||||||||||||
| Content model |
<content>
<sequence minOccurs="1" maxOccurs="1">
<textNode/>
<elementRef key="idno" minOccurs="0"
maxOccurs="unbounded"/>
<elementRef key="ptr" minOccurs="0"
maxOccurs="1"/>
<elementRef key="title" minOccurs="0"
maxOccurs="1"/>
</sequence>
</content>
⚓ |
||||||||||||||||
| Schema Declaration |
element label
{
tei_att.global.attributes,
attribute type { text }?,
attribute subtype { text }?,
( text, tei_idno*, tei_ptr?, tei_title? )
}⚓ |
||||||||||||||||
| <langUsage> (language usage) describes the languages, sublanguages, registers, dialects, etc. represented within a text. [2.4.2. Language Usage 2.4. The Profile Description 16.3.2. Declarable Elements] | |
| Module | header — NHSL TEI P5 Schema Customization |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.analytic (@ana)) (att.global.change (@change)) (att.global.linking (@corresp)) (att.global.rendition (@rend)) (att.global.responsibility (@resp)) (att.global.source (@source)) |
| Contained by |
header:
profileDesc
|
| May contain |
core:
p
|
| Example | <langUsage> <language ident="fr-CA" usage="60">Québecois</language> <language ident="en-CA" usage="20">Canadian business English</language> <language ident="en-GB" usage="20">British English</language>
</langUsage> |
| Schematron |
<sch:pattern is-a="declarable">
<sch:param name="tde" value="tei:langUsage"/>
</sch:pattern> |
| Content model |
<content>
<elementRef key="p"/>
</content>
⚓ |
| Schema Declaration |
element langUsage { tei_att.global.attributes, tei_p }⚓ |
| <licence> contains information about a licence or other legal agreement applicable to the text. [2.2.4. Publication, Distribution, Licensing, etc.] | |
| Module | header — NHSL TEI P5 Schema Customization |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.analytic (@ana)) (att.global.change (@change)) (att.global.linking (@corresp)) (att.global.rendition (@rend)) (att.global.responsibility (@resp)) (att.global.source (@source)) att.pointing (@target) |
| Contained by |
header:
availability
|
| May contain |
core:
p
|
| Note | The <license> element within the <availability> element is used to specify the Creative Commons CC-BY license under which this record is made available. Some records incorporate information from works under copyright (with permission), a fact which is also indicated in the <license> element. |
| Example | <license target="http://creativecommons.org/licenses/by/3.0/">
<p>Distributed under
a Creative Commons Attribution 3.0 Unported License.</p>
</license> |
| Example | <license target="http://creativecommons.org/licenses/by/3.0/">
<p>Distributed under
a Creative Commons Attribution 3.0 Unported License.</p> <p>This entry incorporates copyrighted
material from the following work(s): <listBibl> <bibl> <ptr target="#bib78-3"/> </bibl> <bibl> <ptr target="#bib78-4"/> </bibl> <bibl> <ptr target="#bib78-5"/> </bibl> </listBibl> <note>used under a Creative
Commons Attribution license <ref target="http://creativecommons.org/licenses/by/3.0/"/>
</note> </p>
</license> |
| Content model |
<content>
<elementRef key="p" maxOccurs="unbounded"/>
</content>
⚓ |
| Schema Declaration |
element licence
{
tei_att.global.attributes,
tei_att.pointing.attributes,
tei_p+
}⚓ |
| <listBibl> (citation list) contains a list of bibliographic citations of any kind. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 16.3.2. Declarable Elements] | |||||||||
| Module | core — NHSL TEI P5 Schema Customization | ||||||||
| Attributes | Attributes att.global (@xml:id,
@n, @xml:lang) (att.global.analytic (@ana)) (att.global.change (@change)) (att.global.linking (@corresp)) (att.global.rendition (@rend)) (att.global.responsibility (@resp)) (att.global.source (@source)) att.cmc (@generatedBy) att.typed (type, @subtype)
|
||||||||
| Contained by | |||||||||
| May contain | |||||||||
| Example | <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> |
||||||||
| Schematron |
<sch:rule context="tei:body//tei:listBibl">
<sch:assert test="tei:head"> This <listBibl>
requires a <head>. </sch:assert>
</sch:rule>
<sch:rule context="tei:body//tei:listBibl">
<sch:assert test="tei:desc"> This <listBibl>
requires a <desc>. </sch:assert>
</sch:rule>
<sch:rule context="tei:body//tei:listBibl">
<sch:assert test="@type"> This <listBibl>
requires a @type attribute. </sch:assert>
</sch:rule> |
||||||||
| Schematron |
<sch:pattern is-a="declarable">
<sch:param name="tde" value="tei:listBibl"/>
</sch:pattern> |
||||||||
| Content model |
<content>
<sequence minOccurs="1" maxOccurs="1">
<elementRef key="head" minOccurs="0"
maxOccurs="1"/>
<elementRef key="desc" minOccurs="0"
maxOccurs="1"/>
<elementRef key="bibl" minOccurs="1"
maxOccurs="unbounded"/>
</sequence>
</content>
⚓ |
||||||||
| Schema Declaration |
element listBibl
{
tei_att.global.attributes,
tei_att.cmc.attributes,
tei_att.typed.attribute.subtype,
attribute type { text }?,
( tei_head?, tei_desc?, tei_bibl+ )
}⚓ |
||||||||
| <listRelation> provides information about relationships identified amongst people, places, and organizations, either informally as prose or as formally expressed relation links. [14.3.2.3. Personal Relationships] | |
| Module | namesdates — NHSL TEI P5 Schema Customization |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.analytic (@ana)) (att.global.change (@change)) (att.global.linking (@corresp)) (att.global.rendition (@rend)) (att.global.responsibility (@resp)) (att.global.source (@source)) |
| Contained by |
core:
bibl
|
| May contain |
namesdates:
relation
|
| Note | 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> |
| Content model |
<content>
<elementRef key="relation" minOccurs="1"
maxOccurs="unbounded"/>
</content>
⚓ |
| Schema Declaration |
element listRelation { tei_att.global.attributes, tei_relation+ }⚓ |
| <name> (name, proper noun) contains a proper noun or noun phrase. [3.6.1. Referring Strings] | |
| Module | core — NHSL TEI P5 Schema Customization |
| Attributes | Attributes att.canonical (@ref) att.global (@xml:id, @n, @xml:lang) (att.global.analytic (@ana)) (att.global.change (@change)) (att.global.linking (@corresp)) (att.global.rendition (@rend)) (att.global.responsibility (@resp)) (att.global.source (@source)) att.typed (@type, @subtype) |
| Contained by |
core:
respStmt
|
| May contain | Character data only |
| Note | 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. |
| Example | <name type="person">Thomas Hoccleve</name>
<name type="place">Villingaholt</name>
<name type="org">Vetus Latina Institut</name>
<name type="person" ref="#HOC001">Occleve</name> |
| Schematron |
<sch:rule context="//tei:teiHeader//tei:name/@ref">
<sch:let name="edsDoc"
value="doc('https://raw.githubusercontent.com/srophe/gaddel/master/documentation/editors.xml')"/>
<sch:let name="eds"
value="$edsDoc//tei:body//@xml:id"/>
<sch:let name="refValues" value="for $i in $eds return
concat('http://syriaca.org/documentation/editors.xml#',
$i)"/> <sch:assert test="every $i in . satisfies $i =
$refValues"> Acceptable values for the @ref attribute on
a <name> element inside the <teiHeader> include:
<sch:value-of select="string-join($refValues, ' |
')"/>. </sch:assert> </sch:rule> |
| Schematron |
<sch:rule context="//tei:teiHeader//tei:name">
<sch:assert test="./@ref">A @ref attribute is required
on the <name> element inside
<teiHeader>.</sch:assert>
</sch:rule> |
| Content model |
<content>
<textNode/>
</content>
⚓ |
| Schema Declaration |
element name
{
tei_att.canonical.attributes,
tei_att.global.attributes,
tei_att.typed.attributes,
text
}⚓ |
| <note> (note) contains a note or annotation. [3.9.1. Notes and Simple Annotation 2.2.6. The Notes Statement 3.12.2.8. Notes and Statement of Language 10.3.5.4. Notes within Entries] | |||||||||||
| Module | core — NHSL TEI P5 Schema Customization | ||||||||||
| Attributes | Attributes att.global (@xml:id,
@n, @xml:lang) (att.global.analytic (@ana)) (att.global.change (@change)) (att.global.linking (@corresp)) (att.global.rendition (@rend)) (att.global.responsibility (@resp)) (att.global.source (@source)) att.pointing (@target)
att.typed (type,
@subtype)
|
||||||||||
| Contained by | |||||||||||
| May contain | |||||||||||
| Note | The <note> element is used for a variety of notes about the entity described in the data. All <note> elements must have an xml:lang attribute that facilitates the display of notes by language in The Srophé Application. A type attribute is required and determines how the note is displayed on the page. Available values for this type attribute are: corrigenda, deprecation, disambiguation, errata, incerta license, and misc. Only certain values are allowed in certain contexts within the document. |
||||||||||
| Example | 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. |
||||||||||
| Schematron |
<sch:rule context="tei:body//tei:noteGrp[@type='abstract']/tei:note">
<sch:assert test="@type='abstract'"> This <note>
must contain a @type attribute with value "abstract".
</sch:assert> </sch:rule>
<sch:rule context="tei:body//tei:noteGrp[@type='content']/tei:note">
<sch:assert test="@type='content'"> This <note>
must contain a @type attribute with value "content".
</sch:assert> </sch:rule>
<sch:rule context="tei:body//tei:noteGrp[@type='disambiguation']/tei:note">
<sch:assert test="@type='disambiguation'"> This
<note> must contain a @type attribute with value
"disambiguation". </sch:assert> </sch:rule>
<sch:rule context="tei:body//tei:noteGrp[@type='exerpts']/tei:note">
<sch:assert test="@type='exerpt'"> This <note>
must contain a @type attribute with value "exerpt".
</sch:assert> </sch:rule>
<sch:rule context="tei:body//tei:noteGrp[@type='explicit']/tei:note">
<sch:assert test="@type='explicit'"> This <note>
must contain a @type attribute with value "explicit".
</sch:assert> </sch:rule>
<sch:rule context="tei:body//tei:noteGrp[@type='incipit']/tei:note">
<sch:assert test="@type='incipit'"> This <note>
must contain a @type attribute with value "incipit".
</sch:assert> </sch:rule>
<sch:rule context="tei:body//tei:noteGrp[@type='prologue']/tei:note">
<sch:assert test="@type='prologue'"> This <note>
must contain a @type attribute with value "prologue".
</sch:assert> </sch:rule>
<sch:rule context="tei:body//tei:noteGrp[@type='scope']/tei:note">
<sch:assert test="@type='scope'"> This <note>
must contain a @type attribute with value "scope".
</sch:assert> </sch:rule>
<sch:rule context="tei:body//tei:noteGrp[@type='versions']/tei:note">
<sch:assert test="@type='version'"> This <note>
must contain a @type attribute with value "version".
</sch:assert> </sch:rule> |
||||||||||
| Schematron | <sch:rule context="
tei:body//tei:note[@type=('excerpt','explicit','incipit','prologue')]">
<sch:assert test="tei:quote and count(*) =
count(tei:quote)"> When <note> has type excerpt,
explicit, incipit, or prologue, it must contain only
<quote> elements. </sch:assert>
</sch:rule> |
||||||||||
| Schematron |
<sch:rule context="tei:bibl/tei:listBibl//tei:note">
<sch:report test="@type"> This <note> element
does not take a @type attribute. </sch:report>
</sch:rule> |
||||||||||
| Schematron |
<sch:rule context="tei:text//tei:note">
<sch:report test="@resp and @source">Only one of the
attributes @resp and @source may be
supplied.</sch:report> </sch:rule> |
||||||||||
| Schematron |
<sch:rule context="tei:text//tei:note[not(tei:quote)]">
<sch:assert test="@resp or @source">One of the
attributes @resp or @source must be
supplied.</sch:assert> </sch:rule> |
||||||||||
| Schematron |
<sch:rule context="tei:note[@type='abstract']">
<sch:let name="series"
value="ancestor::tei:TEI//tei:seriesStmt/tei:idno[@type='URI']"/>
<sch:let name="abstractLangPairs" value="for $i in
parent::element()/tei:note[@type='abstract']/tokenize(@corresp,
' ') return concat($i, '-', @xml:lang)"/>
<sch:assert test="every $i in tokenize(@corresp, ' ')
satisfies $i = $series"> Values allowed on @corresp:
<sch:value-of select="string-join($series, '; ')"/>.
</sch:assert>
<sch:assert test="count($abstractLangPairs) eq
count(distinct-values($abstractLangPairs))"> A series
(see individual values of @corresp) may have only one
abstract per language (see @xml:lang). </sch:assert>
</sch:rule> |
||||||||||
| Schematron |
<sch:rule context="tei:note[@type='abstract'][@xml:lang='en']">
<sch:let name="series"
value="ancestor::tei:TEI//tei:seriesStmt/tei:idno[@type='URI']"/>
<sch:let name="corresps"
value="parent::*/tei:note[@xml:lang='en']/@corresp/tokenize(.,
'\s')"/> <sch:assert test="every $i in $series
satisfies $i = $corresps"> Each series in the header must
have an abstract. As such, each of the following must appear
once as a value on the @corresp attribute of an abstract:
<sch:value-of select="string-join($series, '; ')"/>.
</sch:assert> </sch:rule> |
||||||||||
| Schematron |
<sch:rule context="//tei:body//tei:note">
<sch:assert test="./@xml:lang"> All <note>
elements in the <body> must have an @xml:lang
attribute. </sch:assert> </sch:rule> |
||||||||||
| Content model |
<content>
<sequence minOccurs="1" maxOccurs="1">
<textNode/>
<elementRef key="date" minOccurs="0"
maxOccurs="unbounded"/>
<elementRef key="persName" minOccurs="0"
maxOccurs="unbounded"/>
<elementRef key="placeName" minOccurs="0"
maxOccurs="unbounded"/>
<elementRef key="quote" minOccurs="0"
maxOccurs="1"/>
<elementRef key="ref" minOccurs="0"
maxOccurs="1"/>
<elementRef key="title" minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
</content>
⚓ |
||||||||||
| Schema Declaration |
element note
{
tei_att.global.attributes,
tei_att.pointing.attributes,
tei_att.typed.attribute.subtype,
attribute type
{
"abstract"
| "content"
| "disambiguation"
| "excerpt"
| "explicit"
| "incipit"
| "licence"
| "prologue"
| "scope"
| "version"
}?,
(
text,
tei_date*,
tei_persName*,
tei_placeName*,
tei_quote?,
tei_ref?,
tei_title*
)
}⚓ |
||||||||||
| <noteGrp> (note group) contains a group of notes. [3.9.1.1. Encoding Grouped Notes] | |||||||||
| Module | core — NHSL TEI P5 Schema Customization | ||||||||
| Attributes | Attributes att.global (@xml:id,
@n, @xml:lang) (att.global.analytic (@ana)) (att.global.change (@change)) (att.global.linking (@corresp)) (att.global.rendition (@rend)) (att.global.responsibility (@resp)) (att.global.source (@source)) att.anchoring (@anchored, @targetEnd) att.cmc (@generatedBy)
att.placement (@place) att.pointing (@target)
att.written (@hand) att.typed (type, @subtype)
|
||||||||
| Contained by |
core:
bibl
|
||||||||
| May contain | |||||||||
| Example | In the following example, there are two
notes in different languages, each specifying the content of the
annotation relating to the same fragment of text: <p>(...) tamen reuerendos
dominos archiepiscopum et canonicos Leopolienses necnon
episcopum in duplicibus Quatuortemporibus <noteGrp> <note xml:lang="en">Quatuor Tempora, so called dry
fast days (Wednesday, Friday, and Saturday) falling on
each of the quarters of the year. In the first quarter they
were called Cinerum (following Ash Wednesday), second
Spiritus (following Pentecost), third Crucis (after the
Exaltation of the Holy Cross, September 14th), and Luciae
in the fourth (after the feast of St. Lucia, December
13th). </note> <note xml:lang="pl">Quatuor Tempora, tzw. Suche
dni postne (środa, piątek i sobota) przypadające cztery
razy w roku. W pierwszym kwartale zwały się Cinerum (po
Popielcu), w drugim Spiritus (po Zielonych Świętach), w
trzecim Crucis (po święcie Podwyższenia Krzyża 14
września), w czwartym Luciae (po dniu św. Łucji 13
grudnia). </note>
</noteGrp> totaliter
expediui. </p> |
||||||||
| Content model |
<content>
<sequence minOccurs="1" maxOccurs="1">
<elementRef key="desc" minOccurs="1"
maxOccurs="1"/>
<elementRef key="note" minOccurs="1"
maxOccurs="unbounded"/>
</sequence>
</content>
⚓ |
||||||||
| Schema Declaration |
element noteGrp
{
tei_att.global.attributes,
tei_att.anchoring.attributes,
tei_att.cmc.attributes,
tei_att.placement.attributes,
tei_att.pointing.attributes,
tei_att.typed.attribute.subtype,
tei_att.written.attributes,
attribute type { text },
( tei_desc, tei_note+ )
}⚓ |
||||||||
| <p> (paragraph) marks paragraphs in prose. [3.1. Paragraphs 7.2.6. Speech Contents] | |
| Module | core — NHSL TEI P5 Schema Customization |
| Attributes | Attributesatt.global (xml:id, n, @xml:lang) |
| Contained by | |
| May contain | |
| Note | The <p> element is used for paragraphs of text in various contexts. In the body of a record, the <p> element must have an xml:id attribute. |
| Example | <event type="attestation" xml:id="attestation2567-1" when="0473" srophe:computed-start="0473-01-01" srophe:computed-end="0473-12-31" source="#bib2567-3"
xmlns:srophe="https://srophe.app"> <p xml:lang="en">Attestation of name <foreign xml:lang="syr">ܬܠܢܫܐ</foreign> in <title>Vatican Syriac 160</title>.</p> <link target="#name2567-2 #attestation2567-1"/>
</event> |
| Schematron |
<sch:rule context="//tei:text//tei:p">
<sch:assert test="./@xml:lang">A <p> element in
the text body must have an @xml:lang
attribute.</sch:assert> </sch:rule> |
| Schematron |
<sch:rule context="tei:p">
<sch:report test="(ancestor::tei:ab or ancestor::tei:p)
and not( ancestor::tei:floatingText | 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. </sch:report> </sch:rule> |
| Schematron |
<sch:rule context="tei:l//tei:p">
<sch:assert test="ancestor::tei:floatingText |
parent::tei:figure | parent::tei:note"> Abstract model
violation: Metrical 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.
</sch:assert> </sch:rule> |
| Content model |
<content>
<sequence minOccurs="1" maxOccurs="1">
<elementRef key="listBibl" minOccurs="0"
maxOccurs="1"/>
<elementRef key="note" minOccurs="0"
maxOccurs="unbounded"/>
<elementRef key="ref" minOccurs="0"
maxOccurs="unbounded"/>
<textNode/>
</sequence>
</content>
⚓ |
| Schema Declaration |
element p
{
tei_att.global.attribute.xmllang,
( tei_listBibl?, tei_note*, tei_ref*, text )
}⚓ |
| <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. [14.2.1. Personal Names] | |
| Module | namesdates — NHSL TEI P5 Schema Customization |
| Attributes | Attributes att.cmc (@generatedBy) att.personal (@srophe:tags, @sort) (att.naming (@role) (att.canonical (@ref)) ) att.global (n, @xml:id, @xml:lang) att.global.change (@change) att.global.linking (@corresp) att.global.responsibility (@resp) att.global.source (@source) |
| Contained by | |
| May contain | |
| Example | <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[not(parent::tei:author)]">
<sch:assert test="matches(@ref,
concat('http://syriaca.org/person/', '\d+'))"
role="error"> This <persName> element must take a
@ref attribute with a Syriaca.org person URI which reqires
the form 'http://syriaca.org/person/{\d+}' (where {\d+} is a
number). </sch:assert> </sch:rule> |
| Schematron |
<sch:rule context="//tei:persName/@ref">
<sch:assert test="matches(.,
concat('http://syriaca.org/person/', '\d+'))"
role="error"> The @ref attribute on <persName>
must take a Syriaca.org person URI which reqires the form
'http://syriaca.org/person/{\d+}' (where {\d+} is a number).
</sch:assert> </sch:rule>
<sch:rule context="//tei:persName[ancestor::tei:desc][ancestor::tei:note]">
<sch:assert test="@ref">This <persName> requires
a @ref attribute.</sch:assert>
</sch:rule> |
| Content model |
<content>
<sequence minOccurs="1" maxOccurs="1">
<elementRef key="addName" minOccurs="0"
maxOccurs="unbounded"/>
<elementRef key="forename" minOccurs="0"
maxOccurs="unbounded"/>
<elementRef key="persName" minOccurs="0"
maxOccurs="unbounded"/>
<elementRef key="placeName" minOccurs="0"
maxOccurs="unbounded"/>
<elementRef key="roleName" minOccurs="0"
maxOccurs="unbounded"/>
<elementRef key="surname" minOccurs="0"
maxOccurs="unbounded"/>
<textNode/>
</sequence>
</content>
⚓ |
| Schema Declaration |
element persName
{
tei_att.global.attribute.xmlid,
tei_att.global.attribute.xmllang,
tei_att.global.change.attribute.change,
tei_att.global.linking.attribute.corresp,
tei_att.global.responsibility.attribute.resp,
tei_att.global.source.attribute.source,
tei_att.cmc.attributes,
tei_att.personal.attributes,
(
addName*,
forename*,
tei_persName*,
tei_placeName*,
roleName*,
surname*,
text
)
}⚓ |
| <placeName> (place name) contains an absolute or relative place name. [14.2.3. Place Names] | |
| Module | namesdates — NHSL TEI P5 Schema Customization |
| Attributes | Attributes att.cmc (@generatedBy) att.global (n, @xml:id, @xml:lang) att.global.responsibility (@resp) att.global.source (@source) att.personal (@srophe:tags, @sort) att.canonical (@ref) |
| Contained by | |
| May contain | |
| Example | <placeName> <settlement>Rochester</settlement> <region>New York</region>
</placeName> |
| Example | <placeName> <geogName>Arrochar Alps</geogName> <region>Argylshire</region>
</placeName> |
| Example | <placeName> <measure>10 miles</measure> <offset>Northeast of</offset> <settlement>Attica</settlement>
</placeName> |
| Schematron |
<sch:rule context="//tei:placeName/@ref">
<sch:assert test="matches(.,
concat('http://syriaca.org/place/', '\d+'))"
role="error"> The @ref attribute on <placeName>
must take a Syriaca.org place URI which reqires the form
'http://syriaca.org/place/{\d+}' (where {\d+} is a number).
</sch:assert> </sch:rule>
<sch:rule context="//tei:placeName[ancestor::tei:desc][ancestor::tei:note]">
<sch:assert test="@ref">This <placeName>
requires a @ref attribute.</sch:assert>
</sch:rule> |
| Content model |
<content>
<sequence minOccurs="1" maxOccurs="1">
<elementRef key="persName" minOccurs="0"
maxOccurs="unbounded"/>
<elementRef key="placeName" minOccurs="0"
maxOccurs="unbounded"/>
<textNode/>
</sequence>
</content>
⚓ |
| Schema Declaration |
element placeName
{
tei_att.global.attribute.xmlid,
tei_att.global.attribute.xmllang,
tei_att.global.responsibility.attribute.resp,
tei_att.global.source.attribute.source,
tei_att.cmc.attributes,
tei_att.personal.attribute.srophetags,
tei_att.personal.attribute.sort,
tei_att.canonical.attribute.ref,
( tei_persName*, tei_placeName*, text )
}⚓ |
| <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] | |
| Module | header — NHSL TEI P5 Schema Customization |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.analytic (@ana)) (att.global.change (@change)) (att.global.linking (@corresp)) (att.global.rendition (@rend)) (att.global.responsibility (@resp)) (att.global.source (@source)) |
| Contained by |
header:
teiHeader
|
| May contain |
header:
langUsage
|
| Note | The <profileDesc> contains a <langUsage> element that contains a <p> element. The text of the <p> should read: Languages codes used in this record follow the Syriaca.org guidelines. Documentation available at: http://syriaca.org/documentation/langusage.xml |
| Example | <profileDesc> <langUsage> <p> Languages codes used in this record
follow the Syriaca.org guidelines. Documentation available
at: <ref target="http://syriaca.org/documentation/langusage.xml">http://syriaca.org/documentation/langusage.xml</ref> </p> </langUsage>
</profileDesc> |
| Content model |
<content>
<elementRef key="langUsage" minOccurs="1"
maxOccurs="1"/>
</content>
⚓ |
| Schema Declaration |
element profileDesc { tei_att.global.attributes, tei_langUsage }⚓ |
| <ptr> (pointer) defines a pointer to another location. [3.7. Simple Links and Cross-References 17.1. Links] | |||||||||
| Module | core — NHSL TEI P5 Schema Customization | ||||||||
| Attributes | Attributes att.global (@xml:id,
@n, @xml:lang) (att.global.analytic (@ana)) (att.global.change (@change)) (att.global.linking (@corresp)) (att.global.rendition (@rend)) (att.global.responsibility (@resp)) (att.global.source (@source))
|
||||||||
| Contained by | |||||||||
| May contain | Empty element | ||||||||
| Note | Contained within the <bibl> element is a <ptr> element whose target attribute has the value of a URI pointing to the bibliographic item. This URI must be formatted as follows: 'http://syriaca.org/bibl/{\d+}' (where {\d+} is a number). |
||||||||
| Example |
<ptr target="#p143
#p144"/>
<ptr target="http://www.tei-c.org"/>
<ptr cRef="1.3.4"/>
|
||||||||
| Schematron |
<sch:rule context="//tei:body[not(child::tei:bibl)]//tei:bibl/tei:ptr/@target"
role="warning"> <sch:let name="error" value="."/>
<sch:assert test="matches(.,
'http://syriaca.org/cbss/[A-Z\d]{8}')"> The @target
value: "<sch:value-of select="$error"/>" is not a
Syriaca.org cbss URI. These URIs take the form of
"http://syriaca.org/cbss/[A-Z\d]{8}" where [A-Z\d]{8}
indicates an 8-character alpha-numeric string. In
circumstances where the <ptr> element indicates an
external web address (i.e.
http://pleiades.stoa.org/places/922698), the @target should
indicate the correct URL for that resource and this warning
message should be ignored. </sch:assert>
</sch:rule> |
||||||||
| Schematron |
<sch:rule context="tei:ptr">
<sch:report test="@target and @cRef">Only one of the
attributes @target and @cRef may be supplied on
<sch:name/>.</sch:report>
</sch:rule> |
||||||||
| Content model |
<content>
<empty/>
</content>
⚓ |
||||||||
| Schema Declaration |
element ptr
{
tei_att.global.attributes,
attribute target { list { + } },
empty
}⚓ |
||||||||
| <publicationStmt> (publication statement) groups information concerning the publication or distribution of an electronic or other text. [2.2.4. Publication, Distribution, Licensing, etc. 2.2. The File Description] | |
| Module | header — NHSL TEI P5 Schema Customization |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.analytic (@ana)) (att.global.change (@change)) (att.global.linking (@corresp)) (att.global.rendition (@rend)) (att.global.responsibility (@resp)) (att.global.source (@source)) |
| Contained by |
header:
fileDesc
|
| May contain |
core:
date
header:
authority
availability
idno
|
| Note | The <publicationStmt> is where we identify Syriaca.org as the entity responsible for publishing this information, indicate the date of the most recent edit, and identify the use license (Creative Commons CC-BY). The <publicationStmt> contains requires (in order) the following <authority>, <idno>, <availability>, and <date>. |
| Example | <publicationStmt> <authority>Syriaca.org: The Syriac
Reference Portal</authority> <idno type="URI">http://syriaca.org/place/1027/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>2014-01-14-05:00</date>
</publicationStmt> |
| Content model |
<content>
<sequence minOccurs="1" maxOccurs="1">
<elementRef key="authority"/>
<elementRef key="idno"/>
<elementRef key="availability"/>
<elementRef key="date"/>
</sequence>
</content>
⚓ |
| Schema Declaration |
element publicationStmt
{
tei_att.global.attributes,
( tei_authority, tei_idno, tei_availability, tei_date )
}⚓ |
| <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] | |||||||||||
| Module | core — NHSL TEI P5 Schema Customization | ||||||||||
| Attributes | Attributes att.cmc (@generatedBy)
att.typed (@type, @subtype) att.global
(xml:id, n, @xml:lang)
|
||||||||||
| Contained by |
core:
note
|
||||||||||
| May contain | |||||||||||
| Note | 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> |
||||||||||
| Schematron | |||||||||||
| Content model |
<content>
<sequence minOccurs="1" maxOccurs="1">
<elementRef key="bibl" minOccurs="0"
maxOccurs="unbounded"/>
<elementRef key="foreign" minOccurs="0"
maxOccurs="unbounded"/>
<elementRef key="measure" minOccurs="0"
maxOccurs="unbounded"/>
<elementRef key="offset" minOccurs="0"
maxOccurs="unbounded"/>
<elementRef key="orgName" minOccurs="0"
maxOccurs="unbounded"/>
<elementRef key="persName" minOccurs="0"
maxOccurs="unbounded"/>
<elementRef key="placeName" minOccurs="0"
maxOccurs="unbounded"/>
<elementRef key="title" minOccurs="0"
maxOccurs="unbounded"/>
<textNode/>
</sequence>
</content>
⚓ |
||||||||||
| Schema Declaration |
element quote
{
tei_att.global.attribute.xmllang,
tei_att.cmc.attributes,
tei_att.typed.attributes,
attribute source { list { + } },
(
tei_bibl*,
tei_foreign*,
measure*,
offset*,
orgName*,
tei_persName*,
tei_placeName*,
tei_title*,
text
)
}⚓ |
||||||||||
| <ref> (reference) defines a reference to another location, possibly modified by additional text or comment. [3.7. Simple Links and Cross-References 17.1. Links] | |
| Module | core — NHSL TEI P5 Schema Customization |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.analytic (@ana)) (att.global.change (@change)) (att.global.linking (@corresp)) (att.global.rendition (@rend)) (att.global.responsibility (@resp)) (att.global.source (@source)) att.pointing (@target) |
| Contained by | |
| May contain | Character data only |
| Note | The target and cRef attributes are mutually exclusive. |
| Example | See especially <ref target="http://www.natcorp.ox.ac.uk/Texts/A02.xml#s2">the
second sentence</ref> |
| Example | See also <ref target="#locution">s.v. <term>locution</term>
</ref>. |
| Schematron |
<sch:rule context="tei:ref">
<sch:report test="@target and @cRef">Only one of the
attributes @target and @cRef may be supplied on
<sch:name/>.</sch:report>
</sch:rule> |
| Content model |
<content>
<textNode/>
</content>
⚓ |
| Schema Declaration |
element ref { tei_att.global.attributes, tei_att.pointing.attributes, text }⚓ |
| <relation> (relationship) describes any kind of relationship or linkage amongst a specified group of places, events, persons, objects or other items. [14.3.2.3. Personal Relationships] | |||||||||||||||||||||||||
| Module | namesdates — NHSL TEI P5 Schema Customization | ||||||||||||||||||||||||
| Attributes | Attributes att.datable.w3c (@when, @notBefore, @notAfter, @from, @to) att.typed (@type, @subtype) att.global (n, xml:lang, @xml:id) att.global.analytic (@ana)
att.global.change (@change) att.global.linking (@corresp)
att.global.rendition
(@rend) att.global.responsibility (@resp) att.global.source (@source)
|
||||||||||||||||||||||||
| Contained by |
namesdates:
listRelation
|
||||||||||||||||||||||||
| May contain |
core:
desc
|
||||||||||||||||||||||||
| Note | 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. |
||||||||||||||||||||||||
| Example |
<relation type="social" name="supervisor" active="#p1" passive="#p2
#p3 #p4"/>
This indicates that the person with identifier p1 is
supervisor of persons p2, p3, and p4. |
||||||||||||||||||||||||
| Example |
<relation type="personal" name="friends" mutual="#p2 #p3
#p4"/>
This indicates that p2, p3, and p4 are all friends. |
||||||||||||||||||||||||
| Example |
<relation type="CRM" name="P89_falls_within" active="http://id.clarosnet.org/places/metamorphoses/place/italy-orvieto"
passive="http://id.clarosnet.org/places/metamorphoses/country/IT"/>
This indicates that there is a relation, defined by CIDOC
CRM, between two resources identified by URLs. |
||||||||||||||||||||||||
| Example |
<relation resp="http://viaf.org/viaf/44335536/" ref="http://purl.org/saws/ontology#isVariantOf"
active="http://www.ancientwisdoms.ac.uk/cts/urn:cts:greekLit:tlg3017.Syno298.sawsGrc01:divedition.divsection1.o14.a107"
passive="http://data.perseus.org/citations/urn:cts:greekLit:tlg0031.tlg002.perseus-grc1:9.35"/>
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 |
<sch:rule context="tei:body//tei:relation/@passive">
<sch:let name="IDValues"
value="root(.)//tei:body//tei:bibl/@xml:id"/>
<sch:let name="IDPtrValues" value="for $i in $IDValues
return concat('#', $i)"/> <sch:report test="matches(.,
'\s')"> The @passive attribute may only take one value.
</sch:report> <sch:assert test="starts-with(., '#')
or starts-with(., 'http')"> The @passive attribute must
either point to an existing @xml:id in this document
starting with "#" or point to a URI/URL outside of this
document starting with "http". </sch:assert>
<sch:assert test=" not(starts-with(., '#')) or
substring(.,2) = root(.)//tei:body//tei:bibl/@xml:id ">
This @passive attribute must point to a single @xml:id on a
<bibl> element. Available values include:
<sch:value-of select="string-join($IDPtrValues, ';
')"/>. </sch:assert> </sch:rule> |
||||||||||||||||||||||||
| Schematron |
<sch:rule context="tei:body//tei:relation/@active">
<sch:let name="IDValues"
value="root(.)//tei:body//tei:bibl/@xml:id"/>
<sch:let name="IDPtrValues" value="for $i in $IDValues
return concat('#', $i)"/> <sch:report test="matches(.,
'\s')"> The @active attribute may only take one value.
</sch:report> <sch:assert test="starts-with(., '#')
or starts-with(., 'http')"> The @active attribute must
either point to an existing @xml:id in this document
starting with "#" or point to a URI/URL outside of this
document starting with "http". </sch:assert>
<sch:assert test=" not(starts-with(., '#')) or
substring(.,2) = root(.)//tei:body//tei:bibl/@xml:id ">
This @active attribute must point to a single @xml:id on a
<bibl> element. Available values include:
<sch:value-of select="string-join($IDPtrValues, ';
')"/>. </sch:assert> </sch:rule> |
||||||||||||||||||||||||
| Schematron |
<sch:rule context="tei:body/child::tei:bibl/child::tei:listRelation/tei:relation/@ref">
<sch:report test="matches(., 'dcterms:source')">
"dcterms:source" not allowed here. </sch:report>
</sch:rule>
<sch:rule context="tei:body/child::tei:bibl//tei:bibl//tei:listRelation/tei:relation/@ref">
<sch:assert test="matches(., 'dcterms:source')"> The
only value allowed here is "dcterms:source".
</sch:assert> </sch:rule> |
||||||||||||||||||||||||
| Schematron |
<sch:rule context="tei:relation">
<sch:assert test="@ref or @key or @name">One of the
attributes @name, @ref or @key must be
supplied</sch:assert> </sch:rule> |
||||||||||||||||||||||||
| Schematron |
<sch:rule context="tei:relation">
<sch:report test="@active and @mutual">Only one of the
attributes @active and @mutual may be
supplied</sch:report> </sch:rule> |
||||||||||||||||||||||||
| Schematron |
<sch:rule context="tei:relation">
<sch:report test="@passive and not(@active)">the
attribute @passive may be supplied only if the attribute
@active is supplied</sch:report>
</sch:rule> |
||||||||||||||||||||||||
| Content model |
<content>
<elementRef key="desc" minOccurs="1"
maxOccurs="1"/>
</content>
⚓ |
||||||||||||||||||||||||
| Schema Declaration |
element relation
{
tei_att.datable.w3c.attributes,
tei_att.global.attribute.xmlid,
tei_att.global.analytic.attribute.ana,
tei_att.global.change.attribute.change,
tei_att.global.linking.attribute.corresp,
tei_att.global.rendition.attribute.rend,
tei_att.global.responsibility.attribute.resp,
tei_att.global.source.attribute.source,
tei_att.typed.attributes,
attribute ref { text },
attribute passive { list { + } },
( attribute active { text } | attribute mutual { text }? ),
tei_desc
}⚓ |
||||||||||||||||||||||||
| <resp> (responsibility) contains a phrase describing the nature of a person's intellectual responsibility, or an organization's role in the production or distribution of a 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] | |
| Module | core — NHSL TEI P5 Schema Customization |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.analytic (@ana)) (att.global.change (@change)) (att.global.linking (@corresp)) (att.global.rendition (@rend)) (att.global.responsibility (@resp)) (att.global.source (@source)) |
| Contained by |
core:
respStmt
|
| May contain |
core:
title
character data
|
| Note | 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. |
| Example | <respStmt> <resp ref="http://id.loc.gov/vocabulary/relators/com.html">compiler</resp> <name>Edward Child</name>
</respStmt> |
| Content model |
<content>
<sequence minOccurs="1" maxOccurs="1">
<elementRef key="title" minOccurs="0"
maxOccurs="unbounded"/>
<textNode/>
</sequence>
</content>
⚓ |
| Schema Declaration |
element resp { tei_att.global.attributes, ( tei_title*, text ) }⚓ |
| <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] | |
| Module | core — NHSL TEI P5 Schema Customization |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.analytic (@ana)) (att.global.change (@change)) (att.global.linking (@corresp)) (att.global.rendition (@rend)) (att.global.responsibility (@resp)) (att.global.source (@source)) |
| Contained by |
header:
titleStmt
|
| May contain | |
| Note | Both the editors and other parties who are responsible for the creation of this TEI place record are then identified individually in <respStmt> elements (<resp> stands for "responsibility"). The schema requires the record have at least one <respStmt> which would describe the contribution of the <editor> with the role="creator". Most records will have multiple <respStmt> elements, especially in cases where there were contributions made by persons who do not fall into the available @role values. The contents of the <respStmt> element are the description of the responsibility wrapped in a <resp> element followed by the name of the responsible party contained in a <name> element or the name of the responsible organization in an <orgName> element. The <name> element should take a ref attribute which points to the xml:id of the editor within the "editors.xml" document. Additional participants in the creation of the file, for example by entering Syriac or Arabic text, can be given additional <respStmt> entries. |
| Example | <titleStmt> ... <respStmt> <resp>Data merging, Pleiades and Wikipedia
linking, and XML by</resp> <name ref="http://syriaca.org/documentation/editors.xml#tcarlson">Thomas
A. Carlson</name>
</respStmt> <respStmt> <resp>Wilmshurst index
information entry by</resp> <name ref="http://syriaca.org/documentation/editors.xml#adavis">Anthony
Davis</name> </respStmt>
</titleStmt> |
| Example | <respStmt> <resp>These names were received as a
dataset from E-Ktobe : manuscrits syriaques (<ref target="http://syriac.msscatalog.org/">http://syriac.msscatalog.org/</ref>). Née sur
l’initiative d'André Binggeli (IRHT-CNRS), Françoise
Briquel-Chatonnet (Orient et Méditerranée-CNRS), Muriel
Debié (EPHE) et Alain Desreumaux (Orient et
Méditerranée-CNRS) dans le cadre du programme SYRAB de
l'ANR (Agence Nationale de la Recherche), la base e-ktobe
est actuellement placée sous la responsabilité
scientifique d’André Binggeli et Emilie Villey (Orient et
Méditerranée-CNRS). Liste des collaborateurs contribuant ou
ayant contribué à l’alimentation de la base : Youssef
Dergham (Bibliothèque du patriarcat syro-catholique de
Charfet), Margherita Farina (CNRS, Paris), Simone I. M.
Pratelli (U. de Constance), Flavia Ruani (U. de Gand) et
Eleonora Serra (U. de Pise).</resp> <orgName ref="http://syriac.msscatalog.org/">E-Ktobe
: manuscrits syriaques</orgName>
</respStmt> |
| Content model |
<content>
<sequence minOccurs="1" maxOccurs="1">
<elementRef key="resp"/>
<elementRef key="name"/>
</sequence>
</content>
⚓ |
| Schema Declaration |
element respStmt { tei_att.global.attributes, ( tei_resp, tei_name ) }⚓ |
| <revisionDesc> (revision description) summarizes the revision history for a file. [2.6. The Revision Description 2.1.1. The TEI Header and Its Components] | |||||||
| Module | header — NHSL TEI P5 Schema Customization | ||||||
| Attributes | Attributes att.global (@xml:id,
@n, @xml:lang) (att.global.analytic (@ana)) (att.global.change (@change)) (att.global.linking (@corresp)) (att.global.rendition (@rend)) (att.global.responsibility (@resp)) (att.global.source (@source))
|
||||||
| Contained by |
header:
teiHeader
|
||||||
| May contain |
header:
change
|
||||||
| Note | The <revisionDesc> element is used to include a detailed log of which changes have been made to this file, when, and by whom. The <revisionDesc> should have a status attribute which indicates the publication stage of the file. Possible values for this attribute include: “draft,” “incomplete,” “published,” and “underReview”. Each revision contains a <change> element. |
||||||
| Example | <revisionDesc status="published"> <change who="http://syriaca.org/documentation/editors.xml#wsalesky"
when="2014-06-30-04:00">CHANGED tei:author
element to tei:persName under tei:event element.</change> <change who="http://syriaca.org/documentation/editors.xml#tcarlson"
when="2014-06-12-05:00">ADDED: Yaqut
citation and attestation</change> <change who="http://syriaca.org/documentation/editors.xml#wsalesky"
when="2014-01-14">ADDED: relation element with
shares-name-with attribute for all place headwords that
share names</change>
<change who="http://syriaca.org/documentation/editors.xml#wsalesky"
when="2014-01-14">ADDED: syriaca-computed-start
and syriaca-computed-end attributes for searching</change> <change who="http://syriaca.org/documentation/editors.xml#tcarlson"
when="2013-12-18-05:00">CREATED: place</change>
</revisionDesc> |
||||||
| Content model |
<content>
<elementRef key="change" minOccurs="0"
maxOccurs="unbounded"/>
</content>
⚓ |
||||||
| Schema Declaration |
element revisionDesc
{
tei_att.global.attributes,
attribute status
{
"draft" | "incomplete" | "published" | "uncorrected-draft"
},
tei_change*
}⚓ |
||||||
| <seriesStmt> (series statement) groups information about the series, if any, to which a publication belongs. [2.2.5. The Series Statement 2.2. The File Description] | |
| Module | header — NHSL TEI P5 Schema Customization |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.analytic (@ana)) (att.global.change (@change)) (att.global.linking (@corresp)) (att.global.rendition (@rend)) (att.global.responsibility (@resp)) (att.global.source (@source)) |
| Contained by |
header:
fileDesc
|
| May contain | |
| Example | <seriesStmt> <title>Machine-Readable Texts for the
Study of Indian Literature</title> <respStmt> <resp>ed. by</resp> <name>Jan Gonda</name> </respStmt> <biblScope unit="volume">1.2</biblScope> <idno type="ISSN">0 345
6789</idno>
</seriesStmt> |
| Schematron |
<sch:rule context="//tei:seriesStmt//tei:title[@level='s']">
<sch:assert test=" ./node() = 'A New Handbook of Syriac
Literature' or ./node() = 'Gateway to the Syriac
Saints'"> This <title> element must be "A New
Handbook of Syriac Literature" or "Gateway to the Syriac
Saints". </sch:assert> </sch:rule>
<sch:rule context="//tei:seriesStmt[tei:title = 'A New
Handbook of Syriac Literature']/tei:idno">
<sch:assert test="matches(.,
'http://syriaca.org/nhsl')"> This <idno> element
must contain "http://syriaca.org/nhsl". </sch:assert>
</sch:rule>
<sch:rule context="//tei:seriesStmt[tei:title = 'Gateway
to the Syriac Saints']/tei:idno">
<sch:assert test="matches(.,
'http://syriaca.org/saints')"> This <idno> element
must contain "http://syriaca.org/saints".
</sch:assert> </sch:rule> |
| Schematron |
<sch:rule context="//tei:seriesStmt//tei:title[@level='m']">
<sch:assert test=" ./node() = 'Bibliotheca Hagiographica
Syriaca Electronica' or ./node() = 'A Guide to the Bible in
Syriac' or ./node() = 'Syriac Scientific and Philosophical
Literature'"> This <title> element must be
"Bibliotheca Hagiographica Syriaca Electronica" or "Guide to
the Bible in Syriac" or "Syriac Scientific and Philosophical
Literature". </sch:assert> </sch:rule>
<sch:rule context="//tei:seriesStmt[tei:title =
'Bibliotheca Hagiographica Syriaca
Electronica']/tei:idno"> <sch:assert test="matches(.,
'http://syriaca.org/bhse')"> This <idno> element
must contain "http://syriaca.org/bhse". </sch:assert>
</sch:rule>
<sch:rule context="//tei:seriesStmt[tei:title='Bibliotheca
Hagiographica Syriaca Electronica']">
<sch:assert test="tei:biblScope/@n = '1'"> Requires a
<biblScope> element with @n="1" since "Bibliotheca
Hagiographica Syriaca Electronica" is volume 1 of "A New
Handbook of Syriac Literature". </sch:assert>
</sch:rule>
<sch:rule context="//tei:seriesStmt[tei:title = 'A Guide
to the Bible in Syriac']/tei:idno">
<sch:assert test="matches(.,
'http://syriaca.org/bible')"> This <idno> element
must contain "http://syriaca.org/bible". </sch:assert>
</sch:rule>
<sch:rule context="//tei:seriesStmt[tei:title='A Guide to
the Bible in Syriac']">
<sch:assert test="tei:biblScope/@n = '2'"> Requires a
<biblScope> element with @n="2" since "A Guide to the
Bible in Syriac" is volume 2 of "A New Handbook of Syriac
Literature". </sch:assert>
</sch:rule> |
| Schematron |
<sch:pattern is-a="declarable">
<sch:param name="tde" value="tei:seriesStmt"/>
</sch:pattern> |
| Content model |
<content>
<sequence minOccurs="1" maxOccurs="1">
<elementRef key="title" minOccurs="1"
maxOccurs="1"/>
<elementRef key="editor" minOccurs="1"
maxOccurs="unbounded"/>
<elementRef key="biblScope" minOccurs="0"
maxOccurs="1"/>
<elementRef key="idno" minOccurs="1"
maxOccurs="1"/>
</sequence>
</content>
⚓ |
| Schema Declaration |
element seriesStmt
{
tei_att.global.attributes,
( tei_title, tei_editor+, tei_biblScope?, tei_idno )
}⚓ |
| <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] | |
| Module | header — NHSL TEI P5 Schema Customization |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.analytic (@ana)) (att.global.change (@change)) (att.global.linking (@corresp)) (att.global.rendition (@rend)) (att.global.responsibility (@resp)) (att.global.source (@source)) |
| Contained by |
header:
fileDesc
|
| May contain |
core:
p
|
| Note | The <sourceDesc> element is a mandatory component of the <fileDesc> element. Its purpose is to indicate the source of the text which is encoded in this file, for library cataloging among other uses. For Syriaca.org data that is not marking up text from a source, the option of indicating that this TEI is "born digital," should be used. For text encoding projects |
| Example | <sourceDesc xml:id="sourceDesc1"> <biblStruct> <monogr> <editor> <forename>G. H.</forename> <surname>Gwilliam</surname> </editor> <editor> <forename>J.</forename> <surname>Pinkerton</surname> </editor> <editor> <forename>John</forename> <surname>Gwynn</surname> </editor> <title level="m">The New Testament in Syriac [<foreign xml:lang="syr">ܕܝܬܝܩܐ ܚܕܬܐ ܕܡܪܢ
ܝܫܘܥ ܡܫܝܚܐ</foreign>]</title> <idno type="URI">http://syriaca.org/bibl/2491</idno> <idno type="zotero">1049</idno> <idno type="URI">http://zotero.org/groups/392292/items/N4KFR4M9</idno> <ref target="https://archive.org/details/newtestamentinsy00lond"/>
<imprint>
<pubPlace>London</pubPlace> <publisher>British and Foreign Bible
Society</publisher>
<date>1905</date> </imprint> </monogr> </biblStruct>
</sourceDesc> |
| Example | <sourceDesc> <biblStruct> <monogr> <title level="m">Gorgias Encyclopedic Dictionary of
the Syriac Heritage</title> <editor>Sebastian P. Brock</editor> <editor>Aaron M. Butts</editor> <editor>George A.
Kiraz</editor>
<editor>Lucas Van
Rompay</editor>
<imprint>
<pubPlace>Piscataway, N.J.</pubPlace> <publisher>Gorgias Press
for Beth Mardutho: The Syriac Institute</publisher> <date>2011</date> <note>Copyright ©2011 by Beth Mardutho:
The Syriac Institute</note> <note>ISBN: 978-1-59333-714-8</note> </imprint> </monogr> </biblStruct>
</sourceDesc> |
| Schematron |
<sch:pattern is-a="declarable">
<sch:param name="tde" value="tei:sourceDesc"/>
</sch:pattern> |
| Content model |
<content>
<elementRef key="p" minOccurs="1"
maxOccurs="1"/>
</content>
⚓ |
| Schema Declaration |
element sourceDesc { tei_att.global.attributes, tei_p }⚓ |
| <sponsor> (sponsor) specifies the name of a sponsoring organization or institution. [2.2.1. The Title Statement] | |
| Module | header — NHSL TEI P5 Schema Customization |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.analytic (@ana)) (att.global.change (@change)) (att.global.linking (@corresp)) (att.global.rendition (@rend)) (att.global.responsibility (@resp)) (att.global.source (@source)) |
| Contained by |
header:
titleStmt
|
| May contain | Character data only |
| Note | The TEI guidelines recommend that the <titleStmt> element also indicate who is responsible for this TEI file. Since <author> is typically used for the author of a print or manuscript text which was then encoded in TEI, we avoid the use of the <author> element. Instead, we identify Syriaca.org as the sponsoring institution, |
| Example | <titleStmt> ... <sponsor>Syriaca.org: The Syriac Reference
Portal</sponsor> ...
</titleStmt> |
| Content model |
<content>
<textNode/>
</content>
⚓ |
| Schema Declaration |
element sponsor { tei_att.global.attributes, text }⚓ |
| <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] | |
| Module | header — NHSL TEI P5 Schema Customization |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.analytic (@ana)) (att.global.change (@change)) (att.global.linking (@corresp)) (att.global.rendition (@rend)) (att.global.responsibility (@resp)) (att.global.source (@source)) |
| Contained by |
header:
classDecl
|
| May contain |
header:
category
|
| Note | The <taxonomy> contains one or more taxonomies defining any classificatory codes used elsewhere in the text. There are various tags which Syriaca.org uses to mark elements for a variety of purposes. Syriaca.org’s preferred name forms are tagged with "syriaca-headword", for example. |
| Example | <classDecl> <taxonomy> <category xml:id="syriaca-headword"> <catDesc>The name used by
Syriaca.org for document titles, citation, and
disambiguation. These names have been created according to
the Syriac.org guidelines for headwords: <ref target="http://syriaca.org/documentation/headwords.html">http://syriaca.org/documentation/headwords.html</ref>.</catDesc> </category> </taxonomy>
</classDecl> |
| Content model |
<content>
<elementRef key="category" minOccurs="1"
maxOccurs="unbounded"/>
</content>
⚓ |
| Schema Declaration |
element taxonomy { tei_att.global.attributes, tei_category+ }⚓ |
| <teiHeader> (TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources. [2.1.1. The TEI Header and Its Components 16.1. Varieties of Composite Text] | |
| Module | header — NHSL TEI P5 Schema Customization |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.analytic (@ana)) (att.global.change (@change)) (att.global.linking (@corresp)) (att.global.rendition (@rend)) (att.global.responsibility (@resp)) (att.global.source (@source)) |
| Contained by |
textstructure:
TEI
|
| May contain |
header:
encodingDesc
fileDesc
profileDesc
revisionDesc
|
| Note | Every <teiHeader> element contains a <fileDesc> element (information about the creation of a file), an <encodingDesc> element (editorial rules), a <profileDesc> element (non-bibliographic aspects of a text), and a <revisionDesc> element (history of revisions). |
| 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> |
| Content model |
<content>
<sequence minOccurs="1" maxOccurs="1">
<elementRef key="fileDesc" minOccurs="1"
maxOccurs="1"/>
<elementRef key="encodingDesc"
minOccurs="1" maxOccurs="1"/>
<elementRef key="profileDesc"
minOccurs="1" maxOccurs="1"/>
<elementRef key="revisionDesc"
minOccurs="1" maxOccurs="1"/>
</sequence>
</content>
⚓ |
| Schema Declaration |
element teiHeader
{
tei_att.global.attributes,
( tei_fileDesc, tei_encodingDesc, tei_profileDesc, tei_revisionDesc )
}⚓ |
| <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 16.1. Varieties of Composite Text] | |
| Module | textstructure — NHSL TEI P5 Schema Customization |
| Member of | |
| Contained by |
textstructure:
TEI
|
| May contain |
textstructure:
body
|
| Note | The data of the record is contained within the <text> element. The Srophé App requires that all source attributes inside the <text> element point to an xml:id attribute on a <bibl> or <listBibl> element. |
| Example | <text
xmlns:srophe="https://srophe.app"> <body> <listPlace> <place type="diocese"> <placeName resp="http://syriaca.org" xml:id="name3053-1" xml:lang="en" srophe:tags="#syriaca-headword">Arethusa</placeName> <placeName resp="http://syriaca.org" xml:id="name3053-2" xml:lang="syr" srophe:tags="#syriaca-headword">ܐܪܝܣܬܢ</placeName> <placeName xml:id="name3053-3" xml:lang="en" source="#bib3053-1">Arethusa</placeName> <placeName xml:id="name3053-4" xml:lang="syr" source="#bib3053-2">ܐܪܝܣܬܢ</placeName> <desc type="abstract" xml:id="abstract3053-1" xml:lang="en">The diocese associated with
the city of Arethusa</desc> <state resp="http://syriaca.org" type="existence"/>
<idno type="URI">http://syriaca.org/place/3053</idno> <bibl xml:id="bib3053-1"> <ptr target="http://syriaca.org/bibl/668"/>
<citedRange unit="p">73</citedRange> </bibl> <bibl xml:id="bib3053-2"> <ptr target="http://syriaca.org/bibl/666"/>
<citedRange unit="p">81</citedRange> </bibl> </place> </listPlace> </body>
</text> |
| Schematron |
<sch:rule context="//tei:text">
<sch:assert test="count(.//@source) ge 1">At least one
descendent element of <text> must have a @source
attribute (@source attributes point to the @xml:id on a
<bibl> or <listBibl>).</sch:assert>
</sch:rule> |
| Content model |
<content>
<elementRef key="body" minOccurs="1"
maxOccurs="1"/>
</content>
⚓ |
| Schema Declaration |
element text { tei_body }⚓ |
| <textLang> (text language) describes the languages and writing systems identified within the bibliographic work being described, rather than its description. [3.12.2.4. Imprint, Size of a Document, and Reprint Information 11.6.6. Languages and Writing Systems] | |||||||||||||
| Module | core — NHSL TEI P5 Schema Customization | ||||||||||||
| Attributes | Attributes att.global (@xml:id,
@n, @xml:lang) (att.global.analytic (@ana)) (att.global.change (@change)) (att.global.linking (@corresp)) (att.global.rendition (@rend)) (att.global.responsibility (@resp)) (att.global.source (@source))
|
||||||||||||
| Contained by |
core:
bibl
|
||||||||||||
| May contain | Empty element | ||||||||||||
| Note | 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> |
||||||||||||
| Content model |
<content>
<empty/>
</content>
⚓ |
||||||||||||
| Schema Declaration |
element textLang
{
tei_att.global.attributes,
attribute mainLang
{
"ar"
| "ar-Syrc"
| "ar-Syre"
| "ar-Syrj"
| "ar-Syrn"
| "cop"
| "cu"
| "de"
| "el"
| "en"
| "es"
| "fr"
| "gez"
| "grc"
| "hy"
| "it"
| "ka"
| "la"
| "mal"
| "mal-Syrc"
| "mal-Syre"
| "mal-Syrj"
| "mal-Syrn"
| "nl"
| "pt"
| "ru"
| "syr"
| "syr-Syre"
| "syr-Syrj"
| "syr-Syrn"
| "syr-pal"
| "syr-x-syrm"
| "sog"
| "tr"
}?,
attribute otherLangs
{
"ar"
| "ar-Syrc"
| "ar-Syre"
| "ar-Syrj"
| "ar-Syrn"
| "cop"
| "cu"
| "de"
| "el"
| "en"
| "es"
| "fr"
| "gez"
| "grc"
| "hy"
| "it"
| "ka"
| "la"
| "mal"
| "mal-Syrc"
| "mal-Syre"
| "mal-Syrj"
| "mal-Syrn"
| "nl"
| "pt"
| "ru"
| "syr"
| "syr-Syre"
| "syr-Syrj"
| "syr-Syrn"
| "syr-x-syrm"
| "sog"
| "tr"
}?,
empty
}⚓ |
||||||||||||
| <title> (title) contains a title for any kind of work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.5. The Series Statement] | |||||||||||||||||||||||||||
| Module | core — NHSL TEI P5 Schema Customization | ||||||||||||||||||||||||||
| Attributes | Attributes att.global (@xml:id,
@n, @xml:lang) (att.global.analytic (@ana)) (att.global.change (@change)) (att.global.linking (@corresp)) (att.global.rendition (@rend)) (att.global.responsibility (@resp)) (att.global.source (@source)) att.personal (srophe:tags, @sort) att.naming
(@role) att.canonical (@ref)
|
||||||||||||||||||||||||||
| Contained by | |||||||||||||||||||||||||||
| May contain |
core:
foreign
character data
|
||||||||||||||||||||||||||
| Note | 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 xml:id="name1-1" xml:lang="en" srophe:tags="#syriaca-headword"
xmlns:srophe="https://srophe.app">Genesis
(Peshitta Version)</title>
<title xml:id="name1-2" xml:lang="syr" srophe:tags="#syriaca-headword" source="#bib1-1">ܣܦܪܐ ܕܒܪܝܫܝܬ</title>
<title xml:id="name1-3" xml:lang="syr" source="#bib1-1">ܣܦܪܐ ܕܒܪܝܬܐ</title>
<title xml:id="name1-4" xml:lang="en" type="abbreviation" srophe:tags="#canonical" source="#bib1-9">Gen</title>
<title xml:id="name1-5" xml:lang="en" source="#bib1-9">Genesis</title>
<title xml:id="name1-6" xml:lang="syr" source="#bib1-1">ܐܣ̣ܬܝܟ ܣܦ̣ܪܐ ܗܢܐ ܩܕܡܝܐ
ܕܐܘܪܝܬܐ ܒܦ̈ܬܓܡܐ ܐܪ̈ܒܥܐ ܐܠܦ̈ܝܢ ܘܚܡܫ ܡ̈ܠܐ ܘܬܫܥܐ ܕܒܨ̈ܚܚܐ
ܠ̅ܕ̅.</title> |
||||||||||||||||||||||||||
| Example | <title level="a" xml:lang="en">Edessa — <foreign xml:lang="syr">ܐܘܪܗܝ</foreign>
</title> |
||||||||||||||||||||||||||
| Example | <title level="m" xml:lang="en">The Syriac Gazetteer</title> |
||||||||||||||||||||||||||
| Schematron |
<sch:rule context="tei:body/child::tei:bibl/child::tei:title">
<sch:assert test="@xml:lang"> This <title> must
have an @xml:lang attribute. </sch:assert>
<sch:assert test="@source or @resp"> The <title>
element for the main work <bibl> must have either a
@source attribute or a @resp attribute. </sch:assert>
</sch:rule> |
||||||||||||||||||||||||||
| Schematron |
<sch:rule context="//tei:text//tei:bibl/tei:title">
<sch:assert test="./@xml:lang or ./contains(., 'http://')
or ./contains(., 'https://')">A <title> element in
a <bibl> element within the text body must have an
@xml:lang attribute unless the content of the text node is a
URL (i.e. contains "http://" or "https://").
</sch:assert> </sch:rule> |
||||||||||||||||||||||||||
| Schematron |
<sch:rule context="//tei:titleStmt/tei:title">
<sch:assert test="matches(@level, 'a')">A
<title> element of @level="a" is the only title
allowed in the <titleStmt>.</sch:assert>
</sch:rule> |
||||||||||||||||||||||||||
| Schematron |
<sch:rule context="//tei:seriesStmt//tei:title">
<sch:assert test="matches(@level, 'm') or matches(@level,
's')">Only <title> elements of @level="m" or "s"
are allowed in the <seriesStmt>. </sch:assert>
</sch:rule> |
||||||||||||||||||||||||||
| Schematron |
<sch:rule context="//tei:text//tei:desc//tei:title/@ref |
//tei:text//tei:note//tei:title/@ref">
<sch:assert test=" matches(.,
'^http://syriaca\.org/work/\d+$') or matches(.,
'^http://syriaca\.org/cbss/[0-9A-Z]+$') "> This @ref
attribute must take either a Syriaca.org work URI or a
Comprehensive Bibliography of Syriac Studies URI. For a work
URI, the form is "http://syriaca.org/work/{\d+$} where
{\d+$} is a number. For a bibliography URI, the form is
"http://syriaca.org/cbss/{0-9A-Z} where {0-9A-Z} is a string
made up of numbers and capital letters. In both cases these
@ref values should point to URIs for specific work or
bibliography items. </sch:assert> </sch:rule>
<sch:rule context="//tei:text//tei:desc//tei:title |
//tei:text//tei:note//tei:title">
<sch:report test="tei:ptr"> A <ptr> element is
not allowed as child of <title>. Instead use a @target
attribute. </sch:report> </sch:rule> |
||||||||||||||||||||||||||
| Content model |
<content>
<sequence minOccurs="1" maxOccurs="1">
<textNode/>
<elementRef key="foreign" minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
</content>
⚓ |
||||||||||||||||||||||||||
| Schema Declaration |
element title
{
tei_att.global.attributes,
tei_att.personal.attribute.sort,
tei_att.naming.attribute.role,
tei_att.canonical.attribute.ref,
attribute srophe:tags
{
"#anonymous-description"
| "#canonical"
| "#ektobe-headword"
| "#syriaca-headword"
}?,
attribute type
{
"abbreviation" | "final-rubric" | "initial-rubric" | "shelfmark"
}?,
attribute level { "a" | "j" | "s" | "m" }?,
( text, tei_foreign* )
}⚓ |
||||||||||||||||||||||||||
| <titleStmt> (title statement) groups information about the title of a work and those responsible for its content. [2.2.1. The Title Statement 2.2. The File Description] | |
| Module | header — NHSL TEI P5 Schema Customization |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.analytic (@ana)) (att.global.change (@change)) (att.global.linking (@corresp)) (att.global.rendition (@rend)) (att.global.responsibility (@resp)) (att.global.source (@source)) |
| Contained by |
header:
fileDesc
|
| May contain | |
| Note | Each <titleStmt> element contains (in order) one or more <title> elements, optional <sponsor> elements, optional <funder> elements, optional <principal> elements, one or more <sourceDesc> elements, and optional <respStmt> elements. |
| Example | <titleStmt> <title level="a" xml:lang="en">Van</title> <sponsor>Syriaca.org: The Syriac Reference
Portal</sponsor>
<funder>The National
Endowment for the Humanities</funder> <funder>The International Balzan Prize
Foundation</funder>
<editor role="creator" ref="http://syriaca.org/documentation/editors.xml#tcarlson">Thomas
A. Carlson</editor>
<respStmt> <resp>Data merging,
Pleiades and Wikipedia linking, and XML by</resp> <name ref="http://syriaca.org/documentation/editors.xml#tcarlson">Thomas
A. Carlson</name>
</respStmt> <respStmt> <resp>Wilmshurst index
information entry by</resp> <name ref="http://syriaca.org/documentation/editors.xml#adavis">Anthony
Davis</name> </respStmt>
</titleStmt> |
| Content model |
<content>
<sequence minOccurs="1" maxOccurs="1">
<elementRef key="title" minOccurs="1"
maxOccurs="unbounded"/>
<elementRef key="sponsor" minOccurs="1"
maxOccurs="unbounded"/>
<elementRef key="funder" minOccurs="0"
maxOccurs="unbounded"/>
<elementRef key="editor" minOccurs="1"
maxOccurs="unbounded"/>
<elementRef key="respStmt" minOccurs="1"
maxOccurs="unbounded"/>
</sequence>
</content>
⚓ |
| Schema Declaration |
element titleStmt
{
tei_att.global.attributes,
( tei_title+, tei_sponsor+, tei_funder*, tei_editor+, tei_respStmt+ )
}⚓ |
| model.resource groups separate elements which constitute the content of a digital resource, as opposed to its metadata. | |
| Module | tei — NHSL TEI P5 Schema Customization |
| Used by | |
| Members | text |
| att.anchoring (anchoring) provides attributes for use on annotations, e.g. notes and groups of notes describing the existence and position of an anchor for annotations. | |||||||||||||||||||
| Module | tei — NHSL TEI P5 Schema Customization | ||||||||||||||||||
| Members | noteGrp | ||||||||||||||||||
| Attributes | Attributes
|
||||||||||||||||||
| Example | <p>(...) tamen reuerendos dominos
archiepiscopum et canonicos Leopolienses necnon episcopum in
duplicibus Quatuortemporibus<anchor xml:id="A55234"/> totaliter
expediui...</p>
<noteGrp targetEnd="#A55234"> <note xml:lang="en"> Quatuor Tempora, so called
dry fast days. </note>
<note xml:lang="pl"> Quatuor Tempora, tzw. Suche
dni postne. </note>
</noteGrp> |
||||||||||||||||||
| att.calendarSystem provides attributes for indicating calendar systems to which a date belongs. | |||||||||||||||
| Module | tei — NHSL TEI P5 Schema Customization | ||||||||||||||
| Members | date | ||||||||||||||
| Attributes | Attributes
|
||||||||||||||
| att.canonical provides 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. | |||||||||||
| Module | tei — NHSL TEI P5 Schema Customization | ||||||||||
| Members | att.naming[att.personal[persName placeName title] author editor] name relation | ||||||||||
| Attributes | Attributes
|
||||||||||
| Example | In this contrived example, a canonical
reference to the same organisation is provided in four different
ways. <author n="1"> <name ref="http://nzetc.victoria.ac.nz/tm/scholarly/name-427308.html"
type="organisation">New Zealand Parliament,
Legislative Council</name>
</author> <author n="2"> <name ref="nzvn:427308" type="organisation">New Zealand Parliament,
Legislative Council</name>
</author> <author n="3"> <name ref="./named_entities.xml#o427308" type="organisation">New Zealand Parliament,
Legislative Council</name>
</author> <author n="4"> <name key="name-427308" type="organisation">New Zealand Parliament,
Legislative Council</name>
</author> The first
presumes the availability of an internet connection and a
processor that can resolve a URI (most can). The second
requires, in addition, a <prefixDef> that declares how the
nzvm prefix should be interpreted. The third
does not require an internet connection, but does require that a
file named named_entities.xml be in
the same directory as the TEI document. The fourth requires that
an entire external system for key resolution be available. |
||||||||||
| Note | The key attribute is more flexible and general-purpose, but its use in interchange requires that documentation about how the key is to be resolved be sent to the recipient of the TEI document. In contrast values of the ref attribute are resolved using the widely accepted protocols for a URI, and thus less documentation, if any, is likely required by the recipient in data interchange. These guidelines provide no semantic basis or suggested precedence when both key and ref are provided. For this reason simultaneous use of both is not recommended unless documentation explaining the use is provided, probably in an ODD customization, for interchange. |
||||||||||
| att.cmc (computer-mediated communication) provides attributes categorizing how the element content was created in a CMC environment. | |||||||||||||||||||||
| Module | tei — NHSL TEI P5 Schema Customization | ||||||||||||||||||||
| Members | head listBibl noteGrp persName placeName quote | ||||||||||||||||||||
| Attributes | Attributes
|
||||||||||||||||||||
| att.datable provides attributes for normalization of elements that contain dates, times, or datable events. | |||||||||||||
| Module | tei — NHSL TEI P5 Schema Customization | ||||||||||||
| Members | author change date | ||||||||||||
| Attributes | Attributes att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod) att.datable.w3c (@when,
@notBefore, @notAfter, @from, @to)
|
||||||||||||
| 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. |
||||||||||||
| att.datable.custom provides 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). | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| Module | namesdates — NHSL TEI P5 Schema Customization | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Members | att.datable[author change date] | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Attributes | Attributes
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
| att.datable.w3c provides attributes for normalization of elements that contain datable events conforming to the W3C XML Schema Part 2: Datatypes Second Edition. | |||||||||||||||||||||||||||||||||||||
| Module | tei — NHSL TEI P5 Schema Customization | ||||||||||||||||||||||||||||||||||||
| Members | att.datable[author change date] relation | ||||||||||||||||||||||||||||||||||||
| Attributes | Attributes
|
||||||||||||||||||||||||||||||||||||
| 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 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. |
||||||||||||||||||||||||||||||||||||
| att.global provides attributes common to all elements in the TEI encoding scheme. | |||||||||||||||||||||||||||||
| Module | tei — NHSL TEI P5 Schema Customization | ||||||||||||||||||||||||||||
| Members | TEI author authority availability bibl biblScope body catDesc category change citedRange classDecl date desc edition editionStmt editorialDecl encodingDesc fileDesc foreign funder head idno interpretation label langUsage licence listBibl listRelation name note noteGrp p persName placeName profileDesc ptr publicationStmt quote ref relation resp respStmt revisionDesc seriesStmt sourceDesc sponsor taxonomy teiHeader textLang title titleStmt | ||||||||||||||||||||||||||||
| Attributes | Attributes att.global.analytic (@ana) att.global.change (@change) att.global.linking (@corresp) att.global.rendition (@rend) att.global.responsibility (@resp) att.global.source (@source)
|
||||||||||||||||||||||||||||
| att.global.analytic provides additional global attributes for associating specific analyses or interpretations with appropriate portions of a text. | |||||||||
| Module | analysis — NHSL TEI P5 Schema Customization | ||||||||
| Members | att.global[TEI author authority availability bibl biblScope body catDesc category change citedRange classDecl date desc edition editionStmt editorialDecl encodingDesc fileDesc foreign funder head idno interpretation label langUsage licence listBibl listRelation name note noteGrp p persName placeName profileDesc ptr publicationStmt quote ref relation resp respStmt revisionDesc seriesStmt sourceDesc sponsor taxonomy teiHeader textLang title titleStmt] | ||||||||
| Attributes | Attributes
|
||||||||
| att.global.change provides attributes allowing its member elements to specify one or more states or revision campaigns with which they are associated. | |||||||
| Module | transcr — NHSL TEI P5 Schema Customization | ||||||
| Members | att.global[TEI author authority availability bibl biblScope body catDesc category change citedRange classDecl date desc edition editionStmt editorialDecl encodingDesc fileDesc foreign funder head idno interpretation label langUsage licence listBibl listRelation name note noteGrp p persName placeName profileDesc ptr publicationStmt quote ref relation resp respStmt revisionDesc seriesStmt sourceDesc sponsor taxonomy teiHeader textLang title titleStmt] | ||||||
| Attributes | Attributes
|
||||||
| Schematron |
<sch:rule context="//@change">
<sch:let name="changeIDs"
value="//tei:teiHeader//tei:change/@xml:id"/>
<sch:let name="changeIDpointers" value="for $i in
$changeIDs return concat('#', $i)"/>
<sch:assert test=" every $i in tokenize(., ' ') satisfies
$i = $changeIDpointers"> This @change attribute can
contain one or more of the following
<sch:value-of select="$changeIDpointers"/>.
</sch:assert> </sch:rule> |
||||||
| att.global.linking provides a set of attributes for hypertextual linking. | |||||||||||
| Module | linking — NHSL TEI P5 Schema Customization | ||||||||||
| Members | att.global[TEI author authority availability bibl biblScope body catDesc category change citedRange classDecl date desc edition editionStmt editorialDecl encodingDesc fileDesc foreign funder head idno interpretation label langUsage licence listBibl listRelation name note noteGrp p persName placeName profileDesc ptr publicationStmt quote ref relation resp respStmt revisionDesc seriesStmt sourceDesc sponsor taxonomy teiHeader textLang title titleStmt] | ||||||||||
| Attributes | Attributes
|
||||||||||
| att.global.rendition provides rendering attributes common to all elements in the TEI encoding scheme. | |||||||||||
| Module | tei — NHSL TEI P5 Schema Customization | ||||||||||
| Members | att.global[TEI author authority availability bibl biblScope body catDesc category change citedRange classDecl date desc edition editionStmt editorialDecl encodingDesc fileDesc foreign funder head idno interpretation label langUsage licence listBibl listRelation name note noteGrp p persName placeName profileDesc ptr publicationStmt quote ref relation resp respStmt revisionDesc seriesStmt sourceDesc sponsor taxonomy teiHeader textLang title titleStmt] | ||||||||||
| Attributes | Attributes
|
||||||||||
| Note | These guidelines provide no semantic basis or suggested precedence when both rend and rendition are provided. For this reason simultaneous use of both is not recommended for interchange unless documentation explaining the use is provided, probably in an ODD customization. |
||||||||||
| att.global.responsibility provides attributes indicating the agent responsible for some aspect of the text, the markup or something asserted by the markup, and the degree of certainty associated with it. | |||||||||||
| Module | tei — NHSL TEI P5 Schema Customization | ||||||||||
| Members | att.global[TEI author authority availability bibl biblScope body catDesc category change citedRange classDecl date desc edition editionStmt editorialDecl encodingDesc fileDesc foreign funder head idno interpretation label langUsage licence listBibl listRelation name note noteGrp p persName placeName profileDesc ptr publicationStmt quote ref relation resp respStmt revisionDesc seriesStmt sourceDesc sponsor taxonomy teiHeader textLang title titleStmt] | ||||||||||
| Attributes | Attributes
|
||||||||||
| 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. |
||||||||||
| Example | <lg> <l>Punkes, Panders, baſe extortionizing
sla<choice> <sic>n</sic> <corr resp="#JENS1_transcriber">u</corr> </choice>es,</l>
</lg>
<respStmt xml:id="JENS1_transcriber"> <resp when="2014">Transcriber</resp> <name>Janelle Jenstad</name>
</respStmt> |
||||||||||
| att.global.source provides attributes used by elements to point to an external source. | |||||||||||
| Module | tei — NHSL TEI P5 Schema Customization | ||||||||||
| Members | att.global[TEI author authority availability bibl biblScope body catDesc category change citedRange classDecl date desc edition editionStmt editorialDecl encodingDesc fileDesc foreign funder head idno interpretation label langUsage licence listBibl listRelation name note noteGrp p persName placeName profileDesc ptr publicationStmt quote ref relation resp respStmt revisionDesc seriesStmt sourceDesc sponsor taxonomy teiHeader textLang title titleStmt] editor | ||||||||||
| Attributes | Attributes
|
||||||||||
| Schematron |
<sch:rule context="//@source">
<sch:let name="biblIDs"
value="//tei:text//tei:bibl/@xml:id"/>
<sch:let name="biblIDpointers" value="for $i in $biblIDs
return concat('#', $i)"/> <sch:assert test=" every $i
in tokenize(., ' ') satisfies $i = $biblIDpointers"> This
@source attribute can contain one or more of the following
<sch:value-of select="$biblIDpointers"/>.
</sch:assert> </sch:rule> |
||||||||||
| Schematron |
<sch:rule context="tei:*[@source]">
<sch:let name="srcs" value="tokenize(
normalize-space(@source),' ')"/> <sch:report test="(
self::tei:classRef | self::tei:dataRef |
self::tei:elementRef | self::tei:macroRef |
self::tei:moduleRef | self::tei:schemaSpec ) and
$srcs[2]"> When used on a schema description element
(like <sch:value-of select="name(.)"/>), the @source
attribute should have only 1 value. (This one has
<sch:value-of select="count($srcs)"/>.)
</sch:report> </sch:rule> |
||||||||||
| 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"/>
Create a schema using components taken from the file mycompiledODD.xml. |
||||||||||
| att.naming provides attributes common to elements which refer to named persons, places, organizations etc. | |||||||
| Module | tei — NHSL TEI P5 Schema Customization | ||||||
| Members | att.personal[persName placeName title] author editor | ||||||
| Attributes | Attributes att.canonical (@ref)
|
||||||
| 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. | |||||||||||||
| Module | tei — NHSL TEI P5 Schema Customization | ||||||||||||
| Members | persName placeName title | ||||||||||||
| Attributes | Attributes att.naming (@role) (att.canonical (@ref))
|
||||||||||||
| att.placement provides attributes for describing where on the source page or object a textual element appears. | |||||||||||||
| Module | tei — NHSL TEI P5 Schema Customization | ||||||||||||
| Members | head noteGrp | ||||||||||||
| Attributes | Attributes
|
||||||||||||
| att.pointing provides a set of attributes used by all elements which point to other elements by means of one or more URI references. | |||||||||
| Module | tei — NHSL TEI P5 Schema Customization | ||||||||
| Members | citedRange licence note noteGrp ptr ref | ||||||||
| Attributes | Attributes
|
||||||||
| Schematron |
<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> |
||||||||
| att.typed provides attributes that can be used to classify or subclassify elements in any way. | |||||||||||||||||||
| Module | tei — NHSL TEI P5 Schema Customization | ||||||||||||||||||
| Members | bibl change date desc head idno label listBibl name note noteGrp quote relation | ||||||||||||||||||
| Attributes | Attributes
|
||||||||||||||||||
| 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 24.3.1.3. Modification of Attribute and Attribute Value Lists . |
||||||||||||||||||
| att.written provides attributes to indicate the hand in which the content of an element was written in the source being transcribed. | |||||||
| Module | tei — NHSL TEI P5 Schema Customization | ||||||
| Members | head noteGrp | ||||||
| Attributes | Attributes
|
||||||
| teidata.count defines the range of attribute values used for a non-negative integer value used as a count. | |
| Module | tei — NHSL TEI P5 Schema Customization |
| Used by | |
| Content model |
<content>
<dataRef name="nonNegativeInteger"/>
</content>
⚓ |
| Declaration | tei_teidata.count = xsd:nonNegativeInteger⚓ |
| Note | Any positive integer value or zero is permitted |
| teidata.enumerated defines the range of attribute values expressed as a single XML name taken from a list of documented possibilities. | |
| Module | tei — NHSL TEI P5 Schema Customization |
| Used by | |
| Content model |
<content>
<dataRef key="teidata.word"/>
</content>
⚓ |
| Declaration | tei_teidata.enumerated = teidata.word⚓ |
| Note | 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. |
| teidata.language defines the range of attribute values used to identify a particular combination of human language and writing system. | |
| Module | tei — NHSL TEI P5 Schema Customization |
| Used by | |
| Content model |
<content>
<alternate minOccurs="1" maxOccurs="1">
<dataRef name="language"/>
<valList>
<valItem ident=""/>
</valList>
</alternate>
</content>
⚓ |
| Declaration | tei_teidata.language = xsd:language | ( "" )⚓ |
| Note | 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.
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 Examples include
The W3C Internationalization Activity has published a useful introduction to BCP 47, Language tags in HTML and XML. |
| teidata.pointer defines 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. | |
| Module | tei — NHSL TEI P5 Schema Customization |
| Used by | |
| Content model |
<content>
<dataRef restriction="\S+" name="anyURI"/>
</content>
⚓ |
| Declaration |
tei_teidata.pointer = xsd:anyURI { pattern = "\S+" }⚓ |
| Note | 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,
|
| teidata.temporal.w3c defines 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. | |
| Module | tei — NHSL TEI P5 Schema Customization |
| Used by | |
| Content model |
<content>
<alternate minOccurs="1" maxOccurs="1">
<dataRef name="date"/>
<dataRef name="gYear"/>
<dataRef name="gMonth"/>
<dataRef name="gDay"/>
<dataRef name="gYearMonth"/>
<dataRef name="gMonthDay"/>
<dataRef name="time"/>
<dataRef name="dateTime"/>
</alternate>
</content>
⚓ |
| Declaration | tei_teidata.temporal.w3c = xsd:date | xsd:gYear | xsd:gMonth | xsd:gDay | xsd:gYearMonth | xsd:gMonthDay | xsd:time | xsd:dateTime⚓ |
| Note | 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. |
| teidata.text defines the range of attribute values used to express some kind of identifying string as a single sequence of Unicode characters possibly including whitespace. | |
| Module | tei — NHSL TEI P5 Schema Customization |
| Used by | |
| Content model |
<content>
<dataRef name="string"/>
</content>
⚓ |
| Declaration | tei_teidata.text = string⚓ |
| Note | Attributes using this datatype must contain a single ‘token’ in which whitespace and other punctuation characters are permitted. |
| teidata.truthValue defines the range of attribute values used to express a truth value. | |
| Module | tei — NHSL TEI P5 Schema Customization |
| Used by | |
| Content model |
<content>
<dataRef name="boolean"/>
</content>
⚓ |
| Declaration | tei_teidata.truthValue = xsd:boolean⚓ |
| Note | 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. |
| teidata.version defines the range of attribute values which may be used to specify a TEI or Unicode version number. | |
| Module | tei — NHSL TEI P5 Schema Customization |
| Used by |
Element:
|
| Content model |
<content>
<dataRef name="token"
restriction="[\d]+(\.[\d]+){0,2}"/>
</content>
⚓ |
| Declaration |
tei_teidata.version = token { pattern = "[\d]+(\.[\d]+){0,2}" }⚓ |
| Note | The value of this attribute follows the pattern specified by the Unicode consortium for its version number (https://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. |
| teidata.word defines the range of attribute values expressed as a single word or token. | |
| Module | tei — NHSL TEI P5 Schema Customization |
| Used by | |
| Content model |
<content>
<dataRef name="token"
restriction="[^\p{C}\p{Z}]+"/>
</content>
⚓ |
| Declaration |
tei_teidata.word = token { pattern = "[^\p{C}\p{Z}]+" }⚓ |
| Note | Attributes using this datatype must contain a single ‘word’ which contains only letters, digits, punctuation characters, or symbols: thus it cannot include whitespace. |