diff --git a/build/workflow.sh b/build/workflow.sh index 197790a66..cf1813c5f 100755 --- a/build/workflow.sh +++ b/build/workflow.sh @@ -32,7 +32,7 @@ ant echo "Ran app build successfully" echo "Fetching the data repository to build a data xar" -git clone https://github.com/$GITHUB_ORG/$GITHUB_REPOSITORY --branch development --single-branch +git clone https://github.com/$GITHUB_ORG/$GITHUB_REPOSITORY --branch main --single-branch cd $GITHUB_REPOSITORY ### CREATE NECESSARY CONFIG FOR THE BUILD, AND POPULATE VERSION AND PACKAGE_NAME diff --git a/documentation/Schema/SPEAR.html b/documentation/Schema/SPEAR.html new file mode 100644 index 000000000..3848d2b81 --- /dev/null +++ b/documentation/Schema/SPEAR.html @@ -0,0 +1,3455 @@ +TEI Customization for SPEAR: Syriaca Persons, Events, and Relations

TEI Customization for SPEAR: Syriaca Persons, Events, and Relations

Table of contents

This schema has been created to to constrain the TEI P5 for validating the born-digital project SPEAR: Syriac Persons, Events, and Relations. This customization will be used for the encoding of many different documents by many different researchers having differnet levels of training. As such, a schema is particularly important. The highly-structured data model of SPEAR also requires some modifications and additions to TEI P5.

1. Elements

1.1. <TEI>

<TEI> (TEI document) contains a single TEI-conformant document, combining a single TEI header with one or more members of the model.resource class. Multiple <TEI> elements may be combined within a <TEI> (or <teiCorpus>) element. [4. Default Text Structure 15.1. Varieties of Composite Text]
Moduletextstructure
Attributes
versionspecifies the version number of the TEI Guidelines against which this document is valid.
StatusOptional
Datatypeteidata.version
Note

Major editions of the Guidelines have long been informally referred to by a name made up of the letter P (for Proposal) followed by a digit. The current release is one of the many releases of the fifth major edition of the Guidelines, known as P5. This attribute may be used to associate a TEI document with a specific release of the P5 Guidelines, in the absence of a more precise association provided by the source attribute on the associated <schemaSpec>.

Contained by
textstructure: TEI
May contain
header: teiHeader
textstructure: TEI text
Note

This element is required. It is customary to specify the TEI namespace http://www.tei-c.org/ns/1.0 on it, for example: <TEI version="4.4.0" 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>
Schematron
+<sch:ns prefix="tei" + uri="http://www.tei-c.org/ns/1.0"/> +<sch:ns prefix="xs" + uri="http://www.w3.org/2001/XMLSchema"/>
Schematron
+<sch:ns prefix="rng" + uri="http://relaxng.org/ns/structure/1.0"/>
Content model
+<content>
+ <sequence>
+  <elementRef key="teiHeader"/>
+  <alternate>
+   <sequence>
+    <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
+{
+   att.global.attributes,
+   att.typed.attributes,
+   attribute version { text }?,
+   ( teiHeader, ( ( model.resource+, TEI* ) | TEI+ ) )
+}⚓

1.2. <ab>

<ab>
Modulelinking
Attributes
xml:id
StatusRequired
DatatypeID
Schematron
+<sch:assert test="starts-with(., 'factoid-')">An @xml:id attribute + starts with 'factoid-'.</sch:assert> +<sch:report test="matches(substring-after(., '-'), '\D')">A properly formatted + SPEAR factoid URI ends with a hyphen followed by a number.</sch:report> +<sch:assert test="matches(substring-after(., '-'), '\d')">A properly formatted + SPEAR factoid URI ends with a number.</sch:assert>
resp
StatusRequired
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
type
StatusRequired
Datatypeteidata.enumerated
subtype
StatusRequired
Legal values are:
birth
(birth) Used to designate person factoids that encode birth dates and/or locations
citizenship
(citizenship) Used to designate person factoids that encode citizenship
death
(death) Used to designate person factoids that encode death dates and/or locations
education
(education) Used to designate person factoids that encode education
ethnicLabel
(ethnic label) Used to designate person factoids that encode ethnic labels
event
(event) Used to designate event factoids
gender
(gender) Used to designate person factoids that encode gender
langKnown
(language known) Used to designate person factoids that encode language knowledge
mentalState
(mental state) Used to designate person factoids that encode mental states
nameVariant
(name variant) Used to designate person factoids that encode name variants
occupation
(occupation) Used to designate person factoids that encode occupations
physicalTrait
(physical trait) Used to designate person factoids that encode physical traits
relation
(relation) Used to designate relation factoids
residence
(residence) Used to designate person factoids that encode places and dates of residence
sanctity
(sanctity) Used to designate person factoids that encode sanctity
socecStatus
(socio-economic status) Used to designate person factoids that encode socio-econimic status
Contained by
textstructure: body
May contain
core: bibl note
header: idno
namesdates: listEvent listPerson listRelation
Note

This customization requires the basic pattern of SPEAR factoids to be encoded correctly. Each factoid is encoded in an <ab> element. Since each factoid contains data on a Person, Event, or Relation, the schema requires that <ab> must contain a <listPerson>, <listEvent>, or <listRelation> child element. Since every factoid requires a bibliographic reference, every <ab> must contain one or more child <bibl> elements. The encoder also has the option of adding a <note> element to the factoid as well.

This customization also requires that every <ab> element receives @xml:id, @type, @subtype, and @resp attributes. The @xml:id must take the form "factoid-{\d}" where {\d} is a number unique within the document. The @type attribute must be "factoid". The @subtype attribute comes from a closed list of data types encoded in the SPEAR project. The @resp attribute must point to an editor listed in the <titleStmt>. This ensures that all contributions are attributed at the factoid level.

Schematron
+<sch:rule context="tei:ab[ancestor::tei:body]"> +<sch:assert test="@xml:id">An <ab> descendant of <body> requires an @xml:id attribute.</sch:assert> +<sch:assert test="@resp">An <ab> descendant of <body> requires a @resp attribute.</sch:assert> +<sch:assert test="@type='factoid'">An <ab> descendant of <body> requires a @type attribute with the value "factoid".</sch:assert> +</sch:rule> +<sch:rule context="tei:ab[ancestor::tei:body]/@resp"> +<sch:let name="contributorRefs" + value="//tei:name[ancestor::tei:respStmt]/@ref"/> +<sch:let name="respPtrs" + value="for $i in $contributorRefs return substring-after($i, '.xml')"/> +<sch:assert test=" every $i in (tokenize(., ' ')) satisfies $i = $respPtrs"> Acceptable values for this @resp attribute include: +<sch:value-of select="string-join($respPtrs, '; ')"/>. +</sch:assert> +</sch:rule>
Content model
+<content>
+ <alternate minOccurs="1" maxOccurs="1">
+  <sequence minOccurs="1" maxOccurs="1"
+   preserveOrder="true">
+   <elementRef key="idno" minOccurs="1"
+    maxOccurs="1"/>
+   <elementRef key="listPerson"
+    minOccurs="1" maxOccurs="1"/>
+   <elementRef key="bibl" minOccurs="1"
+    maxOccurs="unbounded"/>
+   <elementRef key="note" minOccurs="0"
+    maxOccurs="unbounded"/>
+  </sequence>
+  <sequence minOccurs="1" maxOccurs="1"
+   preserveOrder="true">
+   <elementRef key="idno" minOccurs="1"
+    maxOccurs="1"/>
+   <elementRef key="listEvent"
+    minOccurs="1" maxOccurs="1"/>
+   <elementRef key="bibl" minOccurs="1"
+    maxOccurs="unbounded"/>
+   <elementRef key="listRelation"
+    minOccurs="0" maxOccurs="1"/>
+   <elementRef key="note" minOccurs="0"
+    maxOccurs="unbounded"/>
+  </sequence>
+  <sequence minOccurs="1" maxOccurs="1"
+   preserveOrder="true">
+   <elementRef key="idno" minOccurs="1"
+    maxOccurs="1"/>
+   <elementRef key="listRelation"
+    minOccurs="1" maxOccurs="1"/>
+   <elementRef key="bibl" minOccurs="1"
+    maxOccurs="unbounded"/>
+   <elementRef key="note" minOccurs="0"
+    maxOccurs="unbounded"/>
+  </sequence>
+ </alternate>
+</content>
+    ⚓
Schema Declaration
+element ab
+{
+   attribute xml:id { text },
+   attribute resp { list { + } },
+   attribute type { text },
+   attribute subtype
+   {
+      "birth"
+    | "citizenship"
+    | "death"
+    | "education"
+    | "ethnicLabel"
+    | "event"
+    | "gender"
+    | "langKnown"
+    | "mentalState"
+    | "nameVariant"
+    | "occupation"
+    | "physicalTrait"
+    | "relation"
+    | "residence"
+    | "sanctity"
+    | "socecStatus"
+   },
+   (
+      ( idno, listPerson, bibl+, note* )
+    | ( idno, listEvent, bibl+, listRelation?, note* )
+    | ( idno, listRelation, bibl+, note* )
+   )
+}⚓

1.3. <author>

<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]
Modulecore
Attributes
Contained by
core: bibl
May contain
core: choice corr date name note num orig ptr ref reg rs sic title
namesdates: orgName persName placeName
character data
Note

Particularly where cataloguing is likely to be based on the content of the header, it is advisable to use a generally recognized name authority file to supply the content for this element. The attributes key or ref may also be used to reference canonical information about the author(s) intended from any appropriate authority, such as a library catalogue or online resource.

In the case of a broadcast, use this element for the name of the company or network responsible for making the broadcast.

Where an author is unknown or unspecified, this element may contain text such as Unknown or Anonymous. When the appropriate TEI modules are in use, it may also contain detailed tagging of the names used for people, organizations or places, in particular where multiple names are given.

Example
<author>British Broadcasting Corporation</author> +<author>La Fayette, Marie Madeleine Pioche de la Vergne, comtesse de (1634–1693)</author> +<author>Anonymous</author> +<author>Bill and Melinda Gates Foundation</author> +<author> + <persName>Beaumont, Francis</persName> and +<persName>John Fletcher</persName> +</author> +<author> + <orgName key="BBC">British Broadcasting +   Corporation</orgName>: Radio 3 Network +</author>
Content model
+<content>
+ <macroRef key="macro.phraseSeq"/>
+</content>
+    ⚓
Schema Declaration
+element author
+{
+   att.global.attributes,
+   att.naming.attributes,
+   att.datable.attributes,
+   macro.phraseSeq
+}⚓

1.4. <authority>

<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.]
Moduleheader
Attributes
Contained by
header: publicationStmt
May containCharacter data only
Note

Syriaca.org is identified as the responsible entity using <authority>.

Example
<authority>John Smith</authority>
Schematron
+<sch:rule context="//tei:publicationStmt/tei:authority"> +<sch:assert test="normalize-space(.) = '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 { att.global.attributes, att.canonical.attributes, text }⚓

1.5. <availability>

<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.]
Moduleheader
Attributes
status(status) supplies a code identifying the current availability of the text.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
free
(free) the text is freely available.
unknown
(unknown) the status of the text is unknown.
restricted
(restricted) the text is not freely available.
Contained by
header: publicationStmt
May contain
core: p
header: licence
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>
Content model
+<content>
+ <alternate minOccurs="1"
+  maxOccurs="unbounded">
+  <classRef key="model.availabilityPart"/>
+  <classRef key="model.pLike"/>
+ </alternate>
+</content>
+    ⚓
Schema Declaration
+element availability
+{
+   att.global.attributes,
+   att.declarable.attributes,
+   attribute status { "free" | "unknown" | "restricted" }?,
+   ( model.availabilityPart | model.pLike )+
+}⚓

1.6. <back>

<back> (back matter) contains any appendixes, etc. following the main part of a text. [4.7. Back Matter 4. Default Text Structure]
Moduletextstructure
Attributes
Contained by
textstructure: text
May contain
core: listBibl
Note

The <back> element must contain only one <listBibl>.

Example
<back> + <div type="appendix"> +  <head>The Golden Dream or, the Ingenuous Confession</head> +  <p>TO shew the Depravity of human Nature, and how apt the Mind is to be misled by Trinkets +     and false Appearances, Mrs. Two-Shoes does acknowledge, that after she became rich, she +     had like to have been, too fond of Money +<!-- .... --> +  </p> + </div> +<!-- ... --> + <div type="epistle"> +  <head>A letter from the Printer, which he desires may be inserted</head> +  <salute>Sir.</salute> +  <p>I have done with your Copy, so you may return it to the Vatican, if you please; +   +<!-- ... --> +  </p> + </div> + <div type="advert"> +  <head>The Books usually read by the Scholars of Mrs Two-Shoes are these and are sold at Mr +     Newbery's at the Bible and Sun in St Paul's Church-yard.</head> +  <list> +   <item n="1">The Christmas Box, Price 1d.</item> +   <item n="2">The History of Giles Gingerbread, 1d.</item> +<!-- ... --> +   <item n="42">A Curious Collection of Travels, selected from the Writers of all Nations, +       10 Vol, Pr. bound 1l.</item> +  </list> + </div> + <div type="advert"> +  <head>By the KING's Royal Patent, Are sold by J. NEWBERY, at the Bible and Sun in St. +     Paul's Church-Yard.</head> +  <list> +   <item n="1">Dr. James's Powders for Fevers, the Small-Pox, Measles, Colds, &amp;c. 2s. +       6d</item> +   <item n="2">Dr. Hooper's Female Pills, 1s.</item> +<!-- ... --> +  </list> + </div> +</back>
Content model
+<content>
+ <elementRef key="listBibl" minOccurs="1"
+  maxOccurs="1"/>
+</content>
+    ⚓
Schema Declaration
+element back { att.global.attributes, att.declaring.attributes, listBibl }⚓

1.7. <bibl>

<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 15.3.2. Declarable Elements]
Modulecore
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusRequired
Datatypeteidata.enumerated
Member of
model.biblLike
Contained by
core: corr desc head listBibl note orig p ref reg sic title
header: change
linking: ab
May contain
core: author biblScope citedRange date editor ptr pubPlace publisher title
Note

SPEAR only uses @xml:id and @type attributes on the <bibl> element. SPEAR uses <bibl> elements with an @xml:id only in the <back> of the TEI file. The @type attribute indicates whether the <bibl> is "primary", "secondary", or a "urn".

Since SPEAR relies on the Linked Open Data infrastructure of Syriaca.org, a <bibl> element in the body only requires a <ptr> element indicating the Syriaca.org URI or CTS URN for the bibliographic reference. When indicating a CTS URNs no other additional information is required. When indicating a Syriaca.org URI, a <citedRange> is needed.

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:back//tei:bibl"> +<sch:assert test="@xml:id">A <bibl> element in the back matter must contain an + @xml:id attribute.</sch:assert> +</sch:rule> +<sch:rule context="tei:back//tei:bibl/@xml:id"> +<sch:let name="docURIno" + value="//tei:publicationStmt/tei:idno[@type='URI']/substring-after(substring-before(., + '/tei'), 'spear-prosop.org/')"/> +<sch:assert test="contains(., concat('bibl', $docURIno, '-'))">The @xml:id on + <bibl> in the back matter must take the following form: 'bibl' + + '<sch:value-of select="$docURIno"/>' + '-' + a unique number.</sch:assert> +<sch:assert test="count(distinct-values(//tei:back//tei:bibl/@xml:id)) eq count(//tei:back//tei:bibl/@xml:id)">Each @xml:id attribute on <bibl> must have a unique value.</sch:assert> +<sch:report test="matches(substring-after(., '-'), '\D')">A properly formatted + @xml:id ends with a number.</sch:report> +<sch:assert test="matches(substring-after(., '-'), '\d')">A properly formatted + @xml:id ends with a number.</sch:assert> +</sch:rule>
Content model
+<content>
+ <sequence minOccurs="0" maxOccurs="1"
+  preserveOrder="true">
+  <elementRef key="title" minOccurs="0"
+   maxOccurs="2"/>
+  <elementRef key="author" minOccurs="0"
+   maxOccurs="unbounded"/>
+  <elementRef key="editor" minOccurs="0"
+   maxOccurs="unbounded"/>
+  <elementRef key="pubPlace" minOccurs="0"
+   maxOccurs="1"/>
+  <elementRef key="publisher" minOccurs="0"
+   maxOccurs="1"/>
+  <elementRef key="date" minOccurs="0"
+   maxOccurs="1"/>
+  <elementRef key="biblScope" minOccurs="0"
+   maxOccurs="2"/>
+  <elementRef key="ptr" minOccurs="1"
+   maxOccurs="1"/>
+  <elementRef key="citedRange"
+   minOccurs="0" maxOccurs="3"/>
+ </sequence>
+</content>
+    ⚓
Schema Declaration
+element bibl
+{
+   att.global.attributes,
+   att.declarable.attributes,
+   att.typed.attribute.subtype,
+   att.sortable.attributes,
+   att.docStatus.attributes,
+   attribute type { text },
+   (
+      ( title?, ( title, title? )? ),
+      author*,
+      editor*,
+      pubPlace?,
+      publisher?,
+      date?,
+      ( biblScope?, ( biblScope, biblScope? )? ),
+      ptr,
+      ( citedRange?, ( citedRange, ( citedRange, citedRange? )? )? )
+   )?
+}⚓

1.8. <biblScope>

<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]
Modulecore
Attributes
unitidentifies the unit of information conveyed by the element, e.g. columns, pages, volume, entry.
Derived fromatt.citing
StatusRequired
Datatypeteidata.enumerated
Suggested values include:
volume
(volume) the element contains a volume number.
issue
the element contains an issue number, or volume and issue numbers.
page
(page) the element contains a page number or page range.
line
the element contains a line number or line range.
chapter
(chapter) the element contains a chapter indication (number and/or title)
part
the element identifies a part of a book or collection.
column
the element identifies a column.
entry
the element identifies an entry number or label in a list of entries.
Contained by
core: bibl
header: seriesStmt
May contain
core: title
header: idno
character data
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 <biblScope from="3">p. 3ff</biblScope>.

It is now considered good practice to supply this element as a sibling (rather than a child) of <imprint>, since it supplies information which does not constitute part of the imprint.

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="0" maxOccurs="1">
+  <textNode/>
+  <elementRef key="title" minOccurs="0"
+   maxOccurs="1"/>
+  <elementRef key="idno" minOccurs="0"
+   maxOccurs="1"/>
+ </sequence>
+</content>
+    ⚓
Schema Declaration
+element biblScope
+{
+   att.global.attributes,
+   att.citing.attribute.from,
+   att.citing.attribute.to,
+   attribute unit
+   {
+      "volume"
+    | "issue"
+    | "page"
+    | "line"
+    | "chapter"
+    | "part"
+    | "column"
+    | "entry"
+   },
+   ( text, title?, idno? )?
+}⚓

1.9. <birth>

<birth> (birth) contains information about a person's birth, such as its date and place. [15.2.2. The Participant Description]
Modulenamesdates
Attributes
Contained by
namesdates: person
May contain
core: choice date note
namesdates: placeName
Note

This customization restricts the attribute classes of the <birth> element to att.datable.w3c but excludes the @to and @from attributes. If more precise dating is required for a SPEAR factoid, encoder should use the <date> element.

It also restricts the child elements to those dealing with dates (<date> or <choice>), <placeName>, and <note>.

Example
<birth>Before 1920, Midlands region.</birth>
Example
<birth when="1960-12-10">In a small cottage near <name type="place">Aix-la-Chapelle</name>, + early in the morning of <date>10 Dec 1960</date> +</birth>
Content model
+<content>
+ <sequence minOccurs="1" maxOccurs="1"
+  preserveOrder="true">
+  <alternate minOccurs="0" maxOccurs="1">
+   <elementRef key="date" minOccurs="1"
+    maxOccurs="1"/>
+   <elementRef key="choice" minOccurs="1"
+    maxOccurs="1"/>
+  </alternate>
+  <elementRef key="placeName" minOccurs="0"
+   maxOccurs="1"/>
+  <elementRef key="note" minOccurs="1"
+   maxOccurs="1"/>
+ </sequence>
+</content>
+    ⚓
Schema Declaration
+element birth
+{
+   att.datable.w3c.attribute.when,
+   att.datable.w3c.attribute.notBefore,
+   att.datable.w3c.attribute.notAfter,
+   ( ( date | choice )?, placeName?, note )
+}⚓

1.10. <body>

<body> (text body) contains the whole body of a single unitary text, excluding any front or back matter. [4. Default Text Structure]
Moduletextstructure
Attributes
Contained by
textstructure: text
May contain
linking: ab
Note

The body of a SPEAR file contains factoids, each of which appears in a separate <ab> element. As such, <ab> is the only acceptable child element of <body>.

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="ab" minOccurs="1"
+  maxOccurs="unbounded"/>
+</content>
+    ⚓
Schema Declaration
+element body { att.global.attributes, att.declaring.attributes, ab+ }⚓

1.11. <catDesc>

<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]
Moduleheader
Attributes
Contained by
header: category
May containCharacter data only
Example
<catDesc>Prose reportage</catDesc>
Example
<catDesc> + <textDesc n="novel"> +  <channel mode="w">print; part issues</channel> +  <constitution type="single"/> +  <derivation type="original"/> +  <domain type="art"/> +  <factuality type="fiction"/> +  <interaction type="none"/> +  <preparedness type="prepared"/> +  <purpose type="entertain" degree="high"/> +  <purpose type="inform" degree="medium"/> + </textDesc> +</catDesc>
Content model
+<content>
+ <textNode/>
+</content>
+    ⚓
Schema Declaration
+element catDesc { att.global.attributes, att.canonical.attributes, text }⚓

1.12. <category>

<category> (category) contains an individual descriptive category, possibly nested within a superordinate category, within a user-defined taxonomy. [2.3.7. The Classification Declaration]
Moduleheader
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Derived fromatt.global
StatusOptional
DatatypeID
Contained by
header: taxonomy
May contain
header: catDesc
Example
<category xml:id="b1"> + <catDesc>Prose reportage</catDesc> +</category>
Example
<category xml:id="b2"> + <catDesc>Prose </catDesc> + <category xml:id="b11"> +  <catDesc>journalism</catDesc> + </category> + <category xml:id="b12"> +  <catDesc>fiction</catDesc> + </category> +</category>
Example
<category xml:id="LIT"> + <catDesc xml:lang="pl">literatura piękna</catDesc> + <catDesc xml:lang="en">fiction</catDesc> + <category xml:id="LPROSE"> +  <catDesc xml:lang="pl">proza</catDesc> +  <catDesc xml:lang="en">prose</catDesc> + </category> + <category xml:id="LPOETRY"> +  <catDesc xml:lang="pl">poezja</catDesc> +  <catDesc xml:lang="en">poetry</catDesc> + </category> + <category xml:id="LDRAMA"> +  <catDesc xml:lang="pl">dramat</catDesc> +  <catDesc xml:lang="en">drama</catDesc> + </category> +</category>
Content model
+<content>
+ <elementRef key="catDesc" minOccurs="1"
+  maxOccurs="1"/>
+</content>
+    ⚓
Schema Declaration
+element category
+{
+   att.global.attribute.n,
+   att.global.attribute.xmllang,
+   att.global.attribute.xmlbase,
+   att.global.attribute.xmlspace,
+   att.global.rendition.attribute.rend,
+   att.global.rendition.attribute.style,
+   att.global.rendition.attribute.rendition,
+   att.global.linking.attribute.corresp,
+   att.global.linking.attribute.synch,
+   att.global.linking.attribute.sameAs,
+   att.global.linking.attribute.copyOf,
+   att.global.linking.attribute.next,
+   att.global.linking.attribute.prev,
+   att.global.linking.attribute.exclude,
+   att.global.linking.attribute.select,
+   att.global.analytic.attribute.ana,
+   att.global.responsibility.attribute.cert,
+   att.global.responsibility.attribute.resp,
+   att.global.source.attribute.source,
+   attribute xml:id { text }?,
+   catDesc
+}⚓

1.13. <change>

<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 11.7. Identifying Changes and Revisions]
Moduleheader
Attributes
target(target) points to one or more elements that belong to this change.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Contained by
header: revisionDesc
May contain
core: bibl choice corr date listBibl name note num orig p ptr ref reg rs sic title
namesdates: listRelation orgName persName placeName
character data
Note

The who attribute may be used to point to any other element, but will typically specify a <respStmt> or <person> element elsewhere in the header, identifying the person responsible for the change and their role in making it.

It is recommended that changes be recorded with the most recent first. The status attribute may be used to indicate the status of a document following the change documented.

Example
<titleStmt> + <title> ... </title> + <editor xml:id="LDB">Lou Burnard</editor> + <respStmt xml:id="BZ"> +  <resp>copy editing</resp> +  <name>Brett Zamir</name> + </respStmt> +</titleStmt> +<!-- ... --> +<revisionDesc status="published"> + <change who="#BZ" when="2008-02-02" +  status="public">Finished chapter 23</change> + <change who="#BZ" when="2008-01-02" +  status="draft">Finished chapter 2</change> + <change n="P2.2" when="1991-12-21" +  who="#LDB">Added examples to section 3</change> + <change when="1991-11-11" who="#MSM">Deleted chapter 10</change> +</revisionDesc>
Example
<profileDesc> + <creation> +  <listChange> +   <change xml:id="DRAFT1">First draft in pencil</change> +   <change xml:id="DRAFT2" +    notBefore="1880-12-09">First revision, mostly +       using green ink</change> +   <change xml:id="DRAFT3" +    notBefore="1881-02-13">Final corrections as +       supplied to printer.</change> +  </listChange> + </creation> +</profileDesc>
Content model
+<content>
+ <macroRef key="macro.specialPara"/>
+</content>
+    ⚓
Schema Declaration
+element change
+{
+   att.ascribed.attributes,
+   att.datable.attributes,
+   att.docStatus.attributes,
+   att.global.attributes,
+   att.typed.attributes,
+   attribute target { list { + } }?,
+   macro.specialPara
+}⚓

1.14. <choice>

<choice> (choice) groups a number of alternative encodings for the same point in a text. [3.5. Simple Editorial Changes]
Modulecore
Member of
model.pPart.editorial
Contained by
core: author choice corr date desc editor head name note num orig p pubPlace publisher ref reg resp sic title
header: change edition
namesdates: birth death langKnown orgName persName placeName
May contain
core: choice corr orig reg sic
Note

Because the children of a <choice> element all represent alternative ways of encoding the same sequence, it is natural to think of them as mutually exclusive. However, there may be cases where a full representation of a text requires the alternative encodings to be considered as parallel.

Note also that <choice> elements may self-nest.

Where the purpose of an encoding is to record multiple witnesses of a single work, rather than to identify multiple possible encoding decisions at a given point, the <app> element and associated elements discussed in section 12.1. The Apparatus Entry, Readings, and Witnesses should be preferred.

ExampleAn American encoding of Gulliver's Travels which retains the British spelling but also provides a version regularized to American spelling might be encoded as follows.
<p>Lastly, That, upon his solemn oath to observe all the above + articles, the said man-mountain shall have a daily allowance of + meat and drink sufficient for the support of <choice> +  <sic>1724</sic> +  <corr>1728</corr> + </choice> of our subjects, + with free access to our royal person, and other marks of our +<choice> +  <orig>favour</orig> +  <reg>favor</reg> + </choice>.</p>
Content model
+<content>
+ <alternate minOccurs="2"
+  maxOccurs="unbounded">
+  <classRef key="model.choicePart"/>
+  <elementRef key="choice"/>
+ </alternate>
+</content>
+    ⚓
Schema Declaration
+element choice { ( model.choicePart | choice )+ }⚓

1.15. <citedRange>

<citedRange>
Modulecore
Attributes
unit
StatusRequired
Datatypeteidata.enumerated
Legal values are:
p
the element contains a page number or page range.
line
the element contains a line number or line range.
part
the element contains a part of a book or collection, i.e. chapter and verse of a biblical text.
column
the element identifies a column.
Contained by
core: bibl
May containCharacter data only
Note

SPEAR only allows text in a <citedRange> element and requires the use of a @unit attribute with a closed list. SPEAR prefers that encoders use the part value and cite ancient texts according to section numbers.

Content model
+<content>
+ <textNode/>
+</content>
+    ⚓
Schema Declaration
+element citedRange
+{
+   attribute unit { "p" | "line" | "part" | "column" },
+   text
+}⚓

1.16. <classDecl>

<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]
Moduleheader
Attributes
Contained by
header: encodingDesc
May contain
header: taxonomy
Example
<classDecl> + <taxonomy xml:id="LCSH"> +  <bibl>Library of Congress Subject Headings</bibl> + </taxonomy> +</classDecl> +<!-- ... --> +<textClass> + <keywords scheme="#LCSH"> +  <term>Political science</term> +  <term>United States -- Politics and government — +     Revolution, 1775-1783</term> + </keywords> +</textClass>
Content model
+<content>
+ <elementRef key="taxonomy" minOccurs="1"
+  maxOccurs="1"/>
+</content>
+    ⚓
Schema Declaration
+element classDecl { att.global.attributes, taxonomy }⚓

1.17. <corr>

<corr> (correction) contains the correct form of a passage apparently erroneous in the copy text. [3.5.1. Apparent Errors]
Modulecore
Member of
model.choicePart model.pPart.transcriptional
Contained by
core: author choice corr date editor head name note num orig p pubPlace publisher ref reg sic title
header: change edition
namesdates: orgName persName placeName
May contain
core: bibl choice corr date listBibl name note num orig ptr ref reg rs sic title
namesdates: listRelation orgName persName placeName
character data
ExampleIf all that is desired is to call attention to the fact that the copy text has been corrected, <corr> may be used alone:
I don't know, + Juan. It's so far in the past now — how <corr>can we</corr> prove + or disprove anyone's theories?
ExampleIt is also possible, using the <choice> and <sic> elements, to provide an uncorrected reading:
I don't know, Juan. It's so far in the past now — + how <choice> + <sic>we can</sic> + <corr>can we</corr> +</choice> prove or + disprove anyone's theories?
Content model
+<content>
+ <macroRef key="macro.paraContent"/>
+</content>
+    ⚓
Schema Declaration
+element corr { macro.paraContent }⚓

1.18. <date>

<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 15.2.3. The Setting Description 13.4. Dates]
Modulecore
Attributes
datingMethodsupplies a pointer to a <calendar> element or other means of interpreting the values of the custom dating attributes.
Derived fromatt.datable.custom
StatusOptional
Datatypeteidata.pointer
calendar
StatusOptional
Datatypeteidata.pointer
Schematron
+<sch:rule context="tei:date[parent::tei:reg]/@calendar"> +<sch:assert test=". = 'Gregorian'">A <date> element child of <reg> + must have a @calendar attribute with a value of "Gregorian".</sch:assert> +</sch:rule>
Suggested values include:
Gregorian
The element contains a date according to the Gregorian calendar.
Seleucid
The element contains a date according to the Seleucid calendar.
Member of
model.dateLike
Contained by
core: author bibl corr date desc editor head name note num orig p pubPlace publisher ref reg resp sic title
header: change edition publicationStmt
namesdates: birth death langKnown nationality orgName persName placeName residence
May contain
core: choice corr date name note num orig ptr ref reg rs sic title
namesdates: orgName persName placeName
character data
Example
<date when="1980-02">early February 1980</date>
Example
Given on the <date when="1977-06-12">Twelfth Day + of June in the Year of Our Lord One Thousand Nine Hundred and Seventy-seven of the Republic + the Two Hundredth and first and of the University the Eighty-Sixth.</date>
Example
<date when="1990-09">September 1990</date>
Content model
+<content>
+ <alternate minOccurs="0"
+  maxOccurs="unbounded">
+  <textNode/>
+  <classRef key="model.gLike"/>
+  <classRef key="model.phrase"/>
+  <classRef key="model.global"/>
+ </alternate>
+</content>
+    ⚓
Schema Declaration
+element date
+{
+   att.datable.custom.attribute.when-custom,
+   att.datable.custom.attribute.notBefore-custom,
+   att.datable.custom.attribute.notAfter-custom,
+   att.datable.custom.attribute.from-custom,
+   att.datable.custom.attribute.to-custom,
+   att.datable.custom.attribute.datingPoint,
+   att.datable.w3c.attributes,
+   attribute datingMethod { text }?,
+   attribute calendar { "Gregorian" | "Seleucid" }?,
+   ( text | model.gLike | model.phrase | model.global )*
+}⚓

1.19. <death>

<death> (death) contains information about a person's death, such as its date and place. [15.2.2. The Participant Description]
Modulenamesdates
Attributes
Contained by
namesdates: person
May contain
core: choice date note
namesdates: placeName
Note

This customization restricts the attribute classes of the <death> element to att.datable.w3c but excludes the @to and @from attributes. If more precise dating is required for a SPEAR factoid, encoder should use the <date> element.

It also restricts the child elements to those dealing with dates (<date> or <choice>), <placeName>, and <note>.

Example
<death when="1902-10-01"/>
Example
<death when="1960-12-10">Passed away near <name type="place">Aix-la-Chapelle</name>, after suffering from cerebral palsy. </death>
Content model
+<content>
+ <sequence minOccurs="1" maxOccurs="1"
+  preserveOrder="true">
+  <alternate minOccurs="0" maxOccurs="1">
+   <elementRef key="date" minOccurs="1"
+    maxOccurs="1"/>
+   <elementRef key="choice" minOccurs="1"
+    maxOccurs="1"/>
+  </alternate>
+  <elementRef key="placeName" minOccurs="0"
+   maxOccurs="1"/>
+  <elementRef key="note" minOccurs="1"
+   maxOccurs="1"/>
+ </sequence>
+</content>
+    ⚓
Schema Declaration
+element death
+{
+   att.datable.w3c.attribute.when,
+   att.datable.w3c.attribute.notBefore,
+   att.datable.w3c.attribute.notAfter,
+   ( ( date | choice )?, placeName?, note )
+}⚓

1.20. <desc>

<desc>
Modulecore
Contained by
namesdates: event relation
May contain
core: bibl choice date rs title
namesdates: listRelation orgName persName placeName
character data
Note

This customization does not allow attributes on the <desc> element. It also restricts child elements to <choice>, <date>, <persName>, and <placeName>.

Schematron
+<sch:rule context="//tei:ab//tei:desc"> +<sch:report test="not(*) and string-length(normalize-space(.)) eq 0">Element of type + <desc> cannot be empty.</sch:report> +</sch:rule> +<sch:rule context="tei:ab/tei:listEvent/tei:event/tei:desc" + role="warning"> +<sch:assert test="./tei:persName or tei:placeName">The <desc> element should + generally contain either <persName> or <placeName>. SPEAR + encourages a liberal use of <persName>, <placeName>, and <date> + elements in the <desc> element of event factoids.</sch:assert> +</sch:rule>
Schematron
+<sch:rule context="//tei:body/tei:ab/tei:listRelation/tei:relation"> +<sch:assert test="tei:desc"> This <relation> requires a <desc>. +</sch:assert> +</sch:rule> +<sch:rule context="//tei:sourceDesc//tei:relation"> +<sch:report test="tei:desc"> The <desc> element may not appear here. +</sch:report> +</sch:rule> +<sch:rule context="//tei:ab/tei:listEvent/tei:listRelation/tei:relation/tei:desc"> +<sch:let name="SameEventURIs" + value="tokenize(parent::tei:relation/@mutual, ' ')"/> +<sch:assert test="count(child::tei:rs) = count($SameEventURIs)"> This <desc> must contain <sch:value-of select="count($SameEventURIs)"/> <rs> elements, one for each values in the @mutual attribute on <relation>. +</sch:assert> +<sch:assert test="count(distinct-values(tei:rs/@ref)) = count(tei:rs)"> This <desc> requires <rs> elements with unique @ref attribute values. +</sch:assert> +</sch:rule> +<sch:rule context="//tei:ab/tei:listEvent/tei:listRelation/tei:relation[@ref='syriaca:SameEvent']/tei:desc"> +<sch:let name="SameEventURIs" + value="tokenize(parent::tei:relation/@mutual, ' ')"/> +<sch:assert test="starts-with(normalize-space(.), 'The following factoids deal with + the same event: ')"> This <desc> must begin with "The following factoids deal with the same event: " +</sch:assert> +</sch:rule> +<sch:rule context="//tei:ab/tei:listEvent/tei:listRelation/tei:relation[@ref='syriaca:ProxmiateEvent']/tei:desc"> +<sch:let name="SameEventURIs" + value="tokenize(parent::tei:relation/@mutual, ' ')"/> +<sch:assert test="starts-with(normalize-space(.), 'The following factoids deal with + closely related events: ')"> This <desc> must begin with "The following factoids deal with related events: " +</sch:assert> +</sch:rule>
Content model
+<content>
+ <sequence minOccurs="0"
+  maxOccurs="unbounded" preserveOrder="false">
+  <textNode/>
+  <elementRef key="choice" minOccurs="0"
+   maxOccurs="unbounded"/>
+  <elementRef key="date" minOccurs="0"
+   maxOccurs="unbounded"/>
+  <elementRef key="persName" minOccurs="0"
+   maxOccurs="unbounded"/>
+  <elementRef key="placeName" minOccurs="0"
+   maxOccurs="unbounded"/>
+  <elementRef key="orgName" minOccurs="0"
+   maxOccurs="unbounded"/>
+  <elementRef key="rs" minOccurs="0"
+   maxOccurs="unbounded"/>
+  <elementRef key="bibl" minOccurs="0"
+   maxOccurs="unbounded"/>
+  <elementRef key="listRelation"
+   minOccurs="0" maxOccurs="1"/>
+  <elementRef key="title" minOccurs="0"
+   maxOccurs="unbounded"/>
+ </sequence>
+</content>
+    ⚓
Schema Declaration
+element desc
+{
+   (
+      text,
+      choice*,
+      date*,
+      persName*,
+      placeName*,
+      orgName*,
+      rs*,
+      bibl*,
+      listRelation?,
+      title*
+   )*
+}⚓

1.21. <edition>

<edition> (edition) describes the particularities of one edition of a text. [2.2.2. The Edition Statement]
Moduleheader
Attributes
Contained by
header: editionStmt
May contain
core: choice corr date name note num orig ptr ref reg rs sic title
namesdates: orgName persName placeName
character data
Example
<edition>First edition <date>Oct 1990</date> +</edition> +<edition n="S2">Students' edition</edition>
Content model
+<content>
+ <macroRef key="macro.phraseSeq"/>
+</content>
+    ⚓
Schema Declaration
+element edition { att.global.attributes, macro.phraseSeq }⚓

1.22. <editionStmt>

<editionStmt> (edition statement) groups information relating to one edition of a text. [2.2.2. The Edition Statement 2.2. The File Description]
Moduleheader
Attributes
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="S2">Students' edition</edition> + <respStmt> +  <resp>Adapted by </resp> +  <name>Elizabeth Kirk</name> + </respStmt> +</editionStmt>
Example
<editionStmt> + <p>First edition, <date>Michaelmas Term, 1991.</date> + </p> +</editionStmt>
Content model
+<content>
+ <elementRef key="edition" minOccurs="1"
+  maxOccurs="1"/>
+</content>
+    ⚓
Schema Declaration
+element editionStmt { att.global.attributes, edition }⚓

1.23. <editor>

<editor> contains a secondary statement of responsibility for a bibliographic item, for example the name of an individual, institution or organization, (or of several such) acting as editor, compiler, translator, etc. [3.12.2.2. Titles, Authors, and Editors]
Modulecore
Attributes
role
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
creator
A person involved in the creation of this xml file
general
A person responsible for this xml file or collection of xml files
translator
ref
StatusOptional
Datatypeteidata.pointer
Contained by
core: bibl
header: seriesStmt titleStmt
May contain
core: choice corr date name note num orig ptr ref reg rs sic title
namesdates: orgName persName placeName
character data
Note

This customization limits the attributes available on <desc> to @role and @ref and suggests values for @role.

Example
<editor role="Technical_Editor">Ron Van den Branden</editor> +<editor role="Editor-in-Chief">John Walsh</editor> +<editor role="Managing_Editor">Anne Baillot</editor>
Schematron
+<sch:rule context="//tei:titleStmt/tei:editor"> +<sch:assert test="@role"> This <editor> must have a @role attribute. +</sch:assert> +<sch:assert test="@ref"> This <editor> must have a @ref attribute. +</sch:assert> +</sch:rule> +<sch:rule context="//tei:titleStmt//tei:editor/@ref"> +<sch:let name="edsDoc" + value="doc('https://raw.githubusercontent.com/srophe/srophe-eXist-app/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 this @ref attribute include: +<sch:value-of select="string-join($refValues, ' | ')"/>. +</sch:assert> +</sch:rule>
Content model
+<content>
+ <macroRef key="macro.phraseSeq"/>
+</content>
+    ⚓
Schema Declaration
+element editor
+{
+   attribute role { "creator" | "general" | "translator" }?,
+   attribute ref { text }?,
+   macro.phraseSeq
+}⚓

1.24. <editorialDecl>

<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 15.3.2. Declarable Elements]
Moduleheader
Attributes
Contained by
header: encodingDesc
May contain
core: p
Example
<editorialDecl> + <normalization> +  <p>All words converted to Modern American spelling using +     Websters 9th Collegiate dictionary +  </p> + </normalization> + <quotation marks="all"> +  <p>All opening quotation marks converted to “ all closing +     quotation marks converted to &amp;cdq;.</p> + </quotation> +</editorialDecl>
Content model
+<content>
+ <elementRef key="p" minOccurs="1"
+  maxOccurs="1"/>
+</content>
+    ⚓
Schema Declaration
+element editorialDecl { att.global.attributes, att.declarable.attributes, p }⚓

1.25. <education>

<education> (education) contains a description of the educational experience of a person. [15.2.2. The Participant Description]
Modulenamesdates
Attributes
ana
StatusRequired
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
+<sch:rule context="//tei:education/@ana"> +<sch:let name="anaTokens" + value="tokenize(., ' ')"/> +<sch:let name="ti" + value="doc('https://raw.githubusercontent.com/srophe/syriaca/master/documentation/indexes/taxonomyIndex-old.xml')"/> +<sch:let name="disciplineURIs" + value="$ti//listURI[@type = 'fields-of-study']/uri"/> +<sch:let name="errors" + value="for $i in $anaTokens return $i[not(. = $disciplineURIs)]"/> +<sch:assert test="every $i in $anaTokens satisfies $i = $disciplineURIs" + role="warning"> + <sch:value-of select="string-join($errors, ', ')"/>: URI(s) not in the Taxonomy. If you find no appropriate concept on the following list, + please choose a keyword of your own for the editors to consider: <sch:value-of select="string-join($disciplineURIs, '; ')"/>.</sch:assert> +</sch:rule>
Contained by
namesdates: person personGrp
May contain
core: note
Note

This customization restricts the attribute classes of <education> to att.datable.w3c and the @ana attribute. If more precise dating is required for a SPEAR factoid, the encoder should use the <date> element.

It also restricts the required @ana attribute to keyword URIs in the Syriac Taxonomy that pertain to fields of education.

Example
<education>Left school at age 16</education>
Example
<education from="1986-01-01" + to="1990-06-30">Attended <name>Cherwell School</name> +</education>
Example
<education notBefore="1685-07" + notAfter="1690-06">Anthony Hammond + smuggled her into the University of Cambridge, where she was + disguised as his male cousin, Jack. She remained there for some + months learning grammar, logic, rhetoric, and ethics</education>
Content model
+<content>
+ <elementRef key="note" minOccurs="1"
+  maxOccurs="1"/>
+</content>
+    ⚓
Schema Declaration
+element education
+{
+   att.datable.w3c.attributes,
+   attribute ana { list { + } },
+   note
+}⚓

1.26. <encodingDesc>

<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]
Moduleheader
Attributes
Contained by
header: teiHeader
May contain
header: classDecl editorialDecl
Example
<encodingDesc> + <p>Basic encoding, capturing lexical information only. All +   hyphenation, punctuation, and variant spellings normalized. No +   formatting or layout information preserved.</p> +</encodingDesc>
Content model
+<content>
+ <sequence minOccurs="1" maxOccurs="1"
+  preserveOrder="true">
+  <elementRef key="editorialDecl"
+   minOccurs="1" maxOccurs="1"/>
+  <elementRef key="classDecl" minOccurs="1"
+   maxOccurs="1"/>
+ </sequence>
+</content>
+    ⚓
Schema Declaration
+element encodingDesc { att.global.attributes, ( editorialDecl, classDecl ) }⚓

1.27. <event>

<event> (event) contains data relating to any kind of significant event associated with a person, place, or organization. [13.3.1. Basic Principles]
Modulenamesdates
Attributes
Contained by
namesdates: listEvent
May contain
core: desc
Note

This customization makes <desc> the only acceptable child of <event>. It also requires an @ana attribute and constrains the values of that attribute to the full list of Syriaca.org keyword URIs. In the case of dates associated with an event, the customization also requires that date attributes (@when, @notBefore, @notAfter, @from, and @to) match on the <event> element and within the child <desc> element.

Example
<person> + <event type="mat" when="1972-10-12"> +  <label>matriculation</label> + </event> + <event type="grad" when="1975-06-23"> +  <label>graduation</label> + </event> +</person>
Schematron
+<sch:rule context="tei:event/@ana"> +<sch:let name="anaTokens" + value="tokenize(., ' ')"/> +<sch:let name="ti" + value="doc('https://raw.githubusercontent.com/srophe/syriaca/master/documentation/indexes/taxonomyIndex-old.xml')"/> +<sch:let name="taxonomyAllURIs" + value="$ti//listURI[@type = 'taxonomyAllURIs']/uri"/> +<sch:let name="errors" + value="for $i in $anaTokens return $i[not(. = $taxonomyAllURIs)]"/> +<sch:assert test="every $i in $anaTokens satisfies $i = $taxonomyAllURIs" + role="warning"> + <sch:value-of select="string-join($errors, ', ')"/>: URI(s) not in the Taxonomy. Please ensure that an appropriate URI does + not appear in the Taxonomy before proceeding. If you find no appropriate concept in the Taxonomy, please choose a keyword of your own for the editors to consider. +</sch:assert> +</sch:rule>
Schematron
+<sch:rule context="tei:event[tei:desc/tei:date/@when] | tei:event[tei:desc/tei:choice/tei:corr/tei:date/@when] + | tei:event[tei:desc/tei:choice/tei:reg/tei:date/@when]"> +<sch:assert test="./@when = ./tei:desc/tei:date/@when | ./tei:desc/tei:choice/tei:corr/tei:date/@when + | ./tei:desc/tei:choice/tei:reg/tei:date/@when"> This <event> must have a @when attribute with the value <sch:value-of select="./tei:desc/tei:date/@when | ./tei:desc/tei:choice/tei:corr/tei:date/@when + | ./tei:desc/tei:choice/tei:reg/tei:date/@when"/>. +</sch:assert> +</sch:rule> +<sch:rule context="tei:event[tei:desc/tei:date/@notBefore] | tei:event[tei:desc/tei:choice/tei:corr/tei:date/@notBefore] + | tei:event[tei:desc/tei:choice/tei:reg/tei:date/@notBefore]"> +<sch:assert test="./@notBefore = ./tei:desc/tei:date/@notBefore | ./tei:desc/tei:choice/tei:corr/tei:date/@notBefore + | ./tei:desc/tei:choice/tei:reg/tei:date/@notBefore"> This <event> must have a @notBefore attribute with the value <sch:value-of select="./tei:desc/tei:date/@notBefore | ./tei:desc/tei:choice/tei:corr/tei:date/@notBefore + | ./tei:desc/tei:choice/tei:reg/tei:date/@notBefore"/>. +</sch:assert> +</sch:rule> +<sch:rule context="tei:event[tei:desc/tei:date/@notAfter] | tei:event[tei:desc/tei:choice/tei:corr/tei:date/@notAfter] + | tei:event[tei:desc/tei:choice/tei:reg/tei:date/@notAfter]"> +<sch:assert test="./@notAfter = ./tei:desc/tei:date/@notAfter | ./tei:desc/tei:choice/tei:corr/tei:date/@notAfter + | ./tei:desc/tei:choice/tei:reg/tei:date/@notAfter"> This <event> must have a @notAfter attribute with the value <sch:value-of select="./tei:desc/tei:date/@notAfter | ./tei:desc/tei:choice/tei:corr/tei:date/@notAfter + | ./tei:desc/tei:choice/tei:reg/tei:date/@notAfter"/>. +</sch:assert> +</sch:rule> +<sch:rule context="tei:event[tei:desc/tei:date/@from] | tei:event[tei:desc/tei:choice/tei:corr/tei:date/@from] + | tei:event[tei:desc/tei:choice/tei:reg/tei:date/@from]"> +<sch:assert test="./@from = ./tei:desc/tei:date/@from | ./tei:desc/tei:choice/tei:corr/tei:date/@from + | ./tei:desc/tei:choice/tei:reg/tei:date/@from"> This <event> must have a @from attribute with the value <sch:value-of select="./tei:desc/tei:date/@from | ./tei:desc/tei:choice/tei:corr/tei:date/@from + | ./tei:desc/tei:choice/tei:reg/tei:date/@from"/>. +</sch:assert> +</sch:rule> +<sch:rule context="tei:event[tei:desc/tei:date/@to] | tei:event[tei:desc/tei:choice/tei:corr/tei:date/@to] + | tei:event[tei:desc/tei:choice/tei:reg/tei:date/@to]"> +<sch:assert test="./@to = ./tei:desc/tei:date/@to | ./tei:desc/tei:choice/tei:corr/tei:date/@to + | ./tei:desc/tei:choice/tei:reg/tei:date/@to"> This <event> must have a @to attribute with the value <sch:value-of select="./tei:desc/tei:date/@to | ./tei:desc/tei:choice/tei:corr/tei:date/@to + | ./tei:desc/tei:choice/tei:reg/tei:date/@to"/>. +</sch:assert> +</sch:rule>
Schematron
+<sch:rule context="//tei:ab//tei:event/tei:desc/tei:listRelation/tei:relation"> +<sch:report test="tei:desc">A <relation> element inside of an <event> element cannot take a <desc> element.</sch:report> +</sch:rule>
Content model
+<content>
+ <elementRef key="desc" minOccurs="1"
+  maxOccurs="1"/>
+</content>
+    ⚓
Schema Declaration
+element event
+{
+   att.global.attributes,
+   att.datable.attributes,
+   att.editLike.attributes,
+   att.typed.attributes,
+   att.naming.attributes,
+   att.sortable.attributes,
+   att.locatable.attributes,
+   desc
+}⚓

1.28. <fileDesc>

<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]
Moduleheader
Attributes
Contained by
header: teiHeader
May contain
header: editionStmt publicationStmt seriesStmt sourceDesc titleStmt
Note

Each <fileDesc> 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"
+  preserveOrder="true">
+  <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="1" maxOccurs="unbounded"/>
+  <elementRef key="sourceDesc"
+   minOccurs="1" maxOccurs="1"/>
+ </sequence>
+</content>
+    ⚓
Schema Declaration
+element fileDesc
+{
+   att.global.attributes,
+   ( titleStmt, editionStmt, publicationStmt, seriesStmt+, sourceDesc )
+}⚓

1.29. <funder>

<funder> (funding body) specifies the name of an individual, institution, or organization responsible for the funding of a project or text. [2.2.1. The Title Statement]
Moduleheader
Attributes
Contained by
header: titleStmt
May containCharacter data only
Note

Within the <titleStmt>, funding bodies are identified with the <funder> element. If multiple funding bodies are relevant, then each one receives a separate <funder> element.

Example
<funder>The National Endowment for the Humanities, an independent federal agency</funder> +<funder>Directorate General XIII of the Commission of the European Communities</funder> +<funder>The Andrew W. Mellon Foundation</funder> +<funder>The Social Sciences and Humanities Research Council of Canada</funder>
Content model
+<content>
+ <textNode/>
+</content>
+    ⚓
Schema Declaration
+element funder
+{
+   att.global.attributes,
+   att.canonical.attributes,
+   att.datable.attributes,
+   text
+}⚓

1.30. <head>

<head> (heading) contains any type of heading, for example the title of a section, or the heading of a list, glossary, manuscript description, etc. [4.2.1. Headings and Trailers]
Modulecore
Attributes
Contained by
core: listBibl
May contain
core: bibl choice corr date listBibl name note num orig ptr ref reg rs sic title
namesdates: listRelation orgName persName placeName
character data
Note

When the child of <sourceDesc>, <head> must contain "Sources for the Data in this Born Digital Prosopography". When the child of <back>, <head> must contain "Works Cited".

ExampleThe 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>
ExampleWhen 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>
ExampleThe <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:sourceDesc//tei:head"> +<sch:assert test="normalize-space(.) = 'Sources for the Data in this Born Digital Prosopography'"> A <head> element inside the <sourceDesc> must contain the text node: + "Sources for the Data in this Born Digital Prosopography". </sch:assert> +</sch:rule> +<sch:rule context="tei:back//tei:head"> +<sch:assert test="normalize-space(.) = 'Works Cited'"> A <head> element inside + the <back> must contain the text node: "Works Cited". </sch:assert> +</sch:rule>
Content model
+<content>
+ <alternate minOccurs="0"
+  maxOccurs="unbounded">
+  <textNode/>
+  <elementRef key="lg"/>
+  <classRef key="model.gLike"/>
+  <classRef key="model.phrase"/>
+  <classRef key="model.inter"/>
+  <classRef key="model.lLike"/>
+  <classRef key="model.global"/>
+ </alternate>
+</content>
+    ⚓
Schema Declaration
+element head
+{
+   att.global.attributes,
+   att.typed.attributes,
+   att.placement.attributes,
+   att.written.attributes,
+   (
+      text
+    | lg
+    | model.gLike
+    | model.phrase
+    | model.inter
+    | model.lLike
+    | model.global
+   )*
+}⚓

1.31. <idno>

<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. [13.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]
Moduleheader
Attributes
type
StatusOptional
Datatypeteidata.enumerated
Contained by
core: biblScope
header: idno publicationStmt seriesStmt
linking: ab
May contain
header: idno
character data
Note

This customization requires properly formatted identifiers for each TEI document and for each factoid. It ensures the alignment of the document cool-URI, the document name (always a number), and the factoid cool-URI.

In the <teiHeader>, an <idno> requires a @type attribute indicating that it is a "URI". It must also have the text node "https://spear-prosop.org/{\d}/tei", where {\d} is a number that matches the number of the document name.

Each factoid also requires an <idno> with a @type attribute of "URI". It must contain the full cool-URI for that factoid. This URI is constructed using the <idno> from the <publicationStmt> and attaching to it the "-{\d}" from the @xml:id on the parent <ab>.

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:ab[ancestor::tei:body]/tei:idno"> +<sch:assert test="@type='URI'">An <idno> descendant of <ab> + requires a @type attribute with the value "URI".</sch:assert> +</sch:rule> +<sch:rule context="//tei:publicationStmt/tei:idno"> +<sch:assert test="@type='URI'">This <idno> + requires a @type attribute with the value "URI".</sch:assert> +</sch:rule> +<sch:rule context="//tei:seriesStmt/tei:idno"> +<sch:assert test="@type='URI'">This <idno> element + requires a @type attribute with the value "URI".</sch:assert> +</sch:rule>
Schematron
+<sch:rule context="//tei:publicationStmt/tei:idno[@type='URI']"> +<sch:let name="fileNo" + value="replace(document-uri(/), '[\D]', '')"/> +<sch:assert test=". = concat('https://spear-prosop.org/', $fileNo, '/tei')"> The text node of this <idno> must be "https://spear-prosop.org/<sch:value-of select="$fileNo"/>/tei". +</sch:assert> +</sch:rule>
Schematron
+<sch:rule context="tei:ab[ancestor::tei:body]/tei:idno"> +<sch:let name="factoidNo" + value="parent::tei:ab/@xml:id/substring-after(., 'factoid')"/> +<sch:assert test="contains(., concat(//tei:publicationStmt/tei:idno[@type]/substring-before(., + '/tei'), $factoidNo))">This factoid URI must be: "<sch:value-of select="concat(//tei:publicationStmt/tei:idno[@type]/substring-before(., '/tei'), + $factoidNo)"/>.</sch:assert> +</sch:rule>
Content model
+<content>
+ <alternate minOccurs="0"
+  maxOccurs="unbounded">
+  <textNode/>
+  <classRef key="model.gLike"/>
+  <elementRef key="idno"/>
+ </alternate>
+</content>
+    ⚓
Schema Declaration
+element idno { attribute type { text }?, ( text | model.gLike | idno )* }⚓

1.32. <langKnowledge>

<langKnowledge>
Modulenamesdates
Contained by
namesdates: person personGrp
May contain
core: note
namesdates: langKnown
Note

This customization constrains the child elements under <langKnowledge> to include only <langKnown> and <note>.

Content model
+<content>
+ <sequence minOccurs="1" maxOccurs="1"
+  preserveOrder="true">
+  <elementRef key="langKnown" minOccurs="1"
+   maxOccurs="1"/>
+  <elementRef key="note" minOccurs="1"
+   maxOccurs="1"/>
+ </sequence>
+</content>
+    ⚓
Schema Declaration
+element langKnowledge { langKnown, note }⚓

1.33. <langKnown>

<langKnown> (language known) summarizes the state of a person's linguistic competence, i.e., knowledge of a single language. [15.2.2. The Participant Description]
Modulenamesdates
Attributes
level
StatusOptional
Datatypeteidata.enumerated
Legal values are:
low
medium
high
Contained by
namesdates: langKnowledge
May contain
core: choice date name note num ptr ref rs title
namesdates: orgName persName placeName
character data
Note

This customization allows a closed list of values on the @level attribute ("low", "medium", and "high"). It also restricts the required @ana attribute to keyword URIs in the Syriac Taxonomy that pertain to languages.

Example
<langKnown tag="en-GB" level="H">British English</langKnown> +<langKnown tag="fr" level="M">French</langKnown>
Schematron
+<sch:rule context="//tei:langKnown/@ana"> +<sch:let name="anaTokens" + value="tokenize(., ' ')"/> +<sch:let name="ti" + value="doc('https://raw.githubusercontent.com/srophe/syriaca/master/documentation/indexes/taxonomyIndex-old.xml')"/> +<sch:let name="languageURIs" + value="$ti//listURI[@type = 'languages']/uri"/> +<sch:let name="errors" + value="for $i in $anaTokens return $i[not(. = $languageURIs)]"/> +<sch:assert test="every $i in $anaTokens satisfies $i = $languageURIs" + role="warning"> + <sch:value-of select="string-join($errors, ', ')"/>: URI(s) not in the Taxonomy. If you find no appropriate concept on the following list, + please choose a keyword of your own for the editors to consider: <sch:value-of select="string-join($languageURIs, '; ')"/>. +</sch:assert> +</sch:rule>
Content model
+<content>
+ <macroRef key="macro.phraseSeq.limited"/>
+</content>
+    ⚓
Schema Declaration
+element langKnown
+{
+   att.global.attributes,
+   att.datable.attributes,
+   att.editLike.attributes,
+   attribute level { "low" | "medium" | "high" }?,
+   macro.phraseSeq.limited
+}⚓

1.34. <licence>

<licence> contains information about a licence or other legal agreement applicable to the text. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduleheader
Attributes
Member of
model.availabilityPart
Contained by
header: availability
May contain
core: p
Note

The <license> element, child of <availability>, is used to specify the Creative Commons CC-BY license under which this record is made available. Some records may incorporate information from works under copyright (with permission), a fact which is also indicated with <license>.

Example
<licence target="http://www.nzetc.org/tm/scholarly/tei-NZETC-Help.html#licensing"> Licence: Creative Commons Attribution-Share Alike 3.0 New Zealand Licence +</licence>
Example
<availability> + <licence target="http://creativecommons.org/licenses/by/3.0/" +  notBefore="2013-01-01"> +  <p>The Creative Commons Attribution 3.0 Unported (CC BY 3.0) Licence +     applies to this document.</p> +  <p>The licence was added on January 1, 2013.</p> + </licence> +</availability>
Schematron
+<sch:rule context="//tei:licence/tei:p"> +<sch:assert test="normalize-space(.) = 'Distributed under a Creative Commons Attribution + 3.0 Unported License.'"> The <licence> element must contain <p> with the text: "Distributed under a Creative Commons Attribution 3.0 Unported License." +</sch:assert> +</sch:rule>
Content model
+<content>
+ <elementRef key="p" minOccurs="1"
+  maxOccurs="1"/>
+</content>
+    ⚓
Schema Declaration
+element licence
+{
+   att.global.attributes,
+   att.pointing.attributes,
+   att.datable.attributes,
+   p
+}⚓

1.35. <listBibl>

<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 15.3.2. Declarable Elements]
Modulecore
Attributes
Member of
model.biblLike
Contained by
core: corr head note orig p ref reg sic title
header: change sourceDesc
textstructure: back
May contain
core: bibl head
Note

The <listBibl> element must contain a <head> and at least one <bibl>.

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>
Content model
+<content>
+ <elementRef key="head" minOccurs="1"
+  maxOccurs="1"/>
+ <elementRef key="bibl" minOccurs="1"
+  maxOccurs="unbounded"/>
+</content>
+    ⚓
Schema Declaration
+element listBibl
+{
+   att.global.attributes,
+   att.sortable.attributes,
+   att.declarable.attributes,
+   att.typed.attributes,
+   head,
+   bibl+
+}⚓

1.36. <listEvent>

<listEvent>
Modulenamesdates
Contained by
linking: ab
May contain
namesdates: event
Content model
+<content>
+ <elementRef key="event" minOccurs="1"
+  maxOccurs="1"/>
+</content>
+    ⚓
Schema Declaration
+element listEvent { event }⚓

1.37. <listPerson>

<listPerson>
Modulenamesdates
Contained by
linking: ab
May contain
namesdates: person personGrp
Content model
+<content>
+ <alternate minOccurs="1" maxOccurs="1">
+  <elementRef key="person" minOccurs="1"
+   maxOccurs="1"/>
+  <elementRef key="personGrp" minOccurs="1"
+   maxOccurs="1"/>
+ </alternate>
+</content>
+    ⚓
Schema Declaration
+element listPerson { person | personGrp }⚓

1.38. <listRelation>

<listRelation> provides information about relationships identified amongst people, places, and organizations, either informally as prose or as formally expressed relation links. [13.3.2.3. Personal Relationships]
Modulenamesdates
Attributes
Member of
model.listLike
Contained by
core: corr desc head note orig p ref reg sic title
header: change sourceDesc
linking: ab
May contain
namesdates: relation
Note

SPEAR has three basic types of factoid data that are encoded using <listPerson>, <listEvent>, and <listRelation> elements. The TEI Guidelines allow the first two to nest inside <ab> while the last one is not. For uniformity and ease of encoding, SPEAR makes the <listRelation> element a part of the model class model.listLike so that it can function like other list elements and nest directly under the <ab> element. SPEAR also removes all attributes from the <listRelation> element and restricts the child elements to <relation>.

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
+{
+   att.global.attributes,
+   att.typed.attributes,
+   att.sortable.attributes,
+   relation+
+}⚓

1.39. <name>

<name> (name, proper noun) contains a proper noun or noun phrase. [3.6.1. Referring Strings]
Modulecore
Attributes
Member of
model.nameLike.agent
Contained by
core: author corr date editor head name note num orig p pubPlace publisher ref reg resp respStmt sic title
header: change edition
namesdates: langKnown orgName persName placeName
May contain
core: choice corr date name note num orig ptr ref reg rs sic title
namesdates: orgName persName placeName
character data
Note

This customization limits the vaules of @ref attributes on <name> as child of <titleStmt> to a Syriaca.org URI for project contributors.

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:titleStmt/tei:respStmt/tei:name"> +<sch:assert test="@ref"> A @ref attribute is required. +</sch:assert> +</sch:rule> +<sch:rule context="//tei:titleStmt/tei:respStmt/tei:name/@ref"> +<sch:let name="edsDoc" + value="doc('https://raw.githubusercontent.com/srophe/srophe-eXist-app/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 this @ref attribute include: +<sch:value-of select="string-join($refValues, ' | ')"/>. +</sch:assert> +</sch:rule>
Content model
+<content>
+ <macroRef key="macro.phraseSeq"/>
+</content>
+    ⚓
Schema Declaration
+element name
+{
+   att.global.attributes,
+   att.personal.attributes,
+   att.datable.attributes,
+   att.editLike.attributes,
+   att.typed.attributes,
+   macro.phraseSeq
+}⚓

1.40. <nationality>

<nationality>
Modulenamesdates
Attributes
Contained by
namesdates: person personGrp
May contain
core: date note
namesdates: placeName
Note

The TEI name for the <nationality> element is problematic from a pre-Modern perspective. "Citizenship" would be preferable in one sense, yet could in many instances exclude subaltern people such as the enslaved. SPEAR uses the <nationality> element as a general category for people living under a particular jurisdiction.

This customization limits the attribute classes of the <nationality> element to att.datable.custom and att.datable.w3c and removes the <nationality> element from all model classes. It also requires exactly one <placeName> child and one <note> child and allows an optional <date> child.

Content model
+<content>
+ <sequence minOccurs="1" maxOccurs="1"
+  preserveOrder="true">
+  <elementRef key="placeName" minOccurs="1"
+   maxOccurs="1"/>
+  <elementRef key="date" minOccurs="0"
+   maxOccurs="1"/>
+  <elementRef key="note" minOccurs="1"
+   maxOccurs="1"/>
+ </sequence>
+</content>
+    ⚓
Schema Declaration
+element nationality
+{
+   att.datable.custom.attributes,
+   att.datable.w3c.attributes,
+   ( placeName, date?, note )
+}⚓

1.41. <note>

<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 9.3.5.4. Notes within Entries]
Modulecore
Attributes
ana
StatusOptional
Datatypeteidata.pointer
Legal values are:
#calculated
type
StatusOptional
Datatypeteidata.enumerated
Schematron
+<sch:rule context="tei:note[parent::tei:birth or parent::tei:death or parent::tei:education + or parent::tei:langKnowledge or parent::tei:nationality or parent::tei:occupation + or parent::tei:residence or parent::tei:socecStatus or parent::tei:state + or parent::tei:trait]"> +<sch:assert test="@type = 'desc'">This <note> must contain the + attribute @type="desc" and other <note> types are not allowed in this context. + Other types of notes (those dealing with "certainty") may appear as children of + the <ab> element as needed.</sch:assert> +</sch:rule>
Schematron
+<sch:rule context="tei:note[parent::tei:education | parent::tei:langKnowledge | parent::tei:nationality + | parent::tei:occupation | parent::tei:residence | parent::tei:socecStatus + | parent::tei:state | parent::tei:trait]"> +<sch:report test="./tei:date"> If you wish to apply a date to this factoid, you must use + date attributes (@when, @notBefore, @notAfter, @to, and/or @from) on the + parent of the <note> element. +</sch:report> +</sch:rule>
Legal values are:
desc
certainty
relatedEvent
subtype
StatusOptional
Datatypeteidata.enumerated
Schematron
+<sch:rule context="//tei:note[@type='certainty']"> +<sch:assert test="@subtype"> A <note> element with @type="certainty" requires a @subtype. +</sch:assert> +</sch:rule>
Legal values are:
incerta
dubia
errata
Member of
model.noteLike
Contained by
core: author corr date editor head name note num orig p pubPlace publisher ref reg resp respStmt sic title
header: change edition
linking: ab
namesdates: birth death education langKnowledge langKnown nationality occupation orgName persName placeName residence socecStatus state trait
textstructure: text
May contain
core: bibl choice corr date listBibl name note num orig p ptr ref reg rs sic title
namesdates: listRelation orgName persName placeName
character data
Note

SPEAR factoids contain <note> elements that allow the encoder to offer a more prose-oriented description of the data that they have derived from the source they are analyzing. The content of the <note> is what human users encounter when using the HTML serialization of the data. This customization constrains the use of this element to ensure that the data marked up inside the <note> agrees with the more data-oriented encoding found elsewhere in the factoid.

ExampleIn 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.
ExampleThe 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:note[parent::tei:birth and preceding-sibling::tei:placeName]"> +<sch:assert test="tei:persName">The <note> element in a birth place factoid + must contain a <persName>.</sch:assert> +<sch:assert test="tei:placeName">The <note> element in a birth place factoid + must contain a <placeName>.</sch:assert> +</sch:rule> +<sch:rule context="tei:note[parent::tei:birth and preceding-sibling::tei:date]"> +<sch:assert test="tei:persName">The <note> element in a birth date factoid + must contain a <persName>.</sch:assert> +</sch:rule> +<sch:rule context="tei:note[parent::tei:nationality and preceding-sibling::tei:placeName]"> +<sch:assert test="tei:persName">The <note> element in a citizenship factoid + must contain a <persName>.</sch:assert> +<sch:assert test="tei:placeName">The <note> element in a citizenship factoid + must contain a <placeName>.</sch:assert> +</sch:rule> +<sch:rule context="tei:note[parent::tei:death and preceding-sibling::tei:placeName]"> +<sch:assert test="tei:persName">The <note> element in a death place factoid + must contain a <persName>.</sch:assert> +<sch:assert test="tei:placeName">The <note> element in a birth place factoid + must contain a <placeName>.</sch:assert> +</sch:rule> +<sch:rule context="tei:note[parent::tei:education]"> +<sch:assert test="tei:persName">The <note> element in an education factoid + must contain a <persName>.</sch:assert> +</sch:rule> +<sch:rule context="tei:note[parent::tei:death and preceding-sibling::tei:date]"> +<sch:assert test="tei:persName">The <note> element in a death date factoid + must contain a <persName>.</sch:assert> +</sch:rule> +<sch:rule context="tei:note[parent::tei:occupation]"> +<sch:assert test="tei:persName">The <note> element in an occupation factoid + must contain a <persName>.</sch:assert> +</sch:rule> +<sch:rule context="tei:note[parent::tei:residence and preceding-sibling::tei:placeName]"> +<sch:assert test="tei:persName">The <note> element in a residence factoid must + contain a <persName>.</sch:assert> +<sch:assert test="tei:placeName">The <note> element in a residence factoid + must contain a <placeName>.</sch:assert> +</sch:rule> +<sch:rule context="tei:note[parent::tei:socecStatus]"> +<sch:assert test="tei:persName">The <note> element in a socioeconomic status + factoid must contain a <persName>.</sch:assert> +</sch:rule> +<sch:rule context="tei:note[parent::tei:langKnowledge and preceding-sibling::tei:langKnown]"> +<sch:assert test="tei:persName">The <note> element in a language-known factoid + must contain a <persName>.</sch:assert> +</sch:rule> +<sch:rule context="tei:note[parent::tei:trait]"> +<sch:assert test="tei:persName">The <note> element inside the <trait> + element must contain a <persName>.</sch:assert> +</sch:rule> +<sch:rule context="tei:note[parent::tei:state]"> +<sch:assert test="tei:persName">The <note> element inside the <state> + element must contain a <persName>.</sch:assert> +</sch:rule> +<sch:rule context="tei:note[parent::tei:reg and preceding-sibling::tei:date]"> +<sch:assert test="@ana">This <note> element requires an @ana + attribute.</sch:assert> +</sch:rule>
Schematron
+<sch:rule context="tei:note[parent::tei:birth | parent::tei:death | parent::tei:education + | parent::tei:langKnowledge | parent::tei:nationality | parent::tei:occupation + | parent::tei:residence | parent::tei:socecStatus | parent::tei:state + | parent::tei:trait]/tei:persName[1]/@ref"> +<sch:assert test=". = ancestor::tei:person/tei:persName/@ref | ancestor::tei:personGrp/tei:persName/@ref"> The URI in this @ref attribute and the URI in the @ref attribute on the <persName> that + is the child of <person> must match. +</sch:assert> +</sch:rule> +<sch:rule context="tei:note[parent::tei:birth | parent::tei:death | parent::tei:nationality + | parent::tei:residence]/tei:placeName[1]/@ref"> +<sch:report test=". = ancestor::tei:person/tei:placeName/@ref | ancestor::tei:personGrp/tei:placeName/@ref"> The URI in this @ref attribute and the URI in the @ref attribute on the <placeName> that + is the child of <person> must match. +</sch:report> +</sch:rule>
Schematron
+<sch:rule context="tei:note[parent::tei:reg and preceding-sibling::tei:date]"> +<sch:assert test="normalize-space(.) = 'This regularized date was calculated by the + SPEAR editor from a non-calendrical dating system such as regnal years, + etc.'"> The only note allowed in this context must contain the following text: "This + regularized date was calculated by the SPEAR editor from a non-calendrical dating + system such as regnal years, etc." </sch:assert> +</sch:rule>
Content model
+<content>
+ <macroRef key="macro.specialPara"/>
+</content>
+    ⚓
Schema Declaration
+element note
+{
+   att.global.attribute.xmlid,
+   att.global.attribute.n,
+   att.global.attribute.xmllang,
+   att.global.attribute.xmlbase,
+   att.global.attribute.xmlspace,
+   att.global.rendition.attribute.rend,
+   att.global.rendition.attribute.style,
+   att.global.rendition.attribute.rendition,
+   att.global.linking.attribute.corresp,
+   att.global.linking.attribute.synch,
+   att.global.linking.attribute.sameAs,
+   att.global.linking.attribute.copyOf,
+   att.global.linking.attribute.next,
+   att.global.linking.attribute.prev,
+   att.global.linking.attribute.exclude,
+   att.global.linking.attribute.select,
+   att.global.responsibility.attribute.cert,
+   att.global.responsibility.attribute.resp,
+   att.global.source.attribute.source,
+   att.placement.attributes,
+   att.pointing.attributes,
+   att.written.attributes,
+   attribute ana { "#calculated" }?,
+   attribute type { "desc" | "certainty" | "relatedEvent" }?,
+   attribute subtype { "incerta" | "dubia" | "errata" }?,
+   macro.specialPara
+}⚓

1.42. <num>

<num> (number) contains a number, written in any form. [3.6.3. Numbers and Measures]
Modulecore
Attributes
typeindicates the type of numeric value.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
cardinal
absolute number, e.g. 21, 21.5
ordinal
ordinal number, e.g. 21st
fraction
fraction, e.g. one half or three-quarters
percentage
a percentage
Note

If a different typology is desired, other values can be used for this attribute.

valuesupplies the value of the number in standard form.
StatusOptional
Datatypeteidata.numeric
Valuesa numeric value.
Note

The standard form used is defined by the TEI datatype teidata.numeric.

Member of
model.measureLike
Contained by
core: author corr date editor head name note num orig p pubPlace publisher ref reg resp sic title
header: change edition
namesdates: langKnown orgName persName placeName
May contain
core: choice corr date name note num orig ptr ref reg rs sic title
namesdates: orgName persName placeName
character data
Note

Detailed analyses of quantities and units of measure in historical documents may also use the feature structure mechanism described in chapter 18. Feature Structures. The <num> element is intended for use in simple applications.

Example
<p>I reached <num type="cardinal" value="21">twenty-one</num> on + my <num type="ordinal" value="21">twenty-first</num> birthday</p> +<p>Light travels at <num value="3E10">3×10<hi rend="sup">10</hi> + </num> cm per second.</p>
Content model
+<content>
+ <macroRef key="macro.phraseSeq"/>
+</content>
+    ⚓
Schema Declaration
+element num
+{
+   att.global.attributes,
+   att.typed.attribute.subtype,
+   att.ranging.attributes,
+   attribute type { "cardinal" | "ordinal" | "fraction" | "percentage" }?,
+   attribute value { text }?,
+   macro.phraseSeq
+}⚓

1.43. <occupation>

<occupation> (occupation) contains an informal description of a person's trade, profession or occupation. [15.2.2. The Participant Description]
Modulenamesdates
Attributes
ana
Derived fromatt.global.analytic
StatusRequired
Schematron
+<sch:rule context="//tei:occupation/@ana"> +<sch:let name="anaTokens" + value="tokenize(., ' ')"/> +<sch:let name="ti" + value="doc('https://raw.githubusercontent.com/srophe/syriaca/master/documentation/indexes/taxonomyIndex-old.xml')"/> +<sch:let name="occupationURIs" + value="$ti//listURI[@type = 'occupations']/uri"/> +<sch:let name="errors" + value="for $i in $anaTokens return $i[not(. = $occupationURIs)]"/> +<sch:assert test="every $i in $anaTokens satisfies $i = $occupationURIs" + role="warning"> + <sch:value-of select="string-join($errors, ', ')"/>: URI(s) not in the Taxonomy. If you find no appropriate concept on the following list, + please choose a keyword of your own for the editors to consider: <sch:value-of select="string-join($occupationURIs, '; ')"/>.</sch:assert> +</sch:rule>
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
schemeindicates the classification system or taxonomy in use, for example by supplying the identifier of a <taxonomy> element, or pointing to some other resource.
StatusOptional
Datatypeteidata.pointer
codeidentifies an occupation code defined within the classification system or taxonomy defined by the scheme attribute.
StatusOptional
Datatypeteidata.pointer
Contained by
namesdates: person personGrp
May contain
core: note
Note

This customization restricts the attribute classes of <occupation> to att.datable.w3c and att.global.analytic. If more precise dating is required for a SPEAR factoid, the encoder should use the <date> element.

It only allows <note> as a child element and it restricts the required @ana attribute to keyword URIs in the Syriac Taxonomy that pertain to occupations.

Example
<occupation>accountant</occupation>
Example
<occupation scheme="#occupationtaxonomy" + code="#acc">accountant</occupation>
Content model
+<content>
+ <elementRef key="note" minOccurs="1"
+  maxOccurs="1"/>
+</content>
+    ⚓
Schema Declaration
+element occupation
+{
+   att.datable.w3c.attributes,
+   attribute ana { list { + } },
+   attribute scheme { text }?,
+   attribute code { text }?,
+   note
+}⚓

1.44. <orgName>

<orgName> (organization name) contains an organizational name. [13.2.2. Organizational Names]
Modulenamesdates
Attributes
Member of
model.nameLike.agent
Contained by
core: author corr date desc editor head name note num orig p pubPlace publisher ref reg resp respStmt sic title
header: change edition
namesdates: langKnown orgName persName placeName
May contain
core: choice corr date name note num orig ptr ref reg rs sic title
namesdates: orgName persName placeName
character data
Example
About a year back, a question of considerable interest was agitated in the <orgName key="PAS1" type="voluntary"> + <placeName key="PEN">Pennsyla.</placeName> Abolition Society +</orgName> [...]
Content model
+<content>
+ <macroRef key="macro.phraseSeq"/>
+</content>
+    ⚓
Schema Declaration
+element orgName
+{
+   att.global.attributes,
+   att.datable.attributes,
+   att.editLike.attributes,
+   att.personal.attributes,
+   att.typed.attributes,
+   macro.phraseSeq
+}⚓

1.45. <orig>

<orig> (original form) contains a reading which is marked as following the original, rather than being normalized or corrected. [3.5.2. Regularization and Normalization 12. Critical Apparatus]
Modulecore
Member of
model.choicePart model.pPart.transcriptional
Contained by
core: author choice corr date editor head name note num orig p pubPlace publisher ref reg sic title
header: change edition
namesdates: orgName persName placeName
May contain
core: bibl choice corr date listBibl name note num orig ptr ref reg rs sic title
namesdates: listRelation orgName persName placeName
character data
ExampleIf all that is desired is to call attention to the original version in the copy text, <orig> may be used alone:
<l>But this will be a <orig>meere</orig> confusion</l> +<l>And hardly shall we all be <orig>vnderstoode</orig> +</l>
ExampleMore usually, an <orig> will be combined with a regularized form within a <choice> element:
<l>But this will be a <choice> +  <orig>meere</orig> +  <reg>mere</reg> + </choice> confusion</l> +<l>And hardly shall we all be <choice> +  <orig>vnderstoode</orig> +  <reg>understood</reg> + </choice> +</l>
Content model
+<content>
+ <macroRef key="macro.paraContent"/>
+</content>
+    ⚓
Schema Declaration
+element orig { macro.paraContent }⚓

1.46. <p>

<p> (paragraph) marks paragraphs in prose. [3.1. Paragraphs 7.2.5. Speech Contents]
Modulecore
Attributes
Member of
model.pLike
Contained by
core: note
header: availability change editorialDecl licence
May contain
core: bibl choice corr date listBibl name note num orig ptr ref reg rs sic title
namesdates: listRelation orgName persName placeName
character data
Example
<p>Hallgerd was outside. <q>There is blood on your axe,</q> she said. <q>What have you +   done?</q> +</p> +<p> + <q>I have now arranged that you can be married a second time,</q> replied Thjostolf. +</p> +<p> + <q>Then you must mean that Thorvald is dead,</q> she said. +</p> +<p> + <q>Yes,</q> said Thjostolf. <q>And now you must think up some plan for me.</q> +</p>
Schematron
+<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>
Schematron
+<sch:report test="(ancestor::tei:l or ancestor::tei:lg) and not( ancestor::tei:floatingText + |parent::tei:figure |parent::tei:note )"> Abstract model violation: Lines may not contain higher-level structural elements such as div, p, or ab, unless p is a child of figure or note, or is a descendant of floatingText. +</sch:report>
Content model
+<content>
+ <macroRef key="macro.paraContent"/>
+</content>
+    ⚓
Schema Declaration
+element p
+{
+   att.global.attributes,
+   att.declaring.attributes,
+   att.fragmentable.attributes,
+   att.written.attributes,
+   macro.paraContent
+}⚓

1.47. <persName>

<persName> (personal name) contains a proper noun or proper-noun phrase referring to a person, possibly including one or more of the person's forenames, surnames, honorifics, added names, etc. [13.2.1. Personal Names]
Modulenamesdates
Attributes
ref
StatusRequired
Datatypeteidata.pointer
Schematron
+<sch:rule context="//tei:text//tei:persName/@ref"> +<sch:let name="personIndex" + value="doc('https://raw.githubusercontent.com/srophe/syriaca/master/documentation/indexes/persons.xml')"/> +<sch:let name="personURIs" + value="$personIndex//tei:person/@ref"/> +<sch:let name="error" value="."/> +<sch:report test="contains(., ' ')" + role="error">This @ref may contain only one URI.</sch:report> +<sch:assert test="matches(., concat('http://syriaca.org/person/', '\d+'))" + role="error"> The @ref attribute must take a Syriaca.org person URI which reqires + the form 'http://syriaca.org/person/{\d+}' (where {\d+} is a number). +</sch:assert> +<sch:assert test=" every $i in . satisfies $i = $personURIs" + role="warning"> + <sch:value-of select="$error"/> is not currently in use. + Note that all person URIs take the form 'http://syriaca.org/person/{\d+}' + (where {\d+} is a number). If a URI is not current available, replace the number portion of the URI with + "#" followed without a space by a number that you use consistently when encoding information + about that person. +</sch:assert> +</sch:rule>
Member of
model.nameLike.agent
Contained by
core: author corr date desc editor head name note num orig p pubPlace publisher ref reg resp respStmt sic title
header: change edition
namesdates: langKnown orgName persName person personGrp placeName
May contain
core: choice corr date name note num orig ptr ref reg rs sic title
namesdates: orgName persName placeName
character data
Note

This customization requires <persName> to have a @ref attribute that points to a Syriaca.org authority file for a person.

Example
<persName> + <forename>Edward</forename> + <forename>George</forename> + <surname type="linked">Bulwer-Lytton</surname>, <roleName>Baron Lytton of + <placeName>Knebworth</placeName> + </roleName> +</persName>
Content model
+<content>
+ <macroRef key="macro.phraseSeq"/>
+</content>
+    ⚓
Schema Declaration
+element persName
+{
+   att.datable.w3c.attributes,
+   attribute ref { text },
+   macro.phraseSeq
+}⚓

1.48. <person>

<person> (person) provides information about an identifiable individual, for example a participant in a language interaction, or a person referred to in a historical source. [13.3.2. The Person Element 15.2.2. The Participant Description]
Modulenamesdates
Attributes
rolespecifies a primary role or classification for the person.
StatusOptional
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
Note

Values for this attribute may be locally defined by a project, using arbitrary keywords such as artist, employer, author, relative, or servant, each of which should be associated with a definition. Such local definitions will typically be provided by a <valList> element in the project schema specification.

sexspecifies the sex of the person.
StatusOptional
Datatype1–∞ occurrences of teidata.sex separated by whitespace
Note

Values for this attribute may be defined locally by a project, or they may refer to an external standard.

genderspecifies the gender of the person.
StatusOptional
Datatype1–∞ occurrences of teidata.gender separated by whitespace
Note

Values for this attribute may be defined locally by a project, or they may refer to an external standard.

agespecifies an age group for the person.
StatusOptional
Datatypeteidata.enumerated
Note

Values for this attribute may be locally defined by a project, using arbitrary keywords such as infant, child, teen, adult, or senior, each of which should be associated with a definition. Such local definitions will typically be provided by a <valList> element in the project schema specification.

Contained by
namesdates: listPerson
May contain
namesdates: birth death education langKnowledge nationality occupation persName residence socecStatus state trait
Note

The <person> element contains person factoid data. This customization requires the proper structure for that data. The first child of <person> must be a self-closing <persName> element with a @ref attribute containing a URIs pointing to Syriaca.org authority file for a person. The next child element must be one of the following: <birth>, <death>, <education>, <langKnown>, <nationality>, <occupation>, <residence>, <socecStatus>, <state>, or <trait>.

Example
<person sex="F" age="adult"> + <p>Female respondent, well-educated, born in Shropshire UK, 12 Jan 1950, of unknown occupation. Speaks French fluently. Socio-Economic +   status B2.</p> +</person>
Example
<person sex="intersex" role="god" + age="immortal"> + <persName>Hermaphroditos</persName> + <persName xml:lang="grc">Ἑρμαφρόδιτος</persName> +</person>
Example
<person xml:id="Ovi01" sex="M" role="poet"> + <persName xml:lang="en">Ovid</persName> + <persName xml:lang="la">Publius Ovidius Naso</persName> + <birth when="-0044-03-20"> 20 March 43 BC <placeName> +   <settlement type="city">Sulmona</settlement> +   <country key="IT">Italy</country> +  </placeName> + </birth> + <death notBefore="0017" notAfter="0018">17 or 18 AD <placeName> +   <settlement type="city">Tomis (Constanta)</settlement> +   <country key="RO">Romania</country> +  </placeName> + </death> +</person>
ExampleThe following exemplifies an adaptation of the vCard standard to indicate an unknown gender for a fictional character.
<person xml:id="ariel" gender="U"> + <persName>Ariel</persName> + <note>Character in <title level="m">The Tempest</title>.</note> +</person>
Content model
+<content>
+ <alternate minOccurs="1" maxOccurs="1">
+  <elementRef key="persName" minOccurs="1"
+   maxOccurs="1"/>
+  <sequence minOccurs="1" maxOccurs="1"
+   preserveOrder="true">
+   <elementRef key="persName" minOccurs="1"
+    maxOccurs="1"/>
+   <elementRef key="birth" minOccurs="1"
+    maxOccurs="1"/>
+  </sequence>
+  <sequence minOccurs="1" maxOccurs="1"
+   preserveOrder="true">
+   <elementRef key="persName" minOccurs="1"
+    maxOccurs="1"/>
+   <elementRef key="death" minOccurs="1"
+    maxOccurs="1"/>
+  </sequence>
+  <sequence minOccurs="1" maxOccurs="1"
+   preserveOrder="true">
+   <elementRef key="persName" minOccurs="1"
+    maxOccurs="1"/>
+   <elementRef key="education"
+    minOccurs="1" maxOccurs="1"/>
+  </sequence>
+  <sequence minOccurs="1" maxOccurs="1"
+   preserveOrder="true">
+   <elementRef key="persName" minOccurs="1"
+    maxOccurs="1"/>
+   <elementRef key="langKnowledge"
+    minOccurs="1" maxOccurs="1"/>
+  </sequence>
+  <sequence minOccurs="1" maxOccurs="1"
+   preserveOrder="true">
+   <elementRef key="persName" minOccurs="1"
+    maxOccurs="1"/>
+   <elementRef key="nationality"
+    minOccurs="0" maxOccurs="1"/>
+  </sequence>
+  <sequence minOccurs="1" maxOccurs="1"
+   preserveOrder="true">
+   <elementRef key="persName" minOccurs="1"
+    maxOccurs="1"/>
+   <elementRef key="occupation"
+    minOccurs="1" maxOccurs="1"/>
+  </sequence>
+  <sequence minOccurs="1" maxOccurs="1"
+   preserveOrder="true">
+   <elementRef key="persName" minOccurs="1"
+    maxOccurs="1"/>
+   <elementRef key="residence"
+    minOccurs="1" maxOccurs="1"/>
+  </sequence>
+  <sequence minOccurs="1" maxOccurs="1"
+   preserveOrder="true">
+   <elementRef key="persName" minOccurs="1"
+    maxOccurs="1"/>
+   <elementRef key="socecStatus"
+    minOccurs="0" maxOccurs="1"/>
+  </sequence>
+  <sequence minOccurs="1" maxOccurs="1"
+   preserveOrder="true">
+   <elementRef key="persName" minOccurs="1"
+    maxOccurs="1"/>
+   <elementRef key="state" minOccurs="1"
+    maxOccurs="1"/>
+  </sequence>
+  <sequence minOccurs="1" maxOccurs="1"
+   preserveOrder="true">
+   <elementRef key="persName" minOccurs="1"
+    maxOccurs="1"/>
+   <elementRef key="trait" minOccurs="0"
+    maxOccurs="1"/>
+  </sequence>
+ </alternate>
+</content>
+    ⚓
Schema Declaration
+element person
+{
+   attribute role { list { + } }?,
+   attribute sex { list { + } }?,
+   attribute gender { list { + } }?,
+   attribute age { text }?,
+   (
+      persName
+    | ( persName, birth )
+    | ( persName, death )
+    | ( persName, education )
+    | ( persName, langKnowledge )
+    | ( persName, nationality? )
+    | ( persName, occupation )
+    | ( persName, residence )
+    | ( persName, socecStatus? )
+    | ( persName, state )
+    | ( persName, trait? )
+   )
+}⚓

1.49. <personGrp>

<personGrp> (personal group) describes a group of individuals treated as a single person for analytic purposes. [15.2.2. The Participant Description]
Modulenamesdates
Attributes
sexspecifies the sex of the participant group.
StatusOptional
Datatype1–∞ occurrences of teidata.sex separated by whitespace
Note

Values for this attribute may be defined locally by a project, or they may refer to an external standard.

genderspecifies the gender of the participant group.
StatusOptional
Datatype1–∞ occurrences of teidata.gender separated by whitespace
Note

Values for this attribute may be defined locally by a project, or they may refer to an external standard.

Contained by
namesdates: listPerson
May contain
core: ptr
namesdates: education langKnowledge nationality occupation persName residence socecStatus state trait
Note

May contain a prose description organized as paragraphs, or any sequence of demographic elements in any combination.

The global xml:id attribute should be used to identify each speaking participant in a spoken text if the who attribute is specified on individual utterances.

Example
<personGrp xml:id="pg1" role="audience" + sex="mixed" size="approx 50"/>
Content model
+<content>
+ <alternate minOccurs="1" maxOccurs="1">
+  <sequence minOccurs="1" maxOccurs="1">
+   <elementRef key="persName" minOccurs="1"
+    maxOccurs="1"/>
+   <elementRef key="ptr" minOccurs="1"
+    maxOccurs="1"/>
+  </sequence>
+  <sequence minOccurs="1" maxOccurs="1">
+   <elementRef key="persName" minOccurs="1"
+    maxOccurs="1"/>
+   <elementRef key="education"
+    minOccurs="1" maxOccurs="1"/>
+  </sequence>
+  <sequence minOccurs="1" maxOccurs="1">
+   <elementRef key="persName" minOccurs="1"
+    maxOccurs="1"/>
+   <elementRef key="nationality"
+    minOccurs="0" maxOccurs="1"/>
+  </sequence>
+  <sequence minOccurs="1" maxOccurs="1">
+   <elementRef key="persName" minOccurs="1"
+    maxOccurs="1"/>
+   <elementRef key="residence"
+    minOccurs="1" maxOccurs="1"/>
+  </sequence>
+  <sequence minOccurs="1" maxOccurs="1">
+   <elementRef key="persName" minOccurs="1"
+    maxOccurs="1"/>
+   <elementRef key="occupation"
+    minOccurs="1" maxOccurs="1"/>
+  </sequence>
+  <sequence minOccurs="1" maxOccurs="1">
+   <elementRef key="persName" minOccurs="1"
+    maxOccurs="1"/>
+   <elementRef key="langKnowledge"
+    minOccurs="1" maxOccurs="1"/>
+  </sequence>
+  <sequence minOccurs="1" maxOccurs="1">
+   <elementRef key="persName" minOccurs="1"
+    maxOccurs="1"/>
+   <elementRef key="state" minOccurs="1"
+    maxOccurs="1"/>
+  </sequence>
+  <sequence minOccurs="1" maxOccurs="1">
+   <elementRef key="persName" minOccurs="1"
+    maxOccurs="1"/>
+   <elementRef key="trait" minOccurs="0"
+    maxOccurs="1"/>
+  </sequence>
+  <sequence minOccurs="1" maxOccurs="1">
+   <elementRef key="persName" minOccurs="1"
+    maxOccurs="1"/>
+   <elementRef key="socecStatus"
+    minOccurs="0" maxOccurs="1"/>
+  </sequence>
+ </alternate>
+</content>
+    ⚓
Schema Declaration
+element personGrp
+{
+   attribute sex { list { + } }?,
+   attribute gender { list { + } }?,
+   (
+      ( persName, ptr )
+    | ( persName, education )
+    | ( persName, nationality? )
+    | ( persName, residence )
+    | ( persName, occupation )
+    | ( persName, langKnowledge )
+    | ( persName, state )
+    | ( persName, trait? )
+    | ( persName, socecStatus? )
+   )
+}⚓

1.50. <placeName>

<placeName> (place name) contains an absolute or relative place name. [13.2.3. Place Names]
Modulenamesdates
Attributes
ref
StatusRequired
Datatypeteidata.pointer
Schematron
+<sch:rule context="//tei:text//tei:placeName/@ref"> +<sch:let name="placeIndex" + value="doc('https://raw.githubusercontent.com/srophe/syriaca/master/documentation/indexes/places.xml')"/> +<sch:let name="placeURIs" + value="$placeIndex//tei:place/@ref"/> +<sch:let name="error" value="."/> +<sch:report test="contains(., ' ')" + role="error">This @ref may contain only one URI.</sch:report> +<sch:assert test="matches(., concat('http://syriaca.org/place/', '\d+'))" + role="error"> The @ref attribute must take a Syriaca.org place URI which reqires + the form 'http://syriaca.org/place/{\d+}' (where {\d+} is a number). +</sch:assert> +<sch:assert test=" every $i in . satisfies $i = $placeURIs" + role="warning"> + <sch:value-of select="$error"/> is not currently in use. + Note that all properly formatted place URIs take the form 'http://syriaca.org/place/{\d+}' + (where {\d+} is a number). If a URI is not current available, replace the number portion of the URI with + "#" followed without a space by a number that you use consistently when encoding information + referring to that place. +</sch:assert> +</sch:rule>
Member of
model.placeNamePart
Contained by
core: author corr date desc editor head name note num orig p pubPlace publisher ref reg resp sic title
header: change edition
namesdates: birth death langKnown nationality orgName persName placeName residence
May contain
core: choice corr date name note num orig ptr ref reg rs sic title
namesdates: orgName persName placeName
character data
Note

This customization requires <placeName> to have a @ref attribute that points to a Syriaca.org authority file for a place.

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>
Content model
+<content>
+ <macroRef key="macro.phraseSeq"/>
+</content>
+    ⚓
Schema Declaration
+element placeName { attribute ref { text }, macro.phraseSeq }⚓

1.51. <profileDesc>

<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]
Moduleheader
Attributes
Contained by
header: teiHeader
May containEmpty element
Note

Although the content model permits it, it is rarely meaningful to supply multiple occurrences for any of the child elements of <profileDesc> unless these are documenting multiple texts.

Example
<profileDesc> + <langUsage> +  <language ident="fr">French</language> + </langUsage> + <textDesc n="novel"> +  <channel mode="w">print; part issues</channel> +  <constitution type="single"/> +  <derivation type="original"/> +  <domain type="art"/> +  <factuality type="fiction"/> +  <interaction type="none"/> +  <preparedness type="prepared"/> +  <purpose type="entertain" degree="high"/> +  <purpose type="inform" degree="medium"/> + </textDesc> + <settingDesc> +  <setting> +   <name>Paris, France</name> +   <time>Late 19th century</time> +  </setting> + </settingDesc> +</profileDesc>
Content model
+<content>
+ <classRef key="model.profileDescPart"
+  minOccurs="0" maxOccurs="unbounded"/>
+</content>
+    ⚓
Schema Declaration
+element profileDesc { att.global.attributes, model.profileDescPart* }⚓

1.52. <ptr>

<ptr> (pointer) defines a pointer to another location. [3.7. Simple Links and Cross-References 16.1. Links]
Modulecore
Attributes
target
StatusRequired
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
+<sch:rule context="tei:sourceDesc//tei:bibl[@type = 'primary']/tei:ptr/@target"> +<sch:let name="docURIno" + value="//tei:publicationStmt/tei:idno[@type]/substring-after(substring-before(., + '/tei'), 'spear-prosop.org/')"/> +<sch:assert test=". = concat('http://syriaca.org/work/', $docURIno) or starts-with(., + 'http://syriaca.org/bibl/')"> The @target attribute on a <ptr> element inside a <bibl> element + with @type="primary" takes limited values. It either must be + "http://syriaca.org/work/<sch:value-of select="$docURIno"/>" or + "http://syriaca.org/bibl/" followed by the corresponding Syriaca.org bibl URI + number. </sch:assert> +</sch:rule> +<sch:rule context="tei:sourceDesc//tei:bibl[@type = 'urn']/tei:ptr/@target"> +<sch:let name="docURIno" + value="//tei:publicationStmt/tei:idno[@type]/substring-after(substring-before(., + '/tei'), 'spear-prosop.org/')"/> +<sch:assert test="starts-with(., concat('urn:cts:syriacLit:nhsl', $docURIno, '.syriacCorpus'))"> The @target attribute on a <ptr> element inside a <bibl> element + with @type="urn" must begin either with "urn:cts:syriacLit:nhsl<sch:value-of select="$docURIno"/>.syriacCorpus" followed by the corresponding Syriac + Corpus URI number. </sch:assert> +</sch:rule> +<sch:rule context="//tei:body/tei:ab/tei:bibl[@type = 'urn']/tei:ptr/@target"> +<sch:let name="urnBase" + value="//tei:sourceDesc//tei:bibl[@type = 'urn']/tei:ptr/@target"/> +<sch:assert test="starts-with(., concat($urnBase, ':'))">URN in a <bibl> + element inside a SPEAR factoid must begin with URN in the <sourceDesc> + element of the <teiHeader>: "<sch:value-of select="$urnBase"/>:".</sch:assert> +</sch:rule> +<sch:rule context="//tei:body//tei:bibl[@type = 'primary']/tei:ptr/@target"> +<sch:assert test=". = //tei:sourceDesc//tei:bibl[@type = 'primary']/tei:ptr/@target"> The + @target attribute on the <ptr> element, "<sch:value-of select="."/>," is + not among the valid options contained in the <sourceDesc> element of the + <teiHeader>: (<sch:value-of select="string-join(//tei:sourceDesc//tei:bibl[@type = 'primary']/tei:ptr/@target, + '; ')"/>) </sch:assert> +</sch:rule>
Member of
model.ptrLike
Contained by
core: author bibl corr date editor head name note num orig p pubPlace publisher ref reg resp sic title
header: change edition
namesdates: langKnown orgName persName personGrp placeName
May containEmpty element
Note

This customization requires a <ptr> to have a @type attribute (indicating "primary", "secondary", or "URN") and a @target attribute. It also ensures that the @target attribute with primary and secondary sources indicates a Syriaca.org authority file for a work or a bibliographic item.

Example
<ptr target="#p143 #p144"/> +<ptr target="http://www.tei-c.org"/> +<ptr cRef="1.3.4"/>
Schematron
+<sch:report test="@target and @cRef">Only one of the + attributes @target and @cRef may be supplied on <sch:name/>.</sch:report>
Content model
+<content>
+ <empty/>
+</content>
+    ⚓
Schema Declaration
+element ptr { attribute target { list { + } }, empty }⚓

1.53. <pubPlace>

<pubPlace> (publication place) contains the name of the place where a bibliographic item was published. [3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Modulecore
Attributes
Contained by
core: bibl
May contain
core: choice corr date name note num orig ptr ref reg rs sic title
namesdates: orgName persName placeName
character data
Example
<publicationStmt> + <publisher>Oxford University Press</publisher> + <pubPlace>Oxford</pubPlace> + <date>1989</date> +</publicationStmt>
Content model
+<content>
+ <macroRef key="macro.phraseSeq"/>
+</content>
+    ⚓
Schema Declaration
+element pubPlace
+{
+   att.global.attributes,
+   att.naming.attributes,
+   macro.phraseSeq
+}⚓

1.54. <publicationStmt>

<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]
Moduleheader
Attributes
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).

Example
<publicationStmt> + <publisher>C. Muquardt </publisher> + <pubPlace>Bruxelles &amp; Leipzig</pubPlace> + <date when="1846"/> +</publicationStmt>
Example
<publicationStmt> + <publisher>Chadwyck Healey</publisher> + <pubPlace>Cambridge</pubPlace> + <availability> +  <p>Available under licence only</p> + </availability> + <date when="1992">1992</date> +</publicationStmt>
Example
<publicationStmt> + <publisher>Zea Books</publisher> + <pubPlace>Lincoln, NE</pubPlace> + <date>2017</date> + <availability> +  <p>This is an open access work licensed under a Creative Commons Attribution 4.0 International license.</p> + </availability> + <ptr target="http://digitalcommons.unl.edu/zeabook/55"/> +</publicationStmt>
Content model
+<content>
+ <sequence minOccurs="1" maxOccurs="1"
+  preserveOrder="true">
+  <elementRef key="authority" minOccurs="1"/>
+  <elementRef key="idno" minOccurs="1"/>
+  <elementRef key="availability"
+   minOccurs="1"/>
+  <elementRef key="date" minOccurs="1"/>
+ </sequence>
+</content>
+    ⚓
Schema Declaration
+element publicationStmt
+{
+   att.global.attributes,
+   ( authority, idno, availability, date )
+}⚓

1.55. <publisher>

<publisher> (publisher) provides the name of the organization responsible for the publication or distribution of a bibliographic item. [3.12.2.4. Imprint, Size of a Document, and Reprint Information 2.2.4. Publication, Distribution, Licensing, etc.]
Modulecore
Attributes
Contained by
core: bibl
May contain
core: choice corr date name note num orig ptr ref reg rs sic title
namesdates: orgName persName placeName
character data
Note

Use the full form of the name by which a company is usually referred to, rather than any abbreviation of it which may appear on a title page

Example
<imprint> + <pubPlace>Oxford</pubPlace> + <publisher>Clarendon Press</publisher> + <date>1987</date> +</imprint>
Content model
+<content>
+ <macroRef key="macro.phraseSeq"/>
+</content>
+    ⚓
Schema Declaration
+element publisher
+{
+   att.global.attributes,
+   att.canonical.attributes,
+   macro.phraseSeq
+}⚓

1.56. <ref>

<ref> (reference) defines a reference to another location, possibly modified by additional text or comment. [3.7. Simple Links and Cross-References 16.1. Links]
Modulecore
Attributes
Member of
model.ptrLike
Contained by
core: author corr date editor head name note num orig p pubPlace publisher ref reg resp sic title
header: change edition
namesdates: langKnown orgName persName placeName
May contain
core: bibl choice corr date listBibl name note num orig ptr ref reg rs sic title
namesdates: listRelation orgName persName placeName
character data
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:report test="@target and @cRef">Only one of the + attributes @target' and @cRef' may be supplied on <sch:name/> +</sch:report>
Content model
+<content>
+ <macroRef key="macro.paraContent"/>
+</content>
+    ⚓
Schema Declaration
+element ref
+{
+   att.cReferencing.attributes,
+   att.declaring.attributes,
+   att.global.attributes,
+   att.internetMedia.attributes,
+   att.pointing.attributes,
+   att.typed.attributes,
+   macro.paraContent
+}⚓

1.57. <reg>

<reg> (regularization) contains a reading which has been regularized or normalized in some sense. [3.5.2. Regularization and Normalization 12. Critical Apparatus]
Modulecore
Member of
model.choicePart model.pPart.transcriptional
Contained by
core: author choice corr date editor head name note num orig p pubPlace publisher ref reg sic title
header: change edition
namesdates: orgName persName placeName
May contain
core: bibl choice corr date listBibl name note num orig ptr ref reg rs sic title
namesdates: listRelation orgName persName placeName
character data
ExampleIf all that is desired is to call attention to the fact that the copy text has been regularized, <reg> may be used alone:
<q>Please <reg>knock</reg> if an <reg>answer</reg> is <reg>required</reg> +</q>
ExampleIt is also possible to identify the individual responsible for the regularization, and, using the <choice> and <orig> elements, to provide both the original and regularized readings:
<q>Please <choice> +  <reg resp="#LB">knock</reg> +  <orig>cnk</orig> + </choice> if an <choice> +  <reg>answer</reg> +  <orig>nsr</orig> + </choice> is <choice> +  <reg>required</reg> +  <orig>reqd</orig> + </choice> +</q>
Content model
+<content>
+ <macroRef key="macro.paraContent"/>
+</content>
+    ⚓
Schema Declaration
+element reg { macro.paraContent }⚓

1.58. <relation>

<relation> (relationship) describes any kind of relationship or linkage amongst a specified group of places, events, persons, objects or other items. [13.3.2.3. Personal Relationships]
Modulenamesdates
Attributes
ana
Derived fromatt.global.analytic
StatusRecommended
Schematron
+<sch:rule context="tei:ab/tei:listRelation/tei:relation/@ana"> +<sch:let name="anaTokens" + value="tokenize(., ' ')"/> +<sch:let name="ti" + value="doc('https://raw.githubusercontent.com/srophe/syriaca/master/documentation/indexes/taxonomyIndex-old.xml')"/> +<sch:let name="qrURIs" + value="$ti//listURI[@type = 'qualifier-relationship']//uri"/> +<sch:let name="errors" + value="for $i in $anaTokens return $i[not(. = $qrURIs)]"/> +<sch:assert test="every $i in $anaTokens satisfies $i = $qrURIs"> + <sch:value-of select="string-join($errors, ', ')"/>: URI(s) not in the Taxonomy. If you find no appropriate concept on the following list, + please choose a keyword of your own for the editors to consider: <sch:value-of select="string-join($qrURIs, '; ')"/>.</sch:assert> +</sch:rule> +<sch:rule context="tei:ab/tei:listEvent/tei:listRelation/tei:relation"> +<sch:report test="@ana">A <relation> element inside an event factoid cannot + have an @ana attribute.</sch:report> +</sch:rule>
Datatype0–∞ occurrences of teidata.enumerated separated by whitespace
ref(reference) provides an explicit means of locating a full definition or identity for the entity being named by means of one or more URIs.
Derived fromatt.canonical
StatusOptional
Schematron
+<sch:rule context="tei:ab[@subtype='relation']/tei:listRelation/tei:relation/@ref"> +<sch:let name="ti" + value="doc('https://raw.githubusercontent.com/srophe/syriaca/master/documentation/indexes/taxonomyIndex-old.xml')"/> +<sch:assert test=". = $ti//listURI[@type = 'relationships']//uri">Value must be one of the following from the Syriaca.org taxonomy: +<sch:value-of select="string-join($ti//listURI[@type = 'relationships']//uri, '; ')"/>.</sch:assert> +</sch:rule> +<sch:rule context="tei:ab[@subtype='event']/tei:listRelation/tei:relation/@ref"> +<sch:let name="ti" + value="doc('https://raw.githubusercontent.com/srophe/syriaca/master/documentation/indexes/taxonomyIndex-old.xml')"/> +<sch:assert test=". = $ti//listURI[@type = 'related-event']/uri">Value must be one of the following from the Syriaca.org taxonomy: +<sch:value-of select="string-join($ti//listURI[@type = 'related-event']/uri, '; ')"/>.</sch:assert> +</sch:rule>
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusRequired
Schematron
+<sch:rule context="tei:ab/tei:listEvent/tei:listRelation/tei:relation"> +<sch:assert test="@type = 'event'">A <relation> element inside an event factoid + must take a @type attribute with the value "event".</sch:assert> +</sch:rule> +<sch:rule context="tei:sourceDesc/tei:listRelation/tei:relation"> +<sch:assert test="@type = 'part'">A @type attribute with the value + "part" is required.</sch:assert> +</sch:rule>
Datatypeteidata.enumerated
activeidentifies the ‘active’ participants in a non-mutual relationship, or all the participants in a mutual one.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
mutualsupplies a list of participants amongst all of whom the relationship holds equally.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
namesupplies a name for the kind of relationship of which this is an instance.
StatusOptional
Schematron
+<sch:rule context="tei:sourceDesc/tei:listRelation/tei:relation/@name"> +<sch:assert test=". = 'dcterms:isPartOf'"> This <relation> element must have a @name attribute with a value of "dcterms:isPartOf". +</sch:assert> +</sch:rule> +<sch:rule context="tei:text//tei:relation"> +<sch:report test="/@name">A @name attribute cannot appear here.</sch:report> +</sch:rule>
Datatypeteidata.enumerated
passiveidentifies the ‘passive’ participants in a non-mutual relationship.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Contained by
namesdates: listRelation
May contain
core: desc
Note

The <relation> element is used for personal relationships and constitutes one of the three main data types in SPEAR. When SPEAR encodes straight relationships, they appear in a relationship factoid (tei:ab[@subtype="relation"]/tei:listRelation/tei:relation). Relationships can also appear inside an event factoid in cases where an event creates a relationship, i.e. a wedding is an event that created a spousal relationship. In such cases, SPEAR encodes this relationship inside the event factoid. In addition to these personal relationships, the <relation> element is also used to encode relationships between closely related events. The <relation> element is also used in the <teiHeader>.

In the context of personal relationships, this customization constrains the @ref, @ana, @active, @passive, and @mutual attributes. A @ref attribute is required and must contain a URI pointing to a personal relationship in the Syriac Taxonomy. An @ana attribute is optional but when used must contain a URI pointing to a qualifier relationship in the Syriac Taxonomy, i.e. a sibling relationship might be qualified as a step-sibling relationship using @ana. For mutual relationship where each participant has the same relationship to the other (i.e. spousal), a @mutual attribute is used with all of the participants in that relationship listed. In the case of a directed relationship (i.e. where person X is the parent of person Y) both the @active and @passive attributes are used. The values allowed on the @active, @passive, and @mutual attributes are URIs pointing to Syriaca.org authority files for persons.

In the context of relationships between events, this customization only allows appropriate values on @ref while excluding @ana, @active, and @passive attributes.

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:ab[@subtype='relation']/tei:listRelation/tei:relation | tei:ab[@subtype='event']/tei:listEvent/tei:event/tei:desc/tei:listRelation/tei:relation"> +<sch:let name="ti" + value="doc('https://raw.githubusercontent.com/srophe/syriaca/master/documentation/indexes/taxonomyIndex-old.xml')"/> +<sch:let name="mutual" + value="$ti//listURI[@type = 'relationships']//uri[@ana = 'mutual']"/> +<sch:let name="directed" + value="$ti//listURI[@type = 'relationships']//uri[@ana = 'directed']"/> +<sch:assert test=".[@ref = $mutual]/@mutual or .[@ref = $directed]/@active">This <relation> takes either a @mutual attribute with mutual + relationships or both @active and @passive attributes with directed + relationships. Mutual relationships include: <sch:value-of select="string-join($mutual, '; ')"/>. Directed relationships include: +<sch:value-of select="string-join($directed, '; ')"/>.</sch:assert> +<sch:assert test=".[@ref = $mutual]/@mutual or .[@ref = $directed]/@passive">This <relation> takes either a @mutual attribute with mutual + relationships or both @active and @passive attributes with directed + relationships. Mutual relationships include: <sch:value-of select="string-join($mutual, '; ')"/>. Directed relationships include: +<sch:value-of select="string-join($directed, '; ')"/>.</sch:assert> +</sch:rule> +<sch:rule context="tei:ab[@subtype='event']/tei:listRelation/tei:relation"> +<sch:assert test="@mutual">A @mutual attribute is required on <relation> + in event factoids.</sch:assert> +<sch:report test="@active">@active attributes are not allowed on <relation> + in event factoids.</sch:report> +<sch:report test="@passive">@passive attributes are not allowed on <relation> + in event factoids.</sch:report> +</sch:rule> +<sch:rule context="tei:ab[@subtype='relation']/tei:listRelation/tei:relation/@mutual + | tei:ab[@subtype='relation']/tei:listRelation/tei:relation/@active + | tei:ab[@subtype='relation']/tei:listRelation/tei:relation/@passive + | tei:ab[@subtype='event']/tei:listEvent/tei:event/tei:desc/tei:listRelation/tei:relation/@mutual + | tei:ab[@subtype='event']/tei:listEvent/tei:event/tei:desc/tei:listRelation/tei:relation/@active + | tei:ab[@subtype='event']/tei:listEvent/tei:event/tei:desc/tei:listRelation/tei:relation/@passive"> +<sch:let name="personIndex" + value="doc('https://raw.githubusercontent.com/srophe/syriaca/master/documentation/indexes/persons.xml')"/> +<sch:let name="personURIs" + value="$personIndex//tei:person/@ref"/> +<sch:let name="error" value="."/> +<sch:assert test=" every $i in (tokenize(., ' ')) satisfies $i = $personURIs" + role="warning"> + <sch:value-of select="$error"/> is not currently in use. + Note that all person URIs take the form 'http://syriaca.org/person/{\d+}' + (where {\d+} is a number). If a URI is not current available, replace the number portion of the URI with + "#" followed without a space by a number that you use consistently when encoding information + about that person. +</sch:assert> +</sch:rule>
Schematron
+<sch:rule context="tei:event[@when]//tei:relation"> +<sch:assert test="./@when = ./ancestor::tei:event/@when"> This <relation> must have a @when attribute with the value <sch:value-of select="./ancestor::tei:event/@when"/>. +</sch:assert> +</sch:rule> +<sch:rule context="tei:event[@notBefore]//tei:relation"> +<sch:assert test="./@notBefore = ./ancestor::tei:event/@notBefore"> This <relation> must have a @notBefore attribute with the value <sch:value-of select="./ancestor::tei:event/@notBefore"/>. +</sch:assert> +</sch:rule> +<sch:rule context="tei:event[@notAfter]//tei:relation"> +<sch:assert test="./@notAfter = ./ancestor::tei:event/@notAfter"> This <relation> must have a @notAfter attribute with the value <sch:value-of select="./ancestor::tei:event/@notAfter"/>. +</sch:assert> +</sch:rule> +<sch:rule context="tei:event[@from]//tei:relation"> +<sch:assert test="./@from = ./ancestor::tei:event/@from"> This <relation> must have a @from attribute with the value <sch:value-of select="./ancestor::tei:event/@from"/>. +</sch:assert> +</sch:rule> +<sch:rule context="tei:event[@to]//tei:relation"> +<sch:assert test="./@to = ./ancestor::tei:event/@to"> This <relation> must have a @to attribute with the value <sch:value-of select="./ancestor::tei:event/@to"/>. +</sch:assert> +</sch:rule>
Schematron
+<sch:assert test="@ref or @key or @name">One of the attributes 'name', 'ref' or 'key' must be supplied</sch:assert>
Schematron
+<sch:report test="@active and @mutual">Only one of the attributes @active and @mutual may be supplied</sch:report>
Schematron
+<sch:report test="@passive and not(@active)">the attribute 'passive' may be supplied only if the attribute 'active' is supplied</sch:report>
Content model
+<content>
+ <elementRef key="desc" minOccurs="0"
+  maxOccurs="1"/>
+</content>
+    ⚓
Schema Declaration
+element relation
+{
+   att.global.attribute.xmlid,
+   att.global.attribute.n,
+   att.global.attribute.xmllang,
+   att.global.attribute.xmlbase,
+   att.global.attribute.xmlspace,
+   att.global.rendition.attribute.rend,
+   att.global.rendition.attribute.style,
+   att.global.rendition.attribute.rendition,
+   att.global.linking.attribute.corresp,
+   att.global.linking.attribute.synch,
+   att.global.linking.attribute.sameAs,
+   att.global.linking.attribute.copyOf,
+   att.global.linking.attribute.next,
+   att.global.linking.attribute.prev,
+   att.global.linking.attribute.exclude,
+   att.global.linking.attribute.select,
+   att.global.responsibility.attribute.cert,
+   att.global.responsibility.attribute.resp,
+   att.global.source.attribute.source,
+   att.datable.attributes,
+   att.editLike.attributes,
+   att.canonical.attribute.key,
+   att.sortable.attributes,
+   att.typed.attribute.subtype,
+   attribute ana { list { * } }?,
+   attribute ref { list { + } }?,
+   attribute type { text },
+   ( attribute active { list { + } }? | attribute mutual { list { + } }? ),
+   attribute name { text }?,
+   attribute passive { list { + } }?,
+   desc?
+}⚓

1.59. <residence>

<residence>
Modulenamesdates
Attributes
Contained by
namesdates: person personGrp
May contain
core: date note
namesdates: placeName
Note

This customization limits the attribute classes of the <residence> element to att.datable.custom and att.datable.w3c and removes the <residence> element from all model classes. It also requires exactly one <placeName> child and one <note> child and allows an optional <date> child.

Content model
+<content>
+ <sequence minOccurs="1" maxOccurs="1"
+  preserveOrder="true">
+  <elementRef key="placeName" minOccurs="1"
+   maxOccurs="1"/>
+  <elementRef key="date" minOccurs="0"
+   maxOccurs="1"/>
+  <elementRef key="note" minOccurs="1"
+   maxOccurs="1"/>
+ </sequence>
+</content>
+    ⚓
Schema Declaration
+element residence
+{
+   att.datable.custom.attributes,
+   att.datable.w3c.attributes,
+   ( placeName, date?, note )
+}⚓

1.60. <resp>

<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]
Modulecore
Attributes
Contained by
core: respStmt
May contain
core: choice date name note num ptr ref rs title
namesdates: orgName persName placeName
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>
+ <macroRef key="macro.phraseSeq.limited"/>
+</content>
+    ⚓
Schema Declaration
+element resp
+{
+   att.global.attributes,
+   att.canonical.attributes,
+   att.datable.attributes,
+   macro.phraseSeq.limited
+}⚓

1.61. <respStmt>

<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]
Modulecore
Attributes
Contained by
header: seriesStmt titleStmt
May contain
core: name note resp
namesdates: orgName persName
Example
<respStmt> + <resp>transcribed from original ms</resp> + <persName>Claus Huitfeldt</persName> +</respStmt>
Example
<respStmt> + <resp>converted to XML encoding</resp> + <name>Alan Morrison</name> +</respStmt>
Content model
+<content>
+ <sequence>
+  <alternate>
+   <sequence>
+    <elementRef key="resp" minOccurs="1"
+     maxOccurs="unbounded"/>
+    <classRef key="model.nameLike.agent"
+     minOccurs="1" maxOccurs="unbounded"/>
+   </sequence>
+   <sequence>
+    <classRef key="model.nameLike.agent"
+     minOccurs="1" maxOccurs="unbounded"/>
+    <elementRef key="resp" minOccurs="1"
+     maxOccurs="unbounded"/>
+   </sequence>
+  </alternate>
+  <elementRef key="note" minOccurs="0"
+   maxOccurs="unbounded"/>
+ </sequence>
+</content>
+    ⚓
Schema Declaration
+element respStmt
+{
+   att.global.attributes,
+   att.canonical.attributes,
+   (
+      ( ( resp+, model.nameLike.agent+ ) | ( model.nameLike.agent+, resp+ ) ),
+      note*
+   )
+}⚓

1.62. <revisionDesc>

<revisionDesc> (revision description) summarizes the revision history for a file. [2.6. The Revision Description 2.1.1. The TEI Header and Its Components]
Moduleheader
Attributes
statusdescribes the status of a document either currently or, when associated with a dated element, at the time indicated.
Derived fromatt.docStatus
StatusOptional
Datatypeteidata.enumerated
Sample values include:
approved
candidate
cleared
deprecated
draft
[Default]
embargoed
expired
frozen
galley
proposed
published
recommendation
submitted
unfinished
withdrawn
Contained by
header: teiHeader
May contain
header: change
Note

If present on this element, the status attribute should indicate the current status of the document. The same attribute may appear on any <change> to record the status at the time of that change. Conventionally <change> elements should be given in reverse date order, with the most recent change at the start of the list.

Example
<revisionDesc status="embargoed"> + <change when="1991-11-11" who="#LB"> deleted chapter 10 </change> +</revisionDesc>
Content model
+<content>
+ <elementRef key="change" minOccurs="0"
+  maxOccurs="unbounded"/>
+</content>
+    ⚓
Schema Declaration
+element revisionDesc
+{
+   att.global.attributes,
+   attribute status { text }?,
+   change*
+}⚓

1.63. <rs>

<rs> (referencing string) contains a general purpose name or referring string. [13.2.1. Personal Names 3.6.1. Referring Strings]
Modulecore
Attributes
Member of
model.nameLike
Contained by
core: author corr date desc editor head name note num orig p pubPlace publisher ref reg resp sic title
header: change edition
namesdates: langKnown orgName persName placeName
May containCharacter data only
Example
<q>My dear <rs type="person">Mr. Bennet</rs>, </q> said <rs type="person">his lady</rs> + to him one day, +<q>have you heard that <rs type="place">Netherfield Park</rs> is let at + last?</q>
Schematron
+<sch:rule context="//tei:ab/tei:listEvent/tei:listRelation/tei:relation/tei:desc/tei:rs/@ref"> +<sch:let name="SameEventURIs" + value="tokenize(ancestor::tei:relation/@mutual, ' ')"/> +<sch:let name="countMutual" + value="for $i in $SameEventURIs return count($i)"/> +<sch:assert test=". = $SameEventURIs"> Acceptable values: <sch:value-of select="string-join($SameEventURIs, '; ')"/> +</sch:assert> +</sch:rule> +<sch:rule context="//tei:ab//tei:rs"> +<sch:let name="URIno" + value="substring-after(@ref, 'spear-prosop.org/')"/> +<sch:assert test=". = $URIno"> The text node of this <rs> element must be <sch:value-of select="$URIno"/>. +</sch:assert> +</sch:rule>
Content model
+<content>
+ <textNode/>
+</content>
+    ⚓
Schema Declaration
+element rs
+{
+   att.global.attributes,
+   att.naming.attributes,
+   att.typed.attributes,
+   text
+}⚓

1.64. <seriesStmt>

<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]
Moduleheader
Attributes
Contained by
header: fileDesc
May contain
core: biblScope editor respStmt title
header: idno
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[1]/tei:title[1]"> +<sch:assert test="@level='s'"> The <title> requires a @level attribute with a value of "s". +</sch:assert> +<sch:assert test=". = 'SPEAR: Syriac Persons, Events, and Relations'"> This <title> must be "SPEAR: Syriac Persons, Events, and Relations". +</sch:assert> +</sch:rule> +<sch:rule context="tei:seriesStmt[2]/tei:title[1]"> +<sch:assert test="@level='m'"> The <title> requires a @level attribute with a value of "m". +</sch:assert> +<sch:assert test=" . = 'The Chronicle of Edessa' or . = 'The Letters of Severus of Antioch' + or . = 'The Lives of the Eastern Saints' "> This <title> must be one of the following: "The Chronicle of Edessa", "The Lives of the Eastern Saints", + or "The Letters of Severus of Antioch". +</sch:assert> +</sch:rule> +<sch:rule context="tei:seriesStmt[2]/tei:title[2]"> +<sch:assert test="@type='sub'"> This <title> requires a @type attribute with a value of "sub". +</sch:assert> +<sch:assert test=". = 'A SPEAR Prosopography'"> This <title> must be "A SPEAR Prosopography". +</sch:assert> +</sch:rule>
Schematron
+<sch:rule context="tei:seriesStmt/tei:editor"> +<sch:assert test="@role='general'"> This <editor> must have a @role attribute with a value of "general". +</sch:assert> +</sch:rule> +<sch:rule context="tei:seriesStmt/tei:editor"> +<sch:report test="@role='creator'"> This <editor> cannot have a @role attribute with a value of "creator". +</sch:report> +</sch:rule> +<sch:rule context="tei:seriesStmt[1]/tei:editor"> +<sch:assert test="@ref='http://syriaca.org/documentation/editors.xml#dschwartz'"> This <editor> must have a @ref attribute with a value of "http://syriaca.org/documentation/editors.xml#dschwartz". +</sch:assert> +<sch:assert test=". = 'Daniel L. Schwartz'"> This <editor> must be "Daniel L. Schwartz". +</sch:assert> +</sch:rule>
Schematron
+<sch:rule context="tei:seriesStmt[1]/tei:idno"> +<sch:assert test=". = 'https://spear-prosop.org'"> This <idno> must be "https://spear-prosop.org". +</sch:assert> +</sch:rule> +<sch:rule context="tei:seriesStmt[2]/tei:idno[preceding-sibling::tei:title = 'The Lives + of the Eastern Saints']"> +<sch:assert test=". = 'https://spear-prosop.org/lives-eastern-saints'"> This <idno> must be "https://spear-prosop.org/lives-eastern-saints". +</sch:assert> +</sch:rule> +<sch:rule context="tei:seriesStmt[2]/tei:idno[preceding-sibling::tei:title = 'The Letters + of Severus of Antioch']"> +<sch:assert test=". = 'https://spear-prosop.org/letters-severus'"> This <idno> must be "https://spear-prosop.org/letters-severus". +</sch:assert> +</sch:rule>
Schematron
+<sch:rule context="tei:seriesStmt[1]"> +<sch:report test="tei:biblScope"> This <seriesStmt> cannot contain a <biblScope>. +</sch:report> +</sch:rule> +<sch:rule context="tei:seriesStmt[2]"> +<sch:assert test="tei:biblScope"> This <seriesStmt> requires a <biblScope>. +</sch:assert> +</sch:rule> +<sch:rule context="tei:seriesStmt[2]/tei:biblScope"> +<sch:assert test="@unit='volume'"> This <biblScope> element requires a a @unit + attribute having a value of "volume". +</sch:assert> +<sch:assert test="tei:title"> This <biblScope> element requires a child <title> element. +</sch:assert> +</sch:rule> +<sch:rule context="tei:seriesStmt[2]/tei:biblScope/tei:title"> +<sch:assert test="@level='s'"> This <title> element requires a @level attribute with a value of "s". +</sch:assert> +<sch:assert test=". = 'SPEAR: Syriac Persons, Events, and Relations'"> This <title> element must contain "SPEAR: Syriac Persons, Events, and Relations". +</sch:assert> +</sch:rule>
Content model
+<content>
+ <sequence minOccurs="1"
+  maxOccurs="unbounded">
+  <elementRef key="title" minOccurs="1"
+   maxOccurs="2"/>
+  <elementRef key="editor" minOccurs="1"
+   maxOccurs="unbounded"/>
+  <elementRef key="respStmt" minOccurs="0"
+   maxOccurs="unbounded"/>
+  <elementRef key="idno" minOccurs="1"
+   maxOccurs="1"/>
+  <elementRef key="biblScope" minOccurs="0"
+   maxOccurs="1"/>
+ </sequence>
+</content>
+    ⚓
Schema Declaration
+element seriesStmt
+{
+   att.global.attributes,
+   att.declarable.attributes,
+   ( ( title, title? ), editor+, respStmt*, idno, biblScope? )+
+}⚓

1.65. <sic>

<sic> (Latin for thus or so) contains text reproduced although apparently incorrect or inaccurate. [3.5.1. Apparent Errors]
Modulecore
Member of
model.choicePart model.pPart.transcriptional
Contained by
core: author choice corr date editor head name note num orig p pubPlace publisher ref reg sic title
header: change edition
namesdates: orgName persName placeName
May contain
core: bibl choice corr date listBibl name note num orig ptr ref reg rs sic title
namesdates: listRelation orgName persName placeName
character data
Example
for his nose was as sharp as + a pen, and <sic>a Table</sic> of green fields.
ExampleIf all that is desired is to call attention to the apparent problem in the copy text, <sic> may be used alone:
I don't know, Juan. It's so far in the past now + — how <sic>we can</sic> prove or disprove anyone's theories?
ExampleIt is also possible, using the <choice> and <corr> elements, to provide a corrected reading:
I don't know, Juan. It's so far in the past now + — how <choice> + <sic>we can</sic> + <corr>can we</corr> +</choice> prove or disprove anyone's theories?
Example
for his nose was as sharp as + a pen, and <choice> + <sic>a Table</sic> + <corr>a' babbld</corr> +</choice> of green fields.
Content model
+<content>
+ <macroRef key="macro.paraContent"/>
+</content>
+    ⚓
Schema Declaration
+element sic { macro.paraContent }⚓

1.66. <socecStatus>

<socecStatus> (socio-economic status) contains an informal description of a person's perceived social or economic status. [15.2.2. The Participant Description]
Modulenamesdates
Attributes
ana
Derived fromatt.global.analytic
StatusRequired
Schematron
+<sch:rule context="tei:socecStatus/@ana"> +<sch:let name="anaTokens" + value="tokenize(., ' ')"/> +<sch:let name="ti" + value="doc('https://raw.githubusercontent.com/srophe/syriaca/master/documentation/indexes/taxonomyIndex-old.xml')"/> +<sch:let name="socioeconomicStatusURIs" + value="$ti//listURI[@type = 'socioeconomic-status']/uri"/> +<sch:let name="errors" + value="for $i in $anaTokens return $i[not(. = $socioeconomicStatusURIs)]"/> +<sch:assert test="every $i in $anaTokens satisfies $i = $socioeconomicStatusURIs" + role="warning"> + <sch:value-of select="string-join($errors, ', ')"/>: URI(s) not in the Taxonomy. If you find no appropriate concept on the following list, + please choose a keyword of your own for the editors to consider: <sch:value-of select="string-join($socioeconomicStatusURIs, '; ')"/>.</sch:assert> +</sch:rule>
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
schemeidentifies the classification system or taxonomy in use, for example by pointing to a locally-defined <taxonomy> element or by supplying a URI for an externally-defined system.
StatusOptional
Datatypeteidata.pointer
codeidentifies a status code defined within the classification system or taxonomy defined by the scheme attribute.
StatusOptional
Datatypeteidata.pointer
Contained by
namesdates: person personGrp
May contain
core: note
Note

This customization restricts the attribute classes of <socecStatus> to att.datable.w3c and att.global.analytic. If more precise dating is required for a SPEAR factoid, the encoder should use the <date> element.

It only allows <note> as a child element and it restricts the required @ana attribute to keyword URIs in the Syriac Taxonomy that pertain to socioeconomic status.

Example
<socecStatus scheme="#rg" code="#ab1"/>
Example
<socecStatus>Status AB1 in the RG Classification scheme</socecStatus>
Content model
+<content>
+ <elementRef key="note" minOccurs="1"
+  maxOccurs="unbounded"/>
+</content>
+    ⚓
Schema Declaration
+element socecStatus
+{
+   att.datable.w3c.attributes,
+   attribute ana { list { + } },
+   attribute scheme { text }?,
+   attribute code { text }?,
+   note+
+}⚓

1.67. <sourceDesc>

<sourceDesc> (source description) describes the source(s) from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as "born digital" for a text which has no previous existence. [2.2.7. The Source Description]
Moduleheader
Attributes
Contained by
header: fileDesc
May contain
core: listBibl
namesdates: listRelation
Example
<sourceDesc> + <bibl> +  <title level="a">The Interesting story of the Children in the Wood</title>. In + <author>Victor E Neuberg</author>, <title>The Penny Histories</title>. + <publisher>OUP</publisher> +  <date>1968</date>. </bibl> +</sourceDesc>
Example
<sourceDesc> + <p>Born digital: no previous source exists.</p> +</sourceDesc>
Content model
+<content>
+ <sequence minOccurs="0"
+  maxOccurs="unbounded">
+  <elementRef key="listBibl" minOccurs="1"
+   maxOccurs="1"/>
+  <elementRef key="listRelation"
+   minOccurs="0" maxOccurs="unbounded"/>
+ </sequence>
+</content>
+    ⚓
Schema Declaration
+element sourceDesc
+{
+   att.global.attributes,
+   att.declarable.attributes,
+   ( listBibl, listRelation* )*
+}⚓

1.68. <sponsor>

<sponsor> (sponsor) specifies the name of a sponsoring organization or institution. [2.2.1. The Title Statement]
Moduleheader
Attributes
Contained by
header: titleStmt
May containCharacter 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
<sponsor>Association for Computers and the Humanities</sponsor> +<sponsor>Association for Computational Linguistics</sponsor> +<sponsor ref="http://www.allc.org/">Association for Literary and Linguistic Computing</sponsor>
Content model
+<content>
+ <textNode/>
+</content>
+    ⚓
Schema Declaration
+element sponsor
+{
+   att.global.attributes,
+   att.canonical.attributes,
+   att.datable.attributes,
+   text
+}⚓

1.69. <state>

<state> (state) contains a description of some status or quality attributed to a person, place, or organization often at some specific time or for a specific date range. [13.3.1. Basic Principles 13.3.2.1. Personal Characteristics]
Modulenamesdates
Attributes
ana
Derived fromatt.global.analytic
StatusRequired
Schematron
+<sch:rule context="tei:state[@type='mental']/@ana"> +<sch:let name="anaTokens" + value="tokenize(., ' ')"/> +<sch:let name="ti" + value="doc('https://raw.githubusercontent.com/srophe/syriaca/master/documentation/indexes/taxonomyIndex-old.xml')"/> +<sch:let name="mentalStateURIs" + value="$ti//listURI[@type = 'mental-states']/uri"/> +<sch:let name="errors" + value="for $i in $anaTokens return $i[not(. = $mentalStateURIs)]"/> +<sch:assert test="every $i in $anaTokens satisfies $i = $mentalStateURIs" + role="warning"> + <sch:value-of select="string-join($errors, ', ')"/>: URI(s) not in the Taxonomy. If you find no appropriate concept on the following list, + please choose a keyword of your own for the editors to consider: <sch:value-of select="string-join($mentalStateURIs, '; ')"/>.</sch:assert> +</sch:rule> +<sch:rule context="tei:state[@type='sanctity']/@ana"> +<sch:let name="anaTokens" + value="tokenize(., ' ')"/> +<sch:let name="ti" + value="doc('https://raw.githubusercontent.com/srophe/syriaca/master/documentation/indexes/taxonomyIndex-old.xml')"/> +<sch:let name="sanctityURIs" + value="$ti//listURI[@type = 'sanctity']/uri"/> +<sch:let name="errors" + value="for $i in $anaTokens return $i[not(. = $sanctityURIs)]"/> +<sch:assert test="every $i in $anaTokens satisfies $i = $sanctityURIs" + role="warning"> + <sch:value-of select="string-join($errors, ', ')"/>: URI(s) not in the Taxonomy. If you find no appropriate concept on the following list, + please choose a keyword of your own for the editors to consider: <sch:value-of select="string-join($sanctityURIs, '; ')"/>.</sch:assert> +</sch:rule>
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
type
StatusRequired
Datatypeteidata.enumerated
Legal values are:
mental
used for references to a person's mental traits; such as intelligence, mental disability, wisdom, etc.
religiousAffiliation
used for references to a person's religious affiliation; including but not limited to membership in an organization, adhering to a set of beliefs, or identifying with a religious community in some way.
sanctity
used for references to a person's sanctity.
Contained by
namesdates: person personGrp
May contain
core: note
Note

This customization restricts the attribute classes of <state> to att.datable.w3c and att.global.analytic. If more precise dating is required for a SPEAR factoid, the encoder should use the <date> element.

It only allows <note> as a child element. It restricts the required @type attribute to the values "mental", "religiousAffiliation", and "sanctity". It restricts the required @ana attribute to keyword URIs in the Syriac Taxonomy that pertain to each of these three types.

Example
<state ref="#SCHOL" type="status"> + <label>scholar</label> +</state>
Example
<org> + <orgName notAfter="1960">The Silver Beetles</orgName> + <orgName notBefore="1960">The Beatles</orgName> + <state type="membership" from="1960-08" +  to="1962-05"> +  <desc> +   <persName>John Lennon</persName> +   <persName>Paul McCartney</persName> +   <persName>George Harrison</persName> +   <persName>Stuart Sutcliffe</persName> +   <persName>Pete Best</persName> +  </desc> + </state> + <state type="membership" notBefore="1963"> +  <desc> +   <persName>John Lennon</persName> +   <persName>Paul McCartney</persName> +   <persName>George Harrison</persName> +   <persName>Ringo Starr</persName> +  </desc> + </state> +</org>
Content model
+<content>
+ <elementRef key="note" minOccurs="1"
+  maxOccurs="1"/>
+</content>
+    ⚓
Schema Declaration
+element state
+{
+   att.datable.w3c.attributes,
+   attribute ana { list { + } },
+   attribute type { "mental" | "religiousAffiliation" | "sanctity" },
+   note
+}⚓

1.70. <taxonomy>

<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]
Moduleheader
Attributes
Contained by
header: classDecl
May contain
header: category
Note

Nested taxonomies are common in many fields, so the <taxonomy> element can be nested.

Example
<taxonomy xml:id="tax.b"> + <bibl>Brown Corpus</bibl> + <category xml:id="tax.b.a"> +  <catDesc>Press Reportage</catDesc> +  <category xml:id="tax.b.a1"> +   <catDesc>Daily</catDesc> +  </category> +  <category xml:id="tax.b.a2"> +   <catDesc>Sunday</catDesc> +  </category> +  <category xml:id="tax.b.a3"> +   <catDesc>National</catDesc> +  </category> +  <category xml:id="tax.b.a4"> +   <catDesc>Provincial</catDesc> +  </category> +  <category xml:id="tax.b.a5"> +   <catDesc>Political</catDesc> +  </category> +  <category xml:id="tax.b.a6"> +   <catDesc>Sports</catDesc> +  </category> + </category> + <category xml:id="tax.b.d"> +  <catDesc>Religion</catDesc> +  <category xml:id="tax.b.d1"> +   <catDesc>Books</catDesc> +  </category> +  <category xml:id="tax.b.d2"> +   <catDesc>Periodicals and tracts</catDesc> +  </category> + </category> +</taxonomy>
Example
<taxonomy> + <category xml:id="literature"> +  <catDesc>Literature</catDesc> +  <category xml:id="poetry"> +   <catDesc>Poetry</catDesc> +   <category xml:id="sonnet"> +    <catDesc>Sonnet</catDesc> +    <category xml:id="shakesSonnet"> +     <catDesc>Shakespearean Sonnet</catDesc> +    </category> +    <category xml:id="petraSonnet"> +     <catDesc>Petrarchan Sonnet</catDesc> +    </category> +   </category> +   <category xml:id="haiku"> +    <catDesc>Haiku</catDesc> +   </category> +  </category> +  <category xml:id="drama"> +   <catDesc>Drama</catDesc> +  </category> + </category> + <category xml:id="meter"> +  <catDesc>Metrical Categories</catDesc> +  <category xml:id="feet"> +   <catDesc>Metrical Feet</catDesc> +   <category xml:id="iambic"> +    <catDesc>Iambic</catDesc> +   </category> +   <category xml:id="trochaic"> +    <catDesc>trochaic</catDesc> +   </category> +  </category> +  <category xml:id="feetNumber"> +   <catDesc>Number of feet</catDesc> +   <category xml:id="pentameter"> +    <catDesc>>Pentameter</catDesc> +   </category> +   <category xml:id="tetrameter"> +    <catDesc>>Tetrameter</catDesc> +   </category> +  </category> + </category> +</taxonomy> +<!-- elsewhere in document --> +<lg ana="#shakesSonnet #iambic #pentameter"> + <l>Shall I compare thee to a summer's day</l> +<!-- ... --> +</lg>
Content model
+<content>
+ <elementRef key="category" minOccurs="1"
+  maxOccurs="1"/>
+</content>
+    ⚓
Schema Declaration
+element taxonomy { att.global.attributes, category }⚓

1.71. <teiHeader>

<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 15.1. Varieties of Composite Text]
Moduleheader
Attributes
Contained by
textstructure: TEI
May contain
header: encodingDesc fileDesc profileDesc revisionDesc
Note

Every <teiHeader> contains a <fileDesc> (information about the creation of a file), an <encodingDesc> (editorial rules), a <profileDesc>> (non-bibliographic aspects of a text), and a <revisionDesc> (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"
+  preserveOrder="true">
+  <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
+{
+   att.global.attributes,
+   ( fileDesc, encodingDesc, profileDesc, revisionDesc )
+}⚓

1.72. <text>

<text> (text) contains a single text of any kind, whether unitary or composite, for example a poem or drama, a collection of essays, a novel, a dictionary, or a corpus sample. [4. Default Text Structure 15.1. Varieties of Composite Text]
Moduletextstructure
Attributes
Member of
model.resource
Contained by
textstructure: TEI
May contain
core: note
textstructure: back body
Note

This element should not be used to represent a text which is inserted at an arbitrary point within the structure of another, for example as in an embedded or quoted narrative; the <floatingText> is provided for this purpose.

Example
<text> + <front> +  <docTitle> +   <titlePart>Autumn Haze</titlePart> +  </docTitle> + </front> + <body> +  <l>Is it a dragonfly or a maple leaf</l> +  <l>That settles softly down upon the water?</l> + </body> +</text>
ExampleThe body of a text may be replaced by a group of nested texts, as in the following schematic:
<text> + <front> +<!-- front matter for the whole group --> + </front> + <group> +  <text> +<!-- first text --> +  </text> +  <text> +<!-- second text --> +  </text> + </group> +</text>
Content model
+<content>
+ <sequence>
+  <classRef key="model.global"
+   minOccurs="0" maxOccurs="unbounded"/>
+  <sequence minOccurs="0">
+   <elementRef key="front"/>
+   <classRef key="model.global"
+    minOccurs="0" maxOccurs="unbounded"/>
+  </sequence>
+  <alternate>
+   <elementRef key="body"/>
+   <elementRef key="group"/>
+  </alternate>
+  <classRef key="model.global"
+   minOccurs="0" maxOccurs="unbounded"/>
+  <sequence minOccurs="0">
+   <elementRef key="back"/>
+   <classRef key="model.global"
+    minOccurs="0" maxOccurs="unbounded"/>
+  </sequence>
+ </sequence>
+</content>
+    ⚓
Schema Declaration
+element text
+{
+   att.global.attributes,
+   att.declaring.attributes,
+   att.typed.attributes,
+   att.written.attributes,
+   (
+      model.global*,
+      ( front, model.global* )?,
+      ( body | group ),
+      model.global*,
+      ( back, model.global* )?
+   )
+}⚓

1.73. <title>

<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]
Modulecore
Attributes
typeclassifies the title according to some convenient typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Sample values include:
main
main title
sub
(subordinate) subtitle, title of part
alt
(alternate) alternate title, often in another language, by which the work is also known
short
abbreviated form of title
desc
(descriptive) descriptive paraphrase of the work functioning as a title
Note

This attribute is provided for convenience in analysing titles and processing them according to their type; where such specialized processing is not necessary, there is no need for such analysis, and the entire title, including subtitles and any parallel titles, may be enclosed within a single <title> element.

levelindicates the bibliographic level for a title, that is, whether it identifies an article, book, journal, series, or unpublished material.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
a
(analytic) the title applies to an analytic item, such as an article, poem, or other work published as part of a larger item.
m
(monographic) the title applies to a monograph such as a book or other item considered to be a distinct publication, including single volumes of multi-volume works
j
(journal) the title applies to any serial or periodical publication such as a journal, magazine, or newspaper
s
(series) the title applies to a series of otherwise distinct publications such as a collection
u
(unpublished) the title applies to any unpublished material (including theses and dissertations unless published by a commercial press)
Note

The level of a title is sometimes implied by its context: for example, a title appearing directly within an <analytic> element is ipso facto of level ‘a’, and one appearing within a <series> element of level ‘s’. For this reason, the level attribute is not required in contexts where its value can be unambiguously inferred. Where it is supplied in such contexts, its value should not contradict the value implied by its parent element.

Member of
model.emphLike
Contained by
core: author bibl biblScope corr date desc editor head name note num orig p pubPlace publisher ref reg resp sic title
header: change edition seriesStmt titleStmt
namesdates: langKnown orgName persName placeName
May contain
core: bibl choice corr date listBibl name note num orig ptr ref reg rs sic title
namesdates: listRelation orgName persName placeName
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>Information Technology and the Research Process: Proceedings of + a conference held at Cranfield Institute of Technology, UK, + 18–21 July 1989</title>
Example
<title>Hardy's Tess of the D'Urbervilles: a machine readable + edition</title>
Example
<title type="full"> + <title type="main">Synthèse</title> + <title type="sub">an international journal for +   epistemology, methodology and history of +   science</title> +</title>
Schematron
+<sch:rule context="tei:title/@ref"> +<sch:assert test="matches(., concat('http://syriaca.org/work/', '\d+'))"> The @ref attribute must take a Syriaca.org work URI + which reqires the form 'http://syriaca.org/work/{\d+}' + (where {\d+} is a number). +</sch:assert> +</sch:rule>
Content model
+<content>
+ <macroRef key="macro.paraContent"/>
+</content>
+    ⚓
Schema Declaration
+element title
+{
+   att.global.attributes,
+   att.typed.attribute.subtype,
+   att.canonical.attributes,
+   att.datable.attributes,
+   attribute type { text }?,
+   attribute level { "a" | "m" | "j" | "s" | "u" }?,
+   macro.paraContent
+}⚓

1.74. <titleStmt>

<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]
Moduleheader
Attributes
Contained by
header: fileDesc
May contain
core: editor respStmt title
header: funder sponsor
Example
<titleStmt> + <title>Capgrave's Life of St. John Norbert: a machine-readable transcription</title> + <respStmt> +  <resp>compiled by</resp> +  <name>P.J. Lucas</name> + </respStmt> +</titleStmt>
Schematron
+<sch:rule context="//tei:titleStmt/tei:title[1]"> +<sch:assert test="@level='m' or @level='a'"> The first <title> element child of <titleStmt> must have + @level attribute with a value of "m" indicating "monographic" or "a" indicating + analytic. +</sch:assert> +<sch:assert test="@type='main'"> The first <title> element child of <titleStmt> must have + @type attribute with a value of "main". +</sch:assert> +</sch:rule> +<sch:rule context="//tei:titleStmt/tei:title[2]"> +<sch:assert test="@type='sub'"> The second <title> element child of <titleStmt> must have + @type attribute with a value of "sub". +</sch:assert> +<sch:assert test="normalize-space(.) = 'A SPEAR Prosopography'"> The text node of this subtitle must be "A SPEAR Prosopography". +</sch:assert> +</sch:rule>
Content model
+<content>
+ <sequence minOccurs="1" maxOccurs="1"
+  preserveOrder="true">
+  <elementRef key="title" minOccurs="2"
+   maxOccurs="2"/>
+  <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
+{
+   att.global.attributes,
+   ( ( title, title ), sponsor+, funder*, editor+, respStmt+ )
+}⚓

1.75. <trait>

<trait> (trait) contains a description of some status or quality attributed to a person, place, or organization typically, but not necessarily, independent of the volition or action of the holder and usually not at some specific time or for a specific date range. [13.3.1. Basic Principles 13.3.2.1. Personal Characteristics]
Modulenamesdates
Attributes
ana
Derived fromatt.global.analytic
StatusRequired
Schematron
+<sch:rule context="tei:trait[@type='ethnicLabel']/@ana"> +<sch:let name="anaTokens" + value="tokenize(., ' ')"/> +<sch:let name="ti" + value="doc('https://raw.githubusercontent.com/srophe/syriaca/master/documentation/indexes/taxonomyIndex-old.xml')"/> +<sch:let name="ethnicLabelURIs" + value="$ti//listURI[@type = 'ethnicity']/uri"/> +<sch:let name="errors" + value="for $i in $anaTokens return $i[not(. = $ethnicLabelURIs)]"/> +<sch:assert test="every $i in $anaTokens satisfies $i = $ethnicLabelURIs" + role="warning"> + <sch:value-of select="string-join($errors, ', ')"/>: URI(s) not in the Taxonomy. If you find no appropriate concept on the following list, + please choose a keyword of your own for the editors to consider: <sch:value-of select="string-join($ethnicLabelURIs, '; ')"/>.</sch:assert> +</sch:rule> +<sch:rule context="tei:trait[@type='gender']/@ana"> +<sch:assert test="every $i in (tokenize(., ' ')) satisfies $i = 'http://syriaca.org/keyword/eunuch' + or $i = 'http://syriaca.org/keyword/female' or $i = 'http://syriaca.org/keyword/male' + or $i = 'http://syriaca.org/keyword/nun-as-monk'" + role="warning"> Preferred values for the @ana attribute on a <trait> element + @type="gender" are: + "http://syriaca.org/keyword/eunuch"; "http://syriaca.org/keyword/female"; + "http://syriaca.org/keyword/male"; and + "http://syriaca.org/keyword/nun-as-monk". Use these if applicable. If one of + these does not apply, please use a descriptive term of your + choosing.</sch:assert> +</sch:rule> +<sch:rule context="tei:trait[@type='physical']/@ana"> +<sch:let name="anaTokens" + value="tokenize(., ' ')"/> +<sch:let name="ti" + value="doc('https://raw.githubusercontent.com/srophe/syriaca/master/documentation/indexes/taxonomyIndex-old.xml')"/> +<sch:let name="taxonomyAllURIs" + value="$ti//listURI[@type = 'taxonomyAllURIs']/uri"/> +<sch:let name="errors" + value="for $i in $anaTokens return $i[not(. = $taxonomyAllURIs)]"/> +<sch:assert test="every $i in $anaTokens satisfies $i = $taxonomyAllURIs" + role="warning"> + <sch:value-of select="string-join($errors, ', ')"/>: URI(s) not in the Taxonomy. . +</sch:assert> +</sch:rule>
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
type
StatusRequired
Datatypeteidata.enumerated
Legal values are:
physical
used for references to a person's physical characteristics, such as hair color, height, weight, physical disabilities, etc.
gender
used for references to a person's gender identity (as opposed to their biological sex which SPEAR does not presume to capture).
ethnicLabel
used for references to an ethnic label claimed by a person or ascribed to a person; such as "Goth," "Saracen," etc.
Contained by
namesdates: person personGrp
May contain
core: note
Note

This customization restricts the attribute classes of <trait> to att.datable.w3c and att.global.analytic. If more precise dating is required for a SPEAR factoid, the encoder should use the <date> element.

It only allows <note> as a child element. It restricts the required @type attribute to the values "physical", "gender", and "ethnicLabel". It restricts the required @ana attribute to keyword URIs in the Syriac Taxonomy that pertain to each of these three types.

Example
<trait type="physical"> + <label>Eye colour</label> + <desc>Blue</desc> +</trait>
Content model
+<content>
+ <elementRef key="note" minOccurs="1"
+  maxOccurs="1"/>
+</content>
+    ⚓
Schema Declaration
+element trait
+{
+   att.datable.w3c.attributes,
+   attribute ana { list { + } },
+   attribute type { "physical" | "gender" | "ethnicLabel" },
+   note
+}⚓

2. Model classes

2.1. model.attributable

model.attributable groups elements that contain a word or phrase that can be attributed to a source. [3.3.3. Quotation 4.3.2. Floating Texts]
Moduletei
Used by
macro.phraseSeq model.inter
Membersmodel.quoteLike

2.2. model.availabilityPart

model.availabilityPart groups elements such as licences and paragraphs of text which may appear as part of an availability statement [2.2.4. Publication, Distribution, Licensing, etc.]
Moduletei
Used by
availability
Memberslicence

2.3. model.biblLike

model.biblLike groups elements containing a bibliographic description. [3.12. Bibliographic Citations and References]
Moduletei
Used by
model.inter
Membersbibl listBibl

2.4. model.choicePart

model.choicePart groups elements (other than <choice> itself) which can be used within a <choice> alternation. [3.5. Simple Editorial Changes]
Moduletei
Used by
choice
Memberscorr orig reg sic

2.5. model.dateLike

model.dateLike groups elements containing temporal expressions. [3.6.4. Dates and Times 13.4. Dates]
Moduletei
Used by
model.pPart.data
Membersdate

2.6. model.divPart

model.divPart groups paragraph-level elements appearing directly within divisions. [1.3. The TEI Class System]
Moduletei
Used by
macro.specialPara
Membersmodel.lLike model.pLike[p]
Note

Note that this element class does not include members of the model.inter class, which can appear either within or between paragraph-level items.

2.7. model.emphLike

model.emphLike groups phrase-level elements which are typographically distinct and to which a specific function can be attributed. [3.3. Highlighting and Quotation]
Moduletei
Used by
model.highlighted model.limitedPhrase
Memberstitle

2.8. model.global

model.global groups elements which may appear at any point within a TEI text. [1.3. The TEI Class System]
Moduletei
Used by
date head macro.phraseSeq macro.phraseSeq.limited macro.specialPara model.paraPart text
Membersmodel.global.edit model.global.meta model.milestoneLike model.noteLike[note]

2.9. model.highlighted

model.highlighted groups phrase-level elements which are typographically distinct. [3.3. Highlighting and Quotation]
Moduletei
Used by
model.phrase
Membersmodel.emphLike[title] model.hiLike

2.10. model.inter

model.inter groups elements which can appear either within or between paragraph-like elements. [1.3. The TEI Class System]
Moduletei
Used by
head macro.specialPara model.paraPart
Membersmodel.attributable[model.quoteLike] model.biblLike[bibl listBibl] model.egLike model.labelLike model.listLike[listRelation] model.oddDecl model.stageLike

2.11. model.limitedPhrase

model.limitedPhrase groups phrase-level elements excluding those elements primarily intended for transcription of existing sources. [1.3. The TEI Class System]
Moduletei
Used by
macro.phraseSeq.limited
Membersmodel.emphLike[title] model.hiLike model.pPart.data[model.addressLike model.dateLike[date] model.measureLike[num] model.nameLike[model.nameLike.agent[name orgName persName] model.offsetLike model.persNamePart model.placeStateLike[model.placeNamePart[placeName]] rs]] model.pPart.editorial[choice] model.pPart.msdesc model.phrase.xml model.ptrLike[ptr ref]

2.12. model.listLike

model.listLike groups list-like elements. [3.8. Lists]
Moduletei
Used by
model.inter
MemberslistRelation

2.13. model.measureLike

model.measureLike groups elements which denote a number, a quantity, a measurement, or similar piece of text that conveys some numerical meaning. [3.6.3. Numbers and Measures]
Moduletei
Used by
model.pPart.data
Membersnum

2.14. model.nameLike

model.nameLike groups elements which name or refer to a person, place, or organization.
Moduletei
Used by
model.pPart.data
Membersmodel.nameLike.agent[name orgName persName] model.offsetLike model.persNamePart model.placeStateLike[model.placeNamePart[placeName]] rs
Note

A superset of the naming elements that may appear in datelines, addresses, statements of responsibility, etc.

2.15. model.nameLike.agent

model.nameLike.agent groups elements which contain names of individuals or corporate bodies. [3.6. Names, Numbers, Dates, Abbreviations, and Addresses]
Moduletei
Used by
model.nameLike respStmt
Membersname orgName persName
Note

This class is used in the content model of elements which reference names of people or organizations.

2.16. model.noteLike

model.noteLike groups globally-available note-like elements. [3.9. Notes, Annotation, and Indexing]
Moduletei
Used by
model.global
Membersnote

2.17. model.pLike

model.pLike groups paragraph-like elements.
Moduletei
Used by
availability model.divPart
Membersp

2.18. model.pPart.data

model.pPart.data groups phrase-level elements containing names, dates, numbers, measures, and similar data. [3.6. Names, Numbers, Dates, Abbreviations, and Addresses]
Moduletei
Used by
model.limitedPhrase model.phrase
Membersmodel.addressLike model.dateLike[date] model.measureLike[num] model.nameLike[model.nameLike.agent[name orgName persName] model.offsetLike model.persNamePart model.placeStateLike[model.placeNamePart[placeName]] rs]

2.19. model.pPart.edit

model.pPart.edit groups phrase-level elements for simple editorial correction and transcription. [3.5. Simple Editorial Changes]
Moduletei
Used by
model.phrase
Membersmodel.pPart.editorial[choice] model.pPart.transcriptional[corr orig reg sic]

2.20. model.pPart.editorial

model.pPart.editorial groups phrase-level elements for simple editorial interventions that may be useful both in transcribing and in authoring. [3.5. Simple Editorial Changes]
Moduletei
Used by
model.limitedPhrase model.pPart.edit
Memberschoice

2.21. model.pPart.transcriptional

model.pPart.transcriptional groups phrase-level elements used for editorial transcription of pre-existing source materials. [3.5. Simple Editorial Changes]
Moduletei
Used by
model.pPart.edit
Memberscorr orig reg sic

2.22. model.paraPart

model.paraPart groups elements that may appear in paragraphs and similar elements [3.1. Paragraphs]
Moduletei
Used by
macro.paraContent
Membersmodel.gLike model.global[model.global.edit model.global.meta model.milestoneLike model.noteLike[note]] model.inter[model.attributable[model.quoteLike] model.biblLike[bibl listBibl] model.egLike model.labelLike model.listLike[listRelation] model.oddDecl model.stageLike] model.lLike model.phrase[model.graphicLike model.highlighted[model.emphLike[title] model.hiLike] model.lPart model.pPart.data[model.addressLike model.dateLike[date] model.measureLike[num] model.nameLike[model.nameLike.agent[name orgName persName] model.offsetLike model.persNamePart model.placeStateLike[model.placeNamePart[placeName]] rs]] model.pPart.edit[model.pPart.editorial[choice] model.pPart.transcriptional[corr orig reg sic]] model.pPart.msdesc model.phrase.xml model.ptrLike[ptr ref] model.segLike model.specDescLike]

2.23. model.phrase

model.phrase groups elements which can occur at the level of individual words or phrases. [1.3. The TEI Class System]
Moduletei
Used by
date head macro.phraseSeq macro.specialPara model.paraPart
Membersmodel.graphicLike model.highlighted[model.emphLike[title] model.hiLike] model.lPart model.pPart.data[model.addressLike model.dateLike[date] model.measureLike[num] model.nameLike[model.nameLike.agent[name orgName persName] model.offsetLike model.persNamePart model.placeStateLike[model.placeNamePart[placeName]] rs]] model.pPart.edit[model.pPart.editorial[choice] model.pPart.transcriptional[corr orig reg sic]] model.pPart.msdesc model.phrase.xml model.ptrLike[ptr ref] model.segLike model.specDescLike
Note

This class of elements can occur within paragraphs, list items, lines of verse, etc.

2.24. model.placeNamePart

model.placeNamePart groups elements which form part of a place name. [13.2.3. Place Names]
Moduletei
Used by
model.placeStateLike
MembersplaceName

2.25. model.placeStateLike

model.placeStateLike groups elements which describe changing states of a place.
Moduletei
Used by
model.nameLike
Membersmodel.placeNamePart[placeName]

2.26. model.ptrLike

model.ptrLike groups elements used for purposes of location and reference. [3.7. Simple Links and Cross-References]
Moduletei
Used by
model.limitedPhrase model.phrase
Membersptr ref

2.27. model.resource

model.resource groups separate elements which constitute the content of a digital resource, as opposed to its metadata. [1.3. The TEI Class System]
Moduletei
Used by
TEI
Memberstext

3. Attribute classes

3.1. att.ascribed

att.ascribed provides attributes for elements representing speech or action that can be ascribed to a specific individual. [3.3.3. Quotation 8.3. Elements Unique to Spoken Texts]
Moduletei
Memberschange
Attributes
whoindicates the person, or group of people, to whom the element content is ascribed.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
In the following example from Hamlet, speeches (<sp>) in the body of the play are linked to <castItem> elements in the <castList> using the who attribute.
<castItem type="role"> + <role xml:id="Barnardo">Bernardo</role> +</castItem> +<castItem type="role"> + <role xml:id="Francisco">Francisco</role> + <roleDesc>a soldier</roleDesc> +</castItem> +<!-- ... --> +<sp who="#Barnardo"> + <speaker>Bernardo</speaker> + <l n="1">Who's there?</l> +</sp> +<sp who="#Francisco"> + <speaker>Francisco</speaker> + <l n="2">Nay, answer me: stand, and unfold yourself.</l> +</sp>
Note

For transcribed speech, this will typically identify a participant or participant group; in other contexts, it will point to any identified <person> element.

3.2. att.cReferencing

att.cReferencing provides attributes that may be used to supply a canonical reference as a means of identifying the target of a pointer.
Moduletei
Membersref
Attributes
cRef(canonical reference) specifies the destination of the pointer by supplying a canonical reference expressed using the scheme defined in a <refsDecl> element in the TEI header
StatusOptional
Datatypeteidata.text
Note

The value of cRef should be constructed so that when the algorithm for the resolution of canonical references (described in section 16.2.5. Canonical References) is applied to it the result is a valid URI reference to the intended target.

The <refsDecl> to use may be indicated with the decls attribute.

Currently these Guidelines only provide for a single canonical reference to be encoded on any given <ptr> element.

3.3. att.canonical

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. [13.1.1. Linking Names and Their Referents]
Moduletei
Membersatt.naming[att.personal[name orgName] author event pubPlace rs] authority catDesc funder publisher relation resp respStmt sponsor title
Attributes
keyprovides an externally-defined means of identifying the entity (or entities) being named, using a coded value of some kind.
StatusOptional
Datatypeteidata.text
<author> + <name key="name 427308" +  type="organisation">[New Zealand Parliament, Legislative Council]</name> +</author>
<author> + <name key="Hugo, Victor (1802-1885)" +  ref="http://www.idref.fr/026927608">Victor Hugo</name> +</author>
Note

The value may be a unique identifier from a database, or any other externally-defined string identifying the referent.

No particular syntax is proposed for the values of the key attribute, since its form will depend entirely on practice within a given project. For the same reason, this attribute is not recommended in data interchange, since there is no way of ensuring that the values used by one project are distinct from those used by another. In such a situation, a preferable approach for magic tokens which follows standard practice on the Web is to use a ref attribute whose value is a tag URI as defined in RFC 4151.

ref(reference) provides an explicit means of locating a full definition or identity for the entity being named by means of one or more URIs.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
<name ref="http://viaf.org/viaf/109557338" + type="person">Seamus Heaney</name>
Note

The value must point directly to one or more XML elements or other resources by means of one or more URIs, separated by whitespace. If more than one is supplied the implication is that the name identifies several distinct entities.

3.4. att.datable

att.datable provides attributes for normalization of elements that contain dates, times, or datable events. [3.6.4. Dates and Times 13.4. Dates]
Moduletei
Membersauthor change event funder langKnown licence name orgName relation resp sponsor title
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
+<sch:rule context="tei:*[@calendar]"> +<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more + systems or calendars to which the date represented by the content of this element belongs, + but this <sch:name/> element has no textual content.</sch:assert> +</sch:rule>
He was born on <date calendar="#gregorian">Feb. 22, 1732</date> (<date calendar="#julian" + when="1732-02-22">Feb. 11, 1731/32, + O.S.</date>). +
He was born on <date calendar="#gregorian #julian" + when="1732-02-22">Feb. 22, 1732 + (Feb. 11, 1731/32, O.S.)</date>. +
Note

Note that the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized.

periodsupplies pointers to one or more definitions of named periods of time (typically <category>s or <calendar>s) within which the datable item is understood to have occurred.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

This ‘superclass’ provides attributes that can be used to provide normalized values of temporal information. By default, the attributes from the att.datable.w3c class are provided. If the module for names & dates is loaded, this class also provides attributes from the att.datable.iso and att.datable.custom classes. In general, the possible values of attributes restricted to the W3C datatypes form a subset of those values available via the ISO 8601 standard. However, the greater expressiveness of the ISO datatypes may not be needed, and there exists much greater software support for the W3C datatypes.

3.5. att.datable.custom

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). [13.4. Dates]
Modulenamesdates
Membersatt.datable[author change event funder langKnown licence name orgName relation resp sponsor title] date nationality residence
Attributes
when-customsupplies the value of a date or time in some custom standard form.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
The following are examples of custom date or time formats that are not valid ISO or W3C format normalizations, normalized to a different dating system
<p>Alhazen died in Cairo on the +<date when="1040-03-06" +  when-custom="431-06-12"> 12th day of Jumada t-Tania, 430 AH + </date>.</p> +<p>The current world will end at the +<date when="2012-12-21" +  when-custom="13.0.0.0.0">end of B'ak'tun 13</date>.</p> +<p>The Battle of Meggidu + (<date when-custom="Thutmose_III:23">23rd year of reign of Thutmose III</date>).</p> +<p>Esidorus bixit in pace annos LXX plus minus sub +<date when-custom="Ind:4-10-11">die XI mensis Octobris indictione IIII</date> +</p>
Not all custom date formulations will have Gregorian equivalents.The when-custom attribute and other custom dating are not constrained to a datatype by the TEI, but individual projects are recommended to regularize and document their dating formats.
notBefore-customspecifies the earliest possible date for the event in some custom standard form.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
notAfter-customspecifies the latest possible date for the event in some custom standard form.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
from-customindicates the starting point of the period in some custom standard form.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
<event xml:id="FIRE1" + datingMethod="#julian" + from-custom="1666-09-02" + to-custom="1666-09-05"> + <head>The Great Fire of London</head> + <p>The Great Fire of London burned through a large part +   of the city of London.</p> +</event>
to-customindicates the ending point of the period in some custom standard form.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
datingPointsupplies a pointer to some location defining a named point in time with reference to which the datable item is understood to have occurred
StatusOptional
Datatypeteidata.pointer
datingMethodsupplies a pointer to a <calendar> element or other means of interpreting the values of the custom dating attributes.
StatusOptional
Datatypeteidata.pointer
Contayning the Originall, Antiquity, Increaſe, Moderne + eſtate, and deſcription of that Citie, written in the yeare +<date when-custom="1598" + calendar="#julian" + datingMethod="#julian">1598</date>. by Iohn Stow + Citizen of London.
In this example, the calendar attribute points to a <calendar> element for the Julian calendar, specifying that the text content of the <date> element is a Julian date, and the datingMethod attribute also points to the Julian calendar to indicate that the content of the when-custom attribute value is Julian too.
<date when="1382-06-28" + when-custom="6890-06-20" + datingMethod="#creationOfWorld"> μηνὶ Ἰουνίου εἰς <num>κ</num> ἔτους <num>ςωϞ</num> +</date>
In this example, a date is given in a Mediaeval text measured ‘from the creation of the world’, which is normalized (in when) to the Gregorian date, but is also normalized (in when-custom) to a machine-actionable, numeric version of the date from the Creation.
Note

Note that the datingMethod attribute (unlike calendar defined in att.datable) defines the calendar or dating system to which the date described by the parent element is normalized (i.e. in the when-custom or other X-custom attributes), not the calendar of the original date in the element.

3.6. att.datable.iso

att.datable.iso provides attributes for normalization of elements that contain datable events using the ISO 8601:2004 standard. [3.6.4. Dates and Times 13.4. Dates]
Modulenamesdates
Membersatt.datable[author change event funder langKnown licence name orgName relation resp sponsor title]
Attributes
when-isosupplies the value of a date or time in a standard form.
StatusOptional
Datatypeteidata.temporal.iso
The following are examples of ISO date, time, and date & time formats that are not valid W3C format normalizations.
<date when-iso="1996-09-24T07:25+00">Sept. 24th, 1996 at 3:25 in the morning</date> +<date when-iso="1996-09-24T03:25-04">Sept. 24th, 1996 at 3:25 in the morning</date> +<time when-iso="1999-01-04T20:42-05">4 Jan 1999 at 8:42 pm</time> +<time when-iso="1999-W01-1T20,70-05">4 Jan 1999 at 8:42 pm</time> +<date when-iso="2006-05-18T10:03">a few minutes after ten in the morning on Thu 18 May</date> +<time when-iso="03:00">3 A.M.</time> +<time when-iso="14">around two</time> +<time when-iso="15,5">half past three</time>
All of the examples of the when attribute in the att.datable.w3c class are also valid with respect to this attribute.
He likes to be punctual. I said <q> + <time when-iso="12">around noon</time> +</q>, and he showed up at <time when-iso="12:00:00">12 O'clock</time> on the dot.
The second occurence of <time> could have been encoded with the when attribute, as 12:00:00 is a valid time with respect to the W3C XML Schema Part 2: Datatypes Second Edition specification. The first occurence could not.
notBefore-isospecifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.iso
notAfter-isospecifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.iso
from-isoindicates the starting point of the period in standard form.
StatusOptional
Datatypeteidata.temporal.iso
to-isoindicates the ending point of the period in standard form.
StatusOptional
Datatypeteidata.temporal.iso
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 ISO 8601:2004, using the Gregorian calendar.

If both when-iso and dur-iso are specified, the values should be interpreted as indicating a span of time by its starting time (or date) and duration. That is,
<date when-iso="2007-06-01" dur-iso="P8D"/>
indicates the same time period as
<date when-iso="2007-06-01/P8D"/>

In providing a ‘regularized’ form, no claim is made that the form in the source text is incorrect; the regularized form is simply that chosen as the main form for purposes of unifying variant forms under a single heading.

3.7. att.datable.w3c

att.datable.w3c provides attributes for normalization of elements that contain datable events conforming to the W3C XML Schema Part 2: Datatypes Second Edition. [3.6.4. Dates and Times 13.4. Dates]
Moduletei
Membersatt.datable[author change event funder langKnown licence name orgName relation resp sponsor title] birth date death education nationality occupation persName residence socecStatus state trait
Attributes
whensupplies the value of the date or time in a standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.w3c
Examples of W3C date, time, and date & time formats.
<p> + <date when="1945-10-24">24 Oct 45</date> + <date when="1996-09-24T07:25:00Z">September 24th, 1996 at 3:25 in the morning</date> + <time when="1999-01-04T20:42:00-05:00">Jan 4 1999 at 8 pm</time> + <time when="14:12:38">fourteen twelve and 38 seconds</time> + <date when="1962-10">October of 1962</date> + <date when="--06-12">June 12th</date> + <date when="---01">the first of the month</date> + <date when="--08">August</date> + <date when="2006">MMVI</date> + <date when="0056">AD 56</date> + <date when="-0056">56 BC</date> +</p>
This list begins in + the year 1632, more precisely on Trinity Sunday, i.e. the Sunday after + Pentecost, in that year the +<date calendar="#julian" + when="1632-06-06">27th of May (old style)</date>.
<opener> + <dateline> +  <placeName>Dorchester, Village,</placeName> +  <date when="1828-03-02">March 2d. 1828.</date> + </dateline> + <salute>To +   Mrs. Cornell,</salute> Sunday <time when="12:00:00">noon.</time> +</opener>
notBeforespecifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.w3c
notAfterspecifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.w3c
fromindicates the starting point of the period in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.w3c
toindicates the ending point of the period in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.w3c
Schematron
+<sch:rule context="tei:*[@when]"> +<sch:report test="@notBefore|@notAfter|@from|@to" + role="nonfatal">The @when attribute cannot be used with any other att.datable.w3c attributes.</sch:report> +</sch:rule>
Schematron
+<sch:rule context="tei:*[@from]"> +<sch:report test="@notBefore" + role="nonfatal">The @from and @notBefore attributes cannot be used together.</sch:report> +</sch:rule>
Schematron
+<sch:rule context="tei:*[@to]"> +<sch:report test="@notAfter" + role="nonfatal">The @to and @notAfter attributes cannot be used together.</sch:report> +</sch:rule>
Example
<date from="1863-05-28" to="1863-06-01">28 May through 1 June 1863</date>
Note

The value of these attributes should be a normalized representation of the date, time, or combined date & time intended, in any of the standard formats specified by XML Schema Part 2: Datatypes Second Edition, using the Gregorian calendar.

The most commonly-encountered format for the date portion of a temporal attribute is yyyy-mm-dd, but yyyy, --mm, ---dd, yyyy-mm, or --mm-dd may also be used. For the time part, the form hh:mm:ss is used.

Note that this format does not currently permit use of the value 0000 to represent the year 1 BCE; instead the value -0001 should be used.

3.8. att.declarable

att.declarable provides attributes for those elements in the TEI header which may be independently selected by means of the special purpose decls attribute. [15.3. Associating Contextual Information with a Text]
Moduletei
Membersavailability bibl editorialDecl listBibl seriesStmt sourceDesc
Attributes
defaultindicates whether or not this element is selected by default when its parent is selected.
StatusOptional
Datatypeteidata.truthValue
Legal values are:
true
This element is selected if its parent is selected
false
This element can only be selected explicitly, unless it is the only one of its kind, in which case it is selected if its parent is selected.[Default]
Note

The rules governing the association of declarable elements with individual parts of a TEI text are fully defined in chapter 15.3. Associating Contextual Information with a Text. Only one element of a particular type may have a default attribute with a value of true.

3.9. att.declaring

att.declaring provides attributes for elements which may be independently associated with a particular declarable element within the header, thus overriding the inherited default for that element. [15.3. Associating Contextual Information with a Text]
Moduletei
Membersback body p ref text
Attributes
decls(declarations) identifies one or more declarable elements within the header, which are understood to apply to the element bearing this attribute and its content.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

The rules governing the association of declarable elements with individual parts of a TEI text are fully defined in chapter 15.3. Associating Contextual Information with a Text.

3.10. att.docStatus

att.docStatus provides attributes for use on metadata elements describing the status of a document.
Moduletei
Membersbibl change revisionDesc
Attributes
statusdescribes the status of a document either currently or, when associated with a dated element, at the time indicated.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
approved
candidate
cleared
deprecated
draft
[Default]
embargoed
expired
frozen
galley
proposed
published
recommendation
submitted
unfinished
withdrawn
Example
<revisionDesc status="published"> + <change when="2010-10-21" +  status="published"/> + <change when="2010-10-02" status="cleared"/> + <change when="2010-08-02" +  status="embargoed"/> + <change when="2010-05-01" status="frozen" +  who="#MSM"/> + <change when="2010-03-01" status="draft" +  who="#LB"/> +</revisionDesc>

3.11. att.editLike

att.editLike provides attributes describing the nature of an encoded scholarly intervention or interpretation of any kind. [3.5. Simple Editorial Changes 10.3.1. Origination 13.3.2. The Person Element 11.3.1.1. Core Elements for Transcriptional Work]
Moduletei
Membersevent langKnown name orgName relation
Attributes
evidenceindicates the nature of the evidence supporting the reliability or accuracy of the intervention or interpretation.
StatusOptional
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
Suggested values include:
internal
there is internal evidence to support the intervention.
external
there is external evidence to support the intervention.
conjecture
the intervention or interpretation has been made by the editor, cataloguer, or scholar on the basis of their expertise.
instantindicates whether this is an instant revision or not.
StatusOptional
Datatypeteidata.xTruthValue
Defaultfalse
Note

The members of this attribute class are typically used to represent any kind of editorial intervention in a text, for example a correction or interpretation, or to date or localize manuscripts etc.

Each pointer on the source (if present) corresponding to a witness or witness group should reference a bibliographic citation such as a <witness>, <msDesc>, or <bibl> element, or another external bibliographic citation, documenting the source concerned.

3.12. att.fragmentable

att.fragmentable provides attributes for representing fragmentation of a structural element, typically as a consequence of some overlapping hierarchy.
Moduletei
Membersp
Attributes
partspecifies whether or not its parent element is fragmented in some way, typically by some other overlapping structure: for example a speech which is divided between two or more verse stanzas, a paragraph which is split across a page division, a verse line which is divided between two speakers.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
Y
(yes) the element is fragmented in some (unspecified) respect
N
(no) the element is not fragmented, or no claim is made as to its completeness[Default]
I
(initial) this is the initial part of a fragmented element
M
(medial) this is a medial part of a fragmented element
F
(final) this is the final part of a fragmented element
Note

The values I, M, or F should be used only where it is clear how the element may be reconstituted.

3.13. att.global

att.global provides attributes common to all elements in the TEI encoding scheme. [1.3.1.1. Global Attributes]
Moduletei
MembersTEI author authority availability back bibl biblScope body catDesc category change classDecl edition editionStmt editorialDecl encodingDesc event fileDesc funder head langKnown licence listBibl listRelation name note num orgName p profileDesc pubPlace publicationStmt publisher ref relation resp respStmt revisionDesc rs seriesStmt sourceDesc sponsor taxonomy teiHeader text title titleStmt
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
StatusOptional
DatatypeID
Note

The xml:id attribute may be used to specify a canonical reference for an element; see section 3.11. Reference Systems.

n(number) gives a number (or other label) for an element, which is not necessarily unique within the document.
StatusOptional
Datatypeteidata.text
Note

The value of this attribute is always understood to be a single token, even if it contains space or other punctuation characters, and need not be composed of numbers only. It is typically used to specify the numbering of chapters, sections, list items, etc.; it may also be used in the specification of a standard reference system for the text.

xml:lang(language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
StatusOptional
Datatypeteidata.language
<p> … The consequences of + this rapid depopulation were the loss of the last +<foreign xml:lang="rap">ariki</foreign> or chief + (Routledge 1920:205,210) and their connections to + ancestral territorial organization.</p>
Note

The xml:lang value will be inherited from the immediately enclosing element, or from its parent, and so on up the document hierarchy. It is generally good practice to specify xml:lang at the highest appropriate level, noticing that a different default may be needed for the <teiHeader> from that needed for the associated resource element or elements, and that a single TEI document may contain texts in many languages.

Only attributes with free text values (rare in these guidelines) will be in the scope of xml:lang.

The authoritative list of registered language subtags is maintained by IANA and is available at http://www.iana.org/assignments/language-subtag-registry. For a good general overview of the construction of language tags, see https://www.w3.org/International/articles/language-tags/, and for a practical step-by-step guide, see https://www.w3.org/International/questions/qa-choosing-language-tags.en.php.

The value used must conform with BCP 47. If the value is a private use code (i.e., starts with x- or contains -x-), a <language> element with a matching value for its ident attribute should be supplied in the TEI header to document this value. Such documentation may also optionally be supplied for non-private-use codes, though these must remain consistent with their (IETF)Internet Engineering Task Force definitions.

xml:baseprovides a base URI reference with which applications can resolve relative URI references into absolute URI references.
StatusOptional
Datatypeteidata.pointer
<div type="bibl"> + <head>Bibliography</head> + <listBibl xml:base="http://www.lib.ucdavis.edu/BWRP/Works/"> +  <bibl> +   <author> +    <name>Landon, Letitia Elizabeth</name> +   </author> +   <ref target="LandLVowOf.sgm"> +    <title>The Vow of the Peacock</title> +   </ref> +  </bibl> +  <bibl> +   <author> +    <name>Compton, Margaret Clephane</name> +   </author> +   <ref target="NortMIrene.sgm"> +    <title>Irene, a Poem in Six Cantos</title> +   </ref> +  </bibl> +  <bibl> +   <author> +    <name>Taylor, Jane</name> +   </author> +   <ref target="TaylJEssay.sgm"> +    <title>Essays in Rhyme on Morals and Manners</title> +   </ref> +  </bibl> + </listBibl> +</div>
xml:spacesignals an intention about how white space should be managed by applications.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
default
signals that the application's default white-space processing modes are acceptable
preserve
indicates the intent that applications preserve all white space
Note

The XML specification provides further guidance on the use of this attribute. Note that many parsers may not handle xml:space correctly.

3.14. att.global.analytic

att.global.analytic I have needed to include this because it somehow disappeared from this customization. I do not know why this was necessary.
Modulederived-module-SPEAR
Membersatt.global[TEI author authority availability back bibl biblScope body catDesc category change classDecl edition editionStmt editorialDecl encodingDesc event fileDesc funder head langKnown licence listBibl listRelation name note num orgName p profileDesc pubPlace publicationStmt publisher ref relation resp respStmt revisionDesc rs seriesStmt sourceDesc sponsor taxonomy teiHeader text title titleStmt] occupation socecStatus state trait
Attributes
ana
StatusOptional
Datatypeteidata.text
Schematron
+<sch:rule context="//tei:ab/tei:listEvent/tei:event/@ana | //tei:langKnown/@ana | //tei:occupation/@ana + | //tei:socecStatus/@ana | //tei:state/@ana | //tei:trait/@ana"> +<sch:let name="anaTokens" + value="tokenize(., ' ')"/> +<sch:assert test=" every $i in $anaTokens satisfies matches($i, concat('http://syriaca.org/keyword/', + '\w+'))" + role="error"> Each @ana attribute value must start with "http://syriaca.org/keyword/" and multiple + values must be space separated. +</sch:assert> +<sch:assert test="count(distinct-values($anaTokens)) = count($anaTokens)" + role="error"> The same keyword URI may not appear twice as the value of the @ana attribute. </sch:assert> +<sch:report test="contains(., ',') or contains(., ';')"> Multiple @ana attributes should be separated with one blank space +</sch:report> +<sch:report test=" every $i in $anaTokens satisfies contains(substring-after($i, 'http://syriaca.org/keyword'), + 'http:')" + role="error"> Multiple @ana attributes should be separated with one blank space +</sch:report> +</sch:rule>

3.15. att.global.linking

att.global.linking provides a set of attributes for hypertextual linking. [16. Linking, Segmentation, and Alignment]
Modulelinking
Membersatt.global[TEI author authority availability back bibl biblScope body catDesc category change classDecl edition editionStmt editorialDecl encodingDesc event fileDesc funder head langKnown licence listBibl listRelation name note num orgName p profileDesc pubPlace publicationStmt publisher ref relation resp respStmt revisionDesc rs seriesStmt sourceDesc sponsor taxonomy teiHeader text title titleStmt]
Attributes
corresp(corresponds) points to elements that correspond to the current element in some way.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
<group> + <text xml:id="t1-g1-t1" +  xml:lang="mi"> +  <body xml:id="t1-g1-t1-body1"> +   <div type="chapter"> +    <head>He Whakamaramatanga mo te Ture Hoko, Riihi hoki, i nga Whenua Maori, 1876.</head> +    <p>…</p> +   </div> +  </body> + </text> + <text xml:id="t1-g1-t2" +  xml:lang="en"> +  <body xml:id="t1-g1-t2-body1" +   corresp="#t1-g1-t1-body1"> +   <div type="chapter"> +    <head>An Act to regulate the Sale, Letting, and Disposal of Native Lands, 1876.</head> +    <p>…</p> +   </div> +  </body> + </text> +</group>
In this example a <group> contains two <text>s, each containing the same document in a different language. The correspondence is indicated using corresp. The language is indicated using xml:lang, whose value is inherited; both the tag with the corresp and the tag pointed to by the corresp inherit the value from their immediate parent.
+<!-- In a placeography called "places.xml" --><place xml:id="LOND1" + corresp="people.xml#LOND2 people.xml#GENI1"> + <placeName>London</placeName> + <desc>The city of London...</desc> +</place> +<!-- In a literary personography called "people.xml" --> +<person xml:id="LOND2" + corresp="places.xml#LOND1 #GENI1"> + <persName type="lit">London</persName> + <note> +  <p>Allegorical character representing the city of <placeName ref="places.xml#LOND1">London</placeName>.</p> + </note> +</person> +<person xml:id="GENI1" + corresp="places.xml#LOND1 #LOND2"> + <persName type="lit">London’s Genius</persName> + <note> +  <p>Personification of London’s genius. Appears as an +     allegorical character in mayoral shows. +  </p> + </note> +</person>
In this example, a <place> element containing information about the city of London is linked with two <person> elements in a literary personography. This correspondence represents a slightly looser relationship than the one in the preceding example; there is no sense in which an allegorical character could be substituted for the physical city, or vice versa, but there is obviously a correspondence between them.
synch(synchronous) points to elements that are synchronous with the current element.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
sameAspoints to an element that is the same as the current element.
StatusOptional
Datatypeteidata.pointer
copyOfpoints to an element of which the current element is a copy.
StatusOptional
Datatypeteidata.pointer
Note

Any content of the current element should be ignored. Its true content is that of the element being pointed at.

nextpoints to the next element of a virtual aggregate of which the current element is part.
StatusOptional
Datatypeteidata.pointer
Note

It is recommended that the element indicated be of the same type as the element bearing this attribute.

prev(previous) points to the previous element of a virtual aggregate of which the current element is part.
StatusOptional
Datatypeteidata.pointer
Note

It is recommended that the element indicated be of the same type as the element bearing this attribute.

excludepoints to elements that are in exclusive alternation with the current element.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
selectselects one or more alternants; if one alternant is selected, the ambiguity or uncertainty is marked as resolved. If more than one alternant is selected, the degree of ambiguity or uncertainty is marked as reduced by the number of alternants not selected.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

This attribute should be placed on an element which is superordinate to all of the alternants from which the selection is being made.

3.16. att.global.rendition

att.global.rendition provides rendering attributes common to all elements in the TEI encoding scheme. [1.3.1.1.3. Rendition Indicators]
Moduletei
Membersatt.global[TEI author authority availability back bibl biblScope body catDesc category change classDecl edition editionStmt editorialDecl encodingDesc event fileDesc funder head langKnown licence listBibl listRelation name note num orgName p profileDesc pubPlace publicationStmt publisher ref relation resp respStmt revisionDesc rs seriesStmt sourceDesc sponsor taxonomy teiHeader text title titleStmt]
Attributes
rend(rendition) indicates how the element in question was rendered or presented in the source text.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
<head rend="align(center) case(allcaps)"> + <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, +<lb/>On Her <lb/> + <hi rend="case(mixed)">New Blazing-World</hi>. +</head>
Note

These Guidelines make no binding recommendations for the values of the rend attribute; the characteristics of visual presentation vary too much from text to text and the decision to record or ignore individual characteristics varies too much from project to project. Some potentially useful conventions are noted from time to time at appropriate points in the Guidelines. The values of the rend attribute are a set of sequence-indeterminate individual tokens separated by whitespace.

stylecontains an expression in some formal style definition language which defines the rendering or presentation used for this element in the source text
StatusOptional
Datatypeteidata.text
<head style="text-align: center; font-variant: small-caps"> + <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, <lb/>On Her +<lb/> + <hi style="font-variant: normal">New Blazing-World</hi>. +</head>
Note

Unlike the attribute values of rend, which uses whitespace as a separator, the style attribute may contain whitespace. This attribute is intended for recording inline stylistic information concerning the source, not any particular output.

The formal language in which values for this attribute are expressed may be specified using the <styleDefDecl> element in the TEI header.

If style and rendition are both present on an element, then style overrides or complements rendition. style should not be used in conjunction with rend, because the latter does not employ a formal style definition language.

renditionpoints to a description of the rendering or presentation used for this element in the source text.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
<head rendition="#ac #sc"> + <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, <lb/>On Her +<lb/> + <hi rendition="#normal">New Blazing-World</hi>. +</head> +<!-- elsewhere... --> +<rendition xml:id="sc" + scheme="css">font-variant: small-caps</rendition> +<rendition xml:id="normal" + scheme="css">font-variant: normal</rendition> +<rendition xml:id="ac" + scheme="css">text-align: center</rendition>
Note

The rendition attribute is used in a very similar way to the class attribute defined for XHTML but with the important distinction that its function is to describe the appearance of the source text, not necessarily to determine how that text should be presented on screen or paper.

If rendition is used to refer to a style definition in a formal language like CSS, it is recommended that it not be used in conjunction with rend. Where both rendition and rend are supplied, the latter is understood to override or complement the former.

Each URI provided should indicate a <rendition> element defining the intended rendition in terms of some appropriate style language, as indicated by the scheme attribute.

3.17. att.global.responsibility

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. [1.3.1.1.4. Sources, certainty, and responsibility 3.5. Simple Editorial Changes 11.3.2.2. Hand, Responsibility, and Certainty Attributes 17.3. Spans and Interpretations 13.1.1. Linking Names and Their Referents]
Moduletei
Membersatt.global[TEI author authority availability back bibl biblScope body catDesc category change classDecl edition editionStmt editorialDecl encodingDesc event fileDesc funder head langKnown licence listBibl listRelation name note num orgName p profileDesc pubPlace publicationStmt publisher ref relation resp respStmt revisionDesc rs seriesStmt sourceDesc sponsor taxonomy teiHeader text title titleStmt]
Attributes
cert(certainty) signifies the degree of certainty associated with the intervention or interpretation.
StatusOptional
Datatypeteidata.probCert
resp(responsible party) indicates the agency responsible for the intervention or interpretation, for example an editor or transcriber.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

To reduce the ambiguity of a resp pointing directly to a person or organization, we recommend that resp be used to point not to an agent (<person> or <org>) but to a <respStmt>, <author>, <editor> or similar element which clarifies the exact role played by the agent. Pointing to multiple <respStmt>s allows the encoder to specify clearly each of the roles played in part of a TEI file (creating, transcribing, encoding, editing, proofing etc.).

Example
Blessed are the +<choice> + <sic>cheesemakers</sic> + <corr resp="#editor" cert="high">peacemakers</corr> +</choice>: for they shall be called the children of God.
Example
+<!-- in the <text> ... --><lg> +<!-- ... --> + <l>Punkes, Panders, baſe extortionizing +   sla<choice> +   <sic>n</sic> +   <corr resp="#JENS1_transcriber">u</corr> +  </choice>es,</l> +<!-- ... --> +</lg> +<!-- in the <teiHeader> ... --> +<!-- ... --> +<respStmt xml:id="JENS1_transcriber"> + <resp when="2014">Transcriber</resp> + <name>Janelle Jenstad</name> +</respStmt>

3.18. att.global.source

att.global.source provides attributes used by elements to point to an external source. [1.3.1.1.4. Sources, certainty, and responsibility 3.3.3. Quotation 8.3.4. Writing]
Moduletei
Membersatt.global[TEI author authority availability back bibl biblScope body catDesc category change classDecl edition editionStmt editorialDecl encodingDesc event fileDesc funder head langKnown licence listBibl listRelation name note num orgName p profileDesc pubPlace publicationStmt publisher ref relation resp respStmt revisionDesc rs seriesStmt sourceDesc sponsor taxonomy teiHeader text title titleStmt]
Attributes
sourcespecifies the source from which some aspect of this element is drawn.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
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>
Note

The source attribute points to an external source. When used on an element describing a schema component (<classRef>, <dataRef>, <elementRef>, <macroRef>, <moduleRef>, or <schemaSpec>), it identifies the source from which declarations for the components should be obtained.

On other elements it provides a pointer to the bibliographical source from which a quotation or citation is drawn.

In either case, the location may be provided using any form of URI, for example an absolute URI, a relative URI, a private scheme URI of the form tei:x.y.z, where x.y.z indicates the version number, e.g. tei:4.3.2 for TEI P5 release 4.3.2 or (as a special case) tei:current for whatever is the latest release, or a private scheme URI that is expanded to an absolute URI as documented in a <prefixDef>.

When used on elements describing schema components, source should have only one value; when used on other elements multiple values are permitted.

Example
<p> +<!-- ... --> As Willard McCarty (<bibl xml:id="mcc_2012">2012, p.2</bibl>) tells us, <quote source="#mcc_2012">‘Collaboration’ is a problematic and should be a contested +   term.</quote> +<!-- ... --> +</p>
Example
<p> +<!-- ... --> + <quote source="#chicago_15_ed">Grammatical theories are in flux, and the more we learn, the +   less we seem to know.</quote> +<!-- ... --> +</p> +<!-- ... --> +<bibl xml:id="chicago_15_ed"> + <title level="m">The Chicago Manual of Style</title>, +<edition>15th edition</edition>. <pubPlace>Chicago</pubPlace>: <publisher>University of +   Chicago Press</publisher> (<date>2003</date>), <biblScope unit="page">p.147</biblScope>. + +</bibl>
Example
<elementRef key="p" source="tei:2.0.1"/>
Include in the schema an element named <p> available from the TEI P5 2.0.1 release.
Example
<schemaSpec ident="myODD" + source="mycompiledODD.xml"> +<!-- further declarations specifying the components required --> +</schemaSpec>
Create a schema using components taken from the file mycompiledODD.xml.

3.19. att.internetMedia

att.internetMedia provides attributes for specifying the type of a computer resource using a standard taxonomy.
Moduletei
Membersref
Attributes
mimeType(MIME media type) specifies the applicable multimedia internet mail extension (MIME) media type
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
ExampleIn this example mimeType is used to indicate that the URL points to a TEI XML file encoded in UTF-8.
<ref mimeType="application/tei+xml; charset=UTF-8" + target="https://raw.githubusercontent.com/TEIC/TEI/dev/P5/Source/guidelines-en.xml"/>
Note

This attribute class provides an attribute for describing a computer resource, typically available over the internet, using a value taken from a standard taxonomy. At present only a single taxonomy is supported, the Multipurpose Internet Mail Extensions (MIME) Media Type system. This typology of media types is defined by the Internet Engineering Task Force in RFC 2046. The list of types is maintained by the Internet Assigned Numbers Authority (IANA). The mimeType attribute must have a value taken from this list.

3.20. att.locatable

att.locatable provides attributes for referencing locations by pointing to entries in a canonical list of places. [2.3.9. The Unit Declaration 13.3.4.3. States, Traits, and Events]
Moduletei
Membersevent
Attributes
whereindicates one or more locations by pointing to a <place> element or other canonical description.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace

3.21. att.naming

att.naming provides attributes common to elements which refer to named persons, places, organizations etc. [3.6.1. Referring Strings 13.3.6. Names and Nyms]
Moduletei
Membersatt.personal[name orgName] author event pubPlace rs
Attributes
rolemay be used to specify further information about the entity referenced by this name in the form of a set of whitespace-separated values, for example the occupation of a person, or the status of a place.
StatusOptional
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
nymRef(reference to the canonical name) provides a means of locating the canonical form (nym) of the names associated with the object named by the element bearing it.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

The value must point directly to one or more XML elements by means of one or more URIs, separated by whitespace. If more than one is supplied, the implication is that the name is associated with several distinct canonical names.

3.22. att.personal

att.personal (attributes for components of names usually, but not necessarily, personal names) common attributes for those elements which form part of a name usually, but not necessarily, a personal name. [13.2.1. Personal Names]
Moduletei
Membersname orgName
Attributes
fullindicates whether the name component is given in full, as an abbreviation or simply as an initial.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
yes
(yes) the name component is spelled out in full.[Default]
abb
(abbreviated) the name component is given in an abbreviated form.
init
(initial letter) the name component is indicated only by one initial.
sort(sort) specifies the sort order of the name component in relation to others within the name.
StatusOptional
Datatypeteidata.count

3.23. att.placement

att.placement provides attributes for describing where on the source page or object a textual element appears. [3.5.3. Additions, Deletions, and Omissions 11.3.1.4. Additions and Deletions]
Moduletei
Membershead note
Attributes
placespecifies where this item is placed.
StatusRecommended
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
Suggested values include:
top
at the top of the page
bottom
at the foot of the page
margin
in the margin (left, right, or both)
opposite
on the opposite, i.e. facing, page
overleaf
on the other side of the leaf
above
above the line
right
to the right, e.g. to the right of a vertical line of text, or to the right of a figure
below
below the line
left
to the left, e.g. to the left of a vertical line of text, or to the left of a figure
end
at the end of e.g. chapter or volume.
inline
within the body of the text.
inspace
in a predefined space, for example left by an earlier scribe.
<add place="margin">[An addition written in the margin]</add> +<add place="bottom opposite">[An addition written at the + foot of the current page and also on the facing page]</add>
<note place="bottom">Ibid, p.7</note>

3.24. att.pointing

att.pointing provides a set of attributes used by all elements which point to other elements by means of one or more URI references. [1.3.1.1.2. Language Indicators 3.7. Simple Links and Cross-References]
Moduletei
Memberslicence note ref
Attributes
targetLangspecifies the language of the content to be found at the destination referenced by target, using a ‘language tag’ generated according to BCP 47.
StatusOptional
Datatypeteidata.language
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>
<linkGrp xml:id="pol-swh_aln_2.1-linkGrp"> + <ptr xml:id="pol-swh_aln_2.1.1-ptr" +  target="pol/UDHR/text.xml#pol_txt_1-head" +  type="tuv" +  targetLang="pl"/> + <ptr xml:id="pol-swh_aln_2.1.2-ptr" +  target="swh/UDHR/text.xml#swh_txt_1-head" +  type="tuv" +  targetLang="sw"/> +</linkGrp>
In the example above, the <linkGrp> combines pointers at parallel fragments of the Universal Declaration of Human Rights: one of them is in Polish, the other in Swahili.
Note

The value must conform to BCP 47. If the value is a private use code (i.e., starts with x- or contains -x-), a <language> element with a matching value for its ident attribute should be supplied in the TEI header to document this value. Such documentation may also optionally be supplied for non-private-use codes, though these must remain consistent with their (IETF)Internet Engineering Task Force definitions.

targetspecifies the destination of the reference by supplying one or more URI References
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

One or more syntactically valid URI references, separated by whitespace. Because whitespace is used to separate URIs, no whitespace is permitted inside a single URI. If a whitespace character is required in a URI, it should be escaped with the normal mechanism, e.g. TEI%20Consortium.

evaluate(evaluate) specifies the intended meaning when the target of a pointer is itself a pointer.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
all
if the element pointed to is itself a pointer, then the target of that pointer will be taken, and so on, until an element is found which is not a pointer.
one
if the element pointed to is itself a pointer, then its target (whether a pointer or not) is taken as the target of this pointer.
none
no further evaluation of targets is carried out beyond that needed to find the element specified in the pointer's target.
Note

If no value is given, the application program is responsible for deciding (possibly on the basis of user input) how far to trace a chain of pointers.

3.25. att.ranging

att.ranging provides attributes for describing numerical ranges.
Moduletei
Membersnum
Attributes
atLeastgives a minimum estimated value for the approximate measurement.
StatusOptional
Datatypeteidata.numeric
atMostgives a maximum estimated value for the approximate measurement.
StatusOptional
Datatypeteidata.numeric
minwhere the measurement summarizes more than one observation or a range, supplies the minimum value observed.
StatusOptional
Datatypeteidata.numeric
maxwhere the measurement summarizes more than one observation or a range, supplies the maximum value observed.
StatusOptional
Datatypeteidata.numeric
confidencespecifies the degree of statistical confidence (between zero and one) that a value falls within the range specified by min and max, or the proportion of observed values that fall within that range.
StatusOptional
Datatypeteidata.probability
Example
The MS. was lost in transmission by mail from <del rend="overstrike"> + <gap reason="illegible" +  extent="one or two letters" atLeast="1" atMost="2" unit="chars"/> +</del> Philadelphia to the Graphic office, New York. +
Example
Americares has been supporting the health sector in Eastern + Europe since 1986, and since 1992 has provided <measure atLeast="120000000" unit="USD" + commodity="currency">more than + $120m</measure> in aid to Ukrainians. +

3.26. att.sortable

att.sortable provides attributes for elements in lists or groups that are sortable, but whose sorting key cannot be derived mechanically from the element content. [9.1. Dictionary Body and Overall Structure]
Moduletei
Membersbibl event listBibl listRelation relation
Attributes
sortKeysupplies the sort key for this element in an index, list or group which contains it.
StatusOptional
Datatypeteidata.word
David's other principal backer, Josiah + ha-Kohen <index indexName="NAMES"> + <term sortKey="Azarya_Josiah_Kohen">Josiah ha-Kohen b. Azarya</term> +</index> b. Azarya, son of one of the last gaons of Sura was David's own first + cousin.
Note

The sort key is used to determine the sequence and grouping of entries in an index. It provides a sequence of characters which, when sorted with the other values, will produced the desired order; specifics of sort key construction are application-dependent

Dictionary order often differs from the collation sequence of machine-readable character sets; in English-language dictionaries, an entry for 4-H will often appear alphabetized under ‘fourh’, and McCoy may be alphabetized under ‘maccoy’, while A1, A4, and A5 may all appear in numeric order ‘alphabetized’ between ‘a-’ and ‘AA’. The sort key is required if the orthography of the dictionary entry does not suffice to determine its location.

3.27. att.typed

att.typed provides attributes that can be used to classify or subclassify elements in any way. [1.3.1. Attribute Classes 17.1.1. Words and Above 3.6.1. Referring Strings 3.7. Simple Links and Cross-References 3.6.5. Abbreviations and Their Expansions 3.13.1. Core Tags for Verse 7.2.5. Speech Contents 4.1.1. Un-numbered Divisions 4.1.2. Numbered Divisions 4.2.1. Headings and Trailers 4.4. Virtual Divisions 13.3.2.3. Personal Relationships 11.3.1.1. Core Elements for Transcriptional Work 16.1.1. Pointers and Links 16.3. Blocks, Segments, and Anchors 12.2. Linking the Apparatus to the Text 22.5.1.2. Defining Content Models: RELAX NG 8.3. Elements Unique to Spoken Texts 23.3.1.3. Modification of Attribute and Attribute Value Lists]
Moduletei
MembersTEI bibl change event head listBibl listRelation name note num orgName ref relation rs text title
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
StatusOptional
Datatypeteidata.enumerated
<div type="verse"> + <head>Night in Tarras</head> + <lg type="stanza"> +  <l>At evening tramping on the hot white road</l> +  <l>…</l> + </lg> + <lg type="stanza"> +  <l>A wind sprang up from nowhere as the sky</l> +  <l>…</l> + </lg> +</div>
Note

The type attribute is present on a number of elements, not all of which are members of att.typed, usually because these elements restrict the possible values for the attribute in a specific way.

subtype(subtype) provides a sub-categorization of the element, if needed
StatusOptional
Datatypeteidata.enumerated
Note

The subtype attribute may be used to provide any sub-classification for the element additional to that provided by its type attribute.

Schematron
+<sch:rule context="tei:*[@subtype]"> +<sch:assert test="@type">The <sch:name/> element should not be categorized in detail with @subtype unless also categorized in general with @type</sch:assert> +</sch:rule>
Note

When appropriate, values from an established typology should be used. Alternatively a typology may be defined in the associated TEI header. If values are to be taken from a project-specific list, this should be defined using the <valList> element in the project-specific schema description, as described in 23.3.1.3. Modification of Attribute and Attribute Value Lists .

3.28. att.written

att.written provides attributes to indicate the hand in which the content of an element was written in the source being transcribed. [1.3.1. Attribute Classes]
Moduletei
Membershead note p text
Attributes
handpoints to a <handNote> element describing the hand considered responsible for the content of the element concerned.
StatusOptional
Datatypeteidata.pointer

4. Macros

4.1. macro.paraContent

macro.paraContent (paragraph content) defines the content of paragraphs and similar elements. [1.3. The TEI Class System]
Moduletei
Used by
corr orig p ref reg sic title
Content model
+<content>
+ <alternate minOccurs="0"
+  maxOccurs="unbounded">
+  <textNode/>
+  <classRef key="model.paraPart"/>
+ </alternate>
+</content>
+    ⚓
Declaration
+macro.paraContent = ( text | model.paraPart )*⚓

4.2. macro.phraseSeq

macro.phraseSeq (phrase sequence) defines a sequence of character data and phrase-level elements. [1.4.1. Standard Content Models]
Moduletei
Used by
author edition editor name num orgName persName placeName pubPlace publisher
Content model
+<content>
+ <alternate minOccurs="0"
+  maxOccurs="unbounded">
+  <textNode/>
+  <classRef key="model.gLike"/>
+  <classRef key="model.attributable"/>
+  <classRef key="model.phrase"/>
+  <classRef key="model.global"/>
+ </alternate>
+</content>
+    ⚓
Declaration
+macro.phraseSeq =
+   ( text | model.gLike | model.attributable | model.phrase | model.global )*⚓

4.3. macro.phraseSeq.limited

macro.phraseSeq.limited (limited phrase sequence) defines a sequence of character data and those phrase-level elements that are not typically used for transcribing extant documents. [1.4.1. Standard Content Models]
Moduletei
Used by
langKnown resp
Content model
+<content>
+ <alternate minOccurs="0"
+  maxOccurs="unbounded">
+  <textNode/>
+  <classRef key="model.limitedPhrase"/>
+  <classRef key="model.global"/>
+ </alternate>
+</content>
+    ⚓
Declaration
+macro.phraseSeq.limited = ( text | model.limitedPhrase | model.global )*⚓

4.4. macro.specialPara

macro.specialPara ('special' paragraph content) defines the content model of elements such as notes or list items, which either contain a series of component-level elements or else have the same structure as a paragraph, containing a series of phrase-level and inter-level elements. [1.3. The TEI Class System]
Moduletei
Used by
change note
Content model
+<content>
+ <alternate minOccurs="0"
+  maxOccurs="unbounded">
+  <textNode/>
+  <classRef key="model.gLike"/>
+  <classRef key="model.phrase"/>
+  <classRef key="model.inter"/>
+  <classRef key="model.divPart"/>
+  <classRef key="model.global"/>
+ </alternate>
+</content>
+    ⚓
Declaration
+macro.specialPara =
+   (
+      text
+    | model.gLike
+    | model.phrase
+    | model.inter
+    | model.divPart
+    | model.global
+   )*⚓

5. Datatypes

5.1. teidata.certainty

teidata.certainty defines the range of attribute values expressing a degree of certainty.
Moduletei
Used by
teidata.probCert
Content model
+<content>
+ <valList type="closed">
+  <valItem ident="high"/>
+  <valItem ident="medium"/>
+  <valItem ident="low"/>
+  <valItem ident="unknown"/>
+ </valList>
+</content>
+    ⚓
Declaration
+teidata.certainty = "high" | "medium" | "low" | "unknown"⚓
Note

Certainty may be expressed by one of the predefined symbolic values high, medium, or low. The value unknown should be used in cases where the encoder does not wish to assert an opinion about the matter.

5.2. teidata.count

teidata.count defines the range of attribute values used for a non-negative integer value used as a count.
Moduletei
Used by
Content model
+<content>
+ <dataRef name="nonNegativeInteger"/>
+</content>
+    ⚓
Declaration
+teidata.count = xsd:nonNegativeInteger⚓
Note

Any positive integer value or zero is permitted

5.3. teidata.duration.iso

teidata.duration.iso defines the range of attribute values available for representation of a duration in time using ISO 8601 standard formats
Moduletei
Used by
Content model
+<content>
+ <dataRef name="token"
+  restriction="[0-9.,DHMPRSTWYZ/:+\-]+"/>
+</content>
+    ⚓
Declaration
+teidata.duration.iso = token { pattern = "[0-9.,DHMPRSTWYZ/:+\-]+" }⚓
Example
<time dur-iso="PT0,75H">three-quarters of an hour</time>
Example
<date dur-iso="P1,5D">a day and a half</date>
Example
<date dur-iso="P14D">a fortnight</date>
Example
<time dur-iso="PT0.02S">20 ms</time>
Note

A duration is expressed as a sequence of number-letter pairs, preceded by the letter P; the letter gives the unit and may be Y (year), M (month), D (day), H (hour), M (minute), or S (second), in that order. The numbers are all unsigned integers, except for the last, which may have a decimal component (using either . or , as the decimal point; the latter is preferred). If any number is 0, then that number-letter pair may be omitted. If any of the H (hour), M (minute), or S (second) number-letter pairs are present, then the separator T must precede the first ‘time’ number-letter pair.

For complete details, see ISO 8601 Data elements and interchange formats — Information interchange — Representation of dates and times.

5.4. teidata.duration.w3c

teidata.duration.w3c defines the range of attribute values available for representation of a duration in time using W3C datatypes.
Moduletei
Used by
Content model
+<content>
+ <dataRef name="duration"/>
+</content>
+    ⚓
Declaration
+teidata.duration.w3c = xsd:duration⚓
Example
<time dur="PT45M">forty-five minutes</time>
Example
<date dur="P1DT12H">a day and a half</date>
Example
<date dur="P7D">a week</date>
Example
<time dur="PT0.02S">20 ms</time>
Note

A duration is expressed as a sequence of number-letter pairs, preceded by the letter P; the letter gives the unit and may be Y (year), M (month), D (day), H (hour), M (minute), or S (second), in that order. The numbers are all unsigned integers, except for the S number, which may have a decimal component (using . as the decimal point). If any number is 0, then that number-letter pair may be omitted. If any of the H (hour), M (minute), or S (second) number-letter pairs are present, then the separator T must precede the first ‘time’ number-letter pair.

For complete details, see the W3C specification.

5.5. teidata.enumerated

teidata.enumerated defines the range of attribute values expressed as a single XML name taken from a list of documented possibilities.
Moduletei
Used by
teidata.gender teidata.sexElement:
Content model
+<content>
+ <dataRef key="teidata.word"/>
+</content>
+    ⚓
Declaration
+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.

5.6. teidata.gender

teidata.gender defines the range of attribute values used to represent the gender of a person, persona, or character.
Moduletei
Used by
Element:
Content model
+<content>
+ <dataRef key="teidata.enumerated"/>
+</content>
+    ⚓
Declaration
+teidata.gender = teidata.enumerated⚓
Note

Values for attributes using this datatype may be defined locally by a project, or they may refer to an external standard.

Values for this datatype should not be used to encode morphological gender (cf. <gen>, msd as defined in att.linguistic, and 9.3.1. Information on Written and Spoken Forms).

5.7. teidata.language

teidata.language defines the range of attribute values used to identify a particular combination of human language and writing system. [6.1. Language Identification]
Moduletei
Used by
Content model
+<content>
+ <alternate>
+  <dataRef name="language"/>
+  <valList>
+   <valItem ident=""/>
+  </valList>
+ </alternate>
+</content>
+    ⚓
Declaration
+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.

language
The IANA-registered code for the language. This is almost always the same as the ISO 639 2-letter language code if there is one. The list of available registered language subtags can be found at http://www.iana.org/assignments/language-subtag-registry. It is recommended that this code be written in lower case.
script
The ISO 15924 code for the script. These codes consist of 4 letters, and it is recommended they be written with an initial capital, the other three letters in lower case. The canonical list of codes is maintained by the Unicode Consortium, and is available at http://unicode.org/iso15924/iso15924-codes.html. The IETF recommends this code be omitted unless it is necessary to make a distinction you need.
region
Either an ISO 3166 country code or a UN M.49 region code that is registered with IANA (not all such codes are registered, e.g. UN codes for economic groupings or codes for countries for which there is already an ISO 3166 2-letter code are not registered). The former consist of 2 letters, and it is recommended they be written in upper case; the list of codes can be searched or browsed at https://www.iso.org/obp/ui/#search/code/. The latter consist of 3 digits; the list of codes can be found at http://unstats.un.org/unsd/methods/m49/m49.htm.
variant
An IANA-registered variation. These codes are used to indicate additional, well-recognized variations that define a language or its dialects that are not covered by other available subtags.
extension
An extension has the format of a single letter followed by a hyphen followed by additional subtags. These exist to allow for future extension to BCP 47, but as of this writing no such extensions are in use.
private use
An extension that uses the initial subtag of the single letter x (i.e., starts with x-) has no meaning except as negotiated among the parties involved. These should be used with great care, since they interfere with the interoperability that use of RFC 4646 is intended to promote. In order for a document that makes use of these subtags to be TEI-conformant, a corresponding <language> element must be present in the TEI header.

There are two exceptions to the above format. First, there are language tags in the IANA registry that do not match the above syntax, but are present because they have been ‘grandfathered’ from previous specifications.

Second, an entire language tag can consist of only a private use subtag. These tags start with x-, and do not need to follow any further rules established by the IETF and endorsed by these Guidelines. Like all language tags that make use of private use subtags, the language in question must be documented in a corresponding <language> element in the TEI header.

Examples include

sn
Shona
zh-TW
Taiwanese
zh-Hant-HK
Chinese written in traditional script as used in Hong Kong
en-SL
English as spoken in Sierra Leone
pl
Polish
es-MX
Spanish as spoken in Mexico
es-419
Spanish as spoken in Latin America

The W3C Internationalization Activity has published a useful introduction to BCP 47, Language tags in HTML and XML.

5.8. teidata.name

teidata.name defines the range of attribute values expressed as an XML Name.
Moduletei
Used by
Content model
+<content>
+ <dataRef name="Name"/>
+</content>
+    ⚓
Declaration
+teidata.name = xsd:Name⚓
Note

Attributes using this datatype must contain a single word which follows the rules defining a legal XML name (see https://www.w3.org/TR/REC-xml/#dt-name): for example they cannot include whitespace or begin with digits.

5.9. teidata.numeric

teidata.numeric defines the range of attribute values used for numeric values.
Moduletei
Used by
Element:
Content model
+<content>
+ <alternate>
+  <dataRef name="double"/>
+  <dataRef name="token"
+   restriction="(\-?[\d]+/\-?[\d]+)"/>
+  <dataRef name="decimal"/>
+ </alternate>
+</content>
+    ⚓
Declaration
+teidata.numeric =
+   xsd:double | token { pattern = "(\-?[\d]+/\-?[\d]+)" } | xsd:decimal⚓
Note

Any numeric value, represented as a decimal number, in floating point format, or as a ratio.

To represent a floating point number, expressed in scientific notation, ‘E notation’, a variant of ‘exponential notation’, may be used. In this format, the value is expressed as two numbers separated by the letter E. The first number, the significand (sometimes called the mantissa) is given in decimal format, while the second is an integer. The value is obtained by multiplying the mantissa by 10 the number of times indicated by the integer. Thus the value represented in decimal notation as 1000.0 might be represented in scientific notation as 10E3.

A value expressed as a ratio is represented by two integer values separated by a solidus (/) character. Thus, the value represented in decimal notation as 0.5 might be represented as a ratio by the string 1/2.

5.10. teidata.outputMeasurement

teidata.outputMeasurement defines a range of values for use in specifying the size of an object that is intended for display.
Moduletei
Used by
Content model
+<content>
+ <dataRef name="token"
+  restriction="[\-+]?\d+(\.\d+)?(%|cm|mm|in|pt|pc|px|em|ex|ch|rem|vw|vh|vmin|vmax)"/>
+</content>
+    ⚓
Declaration
+teidata.outputMeasurement =
+   token
+   {
+      pattern = "[\-+]?\d+(\.\d+)?(%|cm|mm|in|pt|pc|px|em|ex|ch|rem|vw|vh|vmin|vmax)"
+   }⚓
Example
<figure> + <head>The TEI Logo</head> + <figDesc>Stylized yellow angle brackets with the letters <mentioned>TEI</mentioned> in +   between and <mentioned>text encoding initiative</mentioned> underneath, all on a white +   background.</figDesc> + <graphic height="600px" width="600px" +  url="http://www.tei-c.org/logos/TEI-600.jpg"/> +</figure>
Note

These values map directly onto the values used by XSL-FO and CSS. For definitions of the units see those specifications; at the time of this writing the most complete list is in the CSS3 working draft.

5.11. teidata.pattern

teidata.pattern defines attribute values which are expressed as a regular expression.
Moduletei
Used by
Content model
+<content>
+ <dataRef name="token"/>
+</content>
+    ⚓
Declaration
+teidata.pattern = token⚓
Note
A regular expression, often called a pattern, is an expression that describes a set of strings. They are usually used to give a concise description of a set, without having to list all elements. For example, the set containing the three strings Handel, Händel, and Haendel can be described by the pattern H(ä|ae?)ndel (or alternatively, it is said that the pattern H(ä|ae?)ndel matches each of the three strings)
Wikipedia

This TEI datatype is mapped to the XSD token datatype, and may therefore contain any string of characters. However, it is recommended that the value used conform to the particular flavour of regular expression syntax supported by XSD Schema.

5.12. teidata.pointer

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.
Moduletei
Used by
Element:
Content model
+<content>
+ <dataRef restriction="\S+" name="anyURI"/>
+</content>
+    ⚓
Declaration
+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, https://secure.wikimedia.org/wikipedia/en/wiki/% is encoded as https://secure.wikimedia.org/wikipedia/en/wiki/%25 while http://موقع.وزارة-الاتصالات.مصر/ is encoded as http://xn--4gbrim.xn----rmckbbajlc6dj7bxne2c.xn--wgbh1c/

5.13. teidata.probCert

teidata.probCert defines a range of attribute values which can be expressed either as a numeric probability or as a coded certainty value.
Moduletei
Used by
Content model
+<content>
+ <alternate>
+  <dataRef key="teidata.probability"/>
+  <dataRef key="teidata.certainty"/>
+ </alternate>
+</content>
+    ⚓
Declaration
+teidata.probCert = teidata.probability | teidata.certainty⚓

5.14. teidata.probability

teidata.probability defines the range of attribute values expressing a probability.
Moduletei
Used by
teidata.probCert
Content model
+<content>
+ <dataRef name="double"/>
+</content>
+    ⚓
Declaration
+teidata.probability = xsd:double⚓
Note

Probability is expressed as a real number between 0 and 1; 0 representing certainly false and 1 representing certainly true.

5.15. teidata.replacement

teidata.replacement defines attribute values which contain a replacement template.
Moduletei
Used by
Content model
+<content>
+ <textNode/>
+</content>
+    ⚓
Declaration
+teidata.replacement = text⚓

5.16. teidata.sex

teidata.sex defines the range of attribute values used to identify the sex of an organism.
Moduletei
Used by
Element:
Content model
+<content>
+ <dataRef key="teidata.enumerated"/>
+</content>
+    ⚓
Declaration
+teidata.sex = teidata.enumerated⚓
Note

Values for attributes using this datatype may be defined locally by a project, or they may refer to an external standard.

5.17. teidata.temporal.iso

teidata.temporal.iso 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 international standard Data elements and interchange formats – Information interchange – Representation of dates and times.
Moduletei
Used by
Content model
+<content>
+ <alternate>
+  <dataRef name="date"/>
+  <dataRef name="gYear"/>
+  <dataRef name="gMonth"/>
+  <dataRef name="gDay"/>
+  <dataRef name="gYearMonth"/>
+  <dataRef name="gMonthDay"/>
+  <dataRef name="time"/>
+  <dataRef name="dateTime"/>
+  <dataRef name="token"
+   restriction="[0-9.,DHMPRSTWYZ/:+\-]+"/>
+ </alternate>
+</content>
+    ⚓
Declaration
+teidata.temporal.iso =
+   xsd:date
+ | xsd:gYear
+ | xsd:gMonth
+ | xsd:gDay
+ | xsd:gYearMonth
+ | xsd:gMonthDay
+ | xsd:time
+ | xsd:dateTime
+ | token { pattern = "[0-9.,DHMPRSTWYZ/:+\-]+" }⚓
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.

For all representations for which ISO 8601:2004 describes both a basic and an extended format, these Guidelines recommend use of the extended format.

5.18. teidata.temporal.w3c

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.
Moduletei
Used by
Content model
+<content>
+ <alternate>
+  <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
+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.

5.19. teidata.text

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.
Moduletei
Used by
Content model
+<content>
+ <dataRef name="string"/>
+</content>
+    ⚓
Declaration
+teidata.text = string⚓
Note

Attributes using this datatype must contain a single ‘token’ in which whitespace and other punctuation characters are permitted.

5.20. teidata.truthValue

teidata.truthValue defines the range of attribute values used to express a truth value.
Moduletei
Used by
Content model
+<content>
+ <dataRef name="boolean"/>
+</content>
+    ⚓
Declaration
+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.

5.21. teidata.version

teidata.version defines the range of attribute values which may be used to specify a TEI or Unicode version number.
Moduletei
Used by
Element:
Content model
+<content>
+ <dataRef name="token"
+  restriction="[\d]+(\.[\d]+){0,2}"/>
+</content>
+    ⚓
Declaration
+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 (http://unicode.org/versions/). A version number contains digits and fullstop characters only. The first number supplied identifies the major version number. A second and third number, for minor and sub-minor version numbers, may also be supplied.

5.22. teidata.versionNumber

teidata.versionNumber defines the range of attribute values used for version numbers.
Moduletei
Used by
Content model
+<content>
+ <dataRef name="token"
+  restriction="[\d]+[a-z]*[\d]*(\.[\d]+[a-z]*[\d]*){0,3}"/>
+</content>
+    ⚓
Declaration
+teidata.versionNumber =
+   token { pattern = "[\d]+[a-z]*[\d]*(\.[\d]+[a-z]*[\d]*){0,3}" }⚓

5.23. teidata.word

teidata.word defines the range of attribute values expressed as a single word or token.
Moduletei
Used by
teidata.enumerated
Content model
+<content>
+ <dataRef name="token"
+  restriction="[^\p{C}\p{Z}]+"/>
+</content>
+    ⚓
Declaration
+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.

5.24. teidata.xTruthValue

teidata.xTruthValue (extended truth value) defines the range of attribute values used to express a truth value which may be unknown.
Moduletei
Used by
Content model
+<content>
+ <alternate>
+  <dataRef name="boolean"/>
+  <valList>
+   <valItem ident="unknown"/>
+   <valItem ident="inapplicable"/>
+  </valList>
+ </alternate>
+</content>
+    ⚓
Declaration
+teidata.xTruthValue = xsd:boolean | ( "unknown" | "inapplicable" )⚓
Note

In cases where where uncertainty is inappropriate, use the datatype teidata.TruthValue.

5.25. teidata.xpath

teidata.xpath defines attribute values which contain an XPath expression.
Moduletei
Used by
Content model
+<content>
+ <textNode/>
+</content>
+    ⚓
Declaration
+teidata.xpath = text⚓
Note

Any XPath expression using the syntax defined in 6.2..

When writing programs that evaluate XPath expressions, programmers should be mindful of the possibility of malicious code injection attacks. For further information about XPath injection attacks, see the article at OWASP.

Home 
Date:
\ No newline at end of file diff --git a/documentation/Schema/SPEAR.odd b/documentation/Schema/SPEAR.odd new file mode 100644 index 000000000..12dc82833 --- /dev/null +++ b/documentation/Schema/SPEAR.odd @@ -0,0 +1,2372 @@ + + + + + + + TEI Customization for SPEAR: Syriaca Persons, Events, and Relations + Daniel L. + Schwartz + + + + + + Syriaca.org: The Syriac Reference Portal + + +

Distributed under a Creative Commons Attribution 3.0 Unported License.

+

The code examples contained in exemplum elements below come from + Syriaca.org projects that have been distributed under a Creative Commons Attribution + 3.0 Unported License. Used by permission.

+

The comments on element and attribute use contained in remarks elements below + share some text with other Syriaca.org documentation distributed under a Creative Commons + Attributiion 3.0 Unported License. This documentation can be found at various links available here: + http://syriaca.org/documentation/index.html + Used by permission. +

+ + + + +

This ODD provides a customization of the TEI P5 All.

+ + + + First + draft + + + + + +

This schema has been created to to constrain the TEI P5 for validating the born-digital + project SPEAR: Syriac Persons, Events, and Relations. This customization will be used for + the encoding of many different documents by many different researchers having differnet + levels of training. As such, a schema is particularly important. The highly-structured data + model of SPEAR also requires some modifications and additions to TEI P5.

+ + + + + + + + + + + + I have needed to include this because it somehow disappeared from this + customization. I do not know why this was necessary. + + + + + + + + + + + Each @ana attribute value must start with "http://syriaca.org/keyword/" and multiple + values must be space separated. + + + The same keyword URI may not appear twice as the value of the @ana attribute. + + Multiple @ana attributes should be separated with one blank space + + + Multiple @ana attributes should be separated with one blank space + + + + + + + + + + + + + + + + + + + +

Every teiHeader contains a fileDesc (information + about the creation of a file), an encodingDesc (editorial rules), a + profileDesc> (non-bibliographic aspects of a text), and a + revisionDesc (history of revisions).

+ + + + + + + + + + + + + + +

Each fileDesc contains (in order) a titleStmt, an + editionStmt, a publicationStmt, an optional seriesStmt, and a sourceDesc.

+ + + + + + + + + + + + + + + + + + The first <title> element child of <titleStmt> must have + @level attribute with a value of "m" indicating "monographic" or "a" indicating + analytic. + + + The first <title> element child of <titleStmt> must have + @type attribute with a value of "main". + + + + + The second <title> element child of <titleStmt> must have + @type attribute with a value of "sub". + + + The text node of this subtitle must be "A SPEAR Prosopography". + + + + + + + + + + + + + +

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.

+ + + + + + + + + + + + + + A @ref attribute is required. + + + + + + + + Acceptable values for this @ref attribute include: + . + + + + + + +

This customization limits the vaules of @ref attributes on name as child of titleStmt + to a Syriaca.org URI for project contributors.

+ + + + + + + + + + +

Within the titleStmt, funding bodies are identified with the + funder element. If multiple funding bodies are relevant, then each one receives + a separate funder element.

+ + + + + + + + + +

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").

+ + + + + + + + + + + + + + +

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 <authority> element should contain the text: "Syriaca.org: The Syriac Reference Portal." + + + + + + +

Syriaca.org is identified as the responsible entity using authority.

+ + + + + + + + + + + + The <licence> element must contain <p> with the text: "Distributed under a Creative Commons Attribution 3.0 Unported License." + + + + + + +

The license element, child of availability, is used to specify the Creative Commons CC-BY license under which + this record is made available. Some records may incorporate information from works under copyright (with permission), a fact which is also + indicated with license.

+ + + + + + + + + + + + + + + + + + + + + The <title> requires a @level attribute with a value of "s". + + + This <title> must be "SPEAR: Syriac Persons, Events, and Relations". + + + + + The <title> requires a @level attribute with a value of "m". + + + This <title> must be one of the following: "The Chronicle of Edessa", "The Lives of the Eastern Saints", + or "The Letters of Severus of Antioch". + + + + + This <title> requires a @type attribute with a value of "sub". + + + This <title> must be "A SPEAR Prosopography". + + + + + + + + + This <editor> must have a @role attribute with a value of "general". + + + + + This <editor> cannot have a @role attribute with a value of "creator". + + + + + This <editor> must have a @ref attribute with a value of "http://syriaca.org/documentation/editors.xml#dschwartz". + + + This <editor> must be "Daniel L. Schwartz". + + + + + + + + + This <idno> must be "https://spear-prosop.org". + + + + + This <idno> must be "https://spear-prosop.org/lives-eastern-saints". + + + + + This <idno> must be "https://spear-prosop.org/letters-severus". + + + + + + + + + This <seriesStmt> cannot contain a <biblScope>. + + + + + This <seriesStmt> requires a <biblScope>. + + + + + This <biblScope> element requires a a @unit + attribute having a value of "volume". + + + This <biblScope> element requires a child <title> element. + + + + + This <title> element requires a @level attribute with a value of "s". + + + This <title> element must contain "SPEAR: Syriac Persons, Events, and Relations". + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

The body of a SPEAR file contains factoids, each of which appears in a separate ab element. + As such, ab is the only acceptable child element of body.

+ + + + + + + + +

SPEAR has three basic types of factoid data that are encoded using listPerson, listEvent, + and listRelation elements. The TEI Guidelines allow the first two to nest inside ab + while the last one is not. For uniformity and ease of encoding, + SPEAR makes the listRelation element a part of the model class + model.listLike so that it can function like other list elements and nest directly + under the ab element. SPEAR also removes all attributes from the + listRelation element and restricts the child elements to relation.

+ + + + + + + + + + + + + + + + + + + + + A <bibl> element in the back matter must contain an + @xml:id attribute. + + + + The @xml:id on + <bibl> in the back matter must take the following form: 'bibl' + + '' + '-' + a unique number. + Each @xml:id attribute on <bibl> must have a unique value. + A properly formatted + @xml:id ends with a number. + A properly formatted + @xml:id ends with a number. + + + + + + + + + + + + + + + + +

SPEAR only uses @xml:id and @type attributes on the bibl element. SPEAR uses + bibl elements with an @xml:id only in the back of the TEI file. The + @type attribute indicates whether the bibl is "primary", "secondary", or a "urn". +

+

Since SPEAR relies on the Linked Open Data infrastructure of Syriaca.org, a bibl + element in the body only requires a ptr element indicating the Syriaca.org URI or CTS URN for + the bibliographic reference. When indicating a CTS URNs no other additional information + is required. When indicating a Syriaca.org URI, a citedRange is needed.

+ + + + + + + + + + + + + + + + the element contains a page number or page range. + + + the element contains a line number or line range. + + + the element contains a part of a book or collection, i.e. chapter and verse + of a biblical text. + + + the element identifies a column. + + + + + + + + + + + + + + + + + + + + the element contains a page number or page range. + + + the element contains a line number or line range. + + + the element contains a part of a book or collection, i.e. chapter and verse + of a biblical text. + + + the element identifies a column. + + + + + + +

SPEAR only allows text in a citedRange element and requires the use of a @unit attribute with a closed list. + SPEAR prefers that encoders use the part value and cite ancient texts according to + section numbers.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + the element contains a date (year) according to the Seleucid + calendar. + + + the element contains a date (month and year) according to the Seleucid + calendar. + + + the element contains a date according to the year of a king's reign. + + + + + + + + + + + A <date> element child of <reg> + must have a @calendar attribute with a value of "Gregorian". + + + + + + The element contains a date according to the Gregorian calendar. + + + The element contains a date according to the Seleucid calendar. + + + + + + + + + +

+ + + + + + + + + + + + + + + + + + + + + + + Element of type + <desc> cannot be empty. + + + The <desc> element should + generally contain either <persName> or <placeName>. SPEAR + encourages a liberal use of <persName>, <placeName>, and <date> + elements in the <desc> element of event factoids. + + + + + + + + + This <relation> requires a <desc>. + + + + + The <desc> element may not appear here. + + + + + + This <desc> must contain <rs> elements, one for each values in the @mutual attribute on <relation>. + + + This <desc> requires <rs> elements with unique @ref attribute values. + + + + + + This <desc> must begin with "The following factoids deal with the same event: " + + + + + + This <desc> must begin with "The following factoids deal with related events: " + + + + + +

This customization does not allow attributes on the desc element. It also + restricts child elements to choice, date, persName, and + placeName.

+ + + + + + + + + The @ref attribute must take a Syriaca.org work URI + which reqires the form 'http://syriaca.org/work/{\d+}' + (where {\d+} is a number). + + + + + + + + + + + + + + + + + + Acceptable values: + + + + + + The text node of this <rs> element must be . + + + + + + + + + + + + + + + This <editor> must have a @role attribute. + + + This <editor> must have a @ref attribute. + + + + + + + + Acceptable values for this @ref attribute include: + . + + + + + + + + + + + + A person involved in the creation of this xml file + + + A person responsible for this xml file or collection of xml files + + + + + + + + + + + +

This customization limits the attributes available on desc to + @role and @ref and suggests values for @role.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + An <ab> descendant of <body> requires an @xml:id attribute. + An <ab> descendant of <body> requires a @resp attribute. + An <ab> descendant of <body> requires a @type attribute with the value "factoid". + + + + + + Acceptable values for this @resp attribute include: + . + + + + + + + + + + + + An @xml:id attribute + starts with 'factoid-'. + A properly formatted + SPEAR factoid URI ends with a hyphen followed by a number. + A properly formatted + SPEAR factoid URI ends with a number. + + + + + + + + + + + + + + + + + + + birth + Used to designate person factoids that encode birth dates and/or locations + + + citizenship + Used to designate person factoids that encode citizenship + + + death + Used to designate person factoids that encode death dates and/or locations + + + education + Used to designate person factoids that encode education + + + ethnic label + Used to designate person factoids that encode ethnic labels + + + event + Used to designate event factoids + + + gender + Used to designate person factoids that encode gender + + + language known + Used to designate person factoids that encode language knowledge + + + mental state + Used to designate person factoids that encode mental states + + + name variant + Used to designate person factoids that encode name variants + + + occupation + Used to designate person factoids that encode occupations + + + physical trait + Used to designate person factoids that encode physical traits + + + relation + Used to designate relation factoids + + + + residence + Used to designate person factoids that encode places and dates of residence + + + sanctity + Used to designate person factoids that encode sanctity + + + socio-economic status + Used to designate person factoids that encode socio-econimic status + + + + + + +

+ This customization requires the basic pattern of SPEAR factoids to be encoded correctly. Each + factoid is encoded in an ab element. Since each factoid contains data on a + Person, Event, or Relation, the schema requires that ab must contain a + listPerson, listEvent, or listRelation child element. Since every + factoid requires a bibliographic reference, every ab must contain one or more child + bibl elements. The encoder also has the option of adding a note + element to the factoid as well.

+

This customization also requires that every ab element receives @xml:id, @type, @subtype, + and @resp attributes. The @xml:id must take the form "factoid-{\d}" where {\d} is a number unique within + the document. The @type attribute must be "factoid". The @subtype attribute comes from a closed list + of data types encoded in the SPEAR project. The @resp attribute must point to an editor listed in the + titleStmt. This ensures that all contributions are attributed at the factoid level.

+ + + + + + + + + + + An <idno> descendant of <ab> + requires a @type attribute with the value "URI". + + + This <idno> + requires a @type attribute with the value "URI". + + + This <idno> element + requires a @type attribute with the value "URI". + + + + + + + + + The text node of this <idno> must be "https://spear-prosop.org//tei". + + + + + + + + + This factoid URI must be: ". + + + + + + + + + + + +

+ This customization requires properly formatted identifiers for each TEI document + and for each factoid. It ensures the alignment of the document cool-URI, the document name (always a number), + and the factoid cool-URI.

+

In the teiHeader, an idno requires a @type attribute indicating that it is a "URI". + It must also have the text node "https://spear-prosop.org/{\d}/tei", where {\d} is a number that matches + the number of the document name.

+

Each factoid also requires an idno with a @type attribute of "URI". + It must contain the full cool-URI for that factoid. This URI is constructed using the idno from the + publicationStmt and attaching to it the "-{\d}" from the @xml:id on the parent ab. +

+ + + + + + + + + + + + + + + + + + : URI(s) not in the Taxonomy. Please ensure that an appropriate URI does + not appear in the Taxonomy before proceeding. If you find no appropriate concept in the Taxonomy, please choose a keyword of your own for the editors to consider. + + + + + + + + + This <event> must have a @when attribute with the value . + + + + + This <event> must have a @notBefore attribute with the value . + + + + + This <event> must have a @notAfter attribute with the value . + + + + + This <event> must have a @from attribute with the value . + + + + + This <event> must have a @to attribute with the value . + + + + + + + + A <relation> element inside of an <event> element cannot take a <desc> element. + + + + +

+ This customization makes desc the only acceptable child of event. It also requires an @ana attribute + and constrains the values of that attribute to the full list of Syriaca.org keyword URIs. In the case of dates associated with an event, + the customization also requires that date attributes (@when, @notBefore, @notAfter, @from, and @to) match on the event element and within the child + desc element.

+ + + + + + + + The <note> element in a birth place factoid + must contain a <persName>. + The <note> element in a birth place factoid + must contain a <placeName>. + + + The <note> element in a birth date factoid + must contain a <persName>. + + + The <note> element in a citizenship factoid + must contain a <persName>. + The <note> element in a citizenship factoid + must contain a <placeName>. + + + The <note> element in a death place factoid + must contain a <persName>. + The <note> element in a birth place factoid + must contain a <placeName>. + + + The <note> element in an education factoid + must contain a <persName>. + + + The <note> element in a death date factoid + must contain a <persName>. + + + The <note> element in an occupation factoid + must contain a <persName>. + + + The <note> element in a residence factoid must + contain a <persName>. + The <note> element in a residence factoid + must contain a <placeName>. + + + The <note> element in a socioeconomic status + factoid must contain a <persName>. + + + The <note> element in a language-known factoid + must contain a <persName>. + + + The <note> element inside the <trait> + element must contain a <persName>. + + + The <note> element inside the <state> + element must contain a <persName>. + + + This <note> element requires an @ana + attribute. + + + + + + + + The URI in this @ref attribute and the URI in the @ref attribute on the <persName> that + is the child of <person> must match. + + + + + The URI in this @ref attribute and the URI in the @ref attribute on the <placeName> that + is the child of <person> must match. + + + + + + + + The only note allowed in this context must contain the following text: "This + regularized date was calculated by the SPEAR editor from a non-calendrical dating + system such as regnal years, etc." + + + + + + + + + + + + + + This <note> must contain the + attribute @type="desc" and other <note> types are not allowed in this context. + Other types of notes (those dealing with "certainty") may appear as children of + the <ab> element as needed. + + + + + + + + If you wish to apply a date to this factoid, you must use + date attributes (@when, @notBefore, @notAfter, @to, and/or @from) on the + parent of the <note> element. + + + + + + + + + + + + + + + + + + + A <note> element with @type="certainty" requires a @subtype. + + + + + + + + + + + + + + + + + + + + +

+ SPEAR factoids contain note elements that allow the encoder to offer a more prose-oriented description of the data that they have + derived from the source they are analyzing. The content of the note is what human users encounter when using the HTML serialization of + the data. This customization constrains the use of this element to ensure that the data + marked up inside the note agrees with the more data-oriented encoding found elsewhere in the factoid.

+ + + + + + + + + + + + + + + + + + + + + + This @ref may contain only one URI. + + The @ref attribute must take a Syriaca.org person URI which reqires + the form 'http://syriaca.org/person/{\d+}' (where {\d+} is a number). + + + is not currently in use. + Note that all person URIs take the form 'http://syriaca.org/person/{\d+}' + (where {\d+} is a number). If a URI is not current available, replace the number portion of the URI with + "#" followed without a space by a number that you use consistently when encoding information + about that person. + + + + + + + +

+ This customization requires persName to have a @ref attribute that points to a Syriaca.org authority file for a person.

+ + + + + + + + + + + + + + + + + + + This @ref may contain only one URI. + + The @ref attribute must take a Syriaca.org place URI which reqires + the form 'http://syriaca.org/place/{\d+}' (where {\d+} is a number). + + + is not currently in use. + Note that all properly formatted place URIs take the form 'http://syriaca.org/place/{\d+}' + (where {\d+} is a number). If a URI is not current available, replace the number portion of the URI with + "#" followed without a space by a number that you use consistently when encoding information + referring to that place. + + + + + + + +

+ This customization requires placeName to have a @ref attribute that points to a Syriaca.org authority file for a place.

+ + + + + + + + + + + + + + + + + + + The @target attribute on a <ptr> element inside a <bibl> element + with @type="primary" takes limited values. It either must be + "http://syriaca.org/work/" or + "http://syriaca.org/bibl/" followed by the corresponding Syriaca.org bibl URI + number. + + + + The @target attribute on a <ptr> element inside a <bibl> element + with @type="urn" must begin either with "urn:cts:syriacLit:nhsl.syriacCorpus" followed by the corresponding Syriac + Corpus URI number. + + + + URN in a <bibl> + element inside a SPEAR factoid must begin with URN in the <sourceDesc> + element of the <teiHeader>: ":". + + + The + @target attribute on the <ptr> element, "," is + not among the valid options contained in the <sourceDesc> element of the + <teiHeader>: () + + + + + + +

+ This customization requires a ptr to have a @type attribute (indicating "primary", "secondary", or "URN") + and a @target attribute. It also ensures that the @target attribute with primary and secondary sources indicates a + Syriaca.org authority file for a work or a bibliographic item. +

+ + + + + + + + + + + + + + + + + This <relation> takes either a @mutual attribute with mutual + relationships or both @active and @passive attributes with directed + relationships. Mutual relationships include: . Directed relationships include: + . + This <relation> takes either a @mutual attribute with mutual + relationships or both @active and @passive attributes with directed + relationships. Mutual relationships include: . Directed relationships include: + . + + + A @mutual attribute is required on <relation> + in event factoids. + @active attributes are not allowed on <relation> + in event factoids. + @passive attributes are not allowed on <relation> + in event factoids. + + + + + + + is not currently in use. + Note that all person URIs take the form 'http://syriaca.org/person/{\d+}' + (where {\d+} is a number). If a URI is not current available, replace the number portion of the URI with + "#" followed without a space by a number that you use consistently when encoding information + about that person. + + + + + + + + + This <relation> must have a @when attribute with the value . + + + + + This <relation> must have a @notBefore attribute with the value . + + + + + This <relation> must have a @notAfter attribute with the value . + + + + + This <relation> must have a @from attribute with the value . + + + + + This <relation> must have a @to attribute with the value . + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Value must be one of the following from the Syriaca.org taxonomy: + . + + + + Value must be one of the following from the Syriaca.org taxonomy: + . + + + + + + + + + + This <relation> element must have a @name attribute with a value of "dcterms:isPartOf". + + + + A @name attribute cannot appear here. + + + + + + + + + + + + A <relation> element inside an event factoid + must take a @type attribute with the value "event". + + + A @type attribute with the value + "part" is required. + + + + + + Used to denote relationships involving persons + + + Used to denote relationships between event factoids + + + + + + + + + + + + + + + + + : URI(s) not in the Taxonomy. If you find no appropriate concept on the following list, + please choose a keyword of your own for the editors to consider: . + + + A <relation> element inside an event factoid cannot + have an @ana attribute. + + + + + + +

+ The relation element is used for personal relationships and constitutes one of the three main data types in SPEAR. + When SPEAR encodes straight relationships, they appear in a relationship factoid (tei:ab[@subtype="relation"]/tei:listRelation/tei:relation). + Relationships can also appear inside an event factoid in cases where an event creates a relationship, i.e. a wedding is an event that + created a spousal relationship. In such cases, SPEAR encodes this relationship inside the event factoid. In addition to these personal relationships, + the relation element is also used to encode relationships between closely related events. The relation element is also used in + the teiHeader. +

+

+ In the context of personal relationships, this customization constrains the @ref, @ana, @active, @passive, and @mutual attributes. + A @ref attribute is required and must contain a URI pointing to a personal relationship in the Syriac Taxonomy. An @ana attribute is optional but when + used must contain a URI pointing to a qualifier relationship in the Syriac Taxonomy, i.e. a sibling relationship might be qualified as a + step-sibling relationship using @ana. For mutual relationship where each participant has the same relationship to the other (i.e. spousal), a + @mutual attribute is used with all of the participants in that relationship listed. In the case of a directed relationship (i.e. where person X + is the parent of person Y) both the @active and @passive attributes are used. The values allowed on the @active, @passive, and @mutual + attributes are URIs pointing to Syriaca.org authority files for persons. +

+

+ In the context of relationships between events, this customization only allows appropriate values on @ref while excluding @ana, @active, and @passive + attributes. +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

+ The person element contains person factoid data. This customization requires the proper structure for that data. + The first child of person must be a self-closing persName element with a @ref attribute containing a + URIs pointing to Syriaca.org authority file for a person. The next child element must be one of the following: + birth, death, education, langKnown, nationality, occupation, + residence, socecStatus, state, or trait. +

+ + + + + + + + + + + + + + + + + + + + + + + + +

This customization restricts the attribute classes of the birth element to + att.datable.w3c but excludes the @to and @from attributes. If more precise dating is + required for a SPEAR factoid, encoder should use the date element.

+

+ It also restricts the child elements to those dealing with dates (date or choice), + placeName, and note. +

+ + + + + + + + + + + + + + + + + + + + + + + +

This customization restricts the attribute classes of the death element to + att.datable.w3c but excludes the @to and @from attributes. If more precise dating is + required for a SPEAR factoid, encoder should use the date element.

+

+ It also restricts the child elements to those dealing with dates (date or choice), + placeName, and note. +

+ + + + + + + + + + + + + + + + + + + + + + + + + : URI(s) not in the Taxonomy. If you find no appropriate concept on the following list, + please choose a keyword of your own for the editors to consider: . + + + + + + + +

This customization restricts the attribute classes of education + to att.datable.w3c and the @ana attribute. If more precise dating is required for a + SPEAR factoid, the encoder should use the date element.

+

+ It also restricts the required @ana attribute to keyword URIs in the Syriac Taxonomy that pertain to + fields of education. +

+ + + + + + + + + + + + + + + + + +

The TEI name for the nationality element is problematic from a + pre-Modern perspective. "Citizenship" would be preferable in one sense, yet could in + many instances exclude subaltern people such as the enslaved. SPEAR uses the + nationality element as a general category for people living under a particular + jurisdiction.

+

This customization limits the attribute classes of the + nationality element to att.datable.custom and att.datable.w3c and removes the + nationality element from all model classes. It also requires exactly one + placeName child and one note child and allows an optional date child.

+ + + + + + + + + + + + + + + + +

This customization limits the attribute classes of the + residence element to att.datable.custom and att.datable.w3c and removes the + residence element from all model classes. It also requires exactly one + placeName child and one note child and allows an optional date child.

+ + + + + + + + + + + + + + + + + + + + + + + + + + : URI(s) not in the Taxonomy. If you find no appropriate concept on the following list, + please choose a keyword of your own for the editors to consider: . + + + + + + +

This customization restricts the attribute classes of occupation + to att.datable.w3c and att.global.analytic. If more precise dating is required for a + SPEAR factoid, the encoder should use the date element.

+

+ It only allows note as a child element and it restricts the required @ana attribute to keyword URIs in the Syriac Taxonomy that pertain to + occupations. +

+ + + + + + + + + + + +

+ This customization constrains the child elements under langKnowledge to include only + langKnown and note. +

+ + + + + + + + + + + + + + : URI(s) not in the Taxonomy. If you find no appropriate concept on the following list, + please choose a keyword of your own for the editors to consider: . + + + + + + + + + + + + + + + + + + +

+ This customization allows a closed list of values on the @level attribute ("low", "medium", and "high"). + It also restricts the required @ana attribute to keyword URIs in the Syriac Taxonomy that pertain to + languages. +

+ + + + + + + + + + + + + + + + + + + + + + + + + + : URI(s) not in the Taxonomy. If you find no appropriate concept on the following list, + please choose a keyword of your own for the editors to consider: . + + + + + + +

This customization restricts the attribute classes of socecStatus + to att.datable.w3c and att.global.analytic. If more precise dating is required for a + SPEAR factoid, the encoder should use the date element.

+

+ It only allows note as a child element and it restricts the required @ana attribute to keyword URIs in the Syriac Taxonomy that pertain to + socioeconomic status. +

+ + + + + + + + + + + + + + + + + + + + used for references to a person's physical characteristics, such as hair + color, height, weight, physical disabilities, etc. + + + + used for references to a person's gender identity (as opposed to their + biological sex which SPEAR does not presume to capture). + + + + used for references to an ethnic label claimed by a person or ascribed to a + person; such as "Goth," "Saracen," etc. + + + + + + + + + + + + + + + + : URI(s) not in the Taxonomy. If you find no appropriate concept on the following list, + please choose a keyword of your own for the editors to consider: . + + + + Preferred values for the @ana attribute on a <trait> element + @type="gender" are: + "http://syriaca.org/keyword/eunuch"; "http://syriaca.org/keyword/female"; + "http://syriaca.org/keyword/male"; and + "http://syriaca.org/keyword/nun-as-monk". Use these if applicable. If one of + these does not apply, please use a descriptive term of your + choosing. + + + + + + + + + : URI(s) not in the Taxonomy. . + + + + + + + +

This customization restricts the attribute classes of trait + to att.datable.w3c and att.global.analytic. If more precise dating is required for a + SPEAR factoid, the encoder should use the date element.

+

+ It only allows note as a child element. It restricts the required @type attribute to the values + "physical", "gender", and "ethnicLabel". It restricts the required @ana attribute to keyword URIs in the + Syriac Taxonomy that pertain to each of these three types. +

+ + + + + + + + + + + +

+ The back element must contain only one listBibl. +

+ + + + + + + + + +

+ The listBibl element must contain a head and at least + one bibl. +

+ + + + + + + + A <head> element inside the <sourceDesc> must contain the text node: + "Sources for the Data in this Born Digital Prosopography". + + + A <head> element inside + the <back> must contain the text node: "Works Cited". + + + + +

+ When the child of sourceDesc, head must contain "Sources for the Data in this Born Digital Prosopography". + When the child of back, head must contain "Works Cited". +

+ + + + + + + + + + + + + + + + + + + + + + + + + + : URI(s) not in the Taxonomy. If you find no appropriate concept on the following list, + please choose a keyword of your own for the editors to consider: . + + + + + + + + : URI(s) not in the Taxonomy. If you find no appropriate concept on the following list, + please choose a keyword of your own for the editors to consider: . + + + + + + + + + + + used for references to a person's mental traits; such as intelligence, + mental disability, wisdom, etc. + + + used for references to a person's religious affiliation; including but + not limited to membership in an organization, adhering to a set of beliefs, + or identifying with a religious community in some way. + + + used for references to a person's sanctity. + + + + + +

This customization restricts the attribute classes of state + to att.datable.w3c and att.global.analytic. If more precise dating is required for a + SPEAR factoid, the encoder should use the date element.

+

+ It only allows note as a child element. It restricts the required @type attribute to the values + "mental", "religiousAffiliation", and "sanctity". It restricts the required @ana attribute to keyword URIs in the + Syriac Taxonomy that pertain to each of these three types. +

+ + + + + + + + + diff --git a/documentation/Schema/out/SPEAR.rng b/documentation/Schema/out/SPEAR.rng new file mode 100644 index 000000000..051724488 --- /dev/null +++ b/documentation/Schema/out/SPEAR.rng @@ -0,0 +1,5378 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + indicates the person, or group of people, to whom the element content is ascribed. + + + + \S+ + + + + + + + + + + + + + + provides an externally-defined means of identifying the entity (or entities) being named, using a coded value of some kind. + + + + + + + + (reference) provides an explicit means of locating a full definition or identity for the entity being named by means of one or more URIs. + + + + \S+ + + + + + + + + + + + + + + + + + gives a minimum estimated value for the approximate measurement. + + + + (\-?[\d]+/\-?[\d]+) + + + + + + + + + + gives a maximum estimated value for the approximate measurement. + + + + (\-?[\d]+/\-?[\d]+) + + + + + + + + + + where the measurement summarizes more than one observation or a range, supplies the minimum value observed. + + + + (\-?[\d]+/\-?[\d]+) + + + + + + + + + + where the measurement summarizes more than one observation or a range, supplies the maximum value observed. + + + + (\-?[\d]+/\-?[\d]+) + + + + + + + + + + specifies the degree of statistical confidence (between zero and one) that a value falls within the range specified by @min and @max, or the proportion of observed values that fall within that range. + + + + + + + + + + + points to a <handNote> element describing the hand considered responsible for the content of the element concerned. + + \S+ + + + + + + + + + + + (canonical reference) specifies the destination of the pointer by supplying a canonical reference expressed using the scheme defined in a <refsDecl> element in the TEI header + + + + + + + + + + + + + + + supplies the value of the date or time in a standard form, e.g. yyyy-mm-dd. + + + + + + + + + + + + + + + + + specifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd. + + + + + + + + + + + + + + + + + specifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd. + + + + + + + + + + + + + + + + + indicates the starting point of the period in standard form, e.g. yyyy-mm-dd. + + + + + + + + + + + + + + + + + indicates the ending point of the period in standard form, e.g. yyyy-mm-dd. + + + + + + + + + + + + + + + + The @when attribute cannot be used with any other att.datable.w3c attributes. + + + + + The @from and @notBefore attributes cannot be used together. + + + + + The @to and @notAfter attributes cannot be used together. + + + + + + + + + + + + + indicates one or more systems or calendars to which the date represented by the content of this element belongs. + + + + \S+ + + + + + + + + + @calendar indicates one or more + systems or calendars to which the date represented by the content of this element belongs, + but this element has no textual content. + + + + + + supplies pointers to one or more definitions of named periods of time (typically <category>s or <calendar>s) within which the datable item is understood to have occurred. + + + + \S+ + + + + + + + + + + + + + indicates whether or not this element is selected by default when its parent is selected. + + true + This element is selected if its parent is selected + false + This element can only be selected explicitly, unless it is the only one of its kind, in which case it is selected if its parent is selected. + + + + + + + + + + + (declarations) identifies one or more declarable elements within the header, which are understood to apply to the element bearing this attribute and its content. + + + + \S+ + + + + + + + + + + + + + specifies whether or not its parent element is fragmented in some way, typically by some other overlapping structure: for example a speech which is divided between two or more verse stanzas, a paragraph which is split across a page division, a verse line which is divided between two speakers. + + Y + (yes) the element is fragmented in some (unspecified) respect + N + (no) the element is not fragmented, or no claim is made as to its completeness + I + (initial) this is the initial part of a fragmented element + M + (medial) this is a medial part of a fragmented element + F + (final) this is the final part of a fragmented element + + + + + + + + + + + describes the status of a document either currently or, when associated with a dated element, at the time indicated. +Sample values include: 1] approved; 2] candidate; 3] cleared; 4] deprecated; 5] draft; 6] embargoed; 7] expired; 8] frozen; 9] galley; 10] proposed; 11] published; 12] recommendation; 13] submitted; 14] unfinished; 15] withdrawn + + [^\p{C}\p{Z}]+ + + + + + + + + + + + + (certainty) signifies the degree of certainty associated with the intervention or interpretation. + + + + high + + medium + + low + + unknown + + + + + + + + + + (responsible party) indicates the agency responsible for the intervention or interpretation, for example an editor or transcriber. + + + + \S+ + + + + + + + + + + + + + + indicates the nature of the evidence supporting the reliability or accuracy of the intervention or interpretation. +Suggested values include: 1] internal; 2] external; 3] conjecture + + + + internal + there is internal evidence to support the intervention. + external + there is external evidence to support the intervention. + conjecture + the intervention or interpretation has been made by the editor, cataloguer, or scholar on the basis of their expertise. + + [^\p{C}\p{Z}]+ + + + + + + + + + + + indicates whether this is an instant revision or not. + + + + unknown + + inapplicable + + + + + + + + + + + + + + + (rendition) indicates how the element in question was rendered or presented in the source text. + + + + [^\p{C}\p{Z}]+ + + + + + + + + + + contains an expression in some formal style definition language which defines the rendering or presentation used for this element in the source text + + + + + + + + points to a description of the rendering or presentation used for this element in the source text. + + + + \S+ + + + + + + + + + + + + + specifies the source from which some aspect of this element is drawn. + + + + \S+ + + + + + + + + + + + When used on a schema description element (like + ), the @source attribute + should have only 1 value. (This one has .) + + + + + + + + + + + + + + + + + + + (identifier) provides a unique identifier for the element bearing the attribute. + + + + + + + + (number) gives a number (or other label) for an element, which is not necessarily unique within the document. + + + + + + + + (language) indicates the language of the element content using a tag generated according to BCP 47. + + + + + + + + + + + + + + provides a base URI reference with which applications can resolve relative URI references into absolute URI references. + + \S+ + + + + + + + + signals an intention about how white space should be managed by applications. + + default + signals that the application's default white-space processing modes are acceptable + preserve + indicates the intent that applications preserve all white space + + + + + + + + + + + (MIME media type) specifies the applicable multimedia internet mail extension (MIME) media type + + + + [^\p{C}\p{Z}]+ + + + + + + + + + + + + + + + may be used to specify further information about the entity referenced by this name in the form of a set of whitespace-separated values, for example the occupation of a person, or the status of a place. + + + + [^\p{C}\p{Z}]+ + + + + + + + + + + (reference to the canonical name) provides a means of locating the canonical form (nym) of the names associated with the object named by the element bearing it. + + + + \S+ + + + + + + + + + + + + + specifies where this item is placed. +Suggested values include: 1] top; 2] bottom; 3] margin; 4] opposite; 5] overleaf; 6] above; 7] right; 8] below; 9] left; 10] end; 11] inline; 12] inspace + + + + top + at the top of the page + bottom + at the foot of the page + margin + in the margin (left, right, or both) + opposite + on the opposite, i.e. facing, page + overleaf + on the other side of the leaf + above + above the line + right + to the right, e.g. to the right of a vertical line of text, or to the right of a figure + below + below the line + left + to the left, e.g. to the left of a vertical line of text, or to the left of a figure + end + at the end of e.g. chapter or volume. + inline + within the body of the text. + inspace + in a predefined space, for example left by an earlier scribe. + + [^\p{C}\p{Z}]+ + + + + + + + + + + + + + + + characterizes the element in some sense, using any convenient classification scheme or typology. + + [^\p{C}\p{Z}]+ + + + + + + + + (subtype) provides a sub-categorization of the element, if needed + + [^\p{C}\p{Z}]+ + + + + + + + The element should not be categorized in detail with @subtype unless also categorized in general with @type + + + + + + + + + + + specifies the language of the content to be found at the destination referenced by @target, using a language tag generated according to BCP 47. + + + + + + + + + + + + + @targetLang should only be used on if @target is specified. + + + + + + specifies the destination of the reference by supplying one or more URI References + + + + \S+ + + + + + + + + + + (evaluate) specifies the intended meaning when the target of a pointer is itself a pointer. + + all + if the element pointed to is itself a pointer, then the target of that pointer will be taken, and so on, until an element is found which is not a pointer. + one + if the element pointed to is itself a pointer, then its target (whether a pointer or not) is taken as the target of this pointer. + none + no further evaluation of targets is carried out beyond that needed to find the element specified in the pointer's target. + + + + + + + + + + + supplies the sort key for this element in an index, list or group which contains it. + + [^\p{C}\p{Z}]+ + + + + + + + + specifies the starting point of the range of units indicated by the @unit attribute. + + [^\p{C}\p{Z}]+ + + + + + + + + specifies the end-point of the range of units indicated by the @unit attribute. + + [^\p{C}\p{Z}]+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + indicates one or more locations by pointing to a <place> element or other canonical description. + + + + \S+ + + + + + + + + + + + + + + + + + + + + indicates whether the name component is given in full, as an abbreviation or simply as an initial. + + yes + (yes) the name component is spelled out in full. + abb + (abbreviated) the name component is given in an abbreviated form. + init + (initial letter) the name component is indicated only by one initial. + + + + + + + + (sort) specifies the sort order of the name component in relation to others within the name. + + + + + + + (paragraph) marks paragraphs in prose. [3.1. Paragraphs 7.2.5. Speech Contents] + + + + + Abstract model violation: Paragraphs may not occur inside other paragraphs or ab elements. + + + + + + + Abstract model violation: Lines may not contain higher-level structural elements such as div, p, or ab, unless p is a child of figure or note, or is a descendant of floatingText. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Element of type + <desc> cannot be empty. + + + The <desc> element should + generally contain either <persName> or <placeName>. SPEAR + encourages a liberal use of <persName>, <placeName>, and <date> + elements in the <desc> element of event factoids. + + + + + + This <relation> requires a <desc>. + + + + + The <desc> element may not appear here. + + + + + + This <desc> must contain <rs> elements, one for each values in the @mutual attribute on <relation>. + + + This <desc> requires <rs> elements with unique @ref attribute values. + + + + + + This <desc> must begin with "The following factoids deal with the same event: " + + + + + + This <desc> must begin with "The following factoids deal with related events: " + + + + + + + + (Latin for thus or so) contains text reproduced although apparently incorrect or inaccurate. [3.5.1. Apparent Errors] + + + + + + (correction) contains the correct form of a passage apparently erroneous in the copy text. [3.5.1. Apparent Errors] + + + + + + (choice) groups a number of alternative encodings for the same point in a text. [3.5. Simple Editorial Changes] + + + + + + + + + + + (regularization) contains a reading which has been regularized or normalized in some sense. [3.5.2. Regularization and +Normalization 12. Critical Apparatus] + + + + + + (original form) contains a reading which is marked as following the original, rather than being normalized or corrected. [3.5.2. Regularization and +Normalization 12. Critical Apparatus] + + + + + + (name, proper noun) contains a proper noun or noun phrase. [3.6.1. Referring Strings] + + + + + A @ref attribute is required. + + + + + + + + Acceptable values for this @ref attribute include: + . + + + + + + + + + + + + + + (referencing string) contains a general purpose name or referring string. [13.2.1. Personal Names 3.6.1. Referring Strings] + + + + + + + Acceptable values: + + + + + + The text node of this <rs> element must be . + + + + + + + + + + + + (number) contains a number, written in any form. [3.6.3. Numbers and +Measures] + + + + + + + indicates the type of numeric value. +Suggested values include: 1] cardinal; 2] ordinal; 3] fraction; 4] percentage + + cardinal + absolute number, e.g. 21, 21.5 + ordinal + ordinal number, e.g. 21st + fraction + fraction, e.g. one half or three-quarters + percentage + a percentage + + [^\p{C}\p{Z}]+ + + + + + + + supplies the value of the number in standard form. + + + + (\-?[\d]+/\-?[\d]+) + + + + + + + + + + + (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 15.2.3. The Setting Description 13.4. Dates] + + + + + + + + + + + + + + + + + + supplies a pointer to a <calendar> element or other means of interpreting the values of the custom dating attributes. + + \S+ + + + + + + +Suggested values include: 1] Gregorian; 2] Seleucid + + Gregorian + The element contains a date according to the Gregorian calendar. + Seleucid + The element contains a date according to the Seleucid calendar. + + \S+ + + + + + + + A <date> element child of <reg> + must have a @calendar attribute with a value of "Gregorian". + + + + + + + + (pointer) defines a pointer to another location. [3.7. Simple Links and Cross-References 16.1. Links] + + + + Only one of the +attributes @target and @cRef may be supplied on . + + + + + + + + \S+ + + + + + + + + The @target attribute on a <ptr> element inside a <bibl> element + with @type="primary" takes limited values. It either must be + "http://syriaca.org/work/" or + "http://syriaca.org/bibl/" followed by the corresponding Syriaca.org bibl URI + number. + + + + The @target attribute on a <ptr> element inside a <bibl> element + with @type="urn" must begin either with "urn:cts:syriacLit:nhsl.syriacCorpus" followed by the corresponding Syriac + Corpus URI number. + + + + URN in a <bibl> + element inside a SPEAR factoid must begin with URN in the <sourceDesc> + element of the <teiHeader>: ":". + + + The + @target attribute on the <ptr> element, "," is + not among the valid options contained in the <sourceDesc> element of the + <teiHeader>: () + + + + + + + + (reference) defines a reference to another location, possibly modified by additional text or comment. [3.7. Simple Links and Cross-References 16.1. Links] + + + + Only one of the + attributes @target' and @cRef' may be supplied on + + + + + + + + + + + + + + + (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] + + + + + + + + + + + + + A <head> element inside the <sourceDesc> must contain the text node: + "Sources for the Data in this Born Digital Prosopography". + + + A <head> element inside + the <back> must contain the text node: "Works Cited". + + + + + + + + + + + + (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 9.3.5.4. Notes within Entries] + + + + The <note> element in a birth place factoid + must contain a <persName>. + The <note> element in a birth place factoid + must contain a <placeName>. + + + The <note> element in a birth date factoid + must contain a <persName>. + + + The <note> element in a citizenship factoid + must contain a <persName>. + The <note> element in a citizenship factoid + must contain a <placeName>. + + + The <note> element in a death place factoid + must contain a <persName>. + The <note> element in a birth place factoid + must contain a <placeName>. + + + The <note> element in an education factoid + must contain a <persName>. + + + The <note> element in a death date factoid + must contain a <persName>. + + + The <note> element in an occupation factoid + must contain a <persName>. + + + The <note> element in a residence factoid must + contain a <persName>. + The <note> element in a residence factoid + must contain a <placeName>. + + + The <note> element in a socioeconomic status + factoid must contain a <persName>. + + + The <note> element in a language-known factoid + must contain a <persName>. + + + The <note> element inside the <trait> + element must contain a <persName>. + + + The <note> element inside the <state> + element must contain a <persName>. + + + This <note> element requires an @ana + attribute. + + + + + + The URI in this @ref attribute and the URI in the @ref attribute on the <persName> that + is the child of <person> must match. + + + + + The URI in this @ref attribute and the URI in the @ref attribute on the <placeName> that + is the child of <person> must match. + + + + + + The only note allowed in this context must contain the following text: "This + regularized date was calculated by the SPEAR editor from a non-calendrical dating + system such as regnal years, etc." + + + + + + + + + + + + + + + + + + + + + + + + + + + + + #calculated + + + + + + + + + desc + + certainty + + relatedEvent + + + + + + + This <note> must contain the + attribute @type="desc" and other <note> types are not allowed in this context. + Other types of notes (those dealing with "certainty") may appear as children of + the <ab> element as needed. + + + + + + If you wish to apply a date to this factoid, you must use + date attributes (@when, @notBefore, @notAfter, @to, and/or @from) on the + parent of the <note> element. + + + + + + + + incerta + + dubia + + errata + + + + + + + + A <note> element with @type="certainty" requires a @subtype. + + + + + + + + + (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] + + + + + + + + + + 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] + + + + + This <editor> must have a @role attribute. + + + This <editor> must have a @ref attribute. + + + + + + + + Acceptable values for this @ref attribute include: + . + + + + + + +Suggested values include: 1] creator; 2] general; 3] translator + + creator + A person involved in the creation of this xml file + general + A person responsible for this xml file or collection of xml files + translator + + + [^\p{C}\p{Z}]+ + + + + + + + + + \S+ + + + + + + + + + (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] + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + (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] + + + + + + + + + + (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] + + + + + The @ref attribute must take a Syriaca.org work URI + which reqires the form 'http://syriaca.org/work/{\d+}' + (where {\d+} is a number). + + + + + + + + + + classifies the title according to some convenient typology. +Sample values include: 1] main; 2] sub (subordinate); 3] alt (alternate); 4] short; 5] desc (descriptive) + + [^\p{C}\p{Z}]+ + + + + + + indicates the bibliographic level for a title, that is, whether it identifies an article, book, journal, series, or unpublished material. + + a + (analytic) the title applies to an analytic item, such as an article, poem, or other work published as part of a larger item. + m + (monographic) the title applies to a monograph such as a book or other item considered to be a distinct publication, including single volumes of multi-volume works + j + (journal) the title applies to any serial or periodical publication such as a journal, magazine, or newspaper + s + (series) the title applies to a series of otherwise distinct publications such as a collection + u + (unpublished) the title applies to any unpublished material (including theses and dissertations unless published by a commercial press) + + + + + + + + + (publisher) provides the name of the organization responsible for the publication or distribution of a bibliographic item. [3.12.2.4. Imprint, Size of a Document, and Reprint Information 2.2.4. Publication, Distribution, Licensing, etc.] + + + + + + + + + (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] + + + + + + + + + + + + + + + + identifies the unit of information conveyed by the element, e.g. columns, pages, volume, entry. +Suggested values include: 1] volume (volume); 2] issue; 3] page (page); 4] line; 5] chapter (chapter); 6] part; 7] column; 8] entry + + volume + (volume) the element contains a volume number. + issue + the element contains an issue number, or volume and issue numbers. + page + (page) the element contains a page number or page range. + line + the element contains a line number or line range. + chapter + (chapter) the element contains a chapter indication (number and/or title) + part + the element identifies a part of a book or collection. + column + the element identifies a column. + entry + the element identifies an entry number or label in a list of entries. + + [^\p{C}\p{Z}]+ + + + + + + + + + + + + + + p + the element contains a page number or page range. + line + the element contains a line number or line range. + part + the element contains a part of a book or collection, i.e. chapter and verse of a biblical text. + column + the element identifies a column. + + + + + + + + (publication place) contains the name of the place where a bibliographic item was published. [3.12.2.4. Imprint, Size of a Document, and Reprint Information] + + + + + + + + + (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 15.3.2. Declarable Elements] + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + A <bibl> element in the back matter must contain an + @xml:id attribute. + + + + The @xml:id on + <bibl> in the back matter must take the following form: 'bibl' + + '' + '-' + a unique number. + Each @xml:id attribute on <bibl> must have a unique value. + A properly formatted + @xml:id ends with a number. + A properly formatted + @xml:id ends with a number. + + + + + + + + + characterizes the element in some sense, using any convenient classification scheme or typology. + + [^\p{C}\p{Z}]+ + + + + + + + + (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 15.3.2. Declarable Elements] + + + + + + + + + + + + + + (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 15.1. Varieties of Composite Text] + + + + + + + + + + + + + (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] + + + + + + + + + + + + + + + + (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] + + + + + + + + + + + + + + + + + + + + + + The first <title> element child of <titleStmt> must have + @level attribute with a value of "m" indicating "monographic" or "a" indicating + analytic. + + + The first <title> element child of <titleStmt> must have + @type attribute with a value of "main". + + + + + The second <title> element child of <titleStmt> must have + @type attribute with a value of "sub". + + + The text node of this subtitle must be "A SPEAR Prosopography". + + + + + + + + + + (sponsor) specifies the name of a sponsoring organization or institution. [2.2.1. The Title Statement] + + + + + + + + + + (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] + + + + + + + + + + (edition statement) groups information relating to one edition of a text. [2.2.2. The Edition Statement 2.2. The File Description] + + + + + + + + (edition) describes the particularities of one edition of a text. [2.2.2. The Edition Statement] + + + + + + + + (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] + + + + + + + + + + + + + (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.] + + + + + The <authority> element should contain the text: "Syriaca.org: The Syriac Reference Portal." + + + + + + + + + + + (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. [13.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] + + + + + + + + + + An <idno> descendant of <ab> + requires a @type attribute with the value "URI". + + + This <idno> + requires a @type attribute with the value "URI". + + + This <idno> element + requires a @type attribute with the value "URI". + + + + + + + The text node of this <idno> must be "https://spear-prosop.org//tei". + + + + + + + This factoid URI must be: ". + + + + + + + [^\p{C}\p{Z}]+ + + + + + + + + + (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.] + + + + + + + + + + + (status) supplies a code identifying the current availability of the text. + + free + (free) the text is freely available. + unknown + (unknown) the status of the text is unknown. + restricted + (restricted) the text is not freely available. + + + + + + + + + contains information about a licence or other legal agreement applicable to the text. [2.2.4. Publication, Distribution, Licensing, etc.] + + + + + The <licence> element must contain <p> with the text: "Distributed under a Creative Commons Attribution 3.0 Unported License." + + + + + + + + + + + + (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] + + + + + + + + + + + + + + + + + + + + + + + + The <title> requires a @level attribute with a value of "s". + + + This <title> must be "SPEAR: Syriac Persons, Events, and Relations". + + + + + The <title> requires a @level attribute with a value of "m". + + + This <title> must be one of the following: "The Chronicle of Edessa", "The Lives of the Eastern Saints", + or "The Letters of Severus of Antioch". + + + + + This <title> requires a @type attribute with a value of "sub". + + + This <title> must be "A SPEAR Prosopography". + + + + + + + This <editor> must have a @role attribute with a value of "general". + + + + + This <editor> cannot have a @role attribute with a value of "creator". + + + + + This <editor> must have a @ref attribute with a value of "http://syriaca.org/documentation/editors.xml#dschwartz". + + + This <editor> must be "Daniel L. Schwartz". + + + + + + + This <idno> must be "https://spear-prosop.org". + + + + + This <idno> must be "https://spear-prosop.org/lives-eastern-saints". + + + + + This <idno> must be "https://spear-prosop.org/letters-severus". + + + + + + + This <seriesStmt> cannot contain a <biblScope>. + + + + + This <seriesStmt> requires a <biblScope>. + + + + + This <biblScope> element requires a a @unit + attribute having a value of "volume". + + + This <biblScope> element requires a child <title> element. + + + + + This <title> element requires a @level attribute with a value of "s". + + + This <title> element must contain "SPEAR: Syriac Persons, Events, and Relations". + + + + + + + + + + + (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] + + + + + + + + + + + + + + + + (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] + + + + + + + + + + + (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 15.3.2. Declarable Elements] + + + + + + + + + (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] + + + + + + + + (taxonomy) defines a typology either implicitly, by means of a bibliographic citation, or explicitly by a structured taxonomy. [2.3.7. The Classification Declaration] + + + + + + + + (category) contains an individual descriptive category, possibly nested within a superordinate category, within a user-defined taxonomy. [2.3.7. The Classification Declaration] + + + + + + + + + + + + + + + + + + + + + + + (identifier) provides a unique identifier for the element bearing the attribute. + + + + + + + + + (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] + + + + + + + + + (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] + + + + + + + + + + (revision description) summarizes the revision history for a file. [2.6. The Revision Description 2.1.1. The TEI Header and Its Components] + + + + + + + describes the status of a document either currently or, when associated with a dated element, at the time indicated. +Sample values include: 1] approved; 2] candidate; 3] cleared; 4] deprecated; 5] draft; 6] embargoed; 7] expired; 8] frozen; 9] galley; 10] proposed; 11] published; 12] recommendation; 13] submitted; 14] unfinished; 15] withdrawn + + [^\p{C}\p{Z}]+ + + + + + + + + + (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 11.7. Identifying Changes and Revisions] + + + + + + + + + (target) points to one or more elements that belong to this change. + + + + \S+ + + + + + + + + + + + + + + + + + + + + + + (corresponds) points to elements that correspond to the current element in some way. + + + + \S+ + + + + + + + + + + (synchronous) points to elements that are synchronous with the current element. + + + + \S+ + + + + + + + + + + points to an element that is the same as the current element. + + \S+ + + + + + + + + points to an element of which the current element is a copy. + + \S+ + + + + + + + + points to the next element of a virtual aggregate of which the current element is part. + + \S+ + + + + + + + + (previous) points to the previous element of a virtual aggregate of which the current element is part. + + \S+ + + + + + + + + points to elements that are in exclusive alternation with the current element. + + + + \S+ + + + + + + + + + + selects one or more alternants; if one alternant is selected, the ambiguity or uncertainty is marked as resolved. If more than one alternant is selected, the degree of ambiguity or uncertainty is marked as reduced by the number of alternants not selected. + + + + \S+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + An <ab> descendant of <body> requires an @xml:id attribute. + An <ab> descendant of <body> requires a @resp attribute. + An <ab> descendant of <body> requires a @type attribute with the value "factoid". + + + + + + Acceptable values for this @resp attribute include: + . + + + + + + + + + + An @xml:id attribute + starts with 'factoid-'. + A properly formatted + SPEAR factoid URI ends with a hyphen followed by a number. + A properly formatted + SPEAR factoid URI ends with a number. + + + + + + + + \S+ + + + + + + + + [^\p{C}\p{Z}]+ + + + + + + birth + (birth) Used to designate person factoids that encode birth dates and/or locations + citizenship + (citizenship) Used to designate person factoids that encode citizenship + death + (death) Used to designate person factoids that encode death dates and/or locations + education + (education) Used to designate person factoids that encode education + ethnicLabel + (ethnic label) Used to designate person factoids that encode ethnic labels + event + (event) Used to designate event factoids + gender + (gender) Used to designate person factoids that encode gender + langKnown + (language known) Used to designate person factoids that encode language knowledge + mentalState + (mental state) Used to designate person factoids that encode mental states + nameVariant + (name variant) Used to designate person factoids that encode name variants + occupation + (occupation) Used to designate person factoids that encode occupations + physicalTrait + (physical trait) Used to designate person factoids that encode physical traits + relation + (relation) Used to designate relation factoids + residence + (residence) Used to designate person factoids that encode places and dates of residence + sanctity + (sanctity) Used to designate person factoids that encode sanctity + socecStatus + (socio-economic status) Used to designate person factoids that encode socio-econimic status + + + + + + + + (TEI document) contains a single TEI-conformant document, combining a single TEI header with one or more members of the model.resource class. Multiple <TEI> elements may be combined within a <TEI> (or <teiCorpus>) element. [4. Default Text Structure 15.1. Varieties of Composite Text] + + + + + + + + + + + + + + + + + + + + + + + + specifies the version number of the TEI Guidelines against which this document is valid. + + [\d]+(\.[\d]+){0,2} + + + + + + + + + (text) contains a single text of any kind, whether unitary or composite, for example a poem or drama, a collection of essays, a novel, a dictionary, or a corpus sample. [4. Default Text Structure 15.1. Varieties of Composite Text] + + + + + + + + + + + + + + + + + + + + + + + + + + + + + (text body) contains the whole body of a single unitary text, excluding any front or back matter. [4. Default Text Structure] + + + + + + + + + + + (back matter) contains any appendixes, etc. following the main part of a text. [4.7. Back Matter 4. Default Text Structure] + + + + + + + + + + + + + + + + + + + supplies the value of a date or time in some custom standard form. + + + + [^\p{C}\p{Z}]+ + + + + + + + + + + specifies the earliest possible date for the event in some custom standard form. + + + + [^\p{C}\p{Z}]+ + + + + + + + + + + specifies the latest possible date for the event in some custom standard form. + + + + [^\p{C}\p{Z}]+ + + + + + + + + + + indicates the starting point of the period in some custom standard form. + + + + [^\p{C}\p{Z}]+ + + + + + + + + + + indicates the ending point of the period in some custom standard form. + + + + [^\p{C}\p{Z}]+ + + + + + + + + + + supplies a pointer to some location defining a named point in time with reference to which the datable item is understood to have occurred + + \S+ + + + + + + + + supplies a pointer to a <calendar> element or other means of interpreting the values of the custom dating attributes. + + \S+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + supplies the value of a date or time in a standard form. + + + + + + + + + + + [0-9.,DHMPRSTWYZ/:+\-]+ + + + + + + + + + specifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd. + + + + + + + + + + + [0-9.,DHMPRSTWYZ/:+\-]+ + + + + + + + + + specifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd. + + + + + + + + + + + [0-9.,DHMPRSTWYZ/:+\-]+ + + + + + + + + + indicates the starting point of the period in standard form. + + + + + + + + + + + [0-9.,DHMPRSTWYZ/:+\-]+ + + + + + + + + + indicates the ending point of the period in standard form. + + + + + + + + + + + [0-9.,DHMPRSTWYZ/:+\-]+ + + + + + + + + (organization name) contains an organizational name. [13.2.2. Organizational Names] + + + + + + + + + + + + (personal name) contains a proper noun or proper-noun phrase referring to a person, possibly including one or more of the person's forenames, surnames, honorifics, added names, etc. [13.2.1. Personal Names] + + + + + + \S+ + + + + + + + + This @ref may contain only one URI. + + The @ref attribute must take a Syriaca.org person URI which reqires + the form 'http://syriaca.org/person/{\d+}' (where {\d+} is a number). + + + is not currently in use. + Note that all person URIs take the form 'http://syriaca.org/person/{\d+}' + (where {\d+} is a number). If a URI is not current available, replace the number portion of the URI with + "#" followed without a space by a number that you use consistently when encoding information + about that person. + + + + + + + + + (place name) contains an absolute or relative place name. [13.2.3. Place Names] + + + + + \S+ + + + + + + + + This @ref may contain only one URI. + + The @ref attribute must take a Syriaca.org place URI which reqires + the form 'http://syriaca.org/place/{\d+}' (where {\d+} is a number). + + + is not currently in use. + Note that all properly formatted place URIs take the form 'http://syriaca.org/place/{\d+}' + (where {\d+} is a number). If a URI is not current available, replace the number portion of the URI with + "#" followed without a space by a number that you use consistently when encoding information + referring to that place. + + + + + + + + + (birth) contains information about a person's birth, such as its date and place. [15.2.2. The Participant Description] + + + + + + + + + + + + + + + + + + + + + (death) contains information about a person's death, such as its date and place. [15.2.2. The Participant Description] + + + + + + + + + + + + + + + + + + + + + (education) contains a description of the educational experience of a person. [15.2.2. The Participant Description] + + + + + + + + \S+ + + + + + + + + + + + + : URI(s) not in the Taxonomy. If you find no appropriate concept on the following list, + please choose a keyword of your own for the editors to consider: . + + + + + + + + (event) contains data relating to any kind of significant event associated with a person, place, or organization. [13.3.1. Basic Principles] + + + + + + + + + : URI(s) not in the Taxonomy. Please ensure that an appropriate URI does + not appear in the Taxonomy before proceeding. If you find no appropriate concept in the Taxonomy, please choose a keyword of your own for the editors to consider. + + + + + + + This <event> must have a @when attribute with the value . + + + + + This <event> must have a @notBefore attribute with the value . + + + + + This <event> must have a @notAfter attribute with the value . + + + + + This <event> must have a @from attribute with the value . + + + + + This <event> must have a @to attribute with the value . + + + + + + A <relation> element inside of an <event> element cannot take a <desc> element. + + + + + + + + + + + + + + + + + + + + + + + + (language known) summarizes the state of a person's linguistic competence, i.e., knowledge of a single language. [15.2.2. The Participant Description] + + + + + + + + + : URI(s) not in the Taxonomy. If you find no appropriate concept on the following list, + please choose a keyword of your own for the editors to consider: . + + + + + + + + + + + low + + medium + + high + + + + + + + + + + + + + + + + + + + + + + + + + provides information about relationships identified amongst people, places, and organizations, either informally as prose or as formally expressed relation links. [13.3.2.3. Personal Relationships] + + + + + + + + + + + + + + + + + + + + + + + + + + + (occupation) contains an informal description of a person's trade, profession or occupation. [15.2.2. The Participant Description] + + + + + + + + \S+ + + + + + + + + + + + + : URI(s) not in the Taxonomy. If you find no appropriate concept on the following list, + please choose a keyword of your own for the editors to consider: . + + + + + indicates the classification system or taxonomy in use, for example by supplying the identifier of a <taxonomy> element, or pointing to some other resource. + + \S+ + + + + + + identifies an occupation code defined within the classification system or taxonomy defined by the @scheme attribute. + + \S+ + + + + + + + + + (person) provides information about an identifiable individual, for example a participant in a language interaction, or a person referred to in a historical source. [13.3.2. The Person Element 15.2.2. The Participant Description] + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + specifies a primary role or classification for the person. + + + + [^\p{C}\p{Z}]+ + + + + + + + + specifies the sex of the person. + + + + [^\p{C}\p{Z}]+ + + + + + + + + specifies the gender of the person. + + + + [^\p{C}\p{Z}]+ + + + + + + + + specifies an age group for the person. + + [^\p{C}\p{Z}]+ + + + + + + + + + (personal group) describes a group of individuals treated as a single person for analytic purposes. [15.2.2. The Participant Description] + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + specifies the sex of the participant group. + + + + [^\p{C}\p{Z}]+ + + + + + + + + specifies the gender of the participant group. + + + + [^\p{C}\p{Z}]+ + + + + + + + + + + + (relationship) describes any kind of relationship or linkage amongst a specified group of places, events, persons, objects or other items. [13.3.2.3. Personal Relationships] + + + + + + + + + This <relation> takes either a @mutual attribute with mutual + relationships or both @active and @passive attributes with directed + relationships. Mutual relationships include: . Directed relationships include: + . + This <relation> takes either a @mutual attribute with mutual + relationships or both @active and @passive attributes with directed + relationships. Mutual relationships include: . Directed relationships include: + . + + + A @mutual attribute is required on <relation> + in event factoids. + @active attributes are not allowed on <relation> + in event factoids. + @passive attributes are not allowed on <relation> + in event factoids. + + + + + + + is not currently in use. + Note that all person URIs take the form 'http://syriaca.org/person/{\d+}' + (where {\d+} is a number). If a URI is not current available, replace the number portion of the URI with + "#" followed without a space by a number that you use consistently when encoding information + about that person. + + + + + + + This <relation> must have a @when attribute with the value . + + + + + This <relation> must have a @notBefore attribute with the value . + + + + + This <relation> must have a @notAfter attribute with the value . + + + + + This <relation> must have a @from attribute with the value . + + + + + This <relation> must have a @to attribute with the value . + + + + + + One of the attributes 'name', 'ref' or 'key' must be supplied + + + + + Only one of the attributes @active and @mutual may be supplied + + + + + the attribute 'passive' may be supplied only if the attribute 'active' is supplied + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + [^\p{C}\p{Z}]+ + + + + + + + + + + + + + : URI(s) not in the Taxonomy. If you find no appropriate concept on the following list, + please choose a keyword of your own for the editors to consider: . + + + A <relation> element inside an event factoid cannot + have an @ana attribute. + + + + + (reference) provides an explicit means of locating a full definition or identity for the entity being named by means of one or more URIs. + + + + \S+ + + + + + + + + + Value must be one of the following from the Syriaca.org taxonomy: + . + + + + Value must be one of the following from the Syriaca.org taxonomy: + . + + + + characterizes the element in some sense, using any convenient classification scheme or typology. + + [^\p{C}\p{Z}]+ + + + + + A <relation> element inside an event factoid + must take a @type attribute with the value "event". + + + A @type attribute with the value + "part" is required. + + + + + + identifies the active participants in a non-mutual relationship, or all the participants in a mutual one. + + + + \S+ + + + + + + + + supplies a list of participants amongst all of whom the relationship holds equally. + + + + \S+ + + + + + + + + + supplies a name for the kind of relationship of which this is an instance. + + [^\p{C}\p{Z}]+ + + + + + + + This <relation> element must have a @name attribute with a value of "dcterms:isPartOf". + + + + A @name attribute cannot appear here. + + + + + identifies the passive participants in a non-mutual relationship. + + + + \S+ + + + + + + + + + + + + + + + + + + + + + + + + + + (socio-economic status) contains an informal description of a person's perceived social or economic status. [15.2.2. The Participant Description] + + + + + + + + + + \S+ + + + + + + + + + + + + : URI(s) not in the Taxonomy. If you find no appropriate concept on the following list, + please choose a keyword of your own for the editors to consider: . + + + + + identifies the classification system or taxonomy in use, for example by pointing to a locally-defined <taxonomy> element or by supplying a URI for an externally-defined system. + + \S+ + + + + + + identifies a status code defined within the classification system or taxonomy defined by the @scheme attribute. + + \S+ + + + + + + + + + (state) contains a description of some status or quality attributed to a person, place, or organization often at some specific time or for a specific date range. [13.3.1. Basic Principles 13.3.2.1. Personal Characteristics] + + + + + + + + \S+ + + + + + + + + + + + + : URI(s) not in the Taxonomy. If you find no appropriate concept on the following list, + please choose a keyword of your own for the editors to consider: . + + + + + + + + : URI(s) not in the Taxonomy. If you find no appropriate concept on the following list, + please choose a keyword of your own for the editors to consider: . + + + + + + mental + used for references to a person's mental traits; such as intelligence, mental disability, wisdom, etc. + religiousAffiliation + used for references to a person's religious affiliation; including but not limited to membership in an organization, adhering to a set of beliefs, or identifying with a religious community in some way. + sanctity + used for references to a person's sanctity. + + + + + + + + (trait) contains a description of some status or quality attributed to a person, place, or organization typically, but not necessarily, independent of the volition or action of the holder and usually not at some specific time or for a specific date range. [13.3.1. Basic Principles 13.3.2.1. Personal Characteristics] + + + + + + + + \S+ + + + + + + + + + + + + : URI(s) not in the Taxonomy. If you find no appropriate concept on the following list, + please choose a keyword of your own for the editors to consider: . + + + + Preferred values for the @ana attribute on a <trait> element + @type="gender" are: + "http://syriaca.org/keyword/eunuch"; "http://syriaca.org/keyword/female"; + "http://syriaca.org/keyword/male"; and + "http://syriaca.org/keyword/nun-as-monk". Use these if applicable. If one of + these does not apply, please use a descriptive term of your + choosing. + + + + + + + + : URI(s) not in the Taxonomy. . + + + + + + + physical + used for references to a person's physical characteristics, such as hair color, height, weight, physical disabilities, etc. + gender + used for references to a person's gender identity (as opposed to their biological sex which SPEAR does not presume to capture). + ethnicLabel + used for references to an ethnic label claimed by a person or ascribed to a person; such as "Goth," "Saracen," etc. + + + + + + + + + + + + + + + + + + + + + Each @ana attribute value must start with "http://syriaca.org/keyword/" and multiple + values must be space separated. + + + The same keyword URI may not appear twice as the value of the @ana attribute. + + Multiple @ana attributes should be separated with one blank space + + + Multiple @ana attributes should be separated with one blank space + + + + + + + + +