Welcome to the Medieval Anglo-Jewish Women Project. Here you will find encoding instructions, administration details, and other information related to the project.
First you will need to learn How to use Subversion (SVN) to check out the repository, update your local copy, and commit your changes.
If youʼre working as an encoder on this project, youʼll need to edit several different types of file:
We keep all our XML files and related documents in a Subversion Repository. This is a version-control system that ensures that every version of every file can be retrieved if necessary, and prevents one person from inadvertently overwriting changes to a file made by someone else.
Subversion runs on one of our HCMC servers, which is at hcmc.uvic.ca/svn
. In order to use it, you will need to install a Subversion client on your computer,
and also learn a couple of simple command-line commands. Subversion is usually abbreviated
to ‘svn’.
If you are working on a computer in HCMC, Subversion will already be installed. If you are working on a different computer, such as your own laptop, you will have to install it.
How you will do this depends on which operating system you are using.
Obtain a command-line client from SilkSVN. There is no cost to download the client. Make sure to download the correct version; there are versions for 32-bit and 64-bit Windows. Once the program is downloaded, install it by double-clicking the downloaded installer and following its instructions.
Installing svn on Mac has become slightly complicated recently because Apple have removed it from their XCode toolset. We now have to install it using Homebrew, which is a package manager for the Mac. Here are the steps:
Command-V)
The Homebrew install process takes a little while. When it completes, go back to the terminal and type this:
brew install svn⚓
When svn is installed, test it by typing:
svn --version⚓
in the terminal. You should see lots of mysterious information, but the first thing should be the svn version number which is now installed on your machine.
Subversion is installed as part of a regular desktop on most Linux distributions.
If it is not, you can simply type sudo apt install subversion
or the equivalent command for your Linux distribution.
Once your subversion client is installed, the first thing we need to do is to check out the repository. To do this, you need to open a terminal window:
cmd
into the search box.Terminal
from the Utilities
folder in Applications
.Control + Alt + T
.Now we'll check that svn is installed and working. Type svn checkout
and press return. If the terminal responses that there are Not enough arguments provided
, then svn is working OK.
And now we'll check out the files from the repository into our home directory, using this command:
svn checkout https://hcmc.uvic.ca/svn/majw⚓
Then the server should ask for your netlink user name and password. After that, you should see the files download to your drive.
These are the basic rules when you're working with svn:
Before you start work, update your local files:
You can leave the terminal open while you work. Then, when you're ready to commit your changes:
svn update⚓(again, just in case anything else has been committed by someone else)
svn commit data -m "A message explaining the changes you have made"⚓
(Aside: we include ‘content’ after the word ‘commit’ to specify that we only want to commit any changes that are in the content
folder. That way, if we've accidentally made changes to program code or other files
in the repo, those changes won't be committed.)
That's basically it. If you see any warnings or error messages from svn, check that you're in the right folder in your terminal. You may also see error messages if two people have been editing the same file at the same time, and Subversion needs you to make a decision about whose changes should be kept.
Your encoding work will all be done in the Oxygen XML Editor. When you install Oxygen, there are lots of applications that come with it: Oxygen Author, Oxygen Developer, Compare Files, Compare Directories and others. But the one you want to work with is always Oxygen XML Editor, which has the blue icon with the red cross on it. Here's how to get started:
majw
folder in your home directory.majw.xpr
.You should see a tree of folders and files down the left of your Oxygen editor. This
includes all the files in the project. You can ignore most of them. The folder that
matters is the data
folder, where all the main XML documents are kept.
Our Oxygen project file has a number of useful keyboard shortcuts built into it, which you can use to speed up your encoding. Generally speaking, to use these, you select some text in the editor, then press the keystroke shortcut shown in the table below. The table uses the following key names:
M1 | represents the Command key on MacOS X, and the Ctrl key on other platforms. |
M2 | represents the Shift key. |
M3 | represents the Option key on MacOS X, and the Alt key on other platforms. |
M4 | represents the Ctrl key on MacOS X, and is undefined on other platforms. |
The following table shows keyboard shortcuts available when the majw.xpr
project file is loaded.
Name | Description | Result | Keystroke |
Analytic (article or poem) title | Wrap in title element with level="a" | <title level="a">${xpath_eval(replace('${selection}', '[“”]+', ''))}</title>${caret} | M1 M2 A |
Curly apostrophe | ʼ | M1 M2 QUOTE | |
En dash | En dash, used between digits | – | ctrl shift MINUS |
Enter comment on merging events. | <!-- MDH ${xpath_eval(format-date(current-date(), '[Y0001]-[M01]-[D01]'))}: merged ev_ into ev_ per AB/JP. --> | M1 M3 M2 SLASH | |
Journal title | <title level="j">${selection}</title>${caret} | M1 M2 J | |
Link to person | Link selected text to a person record | <ref target="pros:${ask('Please type the id of the person (abcd1, wxyz12, etc.)', generic, '')}">${selection}</ref>${caret} | M1 M2 P |
Monograph (book or play) title | <title level="m">${selection}</title>${caret} | M1 M2 M | |
New event record | Add a new event element with placeholder content. | <event xml:id="ev_" resp="pers:[your own id]" notBefore="[year]" notAfter="[year]" period="tm:[period id if relevant, or delete the attribute]" ana="ht:[id]"> <desc> <placeName corresp="plc:[place id]">[place name]</placeName> </desc> <listPerson> <person corresp="pros:"/> </listPerson> <linkGrp type="businesses"> <ptr target="bs:[business id]"/> </linkGrp> <bibl corresp="msd:[msDesc id]"> <biblScope unit="srcMemFol">[membrane or folio num]</biblScope> <textLang mainLang="[en or fr or la or he]"/> </bibl> <bibl corresp="bib:[bibl id]"> <biblScope unit="page">[page num(s)]</biblScope> </bibl> </event> | ctrl alt shift E |
New person record | Add a new person element with placeholder content | <person xml:id="" sex="[M or F]"> <persName> <forename>[forename]</forename> </persName> <persName type="displayName">[descriptive display name]</persName> <trait type="relation"> <label>relationships</label> <desc>[description of person in terms of key relationship(s)]</desc> </trait> <note type="relation">[any note you need to add, or delete the element]</note> </person> | M1 M3 M2 P |
Simple quotation | Removes existing quote marks and wraps selection in <q> | <q>${xpath_eval(replace('${selection}', '[“”]+', ''))}</q> | M1 M2 Q |
personography.xml
file, and is the person entry for Dayne B. Pettyjohn. This means that this person
created or edited the entry and believes it to be correct. The resp attribute can be used anywhere, but it is essential to add it to <person> elements in the prosopography files and <event> elements in the events files. The attribute permits more than one value, so when
Dr. Williams-Boyarin has proofed and confirmed an item, she may add her own resp value
to confirm that the item has been checked:
We are just getting started with a pure-XML dataset, so it will be a little while before we can settle on a reliable and robust workflow. This section provides initial suggestions for entering new data, and will be continually amended as we try this out and settle on best practices.
Before entering records (<event>s) or people (<person>s), itʼs important to make sure all the required bibliographical records are present
in the bibliography.xml
file. This file is in two main sections: primary sources (manuscripts, encoded using
<msDesc> elements), and secondary sources (print publications, encoded as <bibl> elements).
Unlike the manuscripts, the xml:id attributes of print sources are not necessarily predictable from their content; instead they follow two different conventions, one based on the original relational database abbreviations (such as PREJ), and a second which creates an id based on the author name and date.
Events are organized into separate files by year, so open the appropriate file and move to the end before adding an event. (Note that events which run over more than one year are grouped under their starting year.)
Place your cursor after the closing tag of the final event, add a couple of linebreaks,
and then press Control + Alt + Shift + E
on your keyboard to insert a new event. Then:
businesses.html
on the Jenkins site (which is linked from the bottom of the Aboutpage.
sources.html
on the Jenkins site. A similar process is used to encode the secondary source, providing
a pointer to the source itself (found on the sources.html
page) and the relevant page number(s):
Finally, the people mentioned in the case must be encoded in the <linkGrp> with type=people, along with any relationships which are attested in this event.
The focus of this project is women, so any woman mentioned in the record will be added. Generally, men are only added to our event records when they are explicitly mentioned as relatives of women who appear in the record. However, occasionally, where their presence in records aids in reconstructing the family network of a featured woman, attested relationships between men may be added to an event record, and inferred relationships involving men based on existing data may be added to the dataset.
data/prosopography
folder, and all that is required is to supply their id in the corresp attribute with the pros:
prefix. If any of the people mentioned do not yet have records, and/or if the event
attests to relationships between people, then records will have to be created or updated
in the prosopography; this is the subject of a section below.Note the use of <persName> element: this records the exact form the personʼs name takes in the text of the event you are encoding. If multiple variants of the personʼs name are used, then include one <persName> element for each variant. This enables us to track all the variants used for each individual and for each distinct name.
If multiple languages are used for a name, then those variants must also be encoded. For example, if a name appears in Latin rather than, or as well as, English, then we follow these rules:
bene3
(in active) is the father
of ivet9
(in passive). Note that this relationship could also be encoded in reverse, with ivet9
as the daughter
of bene3
. However, we have a single canonical method of encoding relationships to avoid ambiguity: we place the id which comes first alphabetically in the active attribute. If you try to encode the relationship in the wrong orientation, a Schematron
rule should warn you of the error.Add all the relationships attested by this event into the <listRelation> element.
Here is a complete encoded event as a full example.
You will be doing two kinds of edits to the prosopography: adding new people, and adding assertions that two person records may in fact be the same person, signifying that further research is needed.
The prosopography is organized by initial alphabetical letter, so first open the file
for the first letter in the personʼs name. Within the file, there is no need for further
organization; just add your new person at the end. Put your cursor after the closing
tag of the final person, add a couple of linebreaks, and then press Control + Alt + Shift + P
. A new person template will be inserted.
Obviously, if a person already exists in the prosopography, then the only thing you need to do is to edit that personʼs record to add any newly-attested relationships that arise out of the event you are currently editing. FOR THE MOMENT, every case where a relationship is attested by an event requires a new <relation> element to be added to one of the participants, even if the same relationship is already attested by other events. In other words, FOR THE MOMENT, you can only add a single event pointer in the <relation>/source attribute. However, for people appearing in many records, this results in a large number of <relation> elements attesting to the same relationship, which is obviously not ideal, so we will probably move to a system where the source attribute can contain multiple event pointers.
data/prosopography/prosopographyLinks.xml
file:
Sometimes it is important for our dataset to include individuals who are not directly attested in primary source documents. For example, if we know of a father/daughter relationship, but we have no information about the mother, we may infer that a mother must have existed, and must have been the wife of the father. We occasionally do this in order to support work on the family trees of featured women, for instance.
Just as we may often infer the existence of people, we may also infer relationships between such people and attested people, or between attested people. For example, if a man and a woman have the same parents, we can obviously infer that they are brother and sister. It is often helpful to explicitly record relationships which we can infer from the evidence but which are not explicitly mentioned anywhere, because that enables us to build richer networks and in particular to fill out the family trees of featured women.
Inferred relations are encoded in the data/relations_unattested.xml
file. You can add any relation you have confidence in to this file. You may also
want to provide some explanation in the form of an XML comment to say how you decided
that this relationship existed.
bios.xml
file.<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] | |||||||||
Module | textstructure | ||||||||
Attributes |
|
||||||||
Contained by |
textstructure: TEI
|
||||||||
May contain | |||||||||
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"/>
<sch:ns prefix="rna"
uri="http://relaxng.org/ns/compatibility/annotations/1.0"/>
|
||||||||
Schematron |
<sch:ns prefix="sch"
uri="http://purl.oclc.org/dsdl/schematron"/>
<sch:ns prefix="sch1x"
uri="http://www.ascc.net/xml/schematron"/>
|
||||||||
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+ ) ) }⚓ |
<abbr> (abbreviation) contains an abbreviation of any sort. [3.6.5. Abbreviations and Their Expansions] | |||||||||||
Module | core | ||||||||||
Attributes |
|
||||||||||
Member of | |||||||||||
Contained by | |||||||||||
May contain |
core: abbr choice cit corr date email emph expan foreign gloss graphic hi mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
character data
|
||||||||||
Note |
If abbreviations are expanded silently, this practice should be documented in the <editorialDecl>, either with a <normalization> element or a <p>. |
||||||||||
Example |
<choice>
<expan>North Atlantic Treaty Organization</expan>
<abbr cert="low">NorATO</abbr>
<abbr cert="high">NATO</abbr>
<abbr cert="high" xml:lang="fr">OTAN</abbr>
</choice>
|
||||||||||
Example |
<choice>
<abbr>SPQR</abbr>
<expan>senatus populusque romanorum</expan>
</choice>
|
||||||||||
Content model |
<content> <macroRef key="macro.phraseSeq"/> </content> ⚓ |
||||||||||
Schema Declaration |
element abbr { att.global.attributes, att.typed.attribute.subtype, attribute type { text }?, macro.phraseSeq }⚓ |
<addName> (additional name) contains an additional name component, such as a nickname, epithet, or alias, or any other descriptive phrase used within a personal name. [13.2.1. Personal Names] | |
Module | namesdates |
Attributes |
|
Member of | |
Contained by | |
May contain |
core: abbr choice cit corr date email emph expan foreign gloss graphic hi mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
character data
|
Example |
<persName>
<forename>Frederick</forename>
<addName type="epithet">the Great</addName>
<roleName>Emperor of Prussia</roleName>
</persName>
|
Content model |
<content> <macroRef key="macro.phraseSeq"/> </content> ⚓ |
Schema Declaration |
element addName { att.global.attributes, att.personal.attributes, att.typed.attributes, macro.phraseSeq }⚓ |
<affiliation> (affiliation) contains an informal description of a person's present or past affiliation with some organization, for example an employer or sponsor. [15.2.2. The Participant Description] | |||||||||||||||||||
Module | namesdates | ||||||||||||||||||
Attributes |
|
||||||||||||||||||
Member of | |||||||||||||||||||
Contained by | |||||||||||||||||||
May contain |
core: abbr choice cit corr date email emph expan foreign gloss graphic hi mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
character data
|
||||||||||||||||||
Note |
If included, the name of an organization may be tagged using either the <name> element as above, or the more specific <orgName> element. |
||||||||||||||||||
Example |
<affiliation>Junior project officer for the US <name type="org">National Endowment for
the Humanities</name>
</affiliation>
|
||||||||||||||||||
Example | This example indicates that the person was affiliated with the Australian Journalists
Association at some point between the dates listed.
<affiliation notAfter="1960-01-01"
notBefore="1957-02-28">Paid up member of the
<orgName>Australian Journalists Association</orgName>
</affiliation>
|
||||||||||||||||||
Example | This example indicates that the person was affiliated with Mount Holyoke College throughout
the entire span of the date range listed.
<affiliation from="1902-01-01"
to="1906-01-01">Was an assistant professor at Mount Holyoke College.</affiliation>
|
||||||||||||||||||
Content model |
<content> <macroRef key="macro.phraseSeq"/> </content> ⚓ |
||||||||||||||||||
Schema Declaration |
element affiliation { att.global.attributes, att.editLike.attributes, att.datable.attributes, att.naming.attributes, att.typed.attribute.subtype, attribute type { text }?, attribute calendar { list { + } }?, macro.phraseSeq }⚓ |
<age> (age) specifies the age of a person. [13.3.2.1. Personal Characteristics] | |||||||||||||||||||||||||||
Module | namesdates | ||||||||||||||||||||||||||
Attributes |
|
||||||||||||||||||||||||||
Member of | |||||||||||||||||||||||||||
Contained by |
namesdates: person
|
||||||||||||||||||||||||||
May contain |
core: abbr choice date email emph expan foreign gloss hi mentioned name note ptr q ref soCalled term title
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
character data
|
||||||||||||||||||||||||||
Note |
As with other culturally-constructed traits such as sex, the way in which this concept is described in different cultural contexts may vary. The normalizing attributes are provided as a means of simplifying that variety to Western European norms and should not be used where that is inappropriate. The content of the element may be used to describe the intended concept in more detail, using plain text. |
||||||||||||||||||||||||||
Example |
<age value="2" notAfter="1986">under 20 in the early eighties</age>
|
||||||||||||||||||||||||||
Content model |
<content> <macroRef key="macro.phraseSeq.limited"/> </content> ⚓ |
||||||||||||||||||||||||||
Schema Declaration |
element age { att.global.attributes, att.editLike.attributes, att.datable.attributes, att.typed.attribute.subtype, att.dimensions.attributes, attribute type { text }?, attribute calendar { list { + } }?, attribute value { text }?, macro.phraseSeq.limited }⚓ |
<author> (author) in a bibliographic reference, contains the name(s) of an author, personal or corporate, of a work; for example in the same form as that provided by a recognized bibliographic name authority. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement] | |||||||||||
Module | core | ||||||||||
Attributes |
|
||||||||||
Member of | |||||||||||
Contained by |
core: bibl
header: editionStmt titleStmt
|
||||||||||
May contain |
core: abbr choice cit corr date email emph expan foreign gloss graphic hi mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
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, attribute calendar { list { + } }?, macro.phraseSeq }⚓ |
<authority> (release authority) supplies the name of a person or other agency responsible for making a work available, other than a publisher or distributor. [2.2.4. Publication, Distribution, Licensing, etc.] | |
Module | header |
Attributes |
|
Member of | |
Contained by |
header: publicationStmt
|
May contain |
core: abbr choice date email emph expan foreign gloss hi mentioned name note ptr q ref soCalled term title
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
character data
|
Example |
<authority>John Smith</authority>
|
Content model |
<content> <macroRef key="macro.phraseSeq.limited"/> </content> ⚓ |
Schema Declaration |
element authority { att.global.attributes, att.canonical.attributes, macro.phraseSeq.limited }⚓ |
<back> (back matter) contains any appendixes, etc. following the main part of a text. [4.7. Back Matter 4. Default Text Structure] | |
Module | textstructure |
Attributes |
|
Contained by |
textstructure: text
|
May contain | |
Note |
Because cultural conventions differ as to which elements are grouped as back matter and which as front matter, the content models for the <back> and <front> elements are identical. |
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, &c. 2s.
6d</item>
<item n="2">Dr. Hooper's Female Pills, 1s.</item>
<!-- ... -->
</list>
</div>
</back>
|
Content model |
<content> <sequence> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.frontPart"/> <classRef key="model.pLike.front"/> <classRef key="model.pLike"/> <classRef key="model.listLike"/> <classRef key="model.global"/> </alternate> <alternate minOccurs="0"> <sequence> <classRef key="model.div1Like"/> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.frontPart"/> <classRef key="model.div1Like"/> <classRef key="model.global"/> </alternate> </sequence> <sequence> <classRef key="model.divLike"/> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.frontPart"/> <classRef key="model.divLike"/> <classRef key="model.global"/> </alternate> </sequence> </alternate> <sequence minOccurs="0"> <classRef key="model.divBottomPart"/> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.divBottomPart"/> <classRef key="model.global"/> </alternate> </sequence> </sequence> </content> ⚓ |
Schema Declaration |
element back { att.global.attributes, att.declaring.attributes, ( ( model.frontPart | model.pLike.front | model.pLike | model.listLike | model.global )*, ( ( model.div1Like, ( model.frontPart | model.div1Like | model.global )* ) | ( model.divLike, ( model.frontPart | model.divLike | model.global )* ) )?, ( ( model.divBottomPart, ( model.divBottomPart | model.global )* )? ) ) }⚓ |
<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] | |||||||||||
Module | core | ||||||||||
Attributes |
|
||||||||||
Member of | |||||||||||
Contained by | |||||||||||
May contain |
core: abbr author bibl biblScope choice corr date editor email emph expan foreign gloss hi mentioned name note orig ptr pubPlace publisher q ref reg relatedItem respStmt series sic soCalled term textLang title unclear
figures: figure
msdescription: msIdentifier
namesdates: addName affiliation district forename genName geo listRelation location orgName persName placeName population region roleName settlement state surname trait
character data
|
||||||||||
Note |
Contains phrase-level elements, together with any combination of elements from the model.biblPart class |
||||||||||
Example |
<bibl>Blain, Clements and Grundy: Feminist Companion to Literature in English (Yale,
1990)</bibl>
|
||||||||||
Example |
<bibl>
<title level="a">The Interesting story of the Children in the Wood</title>. In
<author>Victor E Neuberg</author>, <title>The Penny Histories</title>.
<publisher>OUP</publisher>
<date>1968</date>.
</bibl>
|
||||||||||
Example |
<bibl type="article" subtype="book_chapter"
xml:id="carlin_2003">
<author>
<name>
<surname>Carlin</surname>
(<forename>Claire</forename>)</name>
</author>,
<title level="a">The Staging of Impotence : France’s last
congrès</title> dans
<bibl type="monogr">
<title level="m">Theatrum mundi : studies in honor of Ronald W.
Tobin</title>, éd.
<editor>
<name>
<forename>Claire</forename>
<surname>Carlin</surname>
</name>
</editor> et
<editor>
<name>
<forename>Kathleen</forename>
<surname>Wine</surname>
</name>
</editor>,
<pubPlace>Charlottesville, Va.</pubPlace>,
<publisher>Rookwood Press</publisher>,
<date when="2003">2003</date>.
</bibl>
</bibl>
|
||||||||||
Content model |
<content> <alternate minOccurs="0" maxOccurs="unbounded"> <textNode/> <classRef key="model.gLike"/> <classRef key="model.highlighted"/> <classRef key="model.pPart.data"/> <classRef key="model.pPart.edit"/> <classRef key="model.segLike"/> <classRef key="model.ptrLike"/> <classRef key="model.biblPart"/> <classRef key="model.global"/> </alternate> </content> ⚓ |
||||||||||
Schema Declaration |
element bibl { 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.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.facs.attribute.facs, att.global.change.attribute.change, att.global.responsibility.attribute.cert, att.global.responsibility.attribute.resp, att.global.source.attribute.source, att.declarable.attributes, att.typed.attributes, att.sortable.attributes, att.docStatus.attributes, attribute corresp { list { ( "msd:msd_bcl_256_307191" | "msd:msd_bl_add_7218" | "msd:msd_bl_add_Ch_1250" | "msd:msd_bl_add_Roll_19299" | "msd:msd_bl_cot_Nero_C_III" | "msd:msd_bl_harl_Ch_43_A_54" | "msd:msd_bl_harl_Ch_43_A_56" | "msd:msd_bl_harl_Ch_84D" | "msd:msd_bl_harl_Chart_43A" | "msd:msd_bl_harl_Chart_43A_59A" | "msd:msd_bl_lans_Ch_665" | "msd:msd_bl_lans_Ch_666" | "msd:msd_bl_lans_Ch_667" | "msd:msd_bl_lans_Ch_668" | "msd:msd_bl_lans_Ch_669" | "msd:msd_magd_ald_34" | "msd:msd_mert_14_D_I_58_i" | "msd:msd_mert_mcr_188" | "msd:msd_tna_13_Item_98" | "msd:msd_tna_15_27_189" | "msd:msd_tna_9_26_115B" | "msd:msd_tna_9_26_35" | "msd:msd_tna_c_143_10_14" | "msd:msd_tna_c_145_17_3" | "msd:msd_tna_c_145_35_56" | "msd:msd_tna_c_255_18_5B" | "msd:msd_tna_c_53_13" | "msd:msd_tna_c_53_2" | "msd:msd_tna_c_53_20" | "msd:msd_tna_c_53_26" | "msd:msd_tna_c_53_29" | "msd:msd_tna_c_53_44" | "msd:msd_tna_c_53_47" | "msd:msd_tna_c_53_64" | "msd:msd_tna_c_53_68" | "msd:msd_tna_c_53_69" | "msd:msd_tna_c_53_70" | "msd:msd_tna_c_53_78" | "msd:msd_tna_c_54_101" | "msd:msd_tna_c_54_105" | "msd:msd_tna_c_54_106" | "msd:msd_tna_c_54_107" | "msd:msd_tna_c_54_114" | "msd:msd_tna_c_54_117" | "msd:msd_tna_c_54_38" | "msd:msd_tna_c_54_41" | "msd:msd_tna_c_54_42" | "msd:msd_tna_c_54_43" | "msd:msd_tna_c_54_44" | "msd:msd_tna_c_54_45" | "msd:msd_tna_c_54_46" | "msd:msd_tna_c_54_47" | "msd:msd_tna_c_54_48" | "msd:msd_tna_c_54_49" | "msd:msd_tna_c_54_51" | "msd:msd_tna_c_54_52" | "msd:msd_tna_c_54_53" | "msd:msd_tna_c_54_57" | "msd:msd_tna_c_54_59" | "msd:msd_tna_c_54_60" | "msd:msd_tna_c_54_61" | "msd:msd_tna_c_54_62" | "msd:msd_tna_c_54_63" | "msd:msd_tna_c_54_64" | "msd:msd_tna_c_54_68" | "msd:msd_tna_c_54_69" | "msd:msd_tna_c_54_70" | "msd:msd_tna_c_54_71" | "msd:msd_tna_c_54_72" | "msd:msd_tna_c_54_73" | "msd:msd_tna_c_54_74" | "msd:msd_tna_c_54_75" | "msd:msd_tna_c_54_76" | "msd:msd_tna_c_54_77" | "msd:msd_tna_c_54_78" | "msd:msd_tna_c_54_82" | "msd:msd_tna_c_54_83" | "msd:msd_tna_c_54_84" | "msd:msd_tna_c_54_85" | "msd:msd_tna_c_54_86" | "msd:msd_tna_c_54_87" | "msd:msd_tna_c_54_88" | "msd:msd_tna_c_54_89" | "msd:msd_tna_c_54_91" | "msd:msd_tna_c_54_92" | "msd:msd_tna_c_54_93" | "msd:msd_tna_c_54_94" | "msd:msd_tna_c_54_95" | "msd:msd_tna_c_54_96" | "msd:msd_tna_c_54_97" | "msd:msd_tna_c_54_98" | "msd:msd_tna_c_54_99" | "msd:msd_tna_c_60_16" | "msd:msd_tna_c_60_24" | "msd:msd_tna_c_60_27" | "msd:msd_tna_c_60_28" | "msd:msd_tna_c_60_29" | "msd:msd_tna_c_60_31" | "msd:msd_tna_c_60_32" | "msd:msd_tna_c_60_34" | "msd:msd_tna_c_60_35" | "msd:msd_tna_c_60_36" | "msd:msd_tna_c_60_37" | "msd:msd_tna_c_60_40" | "msd:msd_tna_c_60_40A" | "msd:msd_tna_c_60_41" | "msd:msd_tna_c_60_46" | "msd:msd_tna_c_60_47" | "msd:msd_tna_c_60_48" | "msd:msd_tna_c_60_49" | "msd:msd_tna_c_60_50" | "msd:msd_tna_c_60_52" | "msd:msd_tna_c_60_53" | "msd:msd_tna_c_60_54" | "msd:msd_tna_c_60_55" | "msd:msd_tna_c_60_56" | "msd:msd_tna_c_60_58" | "msd:msd_tna_c_60_59" | "msd:msd_tna_c_60_80" | "msd:msd_tna_c_60_82" | "msd:msd_tna_c_60_83" | "msd:msd_tna_c_60_9" | "msd:msd_tna_c_67_4" | "msd:msd_tna_c_85_170" | "msd:msd_tna_c_85_3_71" | "msd:msd_tna_c_85_99" | "msd:msd_tna_e_101_13_8_" | "msd:msd_tna_e_101_249" | "msd:msd_tna_e_101_249_19" | "msd:msd_tna_e_101_249_20" | "msd:msd_tna_e_101_249_22" | "msd:msd_tna_e_101_249_8" | "msd:msd_tna_e_101_250" | "msd:msd_tna_e_159_41" | "msd:msd_tna_e_159_42" | "msd:msd_tna_e_159_43" | "msd:msd_tna_e_159_44" | "msd:msd_tna_e_159_45" | "msd:msd_tna_e_159_46" | "msd:msd_tna_e_159_47" | "msd:msd_tna_e_159_48" | "msd:msd_tna_e_159_49" | "msd:msd_tna_e_159_50" | "msd:msd_tna_e_159_51" | "msd:msd_tna_e_159_52" | "msd:msd_tna_e_159_53" | "msd:msd_tna_e_159_54" | "msd:msd_tna_e_159_55" | "msd:msd_tna_e_159_56" | "msd:msd_tna_e_159_57" | "msd:msd_tna_e_159_58" | "msd:msd_tna_e_159_59" | "msd:msd_tna_e_159_60" | "msd:msd_tna_e_159_61" | "msd:msd_tna_e_159_62" | "msd:msd_tna_e_159_63" | "msd:msd_tna_e_159_64" | "msd:msd_tna_e_159_65" | "msd:msd_tna_e_159_66" | "msd:msd_tna_e_199_39" | "msd:msd_tna_e_32_12" | "msd:msd_tna_e_368_41" | "msd:msd_tna_e_368_42" | "msd:msd_tna_e_368_43" | "msd:msd_tna_e_368_44" | "msd:msd_tna_e_368_45" | "msd:msd_tna_e_368_46" | "msd:msd_tna_e_368_47" | "msd:msd_tna_e_368_48" | "msd:msd_tna_e_368_49" | "msd:msd_tna_e_368_50" | "msd:msd_tna_e_368_51" | "msd:msd_tna_e_368_52" | "msd:msd_tna_e_368_53" | "msd:msd_tna_e_368_54" | "msd:msd_tna_e_368_55" | "msd:msd_tna_e_368_56" | "msd:msd_tna_e_368_57" | "msd:msd_tna_e_368_58" | "msd:msd_tna_e_368_59" | "msd:msd_tna_e_368_60" | "msd:msd_tna_e_368_61" | "msd:msd_tna_e_368_62" | "msd:msd_tna_e_368_63" | "msd:msd_tna_e_368_64" | "msd:msd_tna_e_370_2" | "msd:msd_tna_e_371_3" | "msd:msd_tna_e_371_4" | "msd:msd_tna_e_371_7" | "msd:msd_tna_e_401_1564" | "msd:msd_tna_e_401_1565" | "msd:msd_tna_e_401_1573" | "msd:msd_tna_e_401_1574" | "msd:msd_tna_e_401_1576" | "msd:msd_tna_e_401_1586" | "msd:msd_tna_e_401_1590" | "msd:msd_tna_e_401_4" | "msd:msd_tna_e_402_3A" | "msd:msd_tna_e_402_3B" | "msd:msd_tna_e_40_1478" | "msd:msd_tna_e_9_1" | "msd:msd_tna_e_9_10" | "msd:msd_tna_e_9_11" | "msd:msd_tna_e_9_12" | "msd:msd_tna_e_9_13" | "msd:msd_tna_e_9_14" | "msd:msd_tna_e_9_15" | "msd:msd_tna_e_9_16" | "msd:msd_tna_e_9_17" | "msd:msd_tna_e_9_18" | "msd:msd_tna_e_9_183" | "msd:msd_tna_e_9_19" | "msd:msd_tna_e_9_2" | "msd:msd_tna_e_9_20" | "msd:msd_tna_e_9_21" | "msd:msd_tna_e_9_22" | "msd:msd_tna_e_9_23" | "msd:msd_tna_e_9_24" | "msd:msd_tna_e_9_25" | "msd:msd_tna_e_9_26" | "msd:msd_tna_e_9_27" | "msd:msd_tna_e_9_28" | "msd:msd_tna_e_9_29" | "msd:msd_tna_e_9_3" | "msd:msd_tna_e_9_30" | "msd:msd_tna_e_9_31_and_70" | "msd:msd_tna_e_9_32" | "msd:msd_tna_e_9_32_and_64" | "msd:msd_tna_e_9_33" | "msd:msd_tna_e_9_34_and_65" | "msd:msd_tna_e_9_35" | "msd:msd_tna_e_9_36" | "msd:msd_tna_e_9_37" | "msd:msd_tna_e_9_38" | "msd:msd_tna_e_9_39" | "msd:msd_tna_e_9_4" | "msd:msd_tna_e_9_40" | "msd:msd_tna_e_9_41" | "msd:msd_tna_e_9_42" | "msd:msd_tna_e_9_43" | "msd:msd_tna_e_9_45" | "msd:msd_tna_e_9_49" | "msd:msd_tna_e_9_5" | "msd:msd_tna_e_9_52" | "msd:msd_tna_e_9_53" | "msd:msd_tna_e_9_54" | "msd:msd_tna_e_9_6" | "msd:msd_tna_e_9_62" | "msd:msd_tna_e_9_66" | "msd:msd_tna_e_9_7" | "msd:msd_tna_e_9_8" | "msd:msd_tna_e_9_9" | "msd:msd_tna_pat_66_1" | "msd:msd_tna_pat_66_10" | "msd:msd_tna_pat_66_100" | "msd:msd_tna_pat_66_101" | "msd:msd_tna_pat_66_102" | "msd:msd_tna_pat_66_103" | "msd:msd_tna_pat_66_104" | "msd:msd_tna_pat_66_105" | "msd:msd_tna_pat_66_105A" | "msd:msd_tna_pat_66_106" | "msd:msd_tna_pat_66_106A" | "msd:msd_tna_pat_66_107" | "msd:msd_tna_pat_66_108" | "msd:msd_tna_pat_66_109" | "msd:msd_tna_pat_66_11" | "msd:msd_tna_pat_66_110" | "msd:msd_tna_pat_66_111" | "msd:msd_tna_pat_66_112" | "msd:msd_tna_pat_66_113" | "msd:msd_tna_pat_66_114" | "msd:msd_tna_pat_66_115" | "msd:msd_tna_pat_66_116" | "msd:msd_tna_pat_66_117" | "msd:msd_tna_pat_66_118" | "msd:msd_tna_pat_66_119" | "msd:msd_tna_pat_66_12" | "msd:msd_tna_pat_66_120" | "msd:msd_tna_pat_66_121" | "msd:msd_tna_pat_66_122" | "msd:msd_tna_pat_66_123" | "msd:msd_tna_pat_66_124" | "msd:msd_tna_pat_66_125" | "msd:msd_tna_pat_66_126" | "msd:msd_tna_pat_66_127" | "msd:msd_tna_pat_66_128" | "msd:msd_tna_pat_66_129" | "msd:msd_tna_pat_66_13" | "msd:msd_tna_pat_66_130" | "msd:msd_tna_pat_66_14" | "msd:msd_tna_pat_66_15" | "msd:msd_tna_pat_66_16" | "msd:msd_tna_pat_66_17" | "msd:msd_tna_pat_66_18" | "msd:msd_tna_pat_66_19" | "msd:msd_tna_pat_66_2" | "msd:msd_tna_pat_66_20" | "msd:msd_tna_pat_66_21" | "msd:msd_tna_pat_66_22" | "msd:msd_tna_pat_66_23" | "msd:msd_tna_pat_66_24" | "msd:msd_tna_pat_66_25" | "msd:msd_tna_pat_66_26" | "msd:msd_tna_pat_66_27" | "msd:msd_tna_pat_66_28" | "msd:msd_tna_pat_66_29" | "msd:msd_tna_pat_66_3" | "msd:msd_tna_pat_66_30" | "msd:msd_tna_pat_66_31" | "msd:msd_tna_pat_66_32" | "msd:msd_tna_pat_66_33" | "msd:msd_tna_pat_66_34" | "msd:msd_tna_pat_66_35" | "msd:msd_tna_pat_66_36" | "msd:msd_tna_pat_66_37" | "msd:msd_tna_pat_66_38" | "msd:msd_tna_pat_66_39" | "msd:msd_tna_pat_66_4" | "msd:msd_tna_pat_66_40" | "msd:msd_tna_pat_66_41" | "msd:msd_tna_pat_66_42" | "msd:msd_tna_pat_66_43" | "msd:msd_tna_pat_66_44" | "msd:msd_tna_pat_66_45" | "msd:msd_tna_pat_66_46" | "msd:msd_tna_pat_66_47" | "msd:msd_tna_pat_66_48" | "msd:msd_tna_pat_66_49" | "msd:msd_tna_pat_66_5" | "msd:msd_tna_pat_66_50" | "msd:msd_tna_pat_66_51" | "msd:msd_tna_pat_66_52" | "msd:msd_tna_pat_66_53" | "msd:msd_tna_pat_66_54" | "msd:msd_tna_pat_66_55" | "msd:msd_tna_pat_66_56" | "msd:msd_tna_pat_66_57" | "msd:msd_tna_pat_66_58" | "msd:msd_tna_pat_66_59" | "msd:msd_tna_pat_66_6" | "msd:msd_tna_pat_66_60" | "msd:msd_tna_pat_66_61" | "msd:msd_tna_pat_66_62" | "msd:msd_tna_pat_66_63" | "msd:msd_tna_pat_66_64" | "msd:msd_tna_pat_66_65" | "msd:msd_tna_pat_66_66" | "msd:msd_tna_pat_66_67" | "msd:msd_tna_pat_66_68" | "msd:msd_tna_pat_66_69" | "msd:msd_tna_pat_66_7" | "msd:msd_tna_pat_66_70" | "msd:msd_tna_pat_66_71" | "msd:msd_tna_pat_66_72" | "msd:msd_tna_pat_66_73" | "msd:msd_tna_pat_66_74" | "msd:msd_tna_pat_66_75" | "msd:msd_tna_pat_66_76" | "msd:msd_tna_pat_66_77" | "msd:msd_tna_pat_66_78" | "msd:msd_tna_pat_66_79" | "msd:msd_tna_pat_66_8" | "msd:msd_tna_pat_66_80" | "msd:msd_tna_pat_66_81" | "msd:msd_tna_pat_66_82" | "msd:msd_tna_pat_66_83" | "msd:msd_tna_pat_66_84" | "msd:msd_tna_pat_66_85" | "msd:msd_tna_pat_66_86" | "msd:msd_tna_pat_66_87" | "msd:msd_tna_pat_66_88" | "msd:msd_tna_pat_66_89" | "msd:msd_tna_pat_66_9" | "msd:msd_tna_pat_66_90" | "msd:msd_tna_pat_66_91" | "msd:msd_tna_pat_66_92" | "msd:msd_tna_pat_66_93" | "msd:msd_tna_pat_66_94" | "msd:msd_tna_pat_66_95" | "msd:msd_tna_pat_66_96" | "msd:msd_tna_pat_66_97" | "msd:msd_tna_pat_66_98" | "msd:msd_tna_pat_66_99" | "msd:msd_tna_sc_1_14" | "msd:msd_tna_sc_8_180" | "msd:msd_wam_10" | "msd:msd_wam_6075B" | "msd:msd_wam_6690" | "msd:msd_wam_6703" | "msd:msd_wam_6726" | "msd:msd_wam_6733" | "msd:msd_wam_6745" | "msd:msd_wam_6746" | "msd:msd_wam_6754" | "msd:msd_wam_6757" | "msd:msd_wam_6771" | "msd:msd_wam_6781" | "msd:msd_wam_6787" | "msd:msd_wam_6788" | "msd:msd_wam_6789" | "msd:msd_wam_6791" | "msd:msd_wam_6792" | "msd:msd_wam_6793" | "msd:msd_wam_6796" | "msd:msd_wam_6797" | "msd:msd_wam_6799" | "msd:msd_wam_6800" | "msd:msd_wam_6801" | "msd:msd_wam_6802" | "msd:msd_wam_6804" | "msd:msd_wam_6805" | "msd:msd_wam_6806" | "msd:msd_wam_6807" | "msd:msd_wam_6808" | "msd:msd_wam_6810" | "msd:msd_wam_6812" | "msd:msd_wam_6814" | "msd:msd_wam_6815" | "msd:msd_wam_6817" | "msd:msd_wam_6818" | "msd:msd_wam_6819" | "msd:msd_wam_6820" | "msd:msd_wam_6821" | "msd:msd_wam_6822" | "msd:msd_wam_6823" | "msd:msd_wam_6824" | "msd:msd_wam_6827" | "msd:msd_wam_6829" | "msd:msd_wam_6832" | "msd:msd_wam_6835" | "msd:msd_wam_6836" | "msd:msd_wam_6838" | "msd:msd_wam_6841" | "msd:msd_wam_6846" | "msd:msd_wam_6847" | "msd:msd_wam_6848" | "msd:msd_wam_6855" | "msd:msd_wam_6857" | "msd:msd_wam_6861" | "msd:msd_wam_6862" | "msd:msd_wam_6866" | "msd:msd_wam_6869" | "msd:msd_wam_6871" | "msd:msd_wam_6875" | "msd:msd_wam_6879" | "msd:msd_wam_6888" | "msd:msd_wam_6889" | "msd:msd_wam_6893" | "msd:msd_wam_6898" | "msd:msd_wam_6899" | "msd:msd_wam_6901" | "msd:msd_wam_6904" | "msd:msd_wam_6908" | "msd:msd_wam_6934" | "msd:msd_wam_6935" | "msd:msd_wam_6936" | "msd:msd_wam_6939" | "msd:msd_wam_6955" | "msd:msd_wam_6982" | "msd:msd_wam_6989" | "msd:msd_wam_6995" | "msd:msd_wam_9006" | "msd:msd_wam_9007" | "msd:msd_wam_9007d" | "msd:msd_wam_9025" | "msd:msd_wam_9029" | "msd:msd_wam_9036" | "msd:msd_wam_9049" | "msd:msd_wam_9072" | "msd:msd_wam_9079" | "msd:msd_wam_9080" | "msd:msd_wam_9094" | "msd:msd_wam_9127" | "msd:msd_wam_9131" | "msd:msd_wam_9139" | "msd:msd_wam_9146" | "msd:msd_wam_9173" | "bib:bib_SJC" | "bib:bib_abra1_2022" | "bib:bib_adle1_1939" | "bib:bib_bart1_2015" | "bib:bib_bart1_2000" | "bib:bib_bran1_2004" | "bib:bib_brow1_2019" | "bib:bib_butl1_nd" | "bib:bib_Causton" | "bib:bib_chew1_1927" | "bib:bib_dace1_2007" | "bib:bib_Davis" | "bib:bib_elij_1956" | "bib:bib_cave1_2021" | "bib:bib_fogl1_2019" | "bib:bib_fria1_1907" | "bib:bib_frie1_1987" | "bib:bib_gold1_2012" | "bib:bib_CChR_1199" | "bib:bib_CChR_1226" | "bib:bib_CChR_1257" | "bib:bib_CFR_1272" | "bib:bib_CCR_1272" | "bib:bib_CCR_1279" | "bib:bib_CCR_1288" | "bib:bib_CCR_1296" | "bib:bib_CCR_1227" | "bib:bib_CCR_1256" | "bib:bib_CCR_1259" | "bib:bib_CCR_1261" | "bib:bib_CCR_1264" | "bib:bib_CCR_1268" | "bib:bib_CCR_1231" | "bib:bib_CCR_1234" | "bib:bib_CCR_1237" | "bib:bib_CCR_1242" | "bib:bib_CCR_1247" | "bib:bib_CCR_1251" | "bib:bib_CCR_1253" | "bib:bib_CCR_1254" | "bib:bib_CPR_1201" | "bib:bib_CPR_1216" | "bib:bib_CPR_1225" | "bib:bib_CPR_1232" | "bib:bib_CPR_1247" | "bib:bib_CPR_1258" | "bib:bib_CPR_1266" | "bib:bib_CPR_1272a" | "bib:bib_CPR_1272b" | "bib:bib_CPR_1273" | "bib:bib_CPR_1274" | "bib:bib_CPR_1275" | "bib:bib_CPR_1276" | "bib:bib_CPR_1277" | "bib:bib_CPR_1278" | "bib:bib_CPR_1279" | "bib:bib_CPR_1280" | "bib:bib_CPR_1281" | "bib:bib_CPR_1292" | "bib:bib_CPR_1301" | "bib:bib_PREJ_1" | "bib:bib_PREJ_2" | "bib:bib_PREJ_3" | "bib:bib_PREJ_4" | "bib:bib_PREJ_5" | "bib:bib_PREJ_6" | "bib:bib_FRH3" | "bib:bib_PAT_1" | "bib:bib_SPC" | "bib:bib_Rigg" | "bib:bib_hill2_2001" | "bib:bib_hill1_2015" | "bib:bib_towr1_2022" | "bib:bib_hoyl1_2008" | "bib:bib_irwi1_2023" | "bib:bib_Lipman" | "bib:bib_Logan" | "bib:bib_macl1_nd" | "bib:bib_meye1_nd" | "bib:bib_mund1_1998" | "bib:bib_mund1_1992" | "bib:bib_HHLD_1" | "bib:bib_HHLD_2" | "bib:bib_park1_1992" | "bib:bib_roke1_1992a" | "bib:bib_roke1_1992b" | "bib:bib_roke1_2000" | "bib:bib_sira1_2004" | "bib:bib_will1_2021" )+ } }?, ( text | model.gLike | model.highlighted | model.pPart.data | model.pPart.edit | model.segLike | model.ptrLike | model.biblPart | model.global )* }⚓ |
<biblScope> (scope of bibliographic reference) defines the scope of a bibliographic reference, for example as a list of page numbers, or a named subdivision of a larger work. [3.12.2.5. Scopes and Ranges in Bibliographic Citations] | |||||||||||
Module | core | ||||||||||
Attributes |
|
||||||||||
Member of | |||||||||||
Contained by | |||||||||||
May contain |
core: abbr choice cit corr date email emph expan foreign gloss graphic hi mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
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 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> <macroRef key="macro.phraseSeq"/> </content> ⚓ |
||||||||||
Schema Declaration |
element biblScope { att.global.attributes, att.citing.attribute.from, att.citing.attribute.to, attribute unit { "issue" | "page" | "item" | "srcMemFol" | "srcNum" }?, macro.phraseSeq }⚓ |
<birth> (birth) contains information about a person's birth, such as its date and place. [15.2.2. The Participant Description] | |||||||||||||||||||
Module | namesdates | ||||||||||||||||||
Attributes |
|
||||||||||||||||||
Member of | |||||||||||||||||||
Contained by |
namesdates: person
|
||||||||||||||||||
May contain |
core: abbr choice cit corr date email emph expan foreign gloss graphic hi mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
character data
|
||||||||||||||||||
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> <macroRef key="macro.phraseSeq"/> </content> ⚓ |
||||||||||||||||||
Schema Declaration |
element birth { att.global.attributes, att.editLike.attributes, att.datable.attributes, att.dimensions.attributes, att.naming.attributes, att.typed.attribute.subtype, attribute type { text }?, attribute calendar { list { + } }?, macro.phraseSeq }⚓ |
<body> (text body) contains the whole body of a single unitary text, excluding any front or back matter. [4. Default Text Structure] | |
Module | textstructure |
Attributes |
|
Contained by |
textstructure: text
|
May contain | |
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> <sequence> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> <sequence minOccurs="0"> <classRef key="model.divTop"/> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.global"/> <classRef key="model.divTop"/> </alternate> </sequence> <sequence minOccurs="0"> <classRef key="model.divGenLike"/> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.global"/> <classRef key="model.divGenLike"/> </alternate> </sequence> <alternate> <sequence minOccurs="1" maxOccurs="unbounded"> <classRef key="model.divLike"/> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.global"/> <classRef key="model.divGenLike"/> </alternate> </sequence> <sequence minOccurs="1" maxOccurs="unbounded"> <classRef key="model.div1Like"/> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.global"/> <classRef key="model.divGenLike"/> </alternate> </sequence> <sequence> <sequence minOccurs="1" maxOccurs="unbounded"> <alternate minOccurs="1" maxOccurs="1"> <elementRef key="schemaSpec"/> <classRef key="model.common"/> </alternate> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> <alternate minOccurs="0"> <sequence minOccurs="1" maxOccurs="unbounded"> <classRef key="model.divLike"/> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.global"/> <classRef key="model.divGenLike"/> </alternate> </sequence> <sequence minOccurs="1" maxOccurs="unbounded"> <classRef key="model.div1Like"/> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.global"/> <classRef key="model.divGenLike"/> </alternate> </sequence> </alternate> </sequence> </alternate> <sequence minOccurs="0" maxOccurs="unbounded"> <classRef key="model.divBottom"/> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> </sequence> </content> ⚓ |
Schema Declaration |
element body { att.global.attributes, att.declaring.attributes, ( model.global*, ( ( model.divTop, ( model.global | model.divTop )* )? ), ( ( model.divGenLike, ( model.global | model.divGenLike )* )? ), ( ( ( model.divLike, ( model.global | model.divGenLike )* )+ ) | ( ( model.div1Like, ( model.global | model.divGenLike )* )+ ) | ( ( ( ( schemaSpec | model.common ), model.global* )+ ), ( ( ( model.divLike, ( model.global | model.divGenLike )* )+ ) | ( ( model.div1Like, ( model.global | model.divGenLike )* )+ ) )? ) ), ( ( model.divBottom, model.global* )* ) ) }⚓ |
<c> (character) represents a character. [17.1. Linguistic Segment Categories] | |
Module | analysis |
Attributes |
|
Member of | |
Contained by |
core: abbr author bibl biblScope corr date editor email emph expan foreign gloss head hi item label mentioned name note orig p pubPlace publisher q quote ref reg rs sic soCalled term textLang title unclear
figures: cell
namesdates: addName affiliation birth death district education faith floruit forename genName gender occupation orgName persName placeName region residence roleName settlement sex surname
transcr: zone
|
May contain | Character data only |
Note |
Contains a single character, a <g> element, or a sequence of graphemes to be treated as a single character. The type attribute is used to indicate the function of this segmentation, taking values such as letter, punctuation, or digit etc. |
Example |
<phr>
<c>M</c>
<c>O</c>
<c>A</c>
<c>I</c>
<w>doth</w>
<w>sway</w>
<w>my</w>
<w>life</w>
</phr>
|
Content model |
<content> <macroRef key="macro.xtext"/> </content> ⚓ |
Schema Declaration |
element c { att.global.attributes, att.segLike.attributes, att.typed.attributes, att.notated.attributes, macro.xtext }⚓ |
<calendar> (calendar) describes a calendar or dating system used in a dating formula in the text. [2.4.5. Calendar Description] | |
Module | header |
Attributes |
|
Contained by |
header: calendarDesc
|
May contain |
core: p
|
Example |
<calendarDesc>
<calendar xml:id="julianEngland">
<p>Julian Calendar (including proleptic)</p>
</calendar>
</calendarDesc>
|
Example |
<calendarDesc>
<calendar xml:id="egyptian"
target="http://en.wikipedia.org/wiki/Egyptian_calendar">
<p>Egyptian calendar (as defined by Wikipedia)</p>
</calendar>
</calendarDesc>
|
Content model |
<content> <classRef key="model.pLike" minOccurs="1" maxOccurs="unbounded"/> </content> ⚓ |
Schema Declaration |
element calendar { att.global.attributes, att.pointing.attributes, att.typed.attributes, model.pLike+ }⚓ |
<calendarDesc> (calendar description) contains a description of the calendar system used in any dating expression found in the text. [2.4. The Profile Description 2.4.5. Calendar Description] | |
Module | header |
Attributes |
|
Member of | |
Contained by |
header: profileDesc
|
May contain |
header: calendar
|
Note |
In the first example above, calendars and short codes for xml:ids are from W3 guidelines at http://www.w3.org/TR/xpath-functions-11/#lang-cal-country |
Example |
<calendarDesc>
<calendar xml:id="cal_AD">
<p>Anno Domini (Christian Era)</p>
</calendar>
<calendar xml:id="cal_AH">
<p>Anno Hegirae (Muhammedan Era)</p>
</calendar>
<calendar xml:id="cal_AME">
<p>Mauludi Era (solar years since Mohammed's birth)</p>
</calendar>
<calendar xml:id="cal_AM">
<p>Anno Mundi (Jewish Calendar)</p>
</calendar>
<calendar xml:id="cal_AP">
<p>Anno Persici</p>
</calendar>
<calendar xml:id="cal_AS">
<p>Aji Saka Era (Java)</p>
</calendar>
<calendar xml:id="cal_BE">
<p>Buddhist Era</p>
</calendar>
<calendar xml:id="cal_CB">
<p>Cooch Behar Era</p>
</calendar>
<calendar xml:id="cal_CE">
<p>Common Era</p>
</calendar>
<calendar xml:id="cal_CL">
<p>Chinese Lunar Era</p>
</calendar>
<calendar xml:id="cal_CS">
<p>Chula Sakarat Era</p>
</calendar>
<calendar xml:id="cal_EE">
<p>Ethiopian Era</p>
</calendar>
<calendar xml:id="cal_FE">
<p>Fasli Era</p>
</calendar>
<calendar xml:id="cal_ISO">
<p>ISO 8601 calendar</p>
</calendar>
<calendar xml:id="cal_JE">
<p>Japanese Calendar</p>
</calendar>
<calendar xml:id="cal_KE">
<p>Khalsa Era (Sikh calendar)</p>
</calendar>
<calendar xml:id="cal_KY">
<p>Kali Yuga</p>
</calendar>
<calendar xml:id="cal_ME">
<p>Malabar Era</p>
</calendar>
<calendar xml:id="cal_MS">
<p>Monarchic Solar Era</p>
</calendar>
<calendar xml:id="cal_NS">
<p>Nepal Samwat Era</p>
</calendar>
<calendar xml:id="cal_OS">
<p>Old Style (Julian Calendar)</p>
</calendar>
<calendar xml:id="cal_RS">
<p>Rattanakosin (Bangkok) Era</p>
</calendar>
<calendar xml:id="cal_SE">
<p>Saka Era</p>
</calendar>
<calendar xml:id="cal_SH">
<p>Mohammedan Solar Era (Iran)</p>
</calendar>
<calendar xml:id="cal_SS">
<p>Saka Samvat</p>
</calendar>
<calendar xml:id="cal_TE">
<p>Tripurabda Era</p>
</calendar>
<calendar xml:id="cal_VE">
<p>Vikrama Era</p>
</calendar>
<calendar xml:id="cal_VS">
<p>Vikrama Samvat Era</p>
</calendar>
</calendarDesc>
|
Example |
<calendarDesc>
<calendar xml:id="cal_Gregorian">
<p>Gregorian calendar</p>
</calendar>
<calendar xml:id="cal_Julian">
<p>Julian calendar</p>
</calendar>
<calendar xml:id="cal_Islamic">
<p>Islamic or Muslim (hijri) lunar calendar</p>
</calendar>
<calendar xml:id="cal_Hebrew">
<p>Hebrew or Jewish lunisolar calendar</p>
</calendar>
<calendar xml:id="cal_Revolutionary">
<p>French Revolutionary calendar</p>
</calendar>
<calendar xml:id="cal_Iranian">
<p>Iranian or Persian (Jalaali) solar calendar</p>
</calendar>
<calendar xml:id="cal_Coptic">
<p>Coptic or Alexandrian calendar</p>
</calendar>
<calendar xml:id="cal_Chinese">
<p>Chinese lunisolar calendar</p>
</calendar>
</calendarDesc>
|
Example |
<calendarDesc>
<calendar xml:id="cal_Egyptian"
target="http://en.wikipedia.org/wiki/Egyptian_calendar">
<p>Egyptian calendar (as defined by Wikipedia)</p>
</calendar>
</calendarDesc>
|
Content model |
<content> <elementRef key="calendar" minOccurs="1" maxOccurs="unbounded"/> </content> ⚓ |
Schema Declaration |
element calendarDesc { att.global.attributes, calendar+ }⚓ |
<catDesc> (category description) describes some category within a taxonomy or text typology, either in the form of a brief prose description or in terms of the situational parameters used by the TEI formal <textDesc>. [2.3.7. The Classification Declaration] | |
Module | header |
Attributes |
|
Contained by |
header: category
|
May contain | |
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> <alternate minOccurs="0" maxOccurs="unbounded"> <textNode/> <classRef key="model.limitedPhrase"/> <classRef key="model.catDescPart"/> </alternate> </content> ⚓ |
Schema Declaration |
element catDesc { att.global.attributes, att.canonical.attributes, ( text | model.limitedPhrase | model.catDescPart )* }⚓ |
<catRef> (category reference) specifies one or more defined categories within some taxonomy or text typology. [2.4.3. The Text Classification] | |||||||
Module | header | ||||||
Attributes |
|
||||||
Contained by |
header: textClass
|
||||||
May contain | Empty element | ||||||
Note |
The scheme attribute needs to be supplied only if more than one taxonomy has been declared. |
||||||
Example |
<catRef scheme="#myTopics"
target="#news #prov #sales2"/>
<!-- elsewhere -->
<taxonomy xml:id="myTopics">
<category xml:id="news">
<catDesc>Newspapers</catDesc>
</category>
<category xml:id="prov">
<catDesc>Provincial</catDesc>
</category>
<category xml:id="sales2">
<catDesc>Low to average annual sales</catDesc>
</category>
</taxonomy>
|
||||||
Content model |
<content> <empty/> </content> ⚓ |
||||||
Schema Declaration |
element catRef { att.global.attributes, att.pointing.attributes, attribute scheme { text }?, empty }⚓ |
<category> (category) contains an individual descriptive category, possibly nested within a superordinate category, within a user-defined taxonomy. [2.3.7. The Classification Declaration] | |
Module | header |
Attributes |
|
Contained by | |
May contain | |
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> <sequence> <alternate> <elementRef key="catDesc" minOccurs="1" maxOccurs="unbounded"/> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.descLike"/> <elementRef key="equiv"/> <elementRef key="gloss"/> </alternate> </alternate> <elementRef key="category" minOccurs="0" maxOccurs="unbounded"/> </sequence> </content> ⚓ |
Schema Declaration |
element category { att.global.attributes, att.datcat.attributes, ( ( catDesc+ | ( model.descLike | equiv | gloss )* ), category* ) }⚓ |
<cell> (cell) contains one cell of a table. [14.1.1. TEI Tables] | |
Module | figures |
Attributes |
|
Contained by |
figures: row
|
May contain |
core: abbr bibl choice cit corr date desc email emph expan foreign gloss graphic hi label list listBibl mentioned name note orig p ptr q quote ref reg sic soCalled term title unclear
header: idno
msdescription: msDesc
namesdates: addName affiliation district forename genName geo listEvent listOrg listPerson listPlace listRelation location orgName persName placeName population region roleName settlement state surname trait
character data
|
Example |
<row>
<cell role="label">General conduct</cell>
<cell role="data">Not satisfactory, on account of his great unpunctuality
and inattention to duties</cell>
</row>
|
Content model |
<content> <macroRef key="macro.specialPara"/> </content> ⚓ |
Schema Declaration |
element cell { att.global.attributes, att.tableDecoration.attributes, macro.specialPara }⚓ |
<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] | |||||||||||||||||
Module | header | ||||||||||||||||
Attributes |
|
||||||||||||||||
Contained by |
header: revisionDesc
|
||||||||||||||||
May contain |
core: abbr bibl choice cit corr date desc email emph expan foreign gloss graphic hi label list listBibl mentioned name note orig p ptr q quote ref reg sic soCalled term title unclear
header: idno
msdescription: msDesc
namesdates: addName affiliation district forename genName geo listEvent listOrg listPerson listPlace listRelation location orgName persName placeName population region roleName settlement state surname trait
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 calendar { list { + } }?, attribute target { list { + } }?, macro.specialPara }⚓ |
<choice> (choice) groups a number of alternative encodings for the same point in a text. [3.5. Simple Editorial Changes] | |
Module | core |
Attributes |
|
Member of | |
Contained by |
core: abbr author bibl biblScope choice corr date desc editor email emph expan foreign gloss head hi item label mentioned name note orig p pubPlace publisher q quote ref reg resp rs sic soCalled term textLang title unclear
msdescription: repository
namesdates: addName affiliation age birth death district education faith floruit forename genName gender langKnown occupation orgName persName placeName region residence roleName settlement sex surname
transcr: zone
|
May contain | |
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. |
Example | An American encoding of Gulliver's Travels which retains the British spelling but also provides a version regularized to American
spelling might be encoded as follows.
<p>Lastly, That, upon his solemn oath to observe all the above
articles, the said man-mountain shall have a daily allowance of
meat and drink sufficient for the support of <choice>
<sic>1724</sic>
<corr>1728</corr>
</choice> of our subjects,
with free access to our royal person, and other marks of our
<choice>
<orig>favour</orig>
<reg>favor</reg>
</choice>.</p>
|
Content model |
<content> <alternate minOccurs="2" maxOccurs="unbounded"> <classRef key="model.choicePart"/> <elementRef key="choice"/> </alternate> </content> ⚓ |
Schema Declaration |
element choice { att.global.attributes, ( model.choicePart | choice ), ( model.choicePart | choice ), ( model.choicePart | choice )* }⚓ |
<cit> (cited quotation) contains a quotation from some other document, together with a bibliographic reference to its source. In a dictionary it may contain an example text with at least one occurrence of the word form, used in the sense being described, or a translation of the headword, or an example. [3.3.3. Quotation 4.3.1. Grouped Texts 9.3.5.1. Examples] | |
Module | core |
Attributes |
|
Member of | |
Contained by |
core: abbr author biblScope cit corr desc editor email emph expan foreign gloss head hi item label mentioned name note orig p pubPlace publisher q quote ref reg rs sic soCalled term textLang title unclear
|
May contain | |
Example |
<cit>
<quote>and the breath of the whale is frequently attended with such an insupportable smell,
as to bring on disorder of the brain.</quote>
<bibl>Ulloa's South America</bibl>
</cit>
|
Example |
<entry>
<form>
<orth>horrifier</orth>
</form>
<cit type="translation" xml:lang="en">
<quote>to horrify</quote>
</cit>
<cit type="example">
<quote>elle était horrifiée par la dépense</quote>
<cit type="translation" xml:lang="en">
<quote>she was horrified at the expense.</quote>
</cit>
</cit>
</entry>
|
Example |
<cit type="example">
<quote xml:lang="mix">Ka'an yu tsa'a Pedro.</quote>
<media url="soundfiles-gen:S_speak_1s_on_behalf_of_Pedro_01_02_03_TS.wav"
mimeType="audio/wav"/>
<cit type="translation">
<quote xml:lang="en">I'm speaking on behalf of Pedro.</quote>
</cit>
<cit type="translation">
<quote xml:lang="es">Estoy hablando de parte de Pedro.</quote>
</cit>
</cit>
|
Content model |
<content> <alternate minOccurs="1" maxOccurs="unbounded"> <classRef key="model.biblLike"/> <classRef key="model.egLike"/> <classRef key="model.entryPart"/> <classRef key="model.global"/> <classRef key="model.graphicLike"/> <classRef key="model.ptrLike"/> <classRef key="model.attributable"/> <elementRef key="pc"/> <elementRef key="q"/> </alternate> </content> ⚓ |
Schema Declaration |
element cit { att.global.attributes, att.typed.attributes, ( model.biblLike | model.egLike | model.entryPart | model.global | model.graphicLike | model.ptrLike | model.attributable | pc | q )+ }⚓ |
<cl> (clause) represents a grammatical clause. [17.1. Linguistic Segment Categories] | |
Module | analysis |
Attributes |
|
Member of | |
Contained by | |
May contain |
core: abbr choice cit corr date email emph expan foreign gloss graphic hi mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
character data
|
Note |
The type attribute may be used to indicate the type of clause, taking values such as finite, nonfinite, declarative, interrogative, relative etc. as appropriate. |
Example |
<l>
<cl type="relative"
function="clause_modifier">Which frightened
both the heroes so,</cl>
</l>
<l>
<cl>They quite forgot their quarrel.</cl>
</l>
|
Content model |
<content> <macroRef key="macro.phraseSeq"/> </content> ⚓ |
Schema Declaration |
element cl { att.global.attributes, att.segLike.attributes, att.typed.attributes, att.notated.attributes, macro.phraseSeq }⚓ |
<classDecl> (classification declarations) contains one or more taxonomies defining any classificatory codes used elsewhere in the text. [2.3.7. The Classification Declaration 2.3. The Encoding Description] | |
Module | header |
Attributes |
|
Member of | |
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="unbounded"/> </content> ⚓ |
Schema Declaration |
element classDecl { att.global.attributes, taxonomy+ }⚓ |
<code> contains literal code from some formal language such as a programming language. [22.1.1. Phrase Level Terms] | |||||||
Module | tagdocs | ||||||
Attributes |
|
||||||
Member of | |||||||
Contained by | |||||||
May contain | Character data only | ||||||
Example |
<code lang="JAVA"> Size fCheckbox1Size = new Size();
fCheckbox1Size.Height = 500;
fCheckbox1Size.Width = 500;
xCheckbox1.setSize(fCheckbox1Size);
</code>
|
||||||
Content model |
<content> <textNode/> </content> ⚓ |
||||||
Schema Declaration |
element code { att.global.attributes, attribute lang { text }?, text }⚓ |
<corr> (correction) contains the correct form of a passage apparently erroneous in the copy text. [3.5.1. Apparent Errors] | |
Module | core |
Attributes |
|
Member of | |
Contained by | |
May contain |
core: abbr bibl choice cit corr date desc email emph expan foreign gloss graphic hi label list listBibl mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
header: idno
msdescription: msDesc
namesdates: addName affiliation district forename genName geo listEvent listOrg listPerson listPlace listRelation location orgName persName placeName population region roleName settlement state surname trait
character data
|
Example | If all that is desired is to call attention to the fact that the copy text has been
corrected, <corr> may be used alone:
I don't know,
Juan. It's so far in the past now — how <corr>can we</corr> prove
or disprove anyone's theories?
|
Example | It is also possible, using the <choice> and <sic> elements, to provide an uncorrected reading:
I don't know, Juan. It's so far in the past now —
how <choice>
<sic>we can</sic>
<corr>can we</corr>
</choice> prove or
disprove anyone's theories?
|
Content model |
<content> <macroRef key="macro.paraContent"/> </content> ⚓ |
Schema Declaration |
element corr { att.global.attributes, att.editLike.attributes, att.typed.attributes, macro.paraContent }⚓ |
<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] | |
Module | core |
Attributes |
|
Member of | |
Contained by | |
May contain |
core: abbr choice corr date email emph expan foreign gloss graphic hi mentioned name note orig ptr q ref reg sic soCalled term title unclear
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
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.global.attributes, att.canonical.attributes, att.datable.attributes, att.calendarSystem.attributes, att.editLike.attributes, att.dimensions.attributes, att.typed.attributes, ( text | model.gLike | model.phrase | model.global )* }⚓ |
<death> (death) contains information about a person's death, such as its date and place. [15.2.2. The Participant Description] | |||||||||||||||||||||
Module | namesdates | ||||||||||||||||||||
Attributes |
|
||||||||||||||||||||
Member of | |||||||||||||||||||||
Contained by |
namesdates: person
|
||||||||||||||||||||
May contain |
core: abbr choice cit corr date email emph expan foreign gloss graphic hi mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
character data
|
||||||||||||||||||||
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> <macroRef key="macro.phraseSeq"/> </content> ⚓ |
||||||||||||||||||||
Schema Declaration |
element death { att.datable.attributes, att.dimensions.attributes, att.editLike.attributes, att.global.attributes, att.naming.attributes, att.typed.attribute.subtype, attribute type { text }?, attribute calendar { list { + } }?, macro.phraseSeq }⚓ |
<desc> (description) contains a short description of the purpose, function, or use of its parent element, or when the parent is a documentation element, describes or defines the object being documented. [22.4.1. Description of Components] | |||||||||||
Module | core | ||||||||||
Attributes |
|
||||||||||
Member of | |||||||||||
Contained by |
core: corr desc emph graphic head hi item list listBibl note orig p q quote ref reg sic textLang title unclear
header: category change licence listPrefixDef taxonomy
linking: linkGrp
namesdates: event listEvent listOrg listPerson listPlace listRelation location occupation org place population relation state trait
transcr: surface
|
||||||||||
May contain |
core: abbr bibl choice cit date desc email emph expan foreign gloss hi label list listBibl mentioned name ptr q quote ref soCalled term title
figures: table
header: idno
msdescription: msDesc
namesdates: addName affiliation district forename genName geo listEvent listOrg listPerson listPlace listRelation location orgName persName placeName population region roleName settlement state surname trait
character data
|
||||||||||
Note |
When used in a specification element such as <elementSpec>, TEI convention requires that this be expressed as a finite clause, begining with an active verb. |
||||||||||
Example | Example of a <desc> element inside a documentation element.
<dataSpec module="tei"
ident="teidata.point">
<desc versionDate="2010-10-17"
xml:lang="en">defines the data type used to express a point in cartesian space.</desc>
<content>
<dataRef name="token"
restriction="(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)"/>
</content>
<!-- ... -->
</dataSpec>
|
||||||||||
Example | Example of a <desc> element in a non-documentation element.
<place xml:id="KERG2">
<placeName>Kerguelen Islands</placeName>
<!-- ... -->
<terrain>
<desc>antarctic tundra</desc>
</terrain>
<!-- ... -->
</place>
|
||||||||||
Schematron | A <desc> with a type of deprecationInfo should only occur when its parent element is being deprecated. Furthermore, it should
always occur in an element that is being deprecated when <desc> is a valid child of that element.
<sch:rule context="tei:desc[ @type eq 'deprecationInfo']">
<sch:assert test="../@validUntil">Information about a
deprecation should only be present in a specification element
that is being deprecated: that is, only an element that has a
@validUntil attribute should have a child <desc
type="deprecationInfo">.</sch:assert>
</sch:rule>
|
||||||||||
Content model |
<content> <macroRef key="macro.limitedContent"/> </content> ⚓ |
||||||||||
Schema Declaration |
element desc { att.global.attributes, att.translatable.attributes, att.typed.attribute.subtype, attribute type { text }?, macro.limitedContent }⚓ |
<district> (district) contains the name of any kind of subdivision of a settlement, such as a parish, ward, or other administrative or geographic unit. [13.2.3. Place Names] | |||||||||||
Module | namesdates | ||||||||||
Attributes |
|
||||||||||
Member of | |||||||||||
Contained by | |||||||||||
May contain |
core: abbr choice cit corr date email emph expan foreign gloss graphic hi mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
character data
|
||||||||||
Example |
<placeName>
<district type="ward">Jericho</district>
<settlement>Oxford</settlement>
</placeName>
|
||||||||||
Example |
<placeName>
<district type="area">South Side</district>
<settlement>Chicago</settlement>
</placeName>
|
||||||||||
Content model |
<content> <macroRef key="macro.phraseSeq"/> </content> ⚓ |
||||||||||
Schema Declaration |
element district { att.global.attributes, att.naming.attributes, att.typed.attributes, att.datable.attributes, attribute calendar { list { + } }?, macro.phraseSeq }⚓ |
<div> (text division) contains a subdivision of the front, body, or back of a text. [4.1. Divisions of the Body] | |
Module | textstructure |
Attributes |
|
Member of | |
Contained by | |
May contain | |
Example |
<body>
<div type="part">
<head>Fallacies of Authority</head>
<p>The subject of which is Authority in various shapes, and the object, to repress all
exercise of the reasoning faculty.</p>
<div n="1" type="chapter">
<head>The Nature of Authority</head>
<p>With reference to any proposed measures having for their object the greatest
happiness of the greatest number [...]</p>
<div n="1.1" type="section">
<head>Analysis of Authority</head>
<p>What on any given occasion is the legitimate weight or influence to be attached to
authority [...] </p>
</div>
<div n="1.2" type="section">
<head>Appeal to Authority, in What Cases Fallacious.</head>
<p>Reference to authority is open to the charge of fallacy when [...] </p>
</div>
</div>
</div>
</body>
|
Schematron |
<sch:report test="(ancestor::tei:l or ancestor::tei:lg) and not(ancestor::tei:floatingText)">
Abstract model violation: Lines may not contain higher-level structural elements such
as div, unless div is a descendant of floatingText.
</sch:report>
|
Schematron |
<sch:report test="(ancestor::tei:p or ancestor::tei:ab) and not(ancestor::tei:floatingText)">
Abstract model violation: p and ab may not contain higher-level structural elements
such as div, unless div is a descendant of floatingText.
</sch:report>
|
Content model |
<content> <sequence> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.divTop"/> <classRef key="model.global"/> </alternate> <sequence minOccurs="0"> <alternate> <sequence minOccurs="1" maxOccurs="unbounded"> <alternate> <classRef key="model.divLike"/> <classRef key="model.divGenLike"/> </alternate> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> <sequence> <sequence minOccurs="1" maxOccurs="unbounded"> <alternate minOccurs="1" maxOccurs="1"> <elementRef key="schemaSpec"/> <classRef key="model.common"/> </alternate> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> <sequence minOccurs="0" maxOccurs="unbounded"> <alternate> <classRef key="model.divLike"/> <classRef key="model.divGenLike"/> </alternate> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> </sequence> </alternate> <sequence minOccurs="0" maxOccurs="unbounded"> <classRef key="model.divBottom"/> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> </sequence> </sequence> </content> ⚓ |
Schema Declaration |
element div { att.global.attributes, att.divLike.attributes, att.typed.attributes, att.declaring.attributes, att.written.attributes, ( ( model.divTop | model.global )*, ( ( ( ( ( ( model.divLike | model.divGenLike ), model.global* )+ ) | ( ( ( ( schemaSpec | model.common ), model.global* )+ ), ( ( ( model.divLike | model.divGenLike ), model.global* )* ) ) ), ( ( model.divBottom, model.global* )* ) )? ) ) }⚓ |
<divGen> (automatically generated text division) indicates the location at which a textual division generated automatically by a text-processing application is to appear. [3.9.2. Index Entries] | |||||||||||
Module | core | ||||||||||
Attributes |
|
||||||||||
Member of | |||||||||||
Contained by | |||||||||||
May contain |
core: head
|
||||||||||
Note |
This element is intended primarily for use in document production or manipulation, rather than in the transcription of pre-existing materials; it makes it easier to specify the location of indices, tables of contents, etc., to be generated by text preparation or word processing software. |
||||||||||
Example | One use for this element is to allow document preparation software to generate an
index and insert it in the appropriate place in the output. The example below assumes
that the indexName attribute on <index> elements in the text has been used to specify index entries for the two generated
indexes, named NAMES and THINGS:
<back>
<div1 type="backmat">
<head>Bibliography</head>
<!-- ... -->
</div1>
<div1 type="backmat">
<head>Indices</head>
<divGen n="Index Nominum" type="NAMES"/>
<divGen n="Index Rerum" type="THINGS"/>
</div1>
</back>
|
||||||||||
Example | Another use for <divGen> is to specify the location of an automatically produced table of contents:
<front>
<!--<titlePage>...</titlePage>-->
<divGen type="toc"/>
<div>
<head>Preface</head>
<p> ... </p>
</div>
</front>
|
||||||||||
Content model |
<content> <classRef key="model.headLike" minOccurs="0" maxOccurs="unbounded"/> </content> ⚓ |
||||||||||
Schema Declaration |
element divGen { att.global.attributes, att.typed.attribute.subtype, attribute type { text }?, model.headLike* }⚓ |
<edition> (edition) describes the particularities of one edition of a text. [2.2.2. The Edition Statement] | |
Module | header |
Attributes |
|
Member of | |
Contained by |
core: bibl
header: editionStmt
|
May contain |
core: abbr choice cit corr date email emph expan foreign gloss graphic hi mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
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 }⚓ |
<editionStmt> (edition statement) groups information relating to one edition of a text. [2.2.2. The Edition Statement 2.2. The File Description] | |
Module | header |
Attributes |
|
Contained by |
header: fileDesc
|
May contain | |
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> <alternate> <classRef key="model.pLike" minOccurs="1" maxOccurs="unbounded"/> <sequence> <elementRef key="edition"/> <classRef key="model.respLike" minOccurs="0" maxOccurs="unbounded"/> </sequence> </alternate> </content> ⚓ |
Schema Declaration |
element editionStmt { att.global.attributes, ( model.pLike+ | ( edition, model.respLike* ) ) }⚓ |
<editor> contains a secondary statement of responsibility for a bibliographic item, for example the name of an individual, institution or organization, (or of several such) acting as editor, compiler, translator, etc. [3.12.2.2. Titles, Authors, and Editors] | |||||||||||
Module | core | ||||||||||
Attributes |
|
||||||||||
Member of | |||||||||||
Contained by |
header: editionStmt titleStmt
|
||||||||||
May contain |
core: abbr choice cit corr date email emph expan foreign gloss graphic hi mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
character data
|
||||||||||
Note |
A consistent format should be adopted. Particularly where cataloguing is likely to be based on the content of the header, it is advisable to use generally recognized authority lists for the exact form of personal names. |
||||||||||
Example |
<editor role="Technical_Editor">Ron Van den Branden</editor>
<editor role="Editor-in-Chief">John Walsh</editor>
<editor role="Managing_Editor">Anne Baillot</editor>
|
||||||||||
Content model |
<content> <macroRef key="macro.phraseSeq"/> </content> ⚓ |
||||||||||
Schema Declaration |
element editor { att.global.attributes, att.naming.attributes, att.datable.attributes, attribute calendar { list { + } }?, macro.phraseSeq }⚓ |
<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] | |
Module | header |
Attributes |
|
Member of | |
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 &cdq;.</p>
</quotation>
</editorialDecl>
|
Content model |
<content> <alternate minOccurs="1" maxOccurs="unbounded"> <classRef key="model.pLike"/> <classRef key="model.editorialDeclPart"/> </alternate> </content> ⚓ |
Schema Declaration |
element editorialDecl { att.global.attributes, att.declarable.attributes, ( model.pLike | model.editorialDeclPart )+ }⚓ |
<education> (education) contains a description of the educational experience of a person. [15.2.2. The Participant Description] | |||||||||||||||||||
Module | namesdates | ||||||||||||||||||
Attributes |
|
||||||||||||||||||
Member of | |||||||||||||||||||
Contained by |
namesdates: person
|
||||||||||||||||||
May contain |
core: abbr choice cit corr date email emph expan foreign gloss graphic hi mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
character data
|
||||||||||||||||||
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> <macroRef key="macro.phraseSeq"/> </content> ⚓ |
||||||||||||||||||
Schema Declaration |
element education { att.global.attributes, att.editLike.attributes, att.datable.attributes, att.naming.attributes, att.typed.attribute.subtype, attribute type { text }?, attribute calendar { list { + } }?, macro.phraseSeq }⚓ |
<email> (electronic mail address) contains an email address identifying a location to which email messages can be delivered. [3.6.2. Addresses] | |
Module | core |
Attributes |
|
Member of | |
Contained by | |
May contain |
core: abbr choice cit corr date email emph expan foreign gloss graphic hi mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
character data
|
Note |
The format of a modern Internet email address is defined in RFC 2822 |
Example |
<email>membership@tei-c.org</email>
|
Content model |
<content> <macroRef key="macro.phraseSeq"/> </content> ⚓ |
Schema Declaration |
element email { att.global.attributes, macro.phraseSeq }⚓ |
<emph> (emphasized) marks words or phrases which are stressed or emphasized for linguistic or rhetorical effect. [3.3.2.2. Emphatic Words and Phrases 3.3.2. Emphasis, Foreign Words, and Unusual Language] | |
Module | core |
Attributes |
|
Member of | |
Contained by | |
May contain |
core: abbr bibl choice cit corr date desc email emph expan foreign gloss graphic hi label list listBibl mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
header: idno
msdescription: msDesc
namesdates: addName affiliation district forename genName geo listEvent listOrg listPerson listPlace listRelation location orgName persName placeName population region roleName settlement state surname trait
character data
|
Example |
You took the car and did <emph>what</emph>?!!
|
Example |
<q>What it all comes to is this,</q> he said.
<q>
<emph>What
does Christopher Robin do in the morning nowadays?</emph>
</q>
|
Content model |
<content> <macroRef key="macro.paraContent"/> </content> ⚓ |
Schema Declaration |
element emph { att.global.attributes, macro.paraContent }⚓ |
<encodingDesc> (encoding description) documents the relationship between an electronic text and the source or sources from which it was derived. [2.3. The Encoding Description 2.1.1. The TEI Header and Its Components] | |
Module | header |
Attributes |
|
Member of | |
Contained by |
header: teiHeader
|
May contain |
core: p
|
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> <alternate minOccurs="1" maxOccurs="unbounded"> <classRef key="model.encodingDescPart"/> <classRef key="model.pLike"/> </alternate> </content> ⚓ |
Schema Declaration |
element encodingDesc { att.global.attributes, ( model.encodingDescPart | model.pLike )+ }⚓ |
<event> (event) contains data relating to anything of significance that happens in time. [13.3.1. Basic Principles] | |||||||||||||||||||||
Module | namesdates | ||||||||||||||||||||
Attributes |
|
||||||||||||||||||||
Member of | |||||||||||||||||||||
Contained by | |||||||||||||||||||||
May contain | |||||||||||||||||||||
Example |
<listEvent>
<event when="1618-05-23"
xml:id="SecondDefPrague" where="#Prague">
<eventName>1618 Defenestration of Prague</eventName>
<idno>https://www.wikidata.org/wiki/Q13365740</idno>
<listPerson type="defenstrated">
<person>
<persName>Jaroslav Bořita z Martinic</persName>
<idno type="GND">https://d-nb.info/gnd/116810998</idno>
</person>
<person>
<persName>Vilém Slavata z Chlumu a Košumberka</persName>
<idno type="GND">https://d-nb.info/gnd/1018376615</idno>
</person>
<person>
<persName>Filip Fabricius</persName>
<idno type="GND">https://d-nb.info/gnd/133946118</idno>
</person>
</listPerson>
<place xml:id="Prague">
<placeName>Prague</placeName>
</place>
</event>
<event from="1618" to="1648"
xml:id="ThirtyYearsWar">
<eventName>Thirty Years’ War</eventName>
<idno>https://www.wikidata.org/wiki/Q2487</idno>
<event when="1643-03-19"
xml:id="BattleofRocroi" where="#Rocroi">
<eventName>Battle of Rocroi</eventName>
<idno type="Wikidata">https://www.wikidata.org/wiki/Q728480</idno>
<idno type="GND">https://d-nb.info/gnd/4202901-6</idno>
<place xml:id="Rocroi">
<placeName>Rocroi</placeName>
<location>
<geo decls="#WGS">49.926111 4.522222</geo>
</location>
</place>
</event>
</event>
</listEvent>
|
||||||||||||||||||||
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:*[@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>
|
||||||||||||||||||||
Content model |
<content> <sequence minOccurs="1" maxOccurs="1"> <elementRef key="idno" minOccurs="0" maxOccurs="unbounded"/> <classRef key="model.headLike" minOccurs="0" maxOccurs="unbounded"/> <alternate minOccurs="1" maxOccurs="1"> <classRef key="model.pLike" minOccurs="1" maxOccurs="unbounded"/> <classRef key="model.labelLike" minOccurs="1" maxOccurs="unbounded"/> </alternate> <alternate minOccurs="0" maxOccurs="unbounded"> <elementRef key="listPerson"/> <classRef key="model.noteLike"/> <classRef key="model.biblLike"/> <elementRef key="linkGrp"/> <elementRef key="link"/> <elementRef key="idno"/> <elementRef key="ptr"/> </alternate> </sequence> </content> ⚓ |
||||||||||||||||||||
Schema Declaration |
element event { att.global.attributes, att.datable.w3c.attribute.when, att.datable.w3c.attribute.notBefore, att.datable.w3c.attribute.notAfter, att.datable.w3c.attribute.from, att.datable.w3c.attribute.to, att.datable.iso.attribute.when-iso, att.datable.iso.attribute.notBefore-iso, att.datable.iso.attribute.notAfter-iso, att.datable.iso.attribute.from-iso, att.datable.iso.attribute.to-iso, 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.custom.attribute.datingMethod, att.editLike.attributes, att.locatable.attributes, att.naming.attributes, att.sortable.attributes, att.typed.attributes, attribute period { list { ( "tm:tm_Easter" | "tm:tm_Hilary" | "tm:tm_Michaelmas" | "tm:tm_Trinity" )+ } }?, attribute calendar { list { + } }?, ( idno*, model.headLike*, ( model.pLike+ | model.labelLike+ ), ( listPerson | model.noteLike | model.biblLike | linkGrp | link | idno | ptr )* ) }⚓ |
<expan> (expansion) contains the expansion of an abbreviation. [3.6.5. Abbreviations and Their Expansions] | |
Module | core |
Attributes |
|
Member of | |
Contained by | |
May contain |
core: abbr choice cit corr date email emph expan foreign gloss graphic hi mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
character data
|
Note |
The content of this element should be the expanded abbreviation, usually (but not always) a complete word or phrase. The <ex> element provided by the transcr module may be used to mark up sequences of letters supplied within such an expansion. If abbreviations are expanded silently, this practice should be documented in the <editorialDecl>, either with a <normalization> element or a <p>. |
Example |
The address is Southmoor
<choice>
<expan>Road</expan>
<abbr>Rd</abbr>
</choice>
|
Example |
<choice xml:lang="la">
<abbr>Imp</abbr>
<expan>Imp<ex>erator</ex>
</expan>
</choice>
|
Content model |
<content> <macroRef key="macro.phraseSeq"/> </content> ⚓ |
Schema Declaration |
element expan { att.global.attributes, att.editLike.attributes, macro.phraseSeq }⚓ |
<faith> (faith) specifies the faith, religion, or belief set of a person. [13.3.2.1. Personal Characteristics] | |||||||||||||||||||
Module | namesdates | ||||||||||||||||||
Attributes |
|
||||||||||||||||||
Member of | |||||||||||||||||||
Contained by |
namesdates: person
|
||||||||||||||||||
May contain |
core: abbr choice cit corr date email emph expan foreign gloss graphic hi mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
character data
|
||||||||||||||||||
Example |
<faith>protestant</faith>
|
||||||||||||||||||
Example |
<faith ref="http://dbpedia.org/page/Manichaeism">Manichaeism</faith>
|
||||||||||||||||||
Content model |
<content> <macroRef key="macro.phraseSeq"/> </content> ⚓ |
||||||||||||||||||
Schema Declaration |
element faith { att.global.attributes, att.editLike.attributes, att.datable.attributes, att.canonical.attributes, att.typed.attribute.subtype, attribute type { text }?, attribute calendar { list { + } }?, macro.phraseSeq }⚓ |
<figDesc> (description of figure) contains a brief prose description of the appearance or content of a graphic figure, for use when documenting an image without displaying it. [14.4. Specific Elements for Graphic Images] | |
Module | figures |
Attributes |
|
Contained by |
figures: figure
|
May contain |
core: abbr bibl choice cit date desc email emph expan foreign gloss hi label list listBibl mentioned name ptr q quote ref soCalled term title
figures: table
header: idno
msdescription: msDesc
namesdates: addName affiliation district forename genName geo listEvent listOrg listPerson listPlace listRelation location orgName persName placeName population region roleName settlement state surname trait
character data
|
Note |
This element is intended for use as an alternative to the content of its parent <figure> element ; for example, to display when the image is required but the equipment in use cannot display graphic images. It may also be used for indexing or documentary purposes. |
Example |
<figure>
<graphic url="emblem1.png"/>
<head>Emblemi d'Amore</head>
<figDesc>A pair of naked winged cupids, each holding a
flaming torch, in a rural setting.</figDesc>
</figure>
|
Content model |
<content> <macroRef key="macro.limitedContent"/> </content> ⚓ |
Schema Declaration |
element figDesc { att.global.attributes, macro.limitedContent }⚓ |
<figure> (figure) groups elements representing or containing graphic information such as an illustration, formula, or figure. [14.4. Specific Elements for Graphic Images] | |
Module | figures |
Attributes |
|
Member of | |
Contained by |
core: abbr author bibl biblScope cit corr date editor email emph expan foreign gloss head hi item label list mentioned name note orig p pubPlace publisher q quote ref reg resp rs series sic soCalled term textLang title unclear
msdescription: repository
|
May contain | |
Example |
<figure>
<head>The View from the Bridge</head>
<figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a
series of buoys strung out between them.</figDesc>
<graphic url="http://www.example.org/fig1.png"
scale="0.5"/>
</figure>
|
Content model |
<content> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.headLike"/> <classRef key="model.common"/> <elementRef key="figDesc"/> <classRef key="model.graphicLike"/> <classRef key="model.global"/> <classRef key="model.divBottom"/> </alternate> </content> ⚓ |
Schema Declaration |
element figure { att.global.attributes, att.placement.attributes, att.typed.attributes, att.written.attributes, ( model.headLike | model.common | figDesc | model.graphicLike | model.global | model.divBottom )* }⚓ |
<fileDesc> (file description) contains a full bibliographic description of an electronic file. [2.2. The File Description 2.1.1. The TEI Header and Its Components] | |
Module | header |
Attributes |
|
Contained by |
header: teiHeader
|
May contain | |
Note |
The major source of information for those seeking to create a catalogue entry or bibliographic citation for an electronic file. As such, it provides a title and statements of responsibility together with details of the publication or distribution of the file, of any series to which it belongs, and detailed bibliographic notes for matters not addressed elsewhere in the header. It also contains a full bibliographic description for the source or sources from which the electronic text was derived. |
Example |
<fileDesc>
<titleStmt>
<title>The shortest possible TEI document</title>
</titleStmt>
<publicationStmt>
<p>Distributed as part of TEI P5</p>
</publicationStmt>
<sourceDesc>
<p>No print source exists: this is an original digital text</p>
</sourceDesc>
</fileDesc>
|
Content model |
<content> <sequence> <sequence> <elementRef key="titleStmt"/> <elementRef key="editionStmt" minOccurs="0"/> <elementRef key="extent" minOccurs="0"/> <elementRef key="publicationStmt"/> <elementRef key="seriesStmt" minOccurs="0" maxOccurs="unbounded"/> <elementRef key="notesStmt" minOccurs="0"/> </sequence> <elementRef key="sourceDesc" minOccurs="1" maxOccurs="unbounded"/> </sequence> </content> ⚓ |
Schema Declaration |
element fileDesc { att.global.attributes, ( ( titleStmt, editionStmt?, extent?, publicationStmt, seriesStmt*, notesStmt? ), sourceDesc+ ) }⚓ |
<floruit> (floruit) contains information about a person's period of activity. [13.3.2.1. Personal Characteristics] | |||||||||||
Module | namesdates | ||||||||||
Attributes |
|
||||||||||
Member of | |||||||||||
Contained by |
namesdates: person
|
||||||||||
May contain |
core: abbr choice cit corr date email emph expan foreign gloss graphic hi mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
character data
|
||||||||||
Example |
<floruit notBefore="1066" notAfter="1100"/>
|
||||||||||
Content model |
<content> <macroRef key="macro.phraseSeq"/> </content> ⚓ |
||||||||||
Schema Declaration |
element floruit { att.global.attributes, att.datable.attributes, att.dimensions.attributes, att.editLike.attributes, attribute calendar { list { + } }?, macro.phraseSeq }⚓ |
<foreign> (foreign) identifies a word or phrase as belonging to some language other than that of the surrounding text. [3.3.2.1. Foreign Words or Expressions] | |
Module | core |
Attributes |
|
Member of | |
Contained by | |
May contain |
core: abbr choice cit corr date email emph expan foreign gloss graphic hi mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
character data
|
Note |
The global xml:lang attribute should be supplied for this element to identify the language of the word or phrase marked. As elsewhere, its value should be a language tag as defined in 6.1. Language Identification. This element is intended for use only where no other element is available to mark the phrase or words concerned. The global xml:lang attribute should be used in preference to this element where it is intended to mark the language of the whole of some text element. The <distinct> element may be used to identify phrases belonging to sublanguages or registers not generally regarded as true languages. |
Example |
This is
heathen Greek to you still? Your <foreign xml:lang="la">lapis
philosophicus</foreign>?
|
Content model |
<content> <macroRef key="macro.phraseSeq"/> </content> ⚓ |
Schema Declaration |
element foreign { att.global.attributes, macro.phraseSeq }⚓ |
<forename> (forename) contains a forename, given or baptismal name. [13.2.1. Personal Names] | |
Module | namesdates |
Attributes |
|
Member of | |
Contained by | |
May contain |
core: abbr choice cit corr date email emph expan foreign gloss graphic hi mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
character data
|
Example |
<persName>
<roleName>Ex-President</roleName>
<forename>George</forename>
<surname>Bush</surname>
</persName>
|
Content model |
<content> <macroRef key="macro.phraseSeq"/> </content> ⚓ |
Schema Declaration |
element forename { att.global.attributes, att.personal.attributes, att.typed.attributes, macro.phraseSeq }⚓ |
<front> (front matter) contains any prefatory matter (headers, abstracts, title page, prefaces, dedications, etc.) found at the start of a document, before the main body. [4.6. Title Pages 4. Default Text Structure] | |
Module | textstructure |
Attributes |
|
Contained by |
textstructure: text
|
May contain | |
Note |
Because cultural conventions differ as to which elements are grouped as front matter and which as back matter, the content models for the <front> and <back> elements are identical. |
Example |
<front>
<epigraph>
<quote>Nam Sibyllam quidem Cumis ego ipse oculis meis vidi in ampulla
pendere, et cum illi pueri dicerent: <q xml:lang="grc">Σίβυλλα τί
θέλεις</q>; respondebat illa: <q xml:lang="grc">ὰποθανεῖν θέλω.</q>
</quote>
</epigraph>
<div type="dedication">
<p>For Ezra Pound <q xml:lang="it">il miglior fabbro.</q>
</p>
</div>
</front>
|
Example |
<front>
<div type="dedication">
<p>To our three selves</p>
</div>
<div type="preface">
<head>Author's Note</head>
<p>All the characters in this book are purely imaginary, and if the
author has used names that may suggest a reference to living persons
she has done so inadvertently. ...</p>
</div>
</front>
|
Example |
<front>
<div type="abstract">
<div>
<head> BACKGROUND:</head>
<p>Food insecurity can put children at greater risk of obesity because
of altered food choices and nonuniform consumption patterns.</p>
</div>
<div>
<head> OBJECTIVE:</head>
<p>We examined the association between obesity and both child-level
food insecurity and personal food insecurity in US children.</p>
</div>
<div>
<head> DESIGN:</head>
<p>Data from 9,701 participants in the National Health and Nutrition
Examination Survey, 2001-2010, aged 2 to 11 years were analyzed.
Child-level food insecurity was assessed with the US Department of
Agriculture's Food Security Survey Module based on eight
child-specific questions. Personal food insecurity was assessed with
five additional questions. Obesity was defined, using physical
measurements, as body mass index (calculated as kg/m2) greater than
or equal to the age- and sex-specific 95th percentile of the Centers
for Disease Control and Prevention growth charts. Logistic
regressions adjusted for sex, race/ethnic group, poverty level, and
survey year were conducted to describe associations between obesity
and food insecurity.</p>
</div>
<div>
<head> RESULTS:</head>
<p>Obesity was significantly associated with personal food insecurity
for children aged 6 to 11 years (odds ratio=1.81; 95% CI 1.33 to
2.48), but not in children aged 2 to 5 years (odds ratio=0.88; 95%
CI 0.51 to 1.51). Child-level food insecurity was not associated
with obesity among 2- to 5-year-olds or 6- to 11-year-olds.</p>
</div>
<div>
<head> CONCLUSIONS:</head>
<p>Personal food insecurity is associated with an increased risk of
obesity only in children aged 6 to 11 years. Personal
food-insecurity measures may give different results than aggregate
food-insecurity measures in children.</p>
</div>
</div>
</front>
|
Content model |
<content> <sequence> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.frontPart"/> <classRef key="model.pLike"/> <classRef key="model.pLike.front"/> <classRef key="model.global"/> </alternate> <sequence minOccurs="0"> <alternate> <sequence> <classRef key="model.div1Like"/> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.div1Like"/> <classRef key="model.frontPart"/> <classRef key="model.global"/> </alternate> </sequence> <sequence> <classRef key="model.divLike"/> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.divLike"/> <classRef key="model.frontPart"/> <classRef key="model.global"/> </alternate> </sequence> </alternate> <sequence minOccurs="0"> <classRef key="model.divBottom"/> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.divBottom"/> <classRef key="model.global"/> </alternate> </sequence> </sequence> </sequence> </content> ⚓ |
Schema Declaration |
element front { att.global.attributes, att.declaring.attributes, ( ( model.frontPart | model.pLike | model.pLike.front | model.global )*, ( ( ( ( model.div1Like, ( model.div1Like | model.frontPart | model.global )* ) | ( model.divLike, ( model.divLike | model.frontPart | model.global )* ) ), ( ( model.divBottom, ( model.divBottom | model.global )* )? ) )? ) ) }⚓ |
<funder> (funding body) specifies the name of an individual, institution, or organization responsible for the funding of a project or text. [2.2.1. The Title Statement] | |||||||||||
Module | header | ||||||||||
Attributes |
|
||||||||||
Member of | |||||||||||
Contained by |
core: bibl
header: editionStmt titleStmt
|
||||||||||
May contain |
core: abbr choice date email emph expan foreign gloss hi mentioned name note ptr q ref soCalled term title
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
character data
|
||||||||||
Note |
Funders provide financial support for a project; they are distinct from sponsors (see element <sponsor>), who provide intellectual support and authority. |
||||||||||
Example |
<funder>The National Endowment for the Humanities, an independent federal agency</funder>
<funder>Directorate General XIII of the Commission of the European Communities</funder>
<funder>The Andrew W. Mellon Foundation</funder>
<funder>The Social Sciences and Humanities Research Council of Canada</funder>
|
||||||||||
Content model |
<content> <macroRef key="macro.phraseSeq.limited"/> </content> ⚓ |
||||||||||
Schema Declaration |
element funder { att.global.attributes, att.canonical.attributes, att.datable.attributes, attribute calendar { list { + } }?, macro.phraseSeq.limited }⚓ |
<genName> (generational name component) contains a name component used to distinguish otherwise similar names on the basis of the relative ages or generations of the persons named. [13.2.1. Personal Names] | |
Module | namesdates |
Attributes |
|
Member of | |
Contained by | |
May contain |
core: abbr choice cit corr date email emph expan foreign gloss graphic hi mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
character data
|
Example |
<persName>
<forename>Charles</forename>
<genName>II</genName>
</persName>
|
Example |
<persName>
<surname>Pitt</surname>
<genName>the Younger</genName>
</persName>
|
Content model |
<content> <macroRef key="macro.phraseSeq"/> </content> ⚓ |
Schema Declaration |
element genName { att.global.attributes, att.personal.attributes, att.typed.attributes, macro.phraseSeq }⚓ |
<gender> (gender) specifies the gender identity of a person, persona, or character. [13.3.2.1. Personal Characteristics] | |||||||||||||||||||
Module | namesdates | ||||||||||||||||||
Attributes |
|
||||||||||||||||||
Member of | |||||||||||||||||||
Contained by |
namesdates: person
|
||||||||||||||||||
May contain |
core: abbr choice cit corr date email emph expan foreign gloss graphic hi mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
character data
|
||||||||||||||||||
Note |
As with other culturally-constructed traits such as age and sex, the way in which this concept is described in different cultural contexts varies. The normalizing attributes are provided only as an optional means of simplifying that variety for purposes of interoperability or project-internal taxonomies for consistency, and should not be used where that is inappropriate or unhelpful. The content of the element may be used to describe the intended concept in more detail. |
||||||||||||||||||
Example |
<gender value="W">woman</gender>
|
||||||||||||||||||
Example |
<gender value="NB">non-binary</gender>
|
||||||||||||||||||
Content model |
<content> <macroRef key="macro.phraseSeq"/> </content> ⚓ |
||||||||||||||||||
Schema Declaration |
element gender { att.global.attributes, att.editLike.attributes, att.datable.attributes, att.typed.attributes, attribute calendar { list { + } }?, attribute value { list { + } }?, macro.phraseSeq }⚓ |
<geo> (geographical coordinates) contains any expression of a set of geographic coordinates, representing a point, line, or area on the surface of the earth in some notation. [13.3.4.1. Varieties of Location] | |
Module | namesdates |
Attributes |
|
Member of | |
Contained by | |
May contain | Character data only |
Note |
Uses of <geo> can be associated with a coordinate system, defined by a <geoDecl> element supplied in the TEI header, using the decls attribute. If no such link is made, the assumption is that the content of each <geo> element will be a pair of numbers separated by whitespace, to be interpreted as latitude followed by longitude according to the World Geodetic System. |
Example |
<geoDecl xml:id="WGS" datum="WGS84">World Geodetic System</geoDecl>
<geoDecl xml:id="OS" datum="OSGB36">Ordnance Survey</geoDecl>
<!-- ... -->
<location>
<desc>A tombstone plus six lines of
Anglo-Saxon text, built into the west tower (on the south side
of the archway, at 8 ft. above the ground) of the
Church of St. Mary-le-Wigford in Lincoln.</desc>
<geo decls="#WGS">53.226658 -0.541254</geo>
<geo decls="#OS">SK 97481 70947</geo>
</location>
|
Example |
<geo>41.687142 -74.870109</geo>
|
Content model |
<content> <textNode/> </content> ⚓ |
Schema Declaration |
element geo { att.global.attributes, att.declaring.attributes, text }⚓ |
<gloss> (gloss) identifies a phrase or word used to provide a gloss or definition for some other word or phrase. [3.4.1. Terms and Glosses 22.4.1. Description of Components] | |
Module | core |
Attributes |
|
Member of | |
Contained by | |
May contain |
core: abbr choice cit corr date email emph expan foreign gloss graphic hi mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
character data
|
Note |
The target and cRef attributes are mutually exclusive. |
Example |
We may define <term xml:id="tdpv" rend="sc">discoursal point of view</term> as
<gloss target="#tdpv">the relationship, expressed
through discourse structure, between the implied author or some other addresser, and
the
fiction.</gloss>
|
Content model |
<content> <macroRef key="macro.phraseSeq"/> </content> ⚓ |
Schema Declaration |
element gloss { att.global.attributes, att.declaring.attributes, att.translatable.attributes, att.typed.attributes, att.pointing.attributes, att.cReferencing.attributes, macro.phraseSeq }⚓ |
<graphic> (graphic) indicates the location of a graphic or illustration, either forming part of a text, or providing an image of it. [3.10. Graphics and Other Non-textual Components 11.1. Digital Facsimiles] | |
Module | core |
Attributes |
|
Member of | |
Contained by |
core: abbr author biblScope cit corr date editor email emph expan foreign gloss head hi item label mentioned name note orig p pubPlace publisher q quote ref reg rs sic soCalled term textLang title unclear
|
May contain |
core: desc
|
Note |
The mimeType attribute should be used to supply the MIME media type of the image specified by the url attribute. Within the body of a text, a <graphic> element indicates the presence of a graphic component in the source itself. Within the context of a <facsimile> or <sourceDoc> element, however, a <graphic> element provides an additional digital representation of some part of the source being encoded. |
Example |
<figure>
<graphic url="fig1.png"/>
<head>Figure One: The View from the Bridge</head>
<figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a
series of buoys strung out between them.</figDesc>
</figure>
|
Example |
<facsimile>
<surfaceGrp n="leaf1">
<surface>
<graphic url="page1.png"/>
</surface>
<surface>
<graphic url="page2-highRes.png"/>
<graphic url="page2-lowRes.png"/>
</surface>
</surfaceGrp>
</facsimile>
|
Example |
<facsimile>
<surfaceGrp n="leaf1" xml:id="spi001">
<surface xml:id="spi001r">
<graphic type="normal"
subtype="thumbnail" url="spi/thumb/001r.jpg"/>
<graphic type="normal" subtype="low-res"
url="spi/normal/lowRes/001r.jpg"/>
<graphic type="normal"
subtype="high-res" url="spi/normal/highRes/001r.jpg"/>
<graphic type="high-contrast"
subtype="low-res" url="spi/contrast/lowRes/001r.jpg"/>
<graphic type="high-contrast"
subtype="high-res" url="spi/contrast/highRes/001r.jpg"/>
</surface>
<surface xml:id="spi001v">
<graphic type="normal"
subtype="thumbnail" url="spi/thumb/001v.jpg"/>
<graphic type="normal" subtype="low-res"
url="spi/normal/lowRes/001v.jpg"/>
<graphic type="normal"
subtype="high-res" url="spi/normal/highRes/001v.jpg"/>
<graphic type="high-contrast"
subtype="low-res" url="spi/contrast/lowRes/001v.jpg"/>
<graphic type="high-contrast"
subtype="high-res" url="spi/contrast/highRes/001v.jpg"/>
<zone xml:id="spi001v_detail01">
<graphic type="normal"
subtype="thumbnail" url="spi/thumb/001v-detail01.jpg"/>
<graphic type="normal"
subtype="low-res"
url="spi/normal/lowRes/001v-detail01.jpg"/>
<graphic type="normal"
subtype="high-res"
url="spi/normal/highRes/001v-detail01.jpg"/>
<graphic type="high-contrast"
subtype="low-res"
url="spi/contrast/lowRes/001v-detail01.jpg"/>
<graphic type="high-contrast"
subtype="high-res"
url="spi/contrast/highRes/001v-detail01.jpg"/>
</zone>
</surface>
</surfaceGrp>
</facsimile>
|
Content model |
<content> <classRef key="model.descLike" minOccurs="0" maxOccurs="unbounded"/> </content> ⚓ |
Schema Declaration |
element graphic { att.global.attributes, att.media.attributes, att.resourced.attributes, att.declaring.attributes, att.typed.attributes, model.descLike* }⚓ |
<head> (heading) contains any type of heading, for example the title of a section, or the heading of a list, glossary, manuscript description, etc. [4.2.1. Headings and Trailers] | |
Module | core |
Attributes |
|
Member of | |
Contained by | |
May contain |
core: abbr bibl choice cit corr date desc email emph expan foreign gloss graphic hi label list listBibl mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
header: idno
msdescription: msDesc
namesdates: addName affiliation district forename genName geo listEvent listOrg listPerson listPlace listRelation location orgName persName placeName population region roleName settlement state surname trait
character data
|
Note |
The <head> element is used for headings at all levels; software which treats (e.g.) chapter headings, section headings, and list titles differently must determine the proper processing of a <head> element based on its structural position. A <head> occurring as the first element of a list is the title of that list; one occurring as the first element of a <div1> is the title of that chapter or section. |
Example | The most common use for the <head> element is to mark the headings of sections. In older writings, the headings or incipits may be rather longer than usual in modern works. If a section has an explicit ending
as well as a heading, it should be marked as a <trailer>, as in this example:
<div1 n="I" type="book">
<head>In the name of Christ here begins the first book of the ecclesiastical history of
Georgius Florentinus, known as Gregory, Bishop of Tours.</head>
<div2 type="section">
<head>In the name of Christ here begins Book I of the history.</head>
<p>Proposing as I do ...</p>
<p>From the Passion of our Lord until the death of Saint Martin four hundred and twelve
years passed.</p>
<trailer>Here ends the first Book, which covers five thousand, five hundred and ninety-six
years from the beginning of the world down to the death of Saint Martin.</trailer>
</div2>
</div1>
|
Example | When headings are not inline with the running text (see e.g. the heading "Secunda conclusio") they might however be encoded as if. The actual placement in the source document
can be captured with the place attribute.
<div type="subsection">
<head place="margin">Secunda conclusio</head>
<p>
<lb n="1251"/>
<hi rend="large">Potencia: habitus: et actus: recipiunt speciem ab obiectis<supplied>.</supplied>
</hi>
<lb n="1252"/>Probatur sic. Omne importans necessariam habitudinem ad proprium
[...]
</p>
</div>
|
Example | The <head> element is also used to mark headings of other units, such as lists:
With a few exceptions, connectives are equally
useful in all kinds of discourse: description, narration, exposition, argument. <list rend="bulleted">
<head>Connectives</head>
<item>above</item>
<item>accordingly</item>
<item>across from</item>
<item>adjacent to</item>
<item>again</item>
<item>
<!-- ... -->
</item>
</list>
|
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 )* }⚓ |
<ident> (identifier) contains an identifier or name for an object of some kind in a formal language. <ident> is used for tokens such as variable names, class names, type names, function names etc. in formal programming languages. [22.1.1. Phrase Level Terms] | |
Module | tagdocs |
Attributes |
|
Member of | |
Contained by | |
May contain | Character data only |
Note |
In running prose, this element may be used for any kind of identifier in any formal language. It should not be used for element and attribute names in XML, for which the special elements <gi> and <att> are provided. |
Example |
<ident type="ns">http://www.tei-c.org/ns/Examples</ident>
|
Content model |
<content> <textNode/> </content> ⚓ |
Schema Declaration |
element ident { att.global.attributes, att.typed.attributes, text }⚓ |
<idno> (identifier) supplies any form of identifier used to identify some object, such as a bibliographic item, a person, a title, an organization, etc. in a standardized way. [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] | |||||||||||||||||||
Module | header | ||||||||||||||||||
Attributes |
|
||||||||||||||||||
Member of | |||||||||||||||||||
Contained by | |||||||||||||||||||
May contain |
header: idno
character data
|
||||||||||||||||||
Note |
<idno> should be used for labels which identify an object or concept in a formal cataloguing system such as a database or an RDF store, or in a distributed system such as the World Wide Web. Some suggested values for type on <idno> are ISBN, ISSN, DOI, and URI. |
||||||||||||||||||
Example |
<idno type="ISBN">978-1-906964-22-1</idno>
<idno type="ISSN">0143-3385</idno>
<idno type="DOI">10.1000/123</idno>
<idno type="URI">http://www.worldcat.org/oclc/185922478</idno>
<idno type="URI">http://authority.nzetc.org/463/</idno>
<idno type="LT">Thomason Tract E.537(17)</idno>
<idno type="Wing">C695</idno>
<idno type="oldCat">
<g ref="#sym"/>345
</idno> In the last case, the identifier includes a non-Unicode character which is defined
elsewhere by means of a <glyph> or <char> element referenced here as #sym . |
||||||||||||||||||
Content model |
<content> <alternate minOccurs="0" maxOccurs="unbounded"> <textNode/> <classRef key="model.gLike"/> <elementRef key="idno"/> </alternate> </content> ⚓ |
||||||||||||||||||
Schema Declaration |
element idno { att.global.attributes, att.sortable.attributes, att.datable.attributes, att.typed.attribute.subtype, attribute type { text }?, attribute calendar { list { + } }?, ( text | model.gLike | idno )* }⚓ |
<interp> (interpretation) summarizes a specific interpretative annotation which can be linked to a span of text. [17.3. Spans and Interpretations] | |
Module | analysis |
Attributes |
|
Member of | |
Contained by |
core: abbr author bibl biblScope cit corr date editor email emph expan foreign gloss head hi item label list mentioned name note orig p pubPlace publisher q quote ref reg resp rs series sic soCalled term textLang title unclear
linking: standOff
msdescription: repository
|
May contain |
core: desc
character data
|
Note |
Generally, each <interp> element carries an xml:id attribute. This permits the encoder to explicitly associate the interpretation represented by the content of an <interp> with any textual element through its ana attribute. Alternatively (or, in addition) an <interp> may carry an inst attribute that points to one or more textual elements to which the analysis represented by the content of the <interp> applies. |
Example |
<interp type="structuralunit"
xml:id="ana_am">aftermath</interp>
|
Content model |
<content> <alternate minOccurs="0" maxOccurs="unbounded"> <textNode/> <classRef key="model.gLike"/> <classRef key="model.descLike"/> <classRef key="model.certLike"/> </alternate> </content> ⚓ |
Schema Declaration |
element interp { att.global.attributes, att.interpLike.attributes, ( text | model.gLike | model.descLike | model.certLike )* }⚓ |
<interpGrp> (interpretation group) collects together a set of related interpretations which share responsibility or type. [17.3. Spans and Interpretations] | |
Module | analysis |
Attributes |
|
Member of | |
Contained by |
core: abbr author bibl biblScope cit corr date editor email emph expan foreign gloss head hi item label list mentioned name note orig p pubPlace publisher q quote ref reg resp rs series sic soCalled term textLang title unclear
linking: standOff
msdescription: repository
|
May contain | |
Note |
Any number of <interp> elements. |
Example |
<interpGrp resp="#TMA"
type="structuralunit">
<desc>basic structural organization</desc>
<interp xml:id="I1">introduction</interp>
<interp xml:id="I2">conflict</interp>
<interp xml:id="I3">climax</interp>
<interp xml:id="I4">revenge</interp>
<interp xml:id="I5">reconciliation</interp>
<interp xml:id="I6">aftermath</interp>
</interpGrp>
<bibl xml:id="TMA">
<!-- bibliographic citation for source of this
interpretive framework -->
</bibl>
|
Content model |
<content> <sequence> <classRef key="model.descLike" minOccurs="0" maxOccurs="unbounded"/> <elementRef key="interp" minOccurs="1" maxOccurs="unbounded"/> </sequence> </content> ⚓ |
Schema Declaration |
element interpGrp { att.global.attributes, att.interpLike.attributes, ( model.descLike*, interp+ ) }⚓ |
<item> (item) contains one component of a list. [3.8. Lists 2.6. The Revision Description] | |
Module | core |
Attributes |
|
Contained by |
core: list
|
May contain |
core: abbr bibl choice cit corr date desc email emph expan foreign gloss graphic hi label list listBibl mentioned name note orig p ptr q quote ref reg sic soCalled term title unclear
header: idno
msdescription: msDesc
namesdates: addName affiliation district forename genName geo listEvent listOrg listPerson listPlace listRelation location orgName persName placeName population region roleName settlement state surname trait
character data
|
Note |
May contain simple prose or a sequence of chunks. Whatever string of characters is used to label a list item in the copy text may be used as the value of the global n attribute, but it is not required that numbering be recorded explicitly. In ordered lists, the n attribute on the <item> element is by definition synonymous with the use of the <label> element to record the enumerator of the list item. In glossary lists, however, the term being defined should be given with the <label> element, not n. |
Example |
<list rend="numbered">
<head>Here begin the chapter headings of Book IV</head>
<item n="4.1">The death of Queen Clotild.</item>
<item n="4.2">How King Lothar wanted to appropriate one third of the Church revenues.</item>
<item n="4.3">The wives and children of Lothar.</item>
<item n="4.4">The Counts of the Bretons.</item>
<item n="4.5">Saint Gall the Bishop.</item>
<item n="4.6">The priest Cato.</item>
<item> ...</item>
</list>
|
Content model |
<content> <macroRef key="macro.specialPara"/> </content> ⚓ |
Schema Declaration |
element item { att.global.attributes, att.sortable.attributes, macro.specialPara }⚓ |
<label> (label) contains any label or heading used to identify part of a text, typically but not exclusively in a list or glossary. [3.8. Lists] | |
Module | core |
Attributes |
|
Member of | |
Contained by | |
May contain |
core: abbr choice cit corr date email emph expan foreign gloss graphic hi mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
character data
|
Example | Labels are commonly used for the headwords in glossary lists; note the use of the
global xml:lang attribute to set the default language of the glossary list to Middle English, and
identify the glosses and headings as modern English or Latin:
<list type="gloss" xml:lang="enm">
<head xml:lang="en">Vocabulary</head>
<headLabel xml:lang="en">Middle English</headLabel>
<headItem xml:lang="en">New English</headItem>
<label>nu</label>
<item xml:lang="en">now</item>
<label>lhude</label>
<item xml:lang="en">loudly</item>
<label>bloweth</label>
<item xml:lang="en">blooms</item>
<label>med</label>
<item xml:lang="en">meadow</item>
<label>wude</label>
<item xml:lang="en">wood</item>
<label>awe</label>
<item xml:lang="en">ewe</item>
<label>lhouth</label>
<item xml:lang="en">lows</item>
<label>sterteth</label>
<item xml:lang="en">bounds, frisks (cf. <cit>
<ref>Chaucer, K.T.644</ref>
<quote>a courser, <term>sterting</term>as the fyr</quote>
</cit>
</item>
<label>verteth</label>
<item xml:lang="la">pedit</item>
<label>murie</label>
<item xml:lang="en">merrily</item>
<label>swik</label>
<item xml:lang="en">cease</item>
<label>naver</label>
<item xml:lang="en">never</item>
</list>
|
Example | Labels may also be used to record explicitly the numbers or letters which mark list
items in ordered lists, as in this extract from Gibbon's Autobiography. In this usage the <label> element is synonymous with the n attribute on the <item> element:
I will add two facts, which have seldom occurred
in the composition of six, or at least of five quartos. <list rend="runon" type="ordered">
<label>(1)</label>
<item>My first rough manuscript, without any intermediate copy, has been sent to the press.</item>
<label>(2) </label>
<item>Not a sheet has been seen by any human eyes, excepting those of the author and the
printer: the faults and the merits are exclusively my own.</item>
</list>
|
Example | Labels may also be used for other structured list items, as in this extract from the
journal of Edward Gibbon:
<list type="gloss">
<label>March 1757.</label>
<item>I wrote some critical observations upon Plautus.</item>
<label>March 8th.</label>
<item>I wrote a long dissertation upon some lines of Virgil.</item>
<label>June.</label>
<item>I saw Mademoiselle Curchod — <quote xml:lang="la">Omnia vincit amor, et nos cedamus
amori.</quote>
</item>
<label>August.</label>
<item>I went to Crassy, and staid two days.</item>
</list> Note that the <label> might also appear within the <item> rather than as its sibling. Though syntactically valid, this usage is not recommended
TEI practice. |
Example | Labels may also be used to represent a label or heading attached to a paragraph or
sequence of paragraphs not treated as a structural division, or to a group of verse
lines. Note that, in this case, the <label> element appears within the <p> or <lg> element, rather than as a preceding sibling of it.
<p>[...]
<lb/>& n’entrer en mauuais & mal-heu-
<lb/>ré meſnage. Or des que le conſente-
<lb/>ment des parties y eſt le mariage eſt
<lb/> arreſté, quoy que de faict il ne ſoit
<label place="margin">Puiſſance maritale
entre les Romains.</label>
<lb/> conſommé. Depuis la conſomma-
<lb/>tion du mariage la femme eſt ſoubs
<lb/> la puiſſance du mary, s’il n’eſt eſcla-
<lb/>ue ou enfant de famille : car en ce
<lb/> cas, la femme, qui a eſpouſé vn en-
<lb/>fant de famille, eſt ſous la puiſſance
[...]</p> In this example the text of the label appears in the right hand margin of the original
source, next to the paragraph it describes, but approximately in the middle of it.
If so desired the type attribute may be used to distinguish different categories of label. |
Content model |
<content> <macroRef key="macro.phraseSeq"/> </content> ⚓ |
Schema Declaration |
element label { att.global.attributes, att.typed.attributes, att.placement.attributes, att.written.attributes, macro.phraseSeq }⚓ |
<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] | |||||||||||||||||||||||||
Module | namesdates | ||||||||||||||||||||||||
Attributes |
|
||||||||||||||||||||||||
Contained by |
—
|
||||||||||||||||||||||||
May contain |
core: abbr choice date email emph expan foreign gloss hi mentioned name note ptr q ref soCalled term title
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
character data
|
||||||||||||||||||||||||
Example |
<langKnown tag="en-GB" level="H">British English</langKnown>
<langKnown tag="fr" level="M">French</langKnown>
|
||||||||||||||||||||||||
Example |
<person sex="m" role="speaker collaborator">
<!-- other details omitted -->
<langKnowledge>
<langKnown tag="mix">Mixtepec-Mixtec</langKnown>
<langKnown tag="en">English</langKnown>
<langKnown tag="es">Spanish</langKnown>
</langKnowledge>
</person>
|
||||||||||||||||||||||||
Content model |
<content> <macroRef key="macro.phraseSeq.limited"/> </content> ⚓ |
||||||||||||||||||||||||
Schema Declaration |
element langKnown { att.global.attributes, att.datable.attributes, att.editLike.attributes, attribute calendar { list { + } }?, attribute tag { text }, attribute level { text }?, macro.phraseSeq.limited }⚓ |
<langUsage> (language usage) describes the languages, sublanguages, registers, dialects, etc. represented within a text. [2.4.2. Language Usage 2.4. The Profile Description 15.3.2. Declarable Elements] | |
Module | header |
Attributes |
|
Member of | |
Contained by |
header: profileDesc
|
May contain | |
Example |
<langUsage>
<language ident="fr-CA" usage="60">Québecois</language>
<language ident="en-CA" usage="20">Canadian business English</language>
<language ident="en-GB" usage="20">British English</language>
</langUsage>
|
Content model |
<content> <alternate> <classRef key="model.pLike" minOccurs="1" maxOccurs="unbounded"/> <elementRef key="language" minOccurs="1" maxOccurs="unbounded"/> </alternate> </content> ⚓ |
Schema Declaration |
element langUsage { att.global.attributes, att.declarable.attributes, ( model.pLike+ | language+ ) }⚓ |
<language> (language) characterizes a single language or sublanguage used within a text. [2.4.2. Language Usage] | |||||||||||||
Module | header | ||||||||||||
Attributes |
|
||||||||||||
Contained by |
header: langUsage
|
||||||||||||
May contain |
core: abbr choice date email emph expan foreign gloss hi mentioned name note ptr q ref soCalled term title
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
character data
|
||||||||||||
Note |
Particularly for sublanguages, an informal prose characterization should be supplied as content for the element. |
||||||||||||
Example |
<langUsage>
<language ident="en-US" usage="75">modern American English</language>
<language ident="az-Arab" usage="20">Azerbaijani in Arabic script</language>
<language ident="x-lap" usage="05">Pig Latin</language>
</langUsage>
|
||||||||||||
Content model |
<content> <macroRef key="macro.phraseSeq.limited"/> </content> ⚓ |
||||||||||||
Schema Declaration |
element language { att.global.attributes, attribute ident { text }, attribute usage { text }?, macro.phraseSeq.limited }⚓ |
<licence> contains information about a licence or other legal agreement applicable to the text. [2.2.4. Publication, Distribution, Licensing, etc.] | |||||||||||
Module | header | ||||||||||
Attributes |
|
||||||||||
Contained by |
—
|
||||||||||
May contain |
core: abbr bibl choice cit corr date desc email emph expan foreign gloss graphic hi label list listBibl mentioned name note orig p ptr q quote ref reg sic soCalled term title unclear
header: idno
msdescription: msDesc
namesdates: addName affiliation district forename genName geo listEvent listOrg listPerson listPlace listRelation location orgName persName placeName population region roleName settlement state surname trait
character data
|
||||||||||
Note |
A <licence> element should be supplied for each licence agreement applicable to the text in question. The target attribute may be used to reference a full version of the licence. The when, notBefore, notAfter, from or to attributes may be used in combination to indicate the date or dates of applicability of the licence. |
||||||||||
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>
|
||||||||||
Content model |
<content> <macroRef key="macro.specialPara"/> </content> ⚓ |
||||||||||
Schema Declaration |
element licence { att.global.attributes, att.pointing.attributes, att.datable.attributes, attribute calendar { list { + } }?, macro.specialPara }⚓ |
<link> (link) defines an association or hypertextual link among elements or passages, of some type not more precisely specifiable by other elements. [16.1. Links] | |
Module | linking |
Attributes |
|
Member of | |
Contained by |
core: abbr author bibl biblScope cit corr date editor email emph expan foreign gloss head hi item label list mentioned name note orig p pubPlace publisher q quote ref reg resp rs series sic soCalled term textLang title unclear
msdescription: repository
|
May contain | Empty element |
Note |
This element should only be used to encode associations not otherwise provided for by more specific elements. The location of this element within a document has no significance, unless it is included within a <linkGrp>, in which case it may inherit the value of the type attribute from the value given on the <linkGrp>. |
Example |
<s n="1">The state Supreme Court has refused to release <rs xml:id="R1">
<rs xml:id="R2">Rahway State Prison</rs> inmate</rs>
<rs xml:id="R3">James Scott</rs> on bail.</s>
<s n="2">
<rs xml:id="R4">The fighter</rs> is serving 30-40 years
for a 1975 armed robbery conviction in <rs xml:id="R5">the penitentiary</rs>.
</s>
<!-- ... -->
<linkGrp type="periphrasis">
<link target="#R1 #R3 #R4"/>
<link target="#R2 #R5"/>
</linkGrp>
|
Schematron |
<sch:assert test="contains(normalize-space(@target),' ')">You must supply at least
two values for @target or on <sch:name/>
</sch:assert>
|
Content model |
<content> <empty/> </content> ⚓ |
Schema Declaration |
element link { att.global.attributes, att.pointing.attributes, att.typed.attributes, empty }⚓ |
<linkGrp> (link group) defines a collection of associations or hypertextual links. [16.1. Links] | |||||||||||
Module | linking | ||||||||||
Attributes |
|
||||||||||
Member of | |||||||||||
Contained by |
core: abbr author bibl biblScope cit corr date editor email emph expan foreign gloss head hi item label list mentioned name note orig p pubPlace publisher q quote ref reg resp rs series sic soCalled term textLang title unclear
linking: standOff
msdescription: repository
|
||||||||||
May contain | |||||||||||
Note |
May contain one or more <link> or <ptr> elements. A web or link group is an administrative convenience, which should be used to collect a set of links together for any purpose, not simply to supply a default value for the type attribute. |
||||||||||
Example |
<linkGrp type="translation">
<link target="#CCS1 #SW1"/>
<link target="#CCS2 #SW2"/>
<link target="#CCS #SW"/>
</linkGrp>
<div type="volume" xml:id="CCS"
xml:lang="fr">
<p>
<s xml:id="CCS1">Longtemps, je me suis couché de bonne heure.</s>
<s xml:id="CCS2">Parfois, à peine ma bougie éteinte, mes yeux se fermaient si vite que je n'avais pas
le temps de me dire : "Je m'endors."</s>
</p>
<!-- ... -->
</div>
<div type="volume" xml:id="SW" xml:lang="en">
<p>
<s xml:id="SW1">For a long time I used to go to bed early.</s>
<s xml:id="SW2">Sometimes, when I had put out my candle, my eyes would close so quickly that I had
not even time to say "I'm going to sleep."</s>
</p>
<!-- ... -->
</div>
|
||||||||||
Content model |
<content> <sequence minOccurs="1" maxOccurs="1"> <classRef key="model.descLike" minOccurs="0" maxOccurs="unbounded"/> <alternate minOccurs="1" maxOccurs="unbounded"> <elementRef key="link"/> <elementRef key="ptr"/> </alternate> </sequence> </content> ⚓ |
||||||||||
Schema Declaration |
element linkGrp { att.global.attributes, att.pointing.group.attribute.domains, att.pointing.group.attribute.targFunc, att.pointing.attribute.targetLang, att.pointing.attribute.target, att.pointing.attribute.evaluate, att.typed.attribute.subtype, attribute type { "possiblySamePerson" | "notSamePerson" | "businesses" }?, ( model.descLike*, ( link | ptr )+ ) }⚓ |
<list> (list) contains any sequence of items organized as a list. [3.8. Lists] | |||||||||||
Module | core | ||||||||||
Attributes |
|
||||||||||
Member of | |||||||||||
Contained by | |||||||||||
May contain | |||||||||||
Note |
May contain an optional heading followed by a series of items, or a series of label and item pairs, the latter being optionally preceded by one or two specialized headings. |
||||||||||
Example |
<list rend="numbered">
<item>a butcher</item>
<item>a baker</item>
<item>a candlestick maker, with
<list rend="bulleted">
<item>rings on his fingers</item>
<item>bells on his toes</item>
</list>
</item>
</list>
|
||||||||||
Example |
<list type="syllogism" rend="bulleted">
<item>All Cretans are liars.</item>
<item>Epimenides is a Cretan.</item>
<item>ERGO Epimenides is a liar.</item>
</list>
|
||||||||||
Example |
<list type="litany" rend="simple">
<item>God save us from drought.</item>
<item>God save us from pestilence.</item>
<item>God save us from wickedness in high places.</item>
<item>Praise be to God.</item>
</list>
|
||||||||||
Example | The following example treats the short numbered clauses of Anglo-Saxon legal codes
as lists of items. The text is from an ordinance of King Athelstan (924–939):
<div1 type="section">
<head>Athelstan's Ordinance</head>
<list rend="numbered">
<item n="1">Concerning thieves. First, that no thief is to be spared who is caught with
the stolen goods, [if he is] over twelve years and [if the value of the goods
is] over
eightpence.
<list rend="numbered">
<item n="1.1">And if anyone does spare one, he is to pay for the thief with his
wergild — and the thief is to be no nearer a settlement on that account —
or to
clear himself by an oath of that amount.</item>
<item n="1.2">If, however, he [the thief] wishes to defend himself or to escape, he is
not to be spared [whether younger or older than twelve].</item>
<item n="1.3">If a thief is put into prison, he is to be in prison 40 days, and he may
then be redeemed with 120 shillings; and the kindred are to stand surety
for him
that he will desist for ever.</item>
<item n="1.4">And if he steals after that, they are to pay for him with his wergild,
or to bring him back there.</item>
<item n="1.5">And if he steals after that, they are to pay for him with his wergild,
whether to the king or to him to whom it rightly belongs; and everyone of
those who
supported him is to pay 120 shillings to the king as a fine.</item>
</list>
</item>
<item n="2">Concerning lordless men. And we pronounced about these lordless men, from whom
no justice can be obtained, that one should order their kindred to fetch back
such a
person to justice and to find him a lord in public meeting.
<list rend="numbered">
<item n="2.1">And if they then will not, or cannot, produce him on that appointed day,
he is then to be a fugitive afterwards, and he who encounters him is to strike
him
down as a thief.</item>
<item n="2.2">And he who harbours him after that, is to pay for him with his wergild
or to clear himself by an oath of that amount.</item>
</list>
</item>
<item n="3">Concerning the refusal of justice. The lord who refuses justice and upholds
his guilty man, so that the king is appealed to, is to repay the value of the
goods and
120 shillings to the king; and he who appeals to the king before he demands justice
as
often as he ought, is to pay the same fine as the other would have done, if he
had
refused him justice.
<list rend="numbered">
<item n="3.1">And the lord who is an accessory to a theft by his slave, and it becomes
known about him, is to forfeit the slave and be liable to his wergild on
the first
occasionp if he does it more often, he is to be liable to pay all that he
owns.</item>
<item n="3.2">And likewise any of the king's treasurers or of our reeves, who has been
an accessory of thieves who have committed theft, is to liable to the same.</item>
</list>
</item>
<item n="4">Concerning treachery to a lord. And we have pronounced concerning treachery to
a lord, that he [who is accused] is to forfeit his life if he cannot deny it
or is
afterwards convicted at the three-fold ordeal.</item>
</list>
</div1> Note that nested lists have been used so the tagging mirrors the structure indicated
by the two-level numbering of the clauses. The clauses could have been treated as
a one-level list with irregular numbering, if desired. |
||||||||||
Example |
<p>These decrees, most blessed Pope Hadrian, we propounded in the public council ...
and they
confirmed them in our hand in your stead with the sign of the Holy Cross, and afterwards
inscribed with a careful pen on the paper of this page, affixing thus the sign of
the Holy
Cross.
<list rend="simple">
<item>I, Eanbald, by the grace of God archbishop of the holy church of York, have
subscribed to the pious and catholic validity of this document with the sign
of the Holy
Cross.</item>
<item>I, Ælfwold, king of the people across the Humber, consenting have subscribed with
the sign of the Holy Cross.</item>
<item>I, Tilberht, prelate of the church of Hexham, rejoicing have subscribed with the
sign of the Holy Cross.</item>
<item>I, Higbald, bishop of the church of Lindisfarne, obeying have subscribed with the
sign of the Holy Cross.</item>
<item>I, Ethelbert, bishop of Candida Casa, suppliant, have subscribed with thef sign of
the Holy Cross.</item>
<item>I, Ealdwulf, bishop of the church of Mayo, have subscribed with devout will.</item>
<item>I, Æthelwine, bishop, have subscribed through delegates.</item>
<item>I, Sicga, patrician, have subscribed with serene mind with the sign of the Holy
Cross.</item>
</list>
</p>
|
||||||||||
Schematron |
<sch:rule context="tei:list[@type='gloss']">
<sch:assert test="tei:label">The content of a "gloss" list should include a sequence
of one or more pairs of a label element followed by an item element</sch:assert>
</sch:rule>
|
||||||||||
Content model |
<content> <sequence> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.divTop"/> <classRef key="model.global"/> <elementRef key="desc" minOccurs="0" maxOccurs="unbounded"/> </alternate> <alternate> <sequence minOccurs="1" maxOccurs="unbounded"> <elementRef key="item"/> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> <sequence> <elementRef key="headLabel" minOccurs="0"/> <elementRef key="headItem" minOccurs="0"/> <sequence minOccurs="1" maxOccurs="unbounded"> <elementRef key="label"/> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> <elementRef key="item"/> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> </sequence> </alternate> <sequence minOccurs="0" maxOccurs="unbounded"> <classRef key="model.divBottom"/> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> </sequence> </content> ⚓ |
||||||||||
Schema Declaration |
element list { att.global.attributes, att.sortable.attributes, att.typed.attribute.subtype, attribute type { text }?, ( ( model.divTop | model.global | desc* )*, ( ( ( item, model.global* )+ ) | ( headLabel?, headItem?, ( ( label, model.global*, item, model.global* )+ ) ) ), ( ( model.divBottom, model.global* )* ) ) }⚓ |
<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] | |
Module | core |
Attributes |
|
Member of | |
Contained by | |
May contain | |
Example |
<listBibl>
<head>Works consulted</head>
<bibl>Blain, Clements and Grundy: Feminist Companion to
Literature in English (Yale, 1990)
</bibl>
<biblStruct>
<analytic>
<title>The Interesting story of the Children in the Wood</title>
</analytic>
<monogr>
<title>The Penny Histories</title>
<author>Victor E Neuberg</author>
<imprint>
<publisher>OUP</publisher>
<date>1968</date>
</imprint>
</monogr>
</biblStruct>
</listBibl>
|
Content model |
<content> <sequence> <classRef key="model.headLike" minOccurs="0" maxOccurs="unbounded"/> <elementRef key="desc" minOccurs="0" maxOccurs="unbounded"/> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.milestoneLike" minOccurs="1" maxOccurs="1"/> <elementRef key="relation" minOccurs="1" maxOccurs="1"/> <elementRef key="listRelation" minOccurs="1" maxOccurs="1"/> </alternate> <sequence minOccurs="1" maxOccurs="unbounded"> <classRef key="model.biblLike" minOccurs="1" maxOccurs="unbounded"/> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.milestoneLike" minOccurs="1" maxOccurs="1"/> <elementRef key="relation" minOccurs="1" maxOccurs="1"/> <elementRef key="listRelation" minOccurs="1" maxOccurs="1"/> </alternate> </sequence> </sequence> </content> ⚓ |
Schema Declaration |
element listBibl { att.global.attributes, att.sortable.attributes, att.declarable.attributes, att.typed.attributes, ( model.headLike*, desc*, ( model.milestoneLike | relation | listRelation )*, ( ( model.biblLike+, ( model.milestoneLike | relation | listRelation )* )+ ) ) }⚓ |
<listEvent> (list of events) contains a list of descriptions, each of which provides information about an identifiable event. [13.3.1. Basic Principles] | |
Module | namesdates |
Attributes |
|
Member of | |
Contained by | |
May contain | |
Example |
<listEvent>
<head>Battles of the American Civil War: Kentucky</head>
<event xml:id="event01" when="1861-09-19">
<label>Barbourville</label>
<desc>The Battle of Barbourville was one of the early engagements of
the American Civil War. It occurred September 19, 1861, in Knox
County, Kentucky during the campaign known as the Kentucky Confederate
Offensive. The battle is considered the first Confederate victory in
the commonwealth, and threw a scare into Federal commanders, who
rushed troops to central Kentucky in an effort to repel the invasion,
which was finally thwarted at the <ref target="#event02">Battle of
Camp Wildcat</ref> in October.</desc>
</event>
<event xml:id="event02" when="1861-10-21">
<label>Camp Wild Cat</label>
<desc>The Battle of Camp Wildcat (also known as Wildcat Mountain and Camp
Wild Cat) was one of the early engagements of the American Civil
War. It occurred October 21, 1861, in northern Laurel County, Kentucky
during the campaign known as the Kentucky Confederate Offensive. The
battle is considered one of the very first Union victories, and marked
the first engagement of troops in the commonwealth of Kentucky.</desc>
</event>
<event xml:id="event03" from="1864-06-11"
to="1864-06-12">
<label>Cynthiana</label>
<desc>The Battle of Cynthiana (or Kellar’s Bridge) was an engagement
during the American Civil War that was fought on June 11 and 12, 1864,
in Harrison County, Kentucky, near the town of Cynthiana. A part of
Confederate Brigadier General John Hunt Morgan's 1864 Raid into
Kentucky, the battle resulted in a victory by Union forces over the
raiders and saved the town from capture.</desc>
</event>
</listEvent>
|
Content model |
<content> <sequence> <classRef key="model.headLike" minOccurs="0" maxOccurs="unbounded"/> <elementRef key="desc" minOccurs="0" maxOccurs="unbounded"/> <alternate minOccurs="0" maxOccurs="unbounded"> <elementRef key="relation" minOccurs="1" maxOccurs="1"/> <elementRef key="listRelation" minOccurs="1" maxOccurs="1"/> </alternate> <sequence minOccurs="1" maxOccurs="unbounded"> <classRef key="model.eventLike" minOccurs="1" maxOccurs="unbounded"/> <alternate minOccurs="0" maxOccurs="unbounded"> <elementRef key="relation" minOccurs="1" maxOccurs="1"/> <elementRef key="listRelation" minOccurs="1" maxOccurs="1"/> </alternate> </sequence> </sequence> </content> ⚓ |
Schema Declaration |
element listEvent { att.global.attributes, att.typed.attributes, att.declarable.attributes, att.sortable.attributes, ( model.headLike*, desc*, ( relation | listRelation )*, ( ( model.eventLike+, ( relation | listRelation )* )+ ) ) }⚓ |
<listOrg> (list of organizations) contains a list of elements, each of which provides information about an identifiable organization. [13.2.2. Organizational Names] | |
Module | namesdates |
Attributes |
|
Member of | |
Contained by | |
May contain | |
Note |
The type attribute may be used to distinguish lists of organizations of a particular type if convenient. |
Example |
<listOrg>
<head>Libyans</head>
<org>
<orgName>Adyrmachidae</orgName>
<desc>These people have, in most points, the same customs as the Egyptians, but
use the costume of the Libyans. Their women wear on each leg a ring made of
bronze [...]</desc>
</org>
<org>
<orgName>Nasamonians</orgName>
<desc>In summer they leave their flocks and herds upon the sea-shore, and go up
the country to a place called Augila, where they gather the dates from the
palms [...]</desc>
</org>
<org>
<orgName>Garamantians</orgName>
<desc>[...] avoid all society or intercourse with their fellow-men, have no
weapon of war, and do not know how to defend themselves. [...]</desc>
<!-- ... -->
</org>
</listOrg>
|
Content model |
<content> <sequence> <classRef key="model.headLike" minOccurs="0" maxOccurs="unbounded"/> <elementRef key="desc" minOccurs="0" maxOccurs="unbounded"/> <alternate minOccurs="0" maxOccurs="unbounded"> <elementRef key="relation" minOccurs="1" maxOccurs="1"/> <elementRef key="listRelation" minOccurs="1" maxOccurs="1"/> </alternate> <sequence minOccurs="1" maxOccurs="unbounded"> <alternate minOccurs="1" maxOccurs="unbounded"> <elementRef key="org" minOccurs="1" maxOccurs="1"/> <elementRef key="listOrg" minOccurs="1" maxOccurs="1"/> </alternate> <alternate minOccurs="0" maxOccurs="unbounded"> <elementRef key="relation" minOccurs="1" maxOccurs="1"/> <elementRef key="listRelation" minOccurs="1" maxOccurs="1"/> </alternate> </sequence> </sequence> </content> ⚓ |
Schema Declaration |
element listOrg { att.global.attributes, att.typed.attributes, att.declarable.attributes, att.sortable.attributes, ( model.headLike*, desc*, ( relation | listRelation )*, ( ( ( org | listOrg )+, ( relation | listRelation )* )+ ) ) }⚓ |
<listPerson> (list of persons) contains a list of descriptions, each of which provides information about an identifiable person or a group of people, for example the participants in a language interaction, or the people referred to in a historical source. [13.3.2. The Person Element 15.2. Contextual Information 2.4. The Profile Description 15.3.2. Declarable Elements] | |
Module | namesdates |
Attributes |
|
Member of | |
Contained by | |
May contain |
namesdates: listRelation org person
|
Note |
The type attribute may be used to distinguish lists of people of a particular type if convenient. |
Example |
<listPerson type="respondents">
<personGrp xml:id="PXXX"/>
<person xml:id="P1234" sex="2" age="mid"/>
<person xml:id="P4332" sex="1" age="mid"/>
<listRelation>
<relation type="personal" name="spouse"
mutual="#P1234 #P4332"/>
</listRelation>
</listPerson>
|
Content model |
<content> <sequence minOccurs="1" maxOccurs="1"> <classRef key="model.headLike" minOccurs="0" maxOccurs="unbounded"/> <elementRef key="desc" minOccurs="0" maxOccurs="unbounded"/> <classRef key="model.personLike" minOccurs="1" maxOccurs="unbounded"/> <elementRef key="listRelation" minOccurs="0" maxOccurs="1"/> </sequence> </content> ⚓ |
Schema Declaration |
element listPerson { att.global.attributes, att.typed.attributes, att.declarable.attributes, att.sortable.attributes, ( model.headLike*, desc*, model.personLike+, listRelation? ) }⚓ |
<listPlace> (list of places) contains a list of places, optionally followed by a list of relationships (other than containment) defined amongst them. [2.2.7. The Source Description 13.3.4. Places] | |
Module | namesdates |
Attributes |
|
Member of | |
Contained by | |
May contain | |
Example |
<listPlace type="offshoreIslands">
<place>
<placeName>La roche qui pleure</placeName>
</place>
<place>
<placeName>Ile aux cerfs</placeName>
</place>
</listPlace>
|
Content model |
<content> <sequence> <classRef key="model.headLike" minOccurs="0" maxOccurs="unbounded"/> <elementRef key="desc" minOccurs="0" maxOccurs="unbounded"/> <alternate minOccurs="0" maxOccurs="unbounded"> <elementRef key="relation" minOccurs="1" maxOccurs="1"/> <elementRef key="listRelation" minOccurs="1" maxOccurs="1"/> </alternate> <sequence minOccurs="1" maxOccurs="unbounded"> <alternate minOccurs="1" maxOccurs="unbounded"> <classRef key="model.placeLike" minOccurs="1" maxOccurs="1"/> <elementRef key="listPlace" minOccurs="1" maxOccurs="1"/> </alternate> <alternate minOccurs="0" maxOccurs="unbounded"> <elementRef key="relation" minOccurs="1" maxOccurs="1"/> <elementRef key="listRelation" minOccurs="1" maxOccurs="1"/> </alternate> </sequence> </sequence> </content> ⚓ |
Schema Declaration |
element listPlace { att.global.attributes, att.typed.attributes, att.declarable.attributes, att.sortable.attributes, ( model.headLike*, desc*, ( relation | listRelation )*, ( ( ( model.placeLike | listPlace )+, ( relation | listRelation )* )+ ) ) }⚓ |
<listPrefixDef> (list of prefix definitions) contains a list of definitions of prefixing schemes used in teidata.pointer values, showing how abbreviated URIs using each scheme may be expanded into full URIs. [16.2.3. Using Abbreviated Pointers] | |
Module | header |
Attributes |
|
Member of | |
Contained by |
header: encodingDesc listPrefixDef
|
May contain |
core: desc
header: listPrefixDef prefixDef
|
Example | In this example, two private URI scheme prefixes are defined and patterns are provided
for dereferencing them. Each prefix is also supplied with a human-readable explanation
in a <p> element.
<listPrefixDef>
<prefixDef ident="psn"
matchPattern="([A-Z]+)"
replacementPattern="personography.xml#$1">
<p> Private URIs using the <code>psn</code>
prefix are pointers to <gi>person</gi>
elements in the personography.xml file.
For example, <code>psn:MDH</code>
dereferences to <code>personography.xml#MDH</code>.
</p>
</prefixDef>
<prefixDef ident="bibl"
matchPattern="([a-z]+[a-z0-9]*)"
replacementPattern="http://www.example.com/getBibl.xql?id=$1">
<p> Private URIs using the <code>bibl</code> prefix can be
expanded to form URIs which retrieve the relevant
bibliographical reference from www.example.com.
</p>
</prefixDef>
</listPrefixDef>
|
Content model |
<content> <sequence> <elementRef key="desc" minOccurs="0" maxOccurs="unbounded"/> <alternate minOccurs="1" maxOccurs="unbounded"> <elementRef key="prefixDef"/> <elementRef key="listPrefixDef"/> </alternate> </sequence> </content> ⚓ |
Schema Declaration |
element listPrefixDef { att.global.attributes, ( desc*, ( prefixDef | listPrefixDef )+ ) }⚓ |
<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] | |
Module | namesdates |
Attributes |
|
Member of | |
Contained by | |
May contain |
namesdates: listRelation relation
|
Note |
May contain a prose description organized as paragraphs, or a sequence of <relation> elements. |
Example |
<listPerson>
<person xml:id="pp1">
<!-- data about person pp1 -->
</person>
<person xml:id="pp2">
<!-- data about person pp1 -->
</person>
<!-- more person (pp3, pp4) elements here -->
<listRelation type="personal">
<relation name="parent"
active="#pp1 #pp2" passive="#pp3 #pp4"/>
<relation name="spouse"
mutual="#pp1 #pp2"/>
</listRelation>
<listRelation type="social">
<relation name="employer" active="#pp1"
passive="#pp3 #pp5 #pp6 #pp7"/>
</listRelation>
</listPerson> The persons with identifiers pp1 and pp2 are the parents of pp3 and pp4; they are
also married to each other; pp1 is the employer of pp3, pp5, pp6, and pp7. |
Example |
<listPerson>
<person xml:id="en_pp1">
<!-- data about person en_pp1 -->
</person>
<person xml:id="en_pp2">
<!-- data about person en_pp2 -->
</person>
<!-- more person (en_pp3, en_pp4) elements here -->
</listPerson>
<listPlace>
<place xml:id="en_pl1">
<!-- data about place en_pl1 -->
</place>
<!-- more place (en_pl2, en_pl3) elements here -->
</listPlace>
<listRelation>
<relation name="residence"
active="#en_pp1 #en_pp2" passive="#en_pl1"/>
</listRelation> The persons with identifiers en_pp1 and en_pp2 live in en_pl1. |
Example |
<listRelation>
<p>All speakers are members of the Ceruli family, born in Naples.</p>
</listRelation>
|
Content model |
<content> <sequence> <classRef key="model.headLike" minOccurs="0" maxOccurs="unbounded"/> <elementRef key="desc" minOccurs="0" maxOccurs="unbounded"/> <alternate minOccurs="1" maxOccurs="1"> <classRef key="model.pLike"/> <alternate minOccurs="1" maxOccurs="unbounded"> <elementRef key="relation" minOccurs="1" maxOccurs="1"/> <elementRef key="listRelation" minOccurs="1" maxOccurs="1"/> </alternate> </alternate> </sequence> </content> ⚓ |
Schema Declaration |
element listRelation { att.global.attributes, att.typed.attributes, att.sortable.attributes, ( model.headLike*, desc*, ( model.pLike | ( relation | listRelation )+ ) ) }⚓ |
<location> (location) defines the location of a place as a set of geographical coordinates, in terms of other named geo-political entities, or as an address. [13.3.4. Places] | |||||||||||
Module | namesdates | ||||||||||
Attributes |
|
||||||||||
Member of | |||||||||||
Contained by | |||||||||||
May contain | |||||||||||
Example |
<place>
<placeName>Abbey Dore</placeName>
<location>
<geo>51.969604 -2.893146</geo>
</location>
</place>
|
||||||||||
Example |
<place xml:id="BGbuilding" type="building">
<placeName>Brasserie Georges</placeName>
<location>
<country key="FR"/>
<settlement type="city">Lyon</settlement>
<district type="arrondissement">IIème</district>
<district type="quartier">Perrache</district>
<placeName type="street">
<num>30</num>, Cours de Verdun</placeName>
</location>
</place>
|
||||||||||
Example |
<place type="imaginary">
<placeName>Atlantis</placeName>
<location>
<offset>beyond</offset>
<placeName>The Pillars of <persName>Hercules</persName>
</placeName>
</location>
</place>
|
||||||||||
Content model |
<content> <alternate minOccurs="0" maxOccurs="unbounded"> <elementRef key="precision"/> <classRef key="model.labelLike"/> <classRef key="model.placeNamePart"/> <classRef key="model.offsetLike"/> <classRef key="model.measureLike"/> <classRef key="model.addressLike"/> <classRef key="model.noteLike"/> <classRef key="model.biblLike"/> </alternate> </content> ⚓ |
||||||||||
Schema Declaration |
element location { att.global.attributes, att.typed.attributes, att.datable.attributes, att.editLike.attributes, attribute calendar { list { + } }?, ( precision | model.labelLike | model.placeNamePart | model.offsetLike | model.measureLike | model.addressLike | model.noteLike | model.biblLike )* }⚓ |
<m> (morpheme) represents a grammatical morpheme. [17.1. Linguistic Segment Categories] | |||||||
Module | analysis | ||||||
Attributes |
|
||||||
Member of | |||||||
Contained by | |||||||
May contain | |||||||
Note |
The type attribute may be used to indicate the type of morpheme, taking values such as clitic, prefix, stem, etc. as appropriate. |
||||||
Example |
<w type="adjective">
<w type="noun">
<m type="prefix" baseForm="con">com</m>
<m type="root">fort</m>
</w>
<m type="suffix">able</m>
</w>
|
||||||
Content model |
<content> <alternate minOccurs="0" maxOccurs="unbounded"> <textNode/> <classRef key="model.gLike"/> <classRef key="model.hiLike"/> <elementRef key="seg"/> <elementRef key="m"/> <elementRef key="c"/> <classRef key="model.global"/> </alternate> </content> ⚓ |
||||||
Schema Declaration |
element m { att.global.attributes, att.segLike.attributes, att.typed.attributes, att.notated.attributes, attribute baseForm { text }?, ( text | model.gLike | model.hiLike | seg | m | c | model.global )* }⚓ |
<mentioned> marks words or phrases mentioned, not used. [3.3.3. Quotation] | |
Module | core |
Attributes |
|
Member of | |
Contained by | |
May contain |
core: abbr choice cit corr date email emph expan foreign gloss graphic hi mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
character data
|
Example |
There is thus a
striking accentual difference between a verbal form like <mentioned xml:id="X234" xml:lang="el">eluthemen</mentioned>
<gloss target="#X234">we were released,</gloss> accented on the second syllable of the
word, and its participial derivative
<mentioned xml:id="X235" xml:lang="el">lutheis</mentioned>
<gloss target="#X235">released,</gloss> accented on the last.
|
Content model |
<content> <macroRef key="macro.phraseSeq"/> </content> ⚓ |
Schema Declaration |
element mentioned { att.global.attributes, macro.phraseSeq }⚓ |
<msContents> (manuscript contents) describes the intellectual content of a manuscript, manuscript part, or other object either as a series of paragraphs or as a series of structured manuscript items. [10.6. Intellectual Content] | |
Module | msdescription |
Attributes |
|
Contained by |
msdescription: msDesc
|
May contain | |
Note |
Unless it contains a simple prose description, this element should contain at least one of the elements <summary>, <msItem>, or <msItemStruct>. This constraint is not currently enforced by the schema. |
Example |
<msContents class="#sermons">
<p>A collection of Lollard sermons</p>
</msContents>
|
Example |
<msContents>
<msItem n="1">
<locus>fols. 5r-7v</locus>
<title>An ABC</title>
<bibl>
<title>IMEV</title>
<biblScope>239</biblScope>
</bibl>
</msItem>
<msItem n="2">
<locus>fols. 7v-8v</locus>
<title xml:lang="frm">Lenvoy de Chaucer a Scogan</title>
<bibl>
<title>IMEV</title>
<biblScope>3747</biblScope>
</bibl>
</msItem>
<msItem n="3">
<locus>fol. 8v</locus>
<title>Truth</title>
<bibl>
<title>IMEV</title>
<biblScope>809</biblScope>
</bibl>
</msItem>
<msItem n="4">
<locus>fols. 8v-10v</locus>
<title>Birds Praise of Love</title>
<bibl>
<title>IMEV</title>
<biblScope>1506</biblScope>
</bibl>
</msItem>
<msItem n="5">
<locus>fols. 10v-11v</locus>
<title xml:lang="la">De amico ad amicam</title>
<title xml:lang="la">Responcio</title>
<bibl>
<title>IMEV</title>
<biblScope>16 & 19</biblScope>
</bibl>
</msItem>
<msItem n="6">
<locus>fols. 14r-126v</locus>
<title>Troilus and Criseyde</title>
<note>Bk. 1:71-Bk. 5:1701, with additional losses due to mutilation throughout</note>
</msItem>
</msContents>
|
Content model |
<content> <alternate> <classRef key="model.pLike" minOccurs="1" maxOccurs="unbounded"/> <sequence> <elementRef key="summary" minOccurs="0"/> <elementRef key="textLang" minOccurs="0"/> <elementRef key="titlePage" minOccurs="0"/> <alternate minOccurs="0" maxOccurs="unbounded"> <elementRef key="msItem"/> <elementRef key="msItemStruct"/> </alternate> </sequence> </alternate> </content> ⚓ |
Schema Declaration |
element msContents { att.global.attributes, att.msExcerpt.attributes, att.msClass.attributes, ( model.pLike+ | ( summary?, textLang?, titlePage?, ( msItem | msItemStruct )* ) ) }⚓ |
<msDesc> (manuscript description) contains a description of a single identifiable manuscript or other text-bearing object such as an early printed book. [10.1. Overview] | |
Module | msdescription |
Attributes |
|
Member of | |
Contained by | |
May contain |
msdescription: msContents msIdentifier
|
Note |
Although the <msDesc> has primarily been designed with a view to encoding manuscript descriptions, it may also be used for other objects such as early printed books, fascicles, epigraphs, or any text-bearing objects that require substantial description. If an object is not text-bearing or the reasons for describing the object is not primarily the textual content, the more general <object> may be more suitable. |
Example |
<msDesc>
<msIdentifier>
<settlement>Oxford</settlement>
<repository>Bodleian Library</repository>
<idno type="Bod">MS Poet. Rawl. D. 169.</idno>
</msIdentifier>
<msContents>
<msItem>
<author>Geoffrey Chaucer</author>
<title>The Canterbury Tales</title>
</msItem>
</msContents>
<physDesc>
<objectDesc>
<p>A parchment codex of 136 folios, measuring approx
28 by 19 inches, and containing 24 quires.</p>
<p>The pages are margined and ruled throughout.</p>
<p>Four hands have been identified in the manuscript: the first 44
folios being written in two cursive anglicana scripts, while the
remainder is for the most part in a mixed secretary hand.</p>
</objectDesc>
</physDesc>
</msDesc>
|
Schematron |
<sch:rule context="tei:msContents|tei:physDesc|tei:history|tei:additional">
<sch:let name="gi" value="name(.)"/>
<sch:report test="preceding-sibling::*[ name(.) eq $gi ] and not( following-sibling::*[
name(.) eq $gi ] )"> Only one <sch:name/> is allowed as a child of <sch:value-of select="name(..)"/>.
</sch:report>
</sch:rule>
|
Content model |
<content> <sequence> <elementRef key="msIdentifier"/> <classRef key="model.headLike" minOccurs="0" maxOccurs="unbounded"/> <alternate> <classRef key="model.pLike" minOccurs="1" maxOccurs="unbounded"/> <alternate minOccurs="0" maxOccurs="unbounded"> <elementRef key="msContents"/> <elementRef key="physDesc"/> <elementRef key="history"/> <elementRef key="additional"/> <elementRef key="msPart"/> <elementRef key="msFrag"/> </alternate> </alternate> </sequence> </content> ⚓ |
Schema Declaration |
element msDesc { att.global.attributes, att.sortable.attributes, att.typed.attributes, att.declaring.attributes, att.docStatus.attributes, ( msIdentifier, model.headLike*, ( model.pLike+ | ( msContents | physDesc | history | additional | msPart | msFrag )* ) ) }⚓ |
<msIdentifier> (manuscript identifier) contains the information required to identify the manuscript or similar object being described. [10.4. The Manuscript Identifier] | |
Module | msdescription |
Attributes |
|
Member of | |
Contained by | |
May contain | |
Example |
<msIdentifier>
<settlement>San Marino</settlement>
<repository>Huntington Library</repository>
<idno>MS.El.26.C.9</idno>
</msIdentifier>
|
Schematron |
<sch:report test="not(parent::tei:msPart) and (local-name(*[1])='idno' or local-name(*[1])='altIdentifier'
or normalize-space(.)='')">An msIdentifier must contain either a repository or location.</sch:report>
|
Content model |
<content> <sequence> <sequence> <classRef key="model.placeNamePart" expand="sequenceOptional"/> <elementRef key="institution" minOccurs="0"/> <elementRef key="repository" minOccurs="0"/> <elementRef key="collection" minOccurs="0" maxOccurs="unbounded"/> <elementRef key="idno" minOccurs="0" maxOccurs="unbounded"/> </sequence> <alternate minOccurs="0" maxOccurs="unbounded"> <elementRef key="msName"/> <elementRef key="objectName"/> <elementRef key="altIdentifier"/> </alternate> </sequence> </content> ⚓ |
Schema Declaration |
element msIdentifier { att.global.attributes, ( ( placeName?, region?, settlement?, district?, institution?, repository?, collection*, idno* ), ( msName | objectName | altIdentifier )* ) }⚓ |
<msName> (alternative name) contains any form of unstructured alternative name used for a manuscript or other object, such as an ‘ocellus nominum’, or nickname. [10.4. The Manuscript Identifier] | |
Module | msdescription |
Attributes |
|
Contained by |
msdescription: msIdentifier
|
May contain | |
Example |
<msName>The Vercelli Book</msName>
|
Content model |
<content> <alternate minOccurs="0" maxOccurs="unbounded"> <textNode/> <classRef key="model.gLike"/> <elementRef key="rs"/> <elementRef key="name"/> </alternate> </content> ⚓ |
Schema Declaration |
element msName { att.global.attributes, att.typed.attributes, ( text | model.gLike | rs | name )* }⚓ |
<name> (name, proper noun) contains a proper noun or noun phrase. [3.6.1. Referring Strings] | |||||||||||
Module | core | ||||||||||
Attributes |
|
||||||||||
Member of | |||||||||||
Contained by | |||||||||||
May contain |
core: abbr choice cit corr date email emph expan foreign gloss graphic hi mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
character data
|
||||||||||
Note |
Proper nouns referring to people, places, and organizations may be tagged instead with <persName>, <placeName>, or <orgName>, when the TEI module for names and dates is included. |
||||||||||
Example |
<name type="person">Thomas Hoccleve</name>
<name type="place">Villingaholt</name>
<name type="org">Vetus Latina Institut</name>
<name type="person" ref="#HOC001">Occleve</name>
|
||||||||||
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, attribute calendar { list { + } }?, macro.phraseSeq }⚓ |
<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] | |||||||||||
Module | core | ||||||||||
Attributes |
|
||||||||||
Member of | |||||||||||
Contained by |
core: abbr author bibl biblScope cit corr date editor email emph expan foreign gloss head hi item label list mentioned name note orig p pubPlace publisher q quote ref reg resp respStmt rs series sic soCalled term textLang title unclear
linking: standOff
msdescription: repository
|
||||||||||
May contain |
core: abbr bibl choice cit corr date desc email emph expan foreign gloss graphic hi label list listBibl mentioned name note orig p ptr q quote ref reg sic soCalled term title unclear
header: idno
msdescription: msDesc
namesdates: addName affiliation district forename genName geo listEvent listOrg listPerson listPlace listRelation location orgName persName placeName population region roleName settlement state surname trait
character data
|
||||||||||
Example | In the following example, the translator has supplied a footnote containing an explanation
of the term translated as "painterly":
And yet it is not only
in the great line of Italian renaissance art, but even in the
painterly <note place="bottom" type="gloss"
resp="#MDMH">
<term xml:lang="de">Malerisch</term>. This word has, in the German, two
distinct meanings, one objective, a quality residing in the object,
the other subjective, a mode of apprehension and creation. To avoid
confusion, they have been distinguished in English as
<mentioned>picturesque</mentioned> and
<mentioned>painterly</mentioned> respectively.
</note> style of the
Dutch genre painters of the seventeenth century that drapery has this
psychological significance.
<!-- elsewhere in the document -->
<respStmt xml:id="MDMH">
<resp>translation from German to English</resp>
<name>Hottinger, Marie Donald Mackie</name>
</respStmt> For this example to be valid, the code MDMH must be defined elsewhere, for example by means of a responsibility statement in
the associated TEI header. |
||||||||||
Example | The global n attribute may be used to supply the symbol or number used to mark the note's point
of attachment in the source text, as in the following example:
Mevorakh b. Saadya's mother, the matriarch of the
family during the second half of the eleventh century, <note n="126" anchored="true"> The
alleged mention of Judah Nagid's mother in a letter from 1071 is, in fact, a reference
to
Judah's children; cf. above, nn. 111 and 54. </note> is well known from Geniza documents
published by Jacob Mann. However, if notes are numbered in sequence and their numbering can be reconstructed
automatically by processing software, it may well be considered unnecessary to record
the note numbers. |
||||||||||
Content model |
<content> <macroRef key="macro.specialPara"/> </content> ⚓ |
||||||||||
Schema Declaration |
element note { att.global.attributes, att.placement.attributes, att.pointing.attributes, att.typed.attribute.subtype, att.written.attributes, att.anchoring.attributes, attribute type { "dev" | "public" | "relation" | "attestedRelations" | "inferredRelations" }?, macro.specialPara }⚓ |
<occupation> (occupation) contains an informal description of a person's trade, profession or occupation. [15.2.2. The Participant Description] | |||||||||||||||||||||||||||||||
Module | namesdates | ||||||||||||||||||||||||||||||
Attributes |
|
||||||||||||||||||||||||||||||
Member of | |||||||||||||||||||||||||||||||
Contained by |
namesdates: person
|
||||||||||||||||||||||||||||||
May contain |
core: abbr bibl choice cit corr date desc email emph expan foreign gloss graphic hi label list listBibl mentioned name note orig p ptr q quote ref reg sic soCalled term title unclear
header: idno
msdescription: msDesc
namesdates: addName affiliation district forename genName geo listEvent listOrg listPerson listPlace listRelation location orgName persName placeName population region roleName settlement state surname trait
character data
|
||||||||||||||||||||||||||||||
Note |
The content of this element may be used as an alternative to the more formal specification made possible by its attributes; it may also be used to supplement the formal specification with commentary or clarification. |
||||||||||||||||||||||||||||||
Example |
<occupation>accountant</occupation>
|
||||||||||||||||||||||||||||||
Example |
<occupation scheme="#occupationtaxonomy"
code="#acc">accountant</occupation>
|
||||||||||||||||||||||||||||||
Content model |
<content> <macroRef key="macro.specialPara"/> </content> ⚓ |
||||||||||||||||||||||||||||||
Schema Declaration |
element occupation { att.global.attributes, att.datable.attributes, att.editLike.attributes, att.naming.attributes, att.typed.attribute.subtype, attribute type { text }?, attribute calendar { list { + } }?, attribute scheme { text }?, attribute code { text }?, macro.specialPara }⚓ |
<org> (organization) provides information about an identifiable organization such as a business, a tribe, or any other grouping of people. [13.3.3. Organizational Data] | |||||||||
Module | namesdates | ||||||||
Attributes |
|
||||||||
Member of | |||||||||
Contained by |
namesdates: listOrg listPerson org
|
||||||||
May contain | |||||||||
Example |
<org xml:id="JAMs">
<orgName>Justified Ancients of Mummu</orgName>
<desc>An underground anarchist collective spearheaded by
<persName>Hagbard Celine</persName>, who fight the Illuminati
from a golden submarine, the <name>Leif Ericson</name>
</desc>
<bibl>
<author>Robert Shea</author>
<author>Robert Anton Wilson</author>
<title>The Illuminatus! Trilogy</title>
</bibl>
</org>
|
||||||||
Content model |
<content> <sequence> <classRef key="model.headLike" minOccurs="0" maxOccurs="unbounded"/> <alternate> <classRef key="model.pLike" minOccurs="0" maxOccurs="unbounded"/> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.labelLike"/> <classRef key="model.nameLike"/> <classRef key="model.placeLike"/> <classRef key="model.orgPart"/> <classRef key="model.milestoneLike"/> </alternate> </alternate> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.noteLike"/> <classRef key="model.biblLike"/> <elementRef key="linkGrp"/> <elementRef key="link"/> <elementRef key="ptr"/> </alternate> <classRef key="model.personLike" minOccurs="0" maxOccurs="unbounded"/> </sequence> </content> ⚓ |
||||||||
Schema Declaration |
element org { att.global.attributes, att.typed.attributes, att.editLike.attributes, att.sortable.attributes, attribute role { list { + } }?, ( model.headLike*, ( model.pLike* | ( model.labelLike | model.nameLike | model.placeLike | model.orgPart | model.milestoneLike )* ), ( model.noteLike | model.biblLike | linkGrp | link | ptr )*, model.personLike* ) }⚓ |
<orgName> (organization name) contains an organizational name. [13.2.2. Organizational Names] | |||||||||||
Module | namesdates | ||||||||||
Attributes |
|
||||||||||
Member of | |||||||||||
Contained by | |||||||||||
May contain |
core: abbr choice cit corr date email emph expan foreign gloss graphic hi mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
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, attribute calendar { list { + } }?, macro.phraseSeq }⚓ |
<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] | |
Module | core |
Attributes |
|
Member of | |
Contained by | |
May contain |
core: abbr bibl choice cit corr date desc email emph expan foreign gloss graphic hi label list listBibl mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
header: idno
msdescription: msDesc
namesdates: addName affiliation district forename genName geo listEvent listOrg listPerson listPlace listRelation location orgName persName placeName population region roleName settlement state surname trait
character data
|
Example | If all that is desired is to call attention to the original version in the copy text,
<orig> may be used alone:
<l>But this will be a <orig>meere</orig> confusion</l>
<l>And hardly shall we all be <orig>vnderstoode</orig>
</l>
|
Example | More usually, an <orig> will be combined with a regularized form within a <choice> element:
<l>But this will be a <choice>
<orig>meere</orig>
<reg>mere</reg>
</choice> confusion</l>
<l>And hardly shall we all be <choice>
<orig>vnderstoode</orig>
<reg>understood</reg>
</choice>
</l>
|
Content model |
<content> <macroRef key="macro.paraContent"/> </content> ⚓ |
Schema Declaration |
element orig { att.global.attributes, macro.paraContent }⚓ |
<p> (paragraph) marks paragraphs in prose. [3.1. Paragraphs 7.2.5. Speech Contents] | |
Module | core |
Attributes |
|
Member of | |
Contained by |
header: calendar change editionStmt editorialDecl encodingDesc langUsage licence prefixDef projectDesc publicationStmt samplingDecl sourceDesc
msdescription: msContents msDesc
namesdates: event listRelation occupation org person place population state trait
|
May contain |
core: abbr bibl choice cit corr date desc email emph expan foreign gloss graphic hi label list listBibl mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
header: idno
msdescription: msDesc
namesdates: addName affiliation district forename genName geo listEvent listOrg listPerson listPlace listRelation location orgName persName placeName population region roleName settlement state surname trait
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 }⚓ |
<pc> (punctuation character) contains a character or string of characters regarded as constituting a single punctuation mark. [17.1.2. Below the Word Level 17.4.2. Lightweight Linguistic Annotation] | |||||||||||||||||||||
Module | analysis | ||||||||||||||||||||
Attributes |
|
||||||||||||||||||||
Member of | |||||||||||||||||||||
Contained by |
core: abbr author bibl biblScope cit corr date editor email emph expan foreign gloss head hi item label mentioned name note orig p pubPlace publisher q quote ref reg rs sic soCalled term textLang title unclear
figures: cell
namesdates: addName affiliation birth death district education faith floruit forename genName gender occupation orgName persName placeName region residence roleName settlement sex surname
transcr: zone
|
||||||||||||||||||||
May contain | |||||||||||||||||||||
Example |
<phr>
<w>do</w>
<w>you</w>
<w>understand</w>
<pc type="interrogative">?</pc>
</phr>
|
||||||||||||||||||||
Example | Example encoding of the German sentence Wir fahren in den Urlaub., encoded with attributes from att.linguistic discussed in section [[undefined AILALW]].
<s>
<w pos="PPER" msd="1.Pl.*.Nom">Wir</w>
<w pos="VVFIN" msd="1.Pl.Pres.Ind">fahren</w>
<w pos="APPR" msd="--">in</w>
<w pos="ART" msd="Def.Masc.Akk.Sg.">den</w>
<w pos="NN" msd="Masc.Akk.Sg.">Urlaub</w>
<pc pos="$." msd="--" join="left">.</pc>
</s>
|
||||||||||||||||||||
Content model |
<content> <alternate minOccurs="0" maxOccurs="unbounded"> <textNode/> <classRef key="model.gLike"/> <elementRef key="c"/> <classRef key="model.pPart.edit"/> </alternate> </content> ⚓ |
||||||||||||||||||||
Schema Declaration |
element pc { att.global.attributes, att.segLike.attributes, att.typed.attributes, att.linguistic.attributes, attribute force { "strong" | "weak" | "inter" }?, attribute unit { text }?, attribute pre { text }?, ( text | model.gLike | c | model.pPart.edit )* }⚓ |
<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] | |||||||||||
Module | namesdates | ||||||||||
Attributes |
|
||||||||||
Member of | |||||||||||
Contained by | |||||||||||
May contain |
core: abbr choice cit corr date email emph expan foreign gloss graphic hi mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
character data
|
||||||||||
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.global.attributes, att.datable.attributes, att.editLike.attributes, att.personal.attributes, att.typed.attributes, attribute calendar { list { + } }?, macro.phraseSeq }⚓ |
<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] | |||||||||||||||||||||||||||||||||||||||||||||
Module | namesdates | ||||||||||||||||||||||||||||||||||||||||||||
Attributes |
|
||||||||||||||||||||||||||||||||||||||||||||
Member of | |||||||||||||||||||||||||||||||||||||||||||||
Contained by |
namesdates: listPerson org
|
||||||||||||||||||||||||||||||||||||||||||||
May contain | |||||||||||||||||||||||||||||||||||||||||||||
Note |
May contain either a prose description organized as paragraphs, or a sequence of more specific demographic elements drawn from the model.personPart class. |
||||||||||||||||||||||||||||||||||||||||||||
Example |
<person sex="F" age="adult">
<p>Female respondent, well-educated, born in Shropshire UK, 12 Jan 1950, of unknown occupation.
Speaks French fluently. Socio-Economic
status B2.</p>
</person>
|
||||||||||||||||||||||||||||||||||||||||||||
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>
|
||||||||||||||||||||||||||||||||||||||||||||
Example | The 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"> <classRef key="model.pLike" minOccurs="1" maxOccurs="unbounded"/> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.personPart"/> <classRef key="model.global"/> <elementRef key="ptr"/> </alternate> </alternate> </content> ⚓ |
||||||||||||||||||||||||||||||||||||||||||||
Schema Declaration |
element person { 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.analytic.attribute.ana, att.global.facs.attribute.facs, att.global.change.attribute.change, att.global.responsibility.attribute.cert, att.global.responsibility.attribute.resp, att.editLike.attributes, att.sortable.attributes, attribute source { list { "inferred"+ } }?, attribute role { list { + } }?, attribute sex { list { + } }?, attribute gender { list { + } }?, attribute age { text }?, ( model.pLike+ | ( model.personPart | model.global | ptr )* ) }⚓ |
<phr> (phrase) represents a grammatical phrase. [17.1. Linguistic Segment Categories] | |
Module | analysis |
Attributes |
|
Member of | |
Contained by | |
May contain |
core: abbr choice cit corr date email emph expan foreign gloss graphic hi mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
character data
|
Note |
The type attribute may be used to indicate the type of phrase, taking values such as noun, verb, preposition, etc. as appropriate. |
Example |
<phr type="verb"
function="extraposted_modifier">To talk
<phr type="preposition"
function="complement">of
<phr type="noun" function="object">many things</phr>
</phr>
</phr>
|
Content model |
<content> <macroRef key="macro.phraseSeq"/> </content> ⚓ |
Schema Declaration |
element phr { att.global.attributes, att.segLike.attributes, att.typed.attributes, att.notated.attributes, macro.phraseSeq }⚓ |
<place> (place) contains data about a geographic location [13.3.4. Places] | |
Module | namesdates |
Attributes |
|
Member of | |
Contained by | |
May contain | |
Example |
<place>
<country>Lithuania</country>
<country xml:lang="lt">Lietuva</country>
<place>
<settlement>Vilnius</settlement>
</place>
<place>
<settlement>Kaunas</settlement>
</place>
</place>
|
Content model |
<content> <sequence> <classRef key="model.headLike" minOccurs="0" maxOccurs="unbounded"/> <alternate> <classRef key="model.pLike" minOccurs="0" maxOccurs="unbounded"/> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.labelLike"/> <classRef key="model.placeStateLike"/> <classRef key="model.eventLike"/> <elementRef key="name"/> </alternate> </alternate> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.noteLike"/> <classRef key="model.biblLike"/> <elementRef key="idno"/> <elementRef key="ptr"/> <elementRef key="linkGrp"/> <elementRef key="link"/> </alternate> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.placeLike"/> <elementRef key="listPlace"/> </alternate> </sequence> </content> ⚓ |
Schema Declaration |
element place { att.global.attributes, att.typed.attributes, att.editLike.attributes, att.sortable.attributes, ( model.headLike*, ( model.pLike* | ( model.labelLike | model.placeStateLike | model.eventLike | name )* ), ( model.noteLike | model.biblLike | idno | ptr | linkGrp | link )*, ( model.placeLike | listPlace )* ) }⚓ |
<placeName> (place name) contains an absolute or relative place name. [13.2.3. Place Names] | |||||||||||||||||||||||||||||||
Module | namesdates | ||||||||||||||||||||||||||||||
Attributes |
|
||||||||||||||||||||||||||||||
Member of | |||||||||||||||||||||||||||||||
Contained by | |||||||||||||||||||||||||||||||
May contain |
core: abbr choice cit corr date email emph expan foreign gloss graphic hi mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
character data
|
||||||||||||||||||||||||||||||
Example |
<placeName>
<settlement>Rochester</settlement>
<region>New York</region>
</placeName>
|
||||||||||||||||||||||||||||||
Example |
<placeName>
<geogName>Arrochar Alps</geogName>
<region>Argylshire</region>
</placeName>
|
||||||||||||||||||||||||||||||
Example |
<placeName>
<measure>10 miles</measure>
<offset>Northeast of</offset>
<settlement>Attica</settlement>
</placeName>
|
||||||||||||||||||||||||||||||
Schematron |
<sch:rule context="tei:*[@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>
|
||||||||||||||||||||||||||||||
Content model |
<content> <macroRef key="macro.phraseSeq"/> </content> ⚓ |
||||||||||||||||||||||||||||||
Schema Declaration |
element placeName { att.datable.attributes, att.editLike.attributes, 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.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.facs.attribute.facs, att.global.change.attribute.change, att.global.responsibility.attribute.cert, att.global.responsibility.attribute.resp, att.global.source.attribute.source, att.personal.attributes, att.typed.attribute.subtype, attribute corresp { list { ( "plc:pl_bedfordshire" | "plc:pl_berkshire" | "plc:pl_buckinghamshire" | "plc:pl_cambridgeshire" | "plc:pl_cheshire" | "plc:pl_cornwall" | "plc:pl_cumberland" | "plc:pl_derbyshire" | "plc:pl_devon" | "plc:pl_dorset" | "plc:pl_durham" | "plc:pl_essex" | "plc:pl_gloucestershire" | "plc:pl_hampshire" | "plc:pl_herefordshire" | "plc:pl_hertfordshire" | "plc:pl_huntingdonshire" | "plc:pl_kent" | "plc:pl_lancashire" | "plc:pl_leicestershire" | "plc:pl_lincolnshire" | "plc:pl_london" | "plc:pl_middlesex" | "plc:pl_norfolk" | "plc:pl_northamptonshire" | "plc:pl_northumberland" | "plc:pl_nottinghamshire" | "plc:pl_oxfordshire" | "plc:pl_rutland" | "plc:pl_shropshire" | "plc:pl_somerset" | "plc:pl_staffordshire" | "plc:pl_stamford" | "plc:pl_suffolk" | "plc:pl_surrey" | "plc:pl_sussex" | "plc:pl_warwickshire" | "plc:pl_westmoreland" | "plc:pl_wiltshire" | "plc:pl_yorkshire" | "plc:pl_bristol" | "plc:pl_worcestershire" | "plc:pl_southampton" | "plc:pl_MISSING" )+ } }?, attribute type { "witness" | "jurisdiction" | "property" | "abbr" | "missing" }?, attribute calendar { list { + } }?, macro.phraseSeq }⚓ |
<population> (population) contains information about the population of a place. [13.3.4.3. States, Traits, and Events] | |||||||||||
Module | namesdates | ||||||||||
Attributes |
|
||||||||||
Member of | |||||||||||
Contained by | |||||||||||
May contain | |||||||||||
Example |
<population when="2001-04" resp="#UKCensus">
<population type="white">
<desc>54153898</desc>
</population>
<population type="asian">
<desc>11811423</desc>
</population>
<population type="black">
<desc>1148738</desc>
</population>
<population type="mixed">
<desc>677117</desc>
</population>
<population type="chinese">
<desc>247403</desc>
</population>
<population type="other">
<desc>230615</desc>
</population>
</population>
|
||||||||||
Content model |
<content> <sequence> <elementRef key="precision" minOccurs="0" maxOccurs="unbounded"/> <classRef key="model.headLike" minOccurs="0" maxOccurs="unbounded"/> <sequence minOccurs="0"> <alternate> <classRef key="model.pLike" minOccurs="1" maxOccurs="unbounded"/> <classRef key="model.labelLike" minOccurs="1" maxOccurs="unbounded"/> </alternate> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.noteLike"/> <classRef key="model.biblLike"/> </alternate> </sequence> <elementRef key="population" minOccurs="0" maxOccurs="unbounded"/> </sequence> </content> ⚓ |
||||||||||
Schema Declaration |
element population { att.global.attributes, att.datable.attributes, att.editLike.attributes, att.naming.attributes, att.typed.attributes, att.dimensions.attributes, attribute calendar { list { + } }?, ( precision*, model.headLike*, ( ( ( model.pLike+ | model.labelLike+ ), ( model.noteLike | model.biblLike )* )? ), population* ) }⚓ |
<prefixDef> (prefix definition) defines a prefixing scheme used in teidata.pointer values, showing how abbreviated URIs using the scheme may be expanded into full URIs. [16.2.3. Using Abbreviated Pointers] | |||||||||
Module | header | ||||||||
Attributes |
|
||||||||
Contained by |
header: listPrefixDef
|
||||||||
May contain |
core: p
|
||||||||
Note |
The abbreviated pointer may be dereferenced to produce either an absolute or a relative URI reference. In the latter case it is combined with the value of xml:base in force at the place where the pointing attribute occurs to form an absolute URI in the usual manner as prescribed by XML Base. |
||||||||
Example |
<prefixDef ident="ref"
matchPattern="([a-z]+)"
replacementPattern="../../references/references.xml#$1">
<p> In the context of this project, private URIs with
the prefix "ref" point to <gi>div</gi> elements in
the project's global references.xml file.
</p>
</prefixDef>
|
||||||||
Content model |
<content> <classRef key="model.pLike" minOccurs="0" maxOccurs="unbounded"/> </content> ⚓ |
||||||||
Schema Declaration |
element prefixDef { att.global.attributes, att.patternReplacement.attributes, attribute ident { text }, model.pLike* }⚓ |
<profileDesc> (text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting. [2.4. The Profile Description 2.1.1. The TEI Header and Its Components] | |
Module | header |
Attributes |
|
Member of | |
Contained by |
header: teiHeader
|
May contain |
header: calendarDesc langUsage textClass
|
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* }⚓ |
<projectDesc> (project description) describes in detail the aim or purpose for which an electronic file was encoded, together with any other relevant information concerning the process by which it was assembled or collected. [2.3.1. The Project Description 2.3. The Encoding Description 15.3.2. Declarable Elements] | |
Module | header |
Attributes |
|
Member of | |
Contained by |
header: encodingDesc
|
May contain |
core: p
|
Example |
<projectDesc>
<p>Texts collected for use in the Claremont Shakespeare Clinic, June 1990</p>
</projectDesc>
|
Content model |
<content> <classRef key="model.pLike" minOccurs="1" maxOccurs="unbounded"/> </content> ⚓ |
Schema Declaration |
element projectDesc { att.global.attributes, att.declarable.attributes, model.pLike+ }⚓ |
<ptr> (pointer) defines a pointer to another location. [3.7. Simple Links and Cross-References 16.1. Links] | |||||||||||
Module | core | ||||||||||
Attributes |
|
||||||||||
Member of | |||||||||||
Contained by | |||||||||||
May contain | Empty element | ||||||||||
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 { att.cReferencing.attributes, att.declaring.attributes, 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.facs.attribute.facs, att.global.change.attribute.change, att.global.responsibility.attribute.cert, att.global.responsibility.attribute.resp, att.global.source.attribute.source, att.internetMedia.attributes, att.pointing.attributes, att.typed.attributes, attribute ana { list { ( "state:deceased" | "trait:relational" | "rel:wife" | "rel:father" | "rel:brother" | "rel:attorney" | "rel:son" | "rel:mother" | "rel:daughter" | "rel:sister" | "rel:grandmother" | "rel:grandfather" | "rel:granddaughter" | "rel:grandson" | "rel:mother_in_law" | "rel:father_in_law" | "rel:sister_in_law" | "rel:brother_in_law" | "rel:son_in_law" | "rel:daughter_in_law" | "rel:niece" | "rel:nephew" | "rel:child_gender_unknown_" | "rel:aunt" | "rel:uncle" | "rel:cousin" | "rel:husband" | "rel:parent_gender_unknown_" | "rel:related_to" | "rel:spouse" )+ } }?, empty }⚓ |
<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] | |
Module | core |
Attributes |
|
Member of | |
Contained by |
core: bibl
header: publicationStmt
|
May contain |
core: abbr choice cit corr date email emph expan foreign gloss graphic hi mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
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 }⚓ |
<publicationStmt> (publication statement) groups information concerning the publication or distribution of an electronic or other text. [2.2.4. Publication, Distribution, Licensing, etc. 2.2. The File Description] | |
Module | header |
Attributes |
|
Contained by |
header: fileDesc
|
May contain | |
Note |
Where a publication statement contains several members of the model.publicationStmtPart.agency or model.publicationStmtPart.detail classes rather than one or more paragraphs or anonymous blocks, care should be taken to ensure that the repeated elements are presented in a meaningful order. It is a conformance requirement that elements supplying information about publication place, address, identifier, availability, and date be given following the name of the publisher, distributor, or authority concerned, and preferably in that order. |
Example |
<publicationStmt>
<publisher>C. Muquardt </publisher>
<pubPlace>Bruxelles & Leipzig</pubPlace>
<date when="1846"/>
</publicationStmt>
|
Example |
<publicationStmt>
<publisher>Chadwyck Healey</publisher>
<pubPlace>Cambridge</pubPlace>
<availability>
<p>Available under licence only</p>
</availability>
<date when="1992">1992</date>
</publicationStmt>
|
Example |
<publicationStmt>
<publisher>Zea Books</publisher>
<pubPlace>Lincoln, NE</pubPlace>
<date>2017</date>
<availability>
<p>This is an open access work licensed under a Creative Commons Attribution 4.0 International
license.</p>
</availability>
<ptr target="http://digitalcommons.unl.edu/zeabook/55"/>
</publicationStmt>
|
Content model |
<content> <alternate> <sequence minOccurs="1" maxOccurs="unbounded"> <classRef key="model.publicationStmtPart.agency"/> <classRef key="model.publicationStmtPart.detail" minOccurs="0" maxOccurs="unbounded"/> </sequence> <classRef key="model.pLike" minOccurs="1" maxOccurs="unbounded"/> </alternate> </content> ⚓ |
Schema Declaration |
element publicationStmt { att.global.attributes, ( ( ( model.publicationStmtPart.agency, model.publicationStmtPart.detail* )+ ) | model.pLike+ ) }⚓ |
<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.] | |
Module | core |
Attributes |
|
Member of | |
Contained by |
core: bibl
header: publicationStmt
|
May contain |
core: abbr choice cit corr date email emph expan foreign gloss graphic hi mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
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 }⚓ |
<q> (quoted) contains material which is distinguished from the surrounding text using quotation marks or a similar method, for any one of a variety of reasons including, but not limited to: direct speech or thought, technical terms or jargon, authorial distance, quotations from elsewhere, and passages that are mentioned but not used. [3.3.3. Quotation] | |||||||||
Module | core | ||||||||
Attributes |
|
||||||||
Member of | |||||||||
Contained by |
core: abbr author bibl biblScope cit corr date desc editor email emph expan foreign gloss head hi item label mentioned name note orig p pubPlace publisher q quote ref reg resp rs sic soCalled term textLang title unclear
msdescription: repository
namesdates: addName affiliation age birth death district education faith floruit forename genName gender langKnown occupation orgName persName placeName region residence roleName settlement sex surname
transcr: zone
|
||||||||
May contain |
core: abbr bibl choice cit corr date desc email emph expan foreign gloss graphic hi label list listBibl mentioned name note orig p ptr q quote ref reg sic soCalled term title unclear
header: idno
msdescription: msDesc
namesdates: addName affiliation district forename genName geo listEvent listOrg listPerson listPlace listRelation location orgName persName placeName population region roleName settlement state surname trait
character data
|
||||||||
Note |
May be used to indicate that a passage is distinguished from the surrounding text for reasons concerning which no claim is made. When used in this manner, <q> may be thought of as syntactic sugar for <hi> with a value of rend that indicates the use of such mechanisms as quotation marks. |
||||||||
Example |
It is spelled <q>Tübingen</q> — to enter the
letter <q>u</q> with an umlaut hold down the <q>option</q> key and press
<q>0 0 f c</q>
|
||||||||
Content model |
<content> <macroRef key="macro.specialPara"/> </content> ⚓ |
||||||||
Schema Declaration |
element q { att.global.attributes, att.ascribed.directed.attributes, attribute type { "spoken" | "thought" | "written" | "soCalled" | "foreign" | "distinct" | "term" | "emph" | "mentioned" }?, macro.specialPara }⚓ |
<quote> (quotation) contains a phrase or passage attributed by the narrator or author to some agency external to the text. [3.3.3. Quotation 4.3.1. Grouped Texts] | |
Module | core |
Attributes |
|
Member of | |
Contained by |
core: abbr author biblScope cit corr desc editor email emph expan foreign gloss head hi item label mentioned name note orig p pubPlace publisher q quote ref reg rs sic soCalled term textLang title unclear
|
May contain |
core: abbr bibl choice cit corr date desc email emph expan foreign gloss graphic hi label list listBibl mentioned name note orig p ptr q quote ref reg sic soCalled term title unclear
header: idno
msdescription: msDesc
namesdates: addName affiliation district forename genName geo listEvent listOrg listPerson listPlace listRelation location orgName persName placeName population region roleName settlement state surname trait
character data
|
Note |
If a bibliographic citation is supplied for the source of a quotation, the two may be grouped using the <cit> element. |
Example |
Lexicography has shown little sign of being affected by the
work of followers of J.R. Firth, probably best summarized in his
slogan, <quote>You shall know a word by the company it
keeps</quote>
<ref>(Firth, 1957)</ref>
|
Content model |
<content> <macroRef key="macro.specialPara"/> </content> ⚓ |
Schema Declaration |
element quote { att.global.attributes, att.typed.attributes, att.msExcerpt.attributes, att.notated.attributes, macro.specialPara }⚓ |
<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] | |
Module | core |
Attributes |
|
Member of | |
Contained by | |
May contain |
core: abbr bibl choice cit corr date desc email emph expan foreign gloss graphic hi label list listBibl mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
header: idno
msdescription: msDesc
namesdates: addName affiliation district forename genName geo listEvent listOrg listPerson listPlace listRelation location orgName persName placeName population region roleName settlement state surname trait
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 }⚓ |
<reg> (regularization) contains a reading which has been regularized or normalized in some sense. [3.5.2. Regularization and Normalization 12. Critical Apparatus] | |
Module | core |
Attributes |
|
Member of | |
Contained by | |
May contain |
core: abbr bibl choice cit corr date desc email emph expan foreign gloss graphic hi label list listBibl mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
header: idno
msdescription: msDesc
namesdates: addName affiliation district forename genName geo listEvent listOrg listPerson listPlace listRelation location orgName persName placeName population region roleName settlement state surname trait
character data
|
Example | If all that is desired is to call attention to the fact that the copy text has been
regularized, <reg> may be used alone:
<q>Please <reg>knock</reg> if an <reg>answer</reg> is <reg>required</reg>
</q>
|
Example | It is also possible to identify the individual responsible for the regularization,
and, using the <choice> and <orig> elements, to provide both the original and regularized readings:
<q>Please <choice>
<reg resp="#LB">knock</reg>
<orig>cnk</orig>
</choice> if an <choice>
<reg>answer</reg>
<orig>nsr</orig>
</choice> is <choice>
<reg>required</reg>
<orig>reqd</orig>
</choice>
</q>
|
Content model |
<content> <macroRef key="macro.paraContent"/> </content> ⚓ |
Schema Declaration |
element reg { att.global.attributes, att.editLike.attributes, att.typed.attributes, macro.paraContent }⚓ |
<region> (region) contains the name of an administrative unit such as a state, province, or county, larger than a settlement, but smaller than a country. [13.2.3. Place Names] | |||||||||||
Module | namesdates | ||||||||||
Attributes |
|
||||||||||
Member of | |||||||||||
Contained by | |||||||||||
May contain |
core: abbr choice cit corr date email emph expan foreign gloss graphic hi mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
character data
|
||||||||||
Example |
<placeName>
<region type="state" n="IL">Illinois</region>
</placeName>
|
||||||||||
Content model |
<content> <macroRef key="macro.phraseSeq"/> </content> ⚓ |
||||||||||
Schema Declaration |
element region { att.global.attributes, att.naming.attributes, att.typed.attributes, att.datable.attributes, attribute calendar { list { + } }?, macro.phraseSeq }⚓ |
<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] | |||||||||||||||||||||||||||||||||||||
Module | namesdates | ||||||||||||||||||||||||||||||||||||
Attributes |
|
||||||||||||||||||||||||||||||||||||
Contained by |
core: listBibl
namesdates: listEvent listOrg listPlace listRelation
|
||||||||||||||||||||||||||||||||||||
May contain |
core: desc
|
||||||||||||||||||||||||||||||||||||
Note |
Only one of the attributes active and mutual may be supplied; the attribute passive may be supplied only if the attribute active is supplied. Not all of these constraints can be enforced in all schema languages. |
||||||||||||||||||||||||||||||||||||
Example |
<relation type="social" name="supervisor"
active="#p1" passive="#p2 #p3 #p4"/> This indicates that the person with identifier p1 is supervisor of persons p2, p3,
and p4. |
||||||||||||||||||||||||||||||||||||
Example |
<relation type="personal" name="friends"
mutual="#p2 #p3 #p4"/> This indicates that p2, p3, and p4 are all friends. |
||||||||||||||||||||||||||||||||||||
Example |
<relation type="CRM"
name="P89_falls_within"
active="http://id.clarosnet.org/places/metamorphoses/place/italy-orvieto"
passive="http://id.clarosnet.org/places/metamorphoses/country/IT"/> This indicates that there is a relation, defined by CIDOC CRM, between two resources
identified by URLs. |
||||||||||||||||||||||||||||||||||||
Example |
<relation resp="http://viaf.org/viaf/44335536/"
ref="http://purl.org/saws/ontology#isVariantOf"
active="http://www.ancientwisdoms.ac.uk/cts/urn:cts:greekLit:tlg3017.Syno298.sawsGrc01:divedition.divsection1.o14.a107"
passive="http://data.perseus.org/citations/urn:cts:greekLit:tlg0031.tlg002.perseus-grc1:9.35"/> This example records a relationship, defined by the SAWS ontology, between a passage
of text identified by a CTS URN, and a variant passage of text in the Perseus Digital
Library, and assigns the identification of the relationship to a particular editor
(all using resolvable URIs). |
||||||||||||||||||||||||||||||||||||
Schematron |
<sch:rule context="tei:relation[ancestor::tei:event or ancestor::tei:TEI[@xml:id='relations_unattested']]">
<sch:assert test="@active lt @passive"> ERROR: The content of the @active attribute
must come before
the @passive attribute alphabetically. Please invert this
relationship to use the canonical format.
</sch:assert>
</sch:rule>
|
||||||||||||||||||||||||||||||||||||
Schematron |
<sch:rule context="tei:relation">
<sch:assert test="@active and matches(@active, '^pros:[a-z]{4,4}\d+(_((spouse)|(child)))?$')">
ERROR: The @active attribute must contain a pointer to a prosopography
entry in the form: pros:abcd12.
</sch:assert>
</sch:rule>
<sch:rule context="tei:relation">
<sch:assert test="@passive and matches(@passive, '^pros:[a-z]{4,4}\d+$')"> ERROR:
The @passive attribute must contain a pointer to a prosopography
entry in the form: pros:abcd12.
</sch:assert>
</sch:rule>
|
||||||||||||||||||||||||||||||||||||
Schematron |
<sch:rule context="tei:relation">
<sch:let name="strRendering"
value="concat(@name, '|', @active, '|', @passive)"/>
<sch:assert test="not(preceding-sibling::tei:relation[concat(@name, '|', @active,
'|',
@passive) = $strRendering])"> ERROR: A relation element encoding this relationship
already exists.
</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>
|
||||||||||||||||||||||||||||||||||||
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>
|
||||||||||||||||||||||||||||||||||||
Content model |
<content> <elementRef key="desc" minOccurs="0"/> </content> ⚓ |
||||||||||||||||||||||||||||||||||||
Schema Declaration |
element relation { att.global.attributes, att.datable.attributes, att.editLike.attributes, att.canonical.attributes, att.sortable.attributes, att.typed.attributes, ( attribute active { list { + } }? | attribute mutual { list { + } }? ), attribute calendar { list { + } }?, attribute name { "wife" | "sister" | "grandmother" | "grandfather" | "granddaughter" | "grandson" | "mother_in_law" | "father_in_law" | "sister_in_law" | "brother_in_law" | "father" | "son_in_law" | "daughter_in_law" | "niece" | "nephew" | "child_gender_unknown_" | "aunt" | "uncle" | "cousin" | "brother" | "husband" | "parent_gender_unknown_" | "related_to" | "spouse" | "attorney" | "son" | "mother" | "daughter" }, attribute passive { list { + } }?, desc? }⚓ |
<repository> (repository) contains the name of a repository within which manuscripts or other objects are stored, possibly forming part of an institution. [10.4. The Manuscript Identifier] | |
Module | msdescription |
Attributes |
|
Contained by |
msdescription: msIdentifier
|
May contain |
core: abbr choice date email emph expan foreign gloss hi mentioned name note ptr q ref soCalled term title
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
character data
|
Example |
<msIdentifier>
<settlement>Oxford</settlement>
<institution>University of Oxford</institution>
<repository>Bodleian Library</repository>
<idno>MS. Bodley 406</idno>
</msIdentifier>
|
Content model |
<content> <macroRef key="macro.phraseSeq.limited"/> </content> ⚓ |
Schema Declaration |
element repository { att.global.attributes, att.naming.attributes, macro.phraseSeq.limited }⚓ |
<residence> (residence) describes a person's present or past places of residence. [15.2.2. The Participant Description] | |||||||||||||||||||
Module | namesdates | ||||||||||||||||||
Attributes |
|
||||||||||||||||||
Member of | |||||||||||||||||||
Contained by |
namesdates: person
|
||||||||||||||||||
May contain |
core: abbr choice cit corr date email emph expan foreign gloss graphic hi mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
character data
|
||||||||||||||||||
Example |
<residence>Childhood in East Africa and long term resident of Glasgow, Scotland.</residence>
|
||||||||||||||||||
Example |
<residence notAfter="1997">Mbeni estate, Dzukumura region, Matabele land</residence>
<residence notBefore="1903" notAfter="1996">
<placeName>
<settlement>Glasgow</settlement>
<region>Scotland</region>
</placeName>
</residence>
|
||||||||||||||||||
Content model |
<content> <macroRef key="macro.phraseSeq"/> </content> ⚓ |
||||||||||||||||||
Schema Declaration |
element residence { att.global.attributes, att.datable.attributes, att.editLike.attributes, att.naming.attributes, att.typed.attribute.subtype, attribute type { text }?, attribute calendar { list { + } }?, macro.phraseSeq }⚓ |
<resp> (responsibility) contains a phrase describing the nature of a person's intellectual responsibility, or an organization's role in the production or distribution of a work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement] | |||||||||||
Module | core | ||||||||||
Attributes |
|
||||||||||
Contained by |
core: respStmt
|
||||||||||
May contain |
core: abbr choice date email emph expan foreign gloss hi mentioned name note ptr q ref soCalled term title
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
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, attribute calendar { list { + } }?, macro.phraseSeq.limited }⚓ |
<respStmt> (statement of responsibility) supplies a statement of responsibility for the intellectual content of a text, edition, recording, or series, where the specialized elements for authors, editors, etc. do not suffice or do not apply. May also be used to encode information about individuals or organizations which have played a role in the production or distribution of a bibliographic work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement] | |
Module | core |
Attributes |
|
Member of | |
Contained by |
header: editionStmt titleStmt
|
May contain | |
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* ) }⚓ |
<revisionDesc> (revision description) summarizes the revision history for a file. [2.6. The Revision Description 2.1.1. The TEI Header and Its Components] | |
Module | header |
Attributes |
|
Contained by |
header: teiHeader
|
May contain | |
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> <alternate> <elementRef key="list" minOccurs="1" maxOccurs="unbounded"/> <elementRef key="listChange" minOccurs="1" maxOccurs="unbounded"/> <elementRef key="change" minOccurs="1" maxOccurs="unbounded"/> </alternate> </content> ⚓ |
Schema Declaration |
element revisionDesc { att.global.attributes, att.docStatus.attributes, ( list+ | listChange+ | change+ ) }⚓ |
<roleName> (role name) contains a name component which indicates that the referent has a particular role or position in society, such as an official title or rank. [13.2.1. Personal Names] | |
Module | namesdates |
Attributes |
|
Member of | |
Contained by | |
May contain |
core: abbr choice cit corr date email emph expan foreign gloss graphic hi mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
character data
|
Note |
A <roleName> may be distinguished from an <addName> by virtue of the fact that, like a title, it typically exists independently of its holder. |
Example |
<persName>
<forename>William</forename>
<surname>Poulteny</surname>
<roleName>Earl of Bath</roleName>
</persName>
|
Example |
<p>The <roleName role="solicitor_general">S.G.</roleName> is the only national public official,
including the Supreme Court justices, required by statute to be “learned in the law.”</p>
|
Example |
<p>
<persName ref="#NJF">
<roleName role="solicitor_general">Solicitor General</roleName> Noel J. Francisco</persName>,
representing the administration, asserted in rebuttal that there was nothing to disavow
(...)
<persName ref="#NJF">Francisco</persName> had violated the scrupulous standard of candor about the facts and
the law that <roleName role="solicitor_general">S.G.s</roleName>, in Republican and Democratic administrations
alike, have repeatedly said they must honor.
</p>
|
Content model |
<content> <macroRef key="macro.phraseSeq"/> </content> ⚓ |
Schema Declaration |
element roleName { att.global.attributes, att.personal.attributes, att.typed.attributes, macro.phraseSeq }⚓ |
<row> (row) contains one row of a table. [14.1.1. TEI Tables] | |
Module | figures |
Attributes |
|
Contained by |
figures: table
|
May contain |
figures: cell
|
Example |
<row role="data">
<cell role="label">Classics</cell>
<cell>Idle listless and unimproving</cell>
</row>
|
Content model |
<content> <elementRef key="cell" minOccurs="1" maxOccurs="unbounded"/> </content> ⚓ |
Schema Declaration |
element row { att.global.attributes, att.tableDecoration.attributes, cell+ }⚓ |
<rs> (referencing string) contains a general purpose name or referring string. [13.2.1. Personal Names 3.6.1. Referring Strings] | |
Module | core |
Member of | |
Contained by | |
May contain |
core: abbr choice cit corr date email emph expan foreign gloss graphic hi mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
character data
|
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>
|
Content model |
<content> <macroRef key="macro.phraseSeq"/> </content> ⚓ |
Schema Declaration |
element rs { macro.phraseSeq }⚓ |
<s> (s-unit) contains a sentence-like division of a text. [17.1. Linguistic Segment Categories 8.4.1. Segmentation] | |
Module | analysis |
Attributes |
|
Member of | |
Contained by | |
May contain |
core: abbr choice cit corr date email emph expan foreign gloss graphic hi mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
character data
|
Note |
The <s> element may be used to mark orthographic sentences, or any other segmentation of a text, provided that the segmentation is end-to-end, complete, and non-nesting. For segmentation which is partial or recursive, the <seg> should be used instead. The type attribute may be used to indicate the type of segmentation intended, according to any convenient typology. |
Example |
<head>
<s>A short affair</s>
</head>
<s>When are you leaving?</s>
<s>Tomorrow.</s>
|
Schematron |
<sch:report test="tei:s">You may not nest one s element within
another: use seg instead</sch:report>
|
Content model |
<content> <macroRef key="macro.phraseSeq"/> </content> ⚓ |
Schema Declaration |
element s { att.global.attributes, att.segLike.attributes, att.typed.attributes, att.notated.attributes, macro.phraseSeq }⚓ |
<samplingDecl> (sampling declaration) contains a prose description of the rationale and methods used in selecting texts, or parts of a text, for inclusion in the resource. [2.3.2. The Sampling Declaration 2.3. The Encoding Description 15.3.2. Declarable Elements] | |
Module | header |
Attributes |
|
Member of | |
Contained by |
header: encodingDesc
|
May contain |
core: p
|
Note |
This element records all information about systematic inclusion or omission of portions of the text, whether a reflection of sampling procedures in the pure sense or of systematic omission of material deemed either too difficult to transcribe or not of sufficient interest. |
Example |
<samplingDecl>
<p>Samples of up to 2000 words taken at random from the beginning, middle, or end of
each
text identified as relevant by respondents.</p>
</samplingDecl>
|
Content model |
<content> <classRef key="model.pLike" minOccurs="1" maxOccurs="unbounded"/> </content> ⚓ |
Schema Declaration |
element samplingDecl { att.global.attributes, att.declarable.attributes, model.pLike+ }⚓ |
<series> (series information) contains information about the series in which a book or other bibliographic item has appeared. [3.12.2.1. Analytic, Monographic, and Series Levels] | |
Module | core |
Attributes |
|
Member of | |
Contained by |
core: bibl
|
May contain | |
Example |
<series xml:lang="de">
<title level="s">Halbgraue Reihe zur Historischen Fachinformatik</title>
<respStmt>
<resp>Herausgegeben von</resp>
<name type="person">Manfred Thaller</name>
<name type="org">Max-Planck-Institut für Geschichte</name>
</respStmt>
<title level="s">Serie A: Historische Quellenkunden</title>
<biblScope>Band 11</biblScope>
</series>
|
Content model |
<content> <alternate minOccurs="0" maxOccurs="unbounded"> <textNode/> <classRef key="model.gLike"/> <elementRef key="title"/> <classRef key="model.ptrLike"/> <elementRef key="editor"/> <elementRef key="respStmt"/> <elementRef key="biblScope"/> <elementRef key="idno"/> <elementRef key="textLang"/> <classRef key="model.global"/> <elementRef key="availability"/> </alternate> </content> ⚓ |
Schema Declaration |
element series { att.global.attributes, ( text | model.gLike | title | model.ptrLike | editor | respStmt | biblScope | idno | textLang | model.global | availability )* }⚓ |
<settlement> (settlement) contains the name of a settlement such as a city, town, or village identified as a single geo-political or administrative unit. [13.2.3. Place Names] | |||||||||||
Module | namesdates | ||||||||||
Attributes |
|
||||||||||
Member of | |||||||||||
Contained by | |||||||||||
May contain |
core: abbr choice cit corr date email emph expan foreign gloss graphic hi mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
character data
|
||||||||||
Example |
<placeName>
<settlement type="town">Glasgow</settlement>
<region>Scotland</region>
</placeName>
|
||||||||||
Content model |
<content> <macroRef key="macro.phraseSeq"/> </content> ⚓ |
||||||||||
Schema Declaration |
element settlement { att.global.attributes, att.naming.attributes, att.typed.attributes, att.datable.attributes, attribute calendar { list { + } }?, macro.phraseSeq }⚓ |
<sex> (sex) specifies the sex of an organism. [13.3.2.1. Personal Characteristics] | |||||||||||||||||||
Module | namesdates | ||||||||||||||||||
Attributes |
|
||||||||||||||||||
Member of | |||||||||||||||||||
Contained by |
namesdates: person
|
||||||||||||||||||
May contain |
core: abbr choice cit corr date email emph expan foreign gloss graphic hi mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
character data
|
||||||||||||||||||
Note |
As with other culturally-constructed traits such as age and gender, the way in which this concept is described in different cultural contexts varies. The normalizing attributes are provided only as an optional means of simplifying that variety for purposes of interoperability or project-internal taxonomies for consistency, and should not be used where that is inappropriate or unhelpful. The content of the element may be used to describe the intended concept in more detail. |
||||||||||||||||||
Example |
<sex value="F">female</sex>
|
||||||||||||||||||
Example |
<sex value="I">Intersex</sex>
|
||||||||||||||||||
Example |
<sex value="TG F">Female (TransWoman)</sex>
|
||||||||||||||||||
Content model |
<content> <macroRef key="macro.phraseSeq"/> </content> ⚓ |
||||||||||||||||||
Schema Declaration |
element sex { att.global.attributes, att.editLike.attributes, att.datable.attributes, att.typed.attributes, attribute calendar { list { + } }?, attribute value { list { + } }?, macro.phraseSeq }⚓ |
<sic> (Latin for thus or so) contains text reproduced although apparently incorrect or inaccurate. [3.5.1. Apparent Errors] | |
Module | core |
Attributes |
|
Member of | |
Contained by | |
May contain |
core: abbr bibl choice cit corr date desc email emph expan foreign gloss graphic hi label list listBibl mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
header: idno
msdescription: msDesc
namesdates: addName affiliation district forename genName geo listEvent listOrg listPerson listPlace listRelation location orgName persName placeName population region roleName settlement state surname trait
character data
|
Example |
for his nose was as sharp as
a pen, and <sic>a Table</sic> of green fields.
|
Example | If all that is desired is to call attention to the apparent problem in the copy text,
<sic> may be used alone:
I don't know, Juan. It's so far in the past now
— how <sic>we can</sic> prove or disprove anyone's theories?
|
Example | It is also possible, using the <choice> and <corr> elements, to provide a corrected reading:
I don't know, Juan. It's so far in the past now
— how <choice>
<sic>we can</sic>
<corr>can we</corr>
</choice> prove or disprove anyone's theories?
|
Example |
for his nose was as sharp as
a pen, and <choice>
<sic>a Table</sic>
<corr>a' babbld</corr>
</choice> of green fields.
|
Content model |
<content> <macroRef key="macro.paraContent"/> </content> ⚓ |
Schema Declaration |
element sic { att.global.attributes, macro.paraContent }⚓ |
<soCalled> (so called) contains a word or phrase for which the author or narrator indicates a disclaiming of responsibility, for example by the use of scare quotes or italics. [3.3.3. Quotation] | |
Module | core |
Attributes |
|
Member of | |
Contained by | |
May contain |
core: abbr choice cit corr date email emph expan foreign gloss graphic hi mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
character data
|
Example |
To edge his way along
the crowded paths of life, warning all human sympathy to keep its distance, was what
the
knowing ones call <soCalled>nuts</soCalled> to Scrooge.
|
Content model |
<content> <macroRef key="macro.phraseSeq"/> </content> ⚓ |
Schema Declaration |
element soCalled { att.global.attributes, macro.phraseSeq }⚓ |
<sourceDesc> (source description) describes the source(s) from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as "born digital" for a text which has no previous existence. [2.2.7. The Source Description] | |
Module | header |
Attributes |
|
Contained by |
header: fileDesc
|
May contain | |
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> <alternate> <classRef key="model.pLike" minOccurs="1" maxOccurs="unbounded"/> <alternate minOccurs="1" maxOccurs="unbounded"> <classRef key="model.biblLike"/> <classRef key="model.sourceDescPart"/> <classRef key="model.listLike"/> </alternate> </alternate> </content> ⚓ |
Schema Declaration |
element sourceDesc { att.global.attributes, att.declarable.attributes, ( model.pLike+ | ( model.biblLike | model.sourceDescPart | model.listLike )+ ) }⚓ |
<span> associates an interpretative annotation directly with a span of text. [17.3. Spans and Interpretations] | |||||||||||||
Module | analysis | ||||||||||||
Attributes |
|
||||||||||||
Member of | |||||||||||||
Contained by |
core: abbr author bibl biblScope cit corr date editor email emph expan foreign gloss head hi item label list mentioned name note orig p pubPlace publisher q quote ref reg resp rs series sic soCalled term textLang title unclear
linking: standOff
msdescription: repository
|
||||||||||||
May contain |
core: abbr choice date email emph expan foreign gloss hi mentioned name note ptr q ref soCalled term title
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
character data
|
||||||||||||
Example |
<p xml:id="para2">(The "aftermath" starts here)</p>
<p xml:id="para3">(The "aftermath" continues here)</p>
<p xml:id="para4">(The "aftermath" ends in this paragraph)</p>
<!-- ... -->
<span type="structure" from="#para2"
to="#para4">aftermath</span>
|
||||||||||||
Schematron |
<sch:report test="@from and @target">Only one of the attributes @target and @from
may be supplied on <sch:name/>
</sch:report>
|
||||||||||||
Schematron |
<sch:report test="@to and @target">Only one of the attributes @target and @to may
be supplied on <sch:name/>
</sch:report>
|
||||||||||||
Schematron |
<sch:report test="@to and not(@from)">If @to is supplied on <sch:name/>, @from must
be supplied as well</sch:report>
|
||||||||||||
Schematron |
<sch:report test="contains(normalize-space(@to),' ') or contains(normalize-space(@from),'
')">The attributes @to and @from on <sch:name/> may each contain only a single value</sch:report>
|
||||||||||||
Content model |
<content> <macroRef key="macro.phraseSeq.limited"/> </content> ⚓ |
||||||||||||
Schema Declaration |
element span { att.global.attributes, att.interpLike.attributes, att.pointing.attributes, attribute from { text }?, attribute to { text }?, macro.phraseSeq.limited }⚓ |
<spanGrp> (span group) collects together span tags. [17.3. Spans and Interpretations] | |
Module | analysis |
Attributes |
|
Member of | |
Contained by |
core: abbr author bibl biblScope cit corr date editor email emph expan foreign gloss head hi item label list mentioned name note orig p pubPlace publisher q quote ref reg resp rs series sic soCalled term textLang title unclear
linking: standOff
msdescription: repository
|
May contain | |
Example |
<u xml:id="UU1">Can I have ten oranges and a kilo of bananas please?</u>
<u xml:id="UU2">Yes, anything else?</u>
<u xml:id="UU3">No thanks.</u>
<u xml:id="UU4">That'll be dollar forty.</u>
<u xml:id="UU5">Two dollars</u>
<u xml:id="UU6">Sixty, eighty, two dollars.
<anchor xml:id="UU6e"/>Thank you.<anchor xml:id="UU6f"/>
</u>
<spanGrp type="transactions">
<span from="#UU1">sale request</span>
<span from="#UU2" to="#UU3">sale compliance</span>
<span from="#UU4">sale</span>
<span from="#UU5" to="#UU6">purchase</span>
<span from="#UU6e" to="#UU6f">purchase closure</span>
</spanGrp>
|
Content model |
<content> <sequence> <classRef key="model.descLike" minOccurs="0" maxOccurs="unbounded"/> <elementRef key="span" minOccurs="0" maxOccurs="unbounded"/> </sequence> </content> ⚓ |
Schema Declaration |
element spanGrp { att.global.attributes, att.interpLike.attributes, ( model.descLike*, span* ) }⚓ |
<standOff> Functions as a container element for linked data, contextual information, and stand-off annotations embedded in a TEI document. [16.10. The standOff Container] | |
Module | linking |
Attributes |
|
Member of | |
Contained by |
textstructure: TEI
|
May contain | |
Example | This example shows an encoding of morphosyntactic features similar to the encoding
system used by ISO 24611 (MAF).
<TEI xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>
<!-- ... -->
</teiHeader>
<text>
<body>
<!-- ... -->
<p>
<w xml:id="w51">I</w>
<w xml:id="w52">wanna</w>
<w xml:id="w53">put</w>
<w xml:id="w54">up</w>
<w xml:id="w55">new</w>
<w xml:id="w56">wallpaper</w>
<pc>.</pc>
</p>
<!-- ... -->
</body>
</text>
<standOff type="morphosyntax">
<spanGrp type="wordForm">
<span target="#w51" ana="#fs01"/>
<span target="#w52" ana="#fs02"/>
<span target="#w52" ana="#fs03"/>
<span target="#w53 #w54" ana="#fs04"/>
<span target="#w55" ana="#fs05"/>
<span target="#w56" ana="#fs06"/>
</spanGrp>
<fs xml:id="fs01">
<f name="lemma">
<string>I</string>
</f>
<f name="pos">
<symbol value="PP"/>
</f>
</fs>
<fs xml:id="fs02">
<f name="lemma">
<string>want</string>
</f>
<f name="pos">
<symbol value="VBP"/>
</f>
</fs>
<fs xml:id="fs03">
<f name="lemma">
<string>to</string>
</f>
<f name="pos">
<symbol value="TO"/>
</f>
</fs>
<fs xml:id="fs04">
<f name="lemma">
<string>put up</string>
</f>
<f name="pos">
<symbol value="VB"/>
</f>
</fs>
<fs xml:id="fs05">
<f name="lemma">
<string>new</string>
</f>
<f name="pos">
<symbol value="JJ"/>
</f>
</fs>
<fs xml:id="fs06">
<f name="lemma">
<string>wallpaper</string>
</f>
<f name="pos">
<symbol value="NN"/>
</f>
</fs>
</standOff>
</TEI>
|
Example | This example shows an encoding of contextual information which is referred to from
the main text.
<TEI xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>
<!-- ... -->
</teiHeader>
<standOff>
<listPlace>
<place xml:id="LATL">
<placeName>Atlanta</placeName>
<location>
<region key="US-GA">Georgia</region>
<country key="USA">United States of America</country>
<geo>33.755 -84.39</geo>
</location>
<population when="1963"
type="interpolatedCensus" quantity="489359"
source="https://www.biggestuscities.com/city/atlanta-georgia"/>
</place>
<place xml:id="LBHM">
<placeName>Birmingham</placeName>
<location>
<region key="US-AL">Alabama</region>
<country key="USA">United States of America</country>
<geo>33.653333 -86.808889</geo>
</location>
<population when="1963"
type="interpolatedCensus" quantity="332891"
source="https://www.biggestuscities.com/city/birmingham-alabama"/>
</place>
</listPlace>
</standOff>
<text>
<body>
<!-- ... -->
<p>Moreover, I am <choice>
<sic>congnizant</sic>
<corr>cognizant</corr>
</choice> of the interrelatedness of all communities and
<lb/>states. I cannot sit idly by in <placeName ref="#LATL">Atlanta</placeName> and not be concerned about what happens
<lb/>in <placeName ref="#LBHM">Birmingham</placeName>. <seg xml:id="FQ17">Injustice anywhere is a threat to justice everywhere.</seg> We
<lb/>are caught in an inescapable network of mutuality, tied in a single garment
<lb/>of destiny. Whatever affects one directly affects all indirectly. Never
<lb/>again can we afford to live with the narrow, provincial <soCalled rendition="#Rqms">outside agitator</soCalled>
<lb/>idea. Anyone who lives inside the United States can never be considered
<lb/>an outsider anywhere in this country.</p>
<!-- ... -->
</body>
</text>
</TEI>
|
Schematron |
<sch:assert test="@type or not(ancestor::tei:standOff)">This
<sch:name/> element must have a @type attribute, since it is
nested inside a <sch:name/>
</sch:assert>
|
Content model |
<content> <classRef key="model.standOffPart" minOccurs="1" maxOccurs="unbounded"/> </content> ⚓ |
Schema Declaration |
element standOff { att.global.attributes, att.typed.attributes, att.declaring.attributes, model.standOffPart+ }⚓ |
<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] | |||||||||||
Module | namesdates | ||||||||||
Attributes |
|
||||||||||
Member of | |||||||||||
Contained by | |||||||||||
May contain | |||||||||||
Note |
Where there is confusion between <trait> and <state> the more general purpose element <state> should be used even for unchanging characteristics. If you wish to distinguish between characteristics that are generally perceived to be time-bound states and those assumed to be fixed traits, then <trait> is available for the more static of these. The <state> element encodes characteristics which are sometimes assumed to change, often at specific times or over a date range, whereas the <trait> elements are used to record characteristics, such as eye-colour, which are less subject to change. Traits are typically, but not necessarily, independent of the volition or action of the holder. |
||||||||||
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> <sequence> <elementRef key="precision" minOccurs="0" maxOccurs="unbounded"/> <alternate> <elementRef key="state" minOccurs="1" maxOccurs="unbounded"/> <sequence> <classRef key="model.headLike" minOccurs="0" maxOccurs="unbounded"/> <classRef key="model.pLike" minOccurs="1" maxOccurs="unbounded"/> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.noteLike"/> <classRef key="model.biblLike"/> </alternate> </sequence> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.labelLike"/> <classRef key="model.noteLike"/> <classRef key="model.biblLike"/> </alternate> </alternate> </sequence> </content> ⚓ |
||||||||||
Schema Declaration |
element state { att.global.attributes, att.datable.attributes, att.editLike.attributes, att.typed.attributes, att.naming.attributes, att.dimensions.attributes, attribute calendar { list { + } }?, ( precision*, ( state+ | ( model.headLike*, model.pLike+, ( model.noteLike | model.biblLike )* ) | ( model.labelLike | model.noteLike | model.biblLike )* ) ) }⚓ |
<surface> defines a written surface as a two-dimensional coordinate space, optionally grouping one or more graphic representations of that space, zones of interest within that space, and, when using an embedded transcription approach, transcriptions of the writing within them. [11.1. Digital Facsimiles 11.2.2. Embedded Transcription] | |||||||||||||||
Module | transcr | ||||||||||||||
Attributes |
|
||||||||||||||
Contained by | |||||||||||||||
May contain | |||||||||||||||
Note |
The <surface> element represents any two-dimensional space on some physical surface forming part of the source material, such as a piece of paper, a face of a monument, a billboard, a scroll, a leaf etc. The coordinate space defined by this element may be thought of as a grid lrx - ulx units wide and uly - lry units high. The <surface> element may contain graphic representations or transcriptions of written zones, or both. The coordinate values used by every <zone> element contained by this element are to be understood with reference to the same grid. Where it is useful or meaningful to do so, any grouping of multiple <surface> elements may be indicated using the <surfaceGrp> element. |
||||||||||||||
Example |
<facsimile>
<surface ulx="0" uly="0" lrx="200" lry="300">
<graphic url="Bovelles-49r.png"/>
</surface>
</facsimile>
|
||||||||||||||
Content model |
<content> <sequence> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.global"/> <classRef key="model.labelLike"/> <classRef key="model.graphicLike"/> </alternate> <sequence minOccurs="0" maxOccurs="unbounded"> <alternate> <elementRef key="zone"/> <elementRef key="line"/> <elementRef key="path"/> <elementRef key="surface"/> <elementRef key="surfaceGrp"/> </alternate> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> </sequence> </content> ⚓ |
||||||||||||||
Schema Declaration |
element surface { att.global.attributes, att.coordinated.attributes, att.declaring.attributes, att.typed.attributes, attribute attachment { text }?, attribute flipping { text }?, ( ( model.global | model.labelLike | model.graphicLike )*, ( ( ( zone | line | path | surface | surfaceGrp ), model.global* )* ) ) }⚓ |
<surname> (surname) contains a family (inherited) name, as opposed to a given, baptismal, or nick name. [13.2.1. Personal Names] | |
Module | namesdates |
Attributes |
|
Member of | |
Contained by | |
May contain |
core: abbr choice cit corr date email emph expan foreign gloss graphic hi mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
character data
|
Example |
<surname type="combine">St John Stevas</surname>
|
Content model |
<content> <macroRef key="macro.phraseSeq"/> </content> ⚓ |
Schema Declaration |
element surname { att.global.attributes, att.personal.attributes, att.typed.attributes, macro.phraseSeq }⚓ |
<table> (table) contains text displayed in tabular form, in rows and columns. [14.1.1. TEI Tables] | |||||||||||||||||
Module | figures | ||||||||||||||||
Attributes |
|
||||||||||||||||
Member of | |||||||||||||||||
Contained by | |||||||||||||||||
May contain | |||||||||||||||||
Note |
Contains an optional heading and a series of rows. Any rendition information should be supplied using the global rend attribute, at the table, row, or cell level as appropriate. |
||||||||||||||||
Example |
<table rows="4" cols="4">
<head>Poor Men's Lodgings in Norfolk (Mayhew, 1843)</head>
<row role="label">
<cell role="data"/>
<cell role="data">Dossing Cribs or Lodging Houses</cell>
<cell role="data">Beds</cell>
<cell role="data">Needys or Nightly Lodgers</cell>
</row>
<row role="data">
<cell role="label">Bury St Edmund's</cell>
<cell role="data">5</cell>
<cell role="data">8</cell>
<cell role="data">128</cell>
</row>
<row role="data">
<cell role="label">Thetford</cell>
<cell role="data">3</cell>
<cell role="data">6</cell>
<cell role="data">36</cell>
</row>
<row role="data">
<cell role="label">Attleboro'</cell>
<cell role="data">3</cell>
<cell role="data">5</cell>
<cell role="data">20</cell>
</row>
<row role="data">
<cell role="label">Wymondham</cell>
<cell role="data">1</cell>
<cell role="data">11</cell>
<cell role="data">22</cell>
</row>
</table>
|
||||||||||||||||
Content model |
<content> <sequence> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.headLike"/> <classRef key="model.global"/> </alternate> <alternate> <sequence minOccurs="1" maxOccurs="unbounded"> <elementRef key="row"/> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> <sequence minOccurs="1" maxOccurs="unbounded"> <classRef key="model.graphicLike"/> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> </alternate> <sequence minOccurs="0" maxOccurs="unbounded"> <classRef key="model.divBottom"/> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> </sequence> </content> ⚓ |
||||||||||||||||
Schema Declaration |
element table { att.global.attributes, att.typed.attributes, attribute rows { text }?, attribute cols { text }?, ( ( model.headLike | model.global )*, ( ( ( row, model.global* )+ ) | ( ( model.graphicLike, model.global* )+ ) ), ( ( model.divBottom, model.global* )* ) ) }⚓ |
<tagsDecl> (tagging declaration) provides detailed information about the tagging applied to a document. [2.3.4. The Tagging Declaration 2.3. The Encoding Description] | |||||||||
Module | header | ||||||||
Attributes |
|
||||||||
Member of | |||||||||
Contained by |
header: encodingDesc
|
||||||||
May contain | Empty element | ||||||||
Example |
<tagsDecl partial="true">
<rendition xml:id="rend-it" scheme="css"
selector="emph, hi, name, title">font-style: italic;</rendition>
<namespace name="http://www.tei-c.org/ns/1.0">
<tagUsage gi="hi" occurs="467"/>
<tagUsage gi="title" occurs="45"/>
</namespace>
<namespace name="http://docbook.org/ns/docbook">
<tagUsage gi="para" occurs="10"/>
</namespace>
</tagsDecl> If the partial attribute were not specified here, the implication would be that the document in
question contains only <hi>, <title>, and <para> elements. |
||||||||
Content model |
<content> <sequence> <elementRef key="rendition" minOccurs="0" maxOccurs="unbounded"/> <elementRef key="namespace" minOccurs="0" maxOccurs="unbounded"/> </sequence> </content> ⚓ |
||||||||
Schema Declaration |
element tagsDecl { att.global.attributes, attribute partial { text }?, ( rendition*, namespace* ) }⚓ |
<taxonomy> (taxonomy) defines a typology either implicitly, by means of a bibliographic citation, or explicitly by a structured taxonomy. [2.3.7. The Classification Declaration] | |
Module | header |
Attributes |
|
Contained by | |
May contain | |
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> <alternate> <alternate> <alternate minOccurs="1" maxOccurs="unbounded"> <elementRef key="category"/> <elementRef key="taxonomy"/> </alternate> <sequence> <alternate minOccurs="1" maxOccurs="unbounded"> <classRef key="model.descLike" minOccurs="1" maxOccurs="1"/> <elementRef key="equiv" minOccurs="1" maxOccurs="1"/> <elementRef key="gloss" minOccurs="1" maxOccurs="1"/> </alternate> <alternate minOccurs="0" maxOccurs="unbounded"> <elementRef key="category"/> <elementRef key="taxonomy"/> </alternate> </sequence> </alternate> <sequence> <classRef key="model.biblLike"/> <alternate minOccurs="0" maxOccurs="unbounded"> <elementRef key="category"/> <elementRef key="taxonomy"/> </alternate> </sequence> </alternate> </content> ⚓ |
Schema Declaration |
element taxonomy { att.global.attributes, att.datcat.attributes, ( ( ( category | taxonomy )+ | ( ( model.descLike | equiv | gloss )+, ( category | taxonomy )* ) ) | ( model.biblLike, ( category | taxonomy )* ) ) }⚓ |
<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] | |
Module | header |
Attributes |
|
Contained by |
textstructure: TEI
|
May contain |
header: encodingDesc fileDesc profileDesc revisionDesc
|
Note |
One of the few elements unconditionally required in any TEI document. |
Example |
<teiHeader>
<fileDesc>
<titleStmt>
<title>Shakespeare: the first folio (1623) in electronic form</title>
<author>Shakespeare, William (1564–1616)</author>
<respStmt>
<resp>Originally prepared by</resp>
<name>Trevor Howard-Hill</name>
</respStmt>
<respStmt>
<resp>Revised and edited by</resp>
<name>Christine Avern-Carr</name>
</respStmt>
</titleStmt>
<publicationStmt>
<distributor>Oxford Text Archive</distributor>
<address>
<addrLine>13 Banbury Road, Oxford OX2 6NN, UK</addrLine>
</address>
<idno type="OTA">119</idno>
<availability>
<p>Freely available on a non-commercial basis.</p>
</availability>
<date when="1968">1968</date>
</publicationStmt>
<sourceDesc>
<bibl>The first folio of Shakespeare, prepared by Charlton Hinman (The Norton Facsimile,
1968)</bibl>
</sourceDesc>
</fileDesc>
<encodingDesc>
<projectDesc>
<p>Originally prepared for use in the production of a series of old-spelling
concordances in 1968, this text was extensively checked and revised for use
during the
editing of the new Oxford Shakespeare (Wells and Taylor, 1989).</p>
</projectDesc>
<editorialDecl>
<correction>
<p>Turned letters are silently corrected.</p>
</correction>
<normalization>
<p>Original spelling and typography is retained, except that long s and ligatured
forms are not encoded.</p>
</normalization>
</editorialDecl>
<refsDecl xml:id="ASLREF">
<cRefPattern matchPattern="(\S+) ([^.]+)\.(.*)"
replacementPattern="#xpath(//div1[@n='$1']/div2/[@n='$2']//lb[@n='$3'])">
<p>A reference is created by assembling the following, in the reverse order as that
listed here: <list>
<item>the <att>n</att> value of the preceding <gi>lb</gi>
</item>
<item>a period</item>
<item>the <att>n</att> value of the ancestor <gi>div2</gi>
</item>
<item>a space</item>
<item>the <att>n</att> value of the parent <gi>div1</gi>
</item>
</list>
</p>
</cRefPattern>
</refsDecl>
</encodingDesc>
<revisionDesc>
<list>
<item>
<date when="1989-04-12">12 Apr 89</date> Last checked by CAC</item>
<item>
<date when="1989-03-01">1 Mar 89</date> LB made new file</item>
</list>
</revisionDesc>
</teiHeader>
|
Content model |
<content> <sequence> <elementRef key="fileDesc"/> <classRef key="model.teiHeaderPart" minOccurs="0" maxOccurs="unbounded"/> <elementRef key="revisionDesc" minOccurs="0"/> </sequence> </content> ⚓ |
Schema Declaration |
element teiHeader { att.global.attributes, ( fileDesc, model.teiHeaderPart*, revisionDesc? ) }⚓ |
<term> (term) contains a single-word, multi-word, or symbolic designation which is regarded as a technical term. [3.4.1. Terms and Glosses] | |
Module | core |
Attributes |
|
Member of | |
Contained by | |
May contain |
core: abbr choice cit corr date email emph expan foreign gloss graphic hi mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
figures: figure
header: idno
namesdates: addName affiliation district forename genName geo location orgName persName placeName population region roleName settlement state surname trait
character data
|
Note |
When this element appears within an <index> element, it is understood to supply the form under which an index entry is to be made for that location. Elsewhere, it is understood simply to indicate that its content is to be regarded as a technical or specialised term. It may be associated with a <gloss> element by means of its ref attribute; alternatively a <gloss> element may point to a <term> element by means of its target attribute. In formal terminological work, there is frequently discussion over whether terms must be atomic or may include multi-word lexical items, symbolic designations, or phraseological units. The <term> element may be used to mark any of these. No position is taken on the philosophical issue of what a term can be; the looser definition simply allows the <term> element to be used by practitioners of any persuasion. As with other members of the att.canonical class, instances of this element occuring in a text may be associated with a canonical definition, either by means of a URI (using the ref attribute), or by means of some system-specific code value (using the key attribute). Because the mutually exclusive target and cRef attributes overlap with the function of the ref attribute, they are deprecated and may be removed at a subsequent release. |
Example |
A computational device that infers structure
from grammatical strings of words is known as a <term>parser</term>, and much of the history
of NLP over the last 20 years has been occupied with the design of parsers.
|
Example |
We may define <term xml:id="TDPV1" rend="sc">discoursal point of view</term> as
<gloss target="#TDPV1">the relationship, expressed
through discourse structure, between the implied author or some other addresser, and
the
fiction.</gloss>
|
Example |
We may define <term ref="#TDPV2" rend="sc">discoursal point of view</term> as
<gloss xml:id="TDPV2">the relationship, expressed
through discourse structure, between the implied author or some other addresser, and
the
fiction.</gloss>
|
Example |
We discuss Leech's concept of <term ref="myGlossary.xml#TDPV2" rend="sc">discoursal point of view</term> below.
|
Content model |
<content> <macroRef key="macro.phraseSeq"/> </content> ⚓ |
Schema Declaration |
element term { att.global.attributes, att.declaring.attributes, att.pointing.attributes, att.typed.attributes, att.canonical.attributes, att.sortable.attributes, att.cReferencing.attributes, macro.phraseSeq }⚓ |
<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] | |
Module | textstructure |
Attributes |
|
Member of | |
Contained by |
textstructure: TEI
|
May contain | |
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>
|
Example | The body of a text may be replaced by a group of nested texts, as in the following
schematic:
<text>
<front>
<!-- front matter for the whole group -->
</front>
<group>
<text>
<!-- first text -->
</text>
<text>
<!-- second text -->
</text>
</group>
</text>
|
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* )? ) ) }⚓ |
<textClass> (text classification) groups information which describes the nature or topic of a text in terms of a standard classification scheme, thesaurus, etc. [2.4.3. The Text Classification] | |
Module | header |
Attributes |
|
Member of | |
Contained by |
header: profileDesc
|
May contain |
header: catRef
|
Example |
<taxonomy>
<category xml:id="acprose">
<catDesc>Academic prose</catDesc>
</category>
<!-- other categories here -->
</taxonomy>
<!-- ... -->
<textClass>
<catRef target="#acprose"/>
<classCode scheme="http://www.udcc.org">001.9</classCode>
<keywords scheme="http://authorities.loc.gov">
<list>
<item>End of the world</item>
<item>History - philosophy</item>
</list>
</keywords>
</textClass>
|
Content model |
<content> <alternate minOccurs="0" maxOccurs="unbounded"> <elementRef key="classCode"/> <elementRef key="catRef"/> <elementRef key="keywords"/> </alternate> </content> ⚓ |
Schema Declaration |
element textClass { att.global.attributes, att.declarable.attributes, ( classCode | catRef | keywords )* }⚓ |
<textLang> (text language) describes the languages and writing systems identified within the bibliographic work being described, rather than its description. [3.12.2.4. Imprint, Size of a Document, and Reprint Information 10.6.6. Languages and Writing Systems] | |||||||||||||
Module | core | ||||||||||||
Attributes |
|
||||||||||||
Member of | |||||||||||||
Contained by |
msdescription: msContents
|
||||||||||||
May contain |
core: abbr bibl choice cit corr date desc email emph expan foreign gloss graphic hi label list listBibl mentioned name note orig p ptr q quote ref reg sic soCalled term title unclear
header: idno
msdescription: msDesc
namesdates: addName affiliation district forename genName geo listEvent listOrg listPerson listPlace listRelation location orgName persName placeName population region roleName settlement state surname trait
character data
|
||||||||||||
Note |
This element should not be used to document the languages or writing systems used for the bibliographic or manuscript description itself: as for all other TEI elements, such information should be provided by means of the global xml:lang attribute attached to the element containing the description. In all cases, languages should be identified by means of a standardized ‘language tag’ generated according to BCP 47. Additional documentation for the language may be provided by a <language> element in the TEI header. |
||||||||||||
Example |
<textLang mainLang="en" otherLangs="la"> Predominantly in English with Latin
glosses</textLang>
|
||||||||||||
Content model |
<content> <macroRef key="macro.specialPara"/> </content> ⚓ |
||||||||||||
Schema Declaration |
element textLang { att.global.attributes, attribute mainLang { text }?, attribute otherLangs { list { * } }?, macro.specialPara }⚓ |
<title> (title) contains a title for any kind of work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.5. The Series Statement] | |||||||||||||||||||||||||||||||
Module | core | ||||||||||||||||||||||||||||||
Attributes |
|
||||||||||||||||||||||||||||||
Member of | |||||||||||||||||||||||||||||||
Contained by | |||||||||||||||||||||||||||||||
May contain |
core: abbr bibl choice cit corr date desc email emph expan foreign gloss graphic hi label list listBibl mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
header: idno
msdescription: msDesc
namesdates: addName affiliation district forename genName geo listEvent listOrg listPerson listPlace listRelation location orgName persName placeName population region roleName settlement state surname trait
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>
|
||||||||||||||||||||||||||||||
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 calendar { list { + } }?, attribute level { "a" | "m" | "j" | "s" | "u" }?, macro.paraContent }⚓ |
<titleStmt> (title statement) groups information about the title of a work and those responsible for its content. [2.2.1. The Title Statement 2.2. The File Description] | |
Module | header |
Attributes |
|
Contained by |
header: fileDesc
|
May contain | |
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>
|
Content model |
<content> <sequence> <elementRef key="title" minOccurs="1" maxOccurs="unbounded"/> <classRef key="model.respLike" minOccurs="0" maxOccurs="unbounded"/> </sequence> </content> ⚓ |
Schema Declaration |
element titleStmt { att.global.attributes, ( title+, model.respLike* ) }⚓ |
<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] | |||||||||||
Module | namesdates | ||||||||||
Attributes |
|
||||||||||
Member of | |||||||||||
Contained by | |||||||||||
May contain | |||||||||||
Note |
Where there is confusion between <trait> and <state> the more general purpose element <state> should be used even for unchanging characteristics. If you wish to distinguish between characteristics that are generally perceived to be time-bound states and those assumed to be fixed traits, then <trait> is available for the more static of these. The <state> element encodes characteristics which are sometimes assumed to change, often at specific times or over a date range, whereas the <trait> elements are used to record characteristics, such as eye-colour, which are less subject to change. Traits are typically, but not necessarily, independent of the volition or action of the holder. |
||||||||||
Example |
<trait type="physical">
<label>Eye colour</label>
<desc>Blue</desc>
</trait>
|
||||||||||
Content model |
<content> <sequence> <elementRef key="precision" minOccurs="0" maxOccurs="unbounded"/> <alternate> <elementRef key="trait" minOccurs="1" maxOccurs="unbounded"/> <sequence> <classRef key="model.headLike" minOccurs="0" maxOccurs="unbounded"/> <classRef key="model.pLike" minOccurs="1" maxOccurs="unbounded"/> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.noteLike"/> <classRef key="model.biblLike"/> </alternate> </sequence> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.labelLike"/> <classRef key="model.noteLike"/> <classRef key="model.biblLike"/> </alternate> </alternate> </sequence> </content> ⚓ |
||||||||||
Schema Declaration |
element trait { att.global.attributes, att.datable.attributes, att.editLike.attributes, att.naming.attributes, att.typed.attributes, att.dimensions.attributes, attribute calendar { list { + } }?, ( precision*, ( trait+ | ( model.headLike*, model.pLike+, ( model.noteLike | model.biblLike )* ) | ( model.labelLike | model.noteLike | model.biblLike )* ) ) }⚓ |
<unclear> (unclear) contains a word, phrase, or passage which cannot be transcribed with certainty because it is illegible or inaudible in the source. [11.3.3.1. Damage, Illegibility, and Supplied Text 3.5.3. Additions, Deletions, and Omissions] | |||||||||||||||||||||
Module | core | ||||||||||||||||||||
Attributes |
|
||||||||||||||||||||
Member of | |||||||||||||||||||||
Contained by |
core: abbr author bibl biblScope choice corr date editor email emph expan foreign gloss head hi item label mentioned name note orig p pubPlace publisher q quote ref reg rs sic soCalled term textLang title unclear
figures: cell
namesdates: addName affiliation birth death district education faith floruit forename genName gender occupation orgName persName placeName region residence roleName settlement sex surname
transcr: zone
|
||||||||||||||||||||
May contain |
core: abbr bibl choice cit corr date desc email emph expan foreign gloss graphic hi label list listBibl mentioned name note orig ptr q quote ref reg sic soCalled term title unclear
header: idno
msdescription: msDesc
namesdates: addName affiliation district forename genName geo listEvent listOrg listPerson listPlace listRelation location orgName persName placeName population region roleName settlement state surname trait
character data
|
||||||||||||||||||||
Note |
The same element is used for all cases of uncertainty in the transcription of element content, whether for written or spoken material. For other aspects of certainty, uncertainty, and reliability of tagging and transcription, see chapter 21. Certainty, Precision, and Responsibility. The <damage>, <gap>, <del>, <unclear> and <supplied> elements may be closely allied in use. See section 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of which element is appropriate for which circumstance. The hand attribute points to a definition of the hand concerned, as further discussed in section 11.3.2.1. Document Hands. |
||||||||||||||||||||
Example |
<u> ...and then <unclear reason="background-noise">Nathalie</unclear> said ... </u>
|
||||||||||||||||||||
Content model |
<content> <macroRef key="macro.paraContent"/> </content> ⚓ |
||||||||||||||||||||
Schema Declaration |
element unclear { att.global.attributes, att.editLike.attributes, att.dimensions.attributes, attribute reason { list { ( "illegible" | "inaudible" | "faded" | "background_noise" | "eccentric_ductus" )+ } }?, attribute agent { text }?, macro.paraContent }⚓ |
<w> (word) represents a grammatical (not necessarily orthographic) word. [17.1. Linguistic Segment Categories 17.4.2. Lightweight Linguistic Annotation] | |
Module | analysis |
Attributes |
|
Member of | |
Contained by |
core: abbr author bibl biblScope corr date editor email emph expan foreign gloss head hi item label mentioned name note orig p pubPlace publisher q quote ref reg rs sic soCalled term textLang title unclear
figures: cell
namesdates: addName affiliation birth death district education faith floruit forename genName gender occupation orgName persName placeName region residence roleName settlement sex surname
transcr: zone
|
May contain | |
Example | This example is adapted from the Folger Library’s Early Modern English Drama version
of The Wits: a Comedy by William Davenant.
<l>
<w lemma="it" pos="pn"
xml:id="A19883-003-a-0100">IT</w>
<w lemma="have" pos="vvz"
xml:id="A19883-003-a-0110">hath</w>
<w lemma="be" pos="vvn"
xml:id="A19883-003-a-0120">been</w>
<w lemma="say" pos="vvn"
xml:id="A19883-003-a-0130">said</w>
<w lemma="of" pos="acp-p"
xml:id="A19883-003-a-0140">of</w>
<w lemma="old" pos="j"
xml:id="A19883-003-a-0150">old</w>
<pc xml:id="A19883-003-a-0160">,</pc>
<w lemma="that" pos="cs"
xml:id="A19883-003-a-0170">that</w>
<w lemma="play" pos="vvz"
xml:id="A19883-003-a-0180">
<choice>
<orig>Playes</orig>
<reg>Plays</reg>
</choice>
</w>
<w lemma="be" pos="vvb"
xml:id="A19883-003-a-0190">are</w>
<w lemma="feast" pos="n2"
xml:id="A19883-003-a-0200">Feasts</w>
<pc xml:id="A19883-003-a-0210">,</pc>
</l>
<l xml:id="A19883-e100220">
<w lemma="poet" pos="n2"
xml:id="A19883-003-a-0220">Poets</w>
<w lemma="the" pos="d"
xml:id="A19883-003-a-0230">the</w>
<w lemma="cook" pos="n2"
xml:id="A19883-003-a-0240">
<choice>
<orig>Cookes</orig>
<reg>Cooks</reg>
</choice>
</w>
<pc xml:id="A19883-003-a-0250">,</pc>
<w lemma="and" pos="cc"
xml:id="A19883-003-a-0260">and</w>
<w lemma="the" pos="d"
xml:id="A19883-003-a-0270">the</w>
<w lemma="spectator" pos="n2"
xml:id="A19883-003-a-0280">Spectators</w>
<w lemma="guest" pos="n2"
xml:id="A19883-003-a-0290">Guests</w>
<pc xml:id="A19883-003-a-0300">,</pc>
</l>
<l xml:id="A19883-e100230">
<w lemma="the" pos="d"
xml:id="A19883-003-a-0310">The</w>
<w lemma="actor" pos="n2"
xml:id="A19883-003-a-0320">Actors</w>
<w lemma="waiter" pos="n2"
xml:id="A19883-003-a-0330">Waiters</w>
<pc xml:id="A19883-003-a-0340">:</pc>
<!-- ... -->
</l>
|
Content model |
<content> <alternate minOccurs="0" maxOccurs="unbounded"> <textNode/> <classRef key="model.gLike"/> <elementRef key="seg"/> <elementRef key="w"/> <elementRef key="m"/> <elementRef key="c"/> <elementRef key="pc"/> <classRef key="model.global"/> <classRef key="model.lPart"/> <classRef key="model.hiLike"/> <classRef key="model.pPart.edit"/> </alternate> </content> ⚓ |
Schema Declaration |
element w { att.global.attributes, att.segLike.attributes, att.typed.attributes, att.linguistic.attributes, att.notated.attributes, ( text | model.gLike | seg | w | m | c | pc | model.global | model.lPart | model.hiLike | model.pPart.edit )* }⚓ |
<zone> defines any two-dimensional area within a <surface> element. [11.1. Digital Facsimiles 11.2.2. Embedded Transcription] | |||||||||
Module | transcr | ||||||||
Attributes |
|
||||||||
Member of | |||||||||
Contained by | |||||||||
May contain | |||||||||
Note |
The position of every zone for a given surface is always defined by reference to the coordinate system defined for that surface. A graphic element contained by a zone represents the whole of the zone. A zone may be of any shape. The attribute points may be used to define a polygonal zone, using the coordinate system defined by its parent surface. A zone is always a closed polygon. Repeating the initial coordinate at the end of the sequence is optional. To encode an unclosed path, use the <path> element. |
||||||||
Example |
<surface ulx="14.54" uly="16.14" lrx="0"
lry="0">
<graphic url="stone.jpg"/>
<zone points="4.6,6.3 5.25,5.85 6.2,6.6 8.19222,7.4125 9.89222,6.5875 10.9422,6.1375
11.4422,6.7125 8.21722,8.3125 6.2,7.65"/>
</surface> This example defines a non-rectangular zone: see the illustration in section [[undefined
PH-surfzone]]. |
||||||||
Example |
<facsimile>
<surface ulx="50" uly="20" lrx="400"
lry="280">
<zone ulx="0" uly="0" lrx="500" lry="321">
<graphic url="graphic.png"/>
</zone>
</surface>
</facsimile> This example defines a zone which has been defined as larger than its parent surface
in order to match the dimensions of the graphic it contains. |
||||||||
Content model |
<content> <alternate minOccurs="0" maxOccurs="unbounded"> <textNode/> <classRef key="model.gLike"/> <classRef key="model.graphicLike"/> <classRef key="model.global"/> <elementRef key="surface"/> <classRef key="model.linePart"/> </alternate> </content> ⚓ |
||||||||
Schema Declaration |
element zone { att.global.attributes, att.coordinated.attributes, att.typed.attributes, att.written.attributes, attribute rotate { text }?, ( text | model.gLike | model.graphicLike | model.global | surface | model.linePart )* }⚓ |
model.addressLike groups elements used to represent a postal or email address. [1. The TEI Infrastructure] | |
Module | tei |
Used by | |
Members | affiliation email |
model.annotationLike groups elements used to represent annotations. [16.10. The standOff Container] | |
Module | tei |
Used by | |
Members | note |
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] | |
Module | tei |
Used by | |
Members | model.quoteLike[cit quote] |
model.biblLike groups elements containing a bibliographic description. [3.12. Bibliographic Citations and References] | |
Module | tei |
Used by | |
Members | bibl listBibl msDesc |
model.biblPart groups elements which represent components of a bibliographic description. [3.12. Bibliographic Citations and References] | |
Module | tei |
Used by | |
Members | model.imprintPart[biblScope pubPlace publisher] model.respLike[author editor funder respStmt] bibl edition listRelation msIdentifier relatedItem series textLang |
model.common groups common chunk- and inter-level elements. [1.3. The TEI Class System] | |
Module | tei |
Used by | |
Members | model.divPart[model.lLike model.pLike[p]] model.inter[model.attributable[model.quoteLike[cit quote]] model.biblLike[bibl listBibl msDesc] model.egLike model.labelLike[desc label] model.listLike[list listEvent listOrg listPerson listPlace listRelation table] model.oddDecl model.stageLike] q |
Note |
This class defines the set of chunk- and inter-level elements; it is used in many content models, including those for textual divisions. |
model.dateLike groups elements containing temporal expressions. [3.6.4. Dates and Times 13.4. Dates] | |
Module | tei |
Used by | |
Members | date |
model.divPart groups paragraph-level elements appearing directly within divisions. [1.3. The TEI Class System] | |
Module | tei |
Used by | |
Members | model.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. |
model.divTop groups elements appearing at the beginning of a text division. [4.2. Elements Common to All Divisions] | |
Module | tei |
Used by | |
Members | model.divTopPart[model.headLike[head]] model.divWrapper |
model.divTopPart groups elements which can occur only at the beginning of a text division. [4.6. Title Pages] | |
Module | tei |
Used by | |
Members | model.headLike[head] |
model.encodingDescPart groups elements which may be used inside <encodingDesc> and appear multiple times. | |
Module | tei |
Used by | |
Members | classDecl editorialDecl listPrefixDef projectDesc samplingDecl tagsDecl |
model.frontPart groups elements which appear at the level of divisions within front or back matter. [7.1. Front and Back Matter ] | |
Module | tei |
Used by | |
Members | model.frontPart.drama divGen listBibl |
model.global groups elements which may appear at any point within a TEI text. [1.3. The TEI Class System] | |
Module | tei |
Used by | |
Members | model.global.edit model.global.meta[interp interpGrp link linkGrp span spanGrp] model.milestoneLike model.noteLike[note] figure |
model.global.meta groups globally available elements which describe the status of other elements. [1.3. The TEI Class System] | |
Module | tei |
Used by | |
Members | interp interpGrp link linkGrp span spanGrp |
Note |
Elements in this class are typically used to hold groups of links or of abstract interpretations, or by provide indications of certainty etc. It may find be convenient to localize all metadata elements, for example to contain them within the same divison as the elements that they relate to; or to locate them all to a division of their own. They may however appear at any point in a TEI text. |
model.graphicLike groups elements containing images, formulae, and similar objects. [3.10. Graphics and Other Non-textual Components] | |
Module | tei |
Used by | |
Members | graphic |
model.headLike groups elements used to provide a title or heading at the start of a text division. | |
Module | tei |
Used by | |
Members | head |
model.hiLike groups phrase-level elements which are typographically distinct but to which no specific function can be attributed. [3.3. Highlighting and Quotation] | |
Module | tei |
Used by | |
Members | hi q |
model.highlighted groups phrase-level elements which are typographically distinct. [3.3. Highlighting and Quotation] | |
Module | tei |
Used by | |
Members | model.emphLike[code emph foreign gloss ident mentioned soCalled term title] model.hiLike[hi q] |
model.imprintPart groups the bibliographic elements which occur inside imprints. [3.12. Bibliographic Citations and References] | |
Module | tei |
Used by | |
Members | biblScope pubPlace publisher |
model.inter groups elements which can appear either within or between paragraph-like elements. [1.3. The TEI Class System] | |
Module | tei |
Used by | |
Members | model.attributable[model.quoteLike[cit quote]] model.biblLike[bibl listBibl msDesc] model.egLike model.labelLike[desc label] model.listLike[list listEvent listOrg listPerson listPlace listRelation table] model.oddDecl model.stageLike |
model.limitedPhrase groups phrase-level elements excluding those elements primarily intended for transcription of existing sources. [1.3. The TEI Class System] | |
Module | tei |
Used by | |
Members | model.emphLike[code emph foreign gloss ident mentioned soCalled term title] model.hiLike[hi q] model.pPart.data[model.addressLike[affiliation email] model.dateLike[date] model.measureLike[geo] model.nameLike[model.nameLike.agent[name orgName persName] model.offsetLike model.persNamePart[addName forename genName roleName surname] model.placeStateLike[model.placeNamePart[district placeName region settlement] location population state trait] idno]] model.pPart.editorial[abbr choice expan] model.pPart.msdesc model.phrase.xml model.ptrLike[ptr ref] |
model.listLike groups list-like elements. [3.8. Lists] | |
Module | tei |
Used by | |
Members | list listEvent listOrg listPerson listPlace listRelation table |
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] | |
Module | tei |
Used by | |
Members | geo |
model.nameLike groups elements which name or refer to a person, place, or organization. | |
Module | tei |
Used by | |
Members | model.nameLike.agent[name orgName persName] model.offsetLike model.persNamePart[addName forename genName roleName surname] model.placeStateLike[model.placeNamePart[district placeName region settlement] location population state trait] idno |
Note |
A superset of the naming elements that may appear in datelines, addresses, statements of responsibility, etc. |
model.nameLike.agent groups elements which contain names of individuals or corporate bodies. [3.6. Names, Numbers, Dates, Abbreviations, and Addresses] | |
Module | tei |
Used by | |
Members | name orgName persName |
Note |
This class is used in the content model of elements which reference names of people or organizations. |
model.noteLike groups globally-available note-like elements. [3.9. Notes, Annotation, and Indexing] | |
Module | tei |
Used by | |
Members | note |
model.orgPart groups elements which form part of the description of an organization. | |
Module | tei |
Used by | |
Members | model.eventLike[event listEvent] listOrg listPerson listPlace |
model.pLike groups paragraph-like elements. | |
Module | tei |
Used by | |
Members | p |
model.pLike.front groups paragraph-like elements which can occur as direct constituents of front matter. [4.6. Title Pages] | |
Module | tei |
Used by | |
Members | head |
model.pPart.data groups phrase-level elements containing names, dates, numbers, measures, and similar data. [3.6. Names, Numbers, Dates, Abbreviations, and Addresses] | |
Module | tei |
Used by | |
Members | model.addressLike[affiliation email] model.dateLike[date] model.measureLike[geo] model.nameLike[model.nameLike.agent[name orgName persName] model.offsetLike model.persNamePart[addName forename genName roleName surname] model.placeStateLike[model.placeNamePart[district placeName region settlement] location population state trait] idno] |
model.pPart.edit groups phrase-level elements for simple editorial correction and transcription. [3.5. Simple Editorial Changes] | |
Module | tei |
Used by | |
Members | model.pPart.editorial[abbr choice expan] model.pPart.transcriptional[corr orig reg sic unclear] |
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] | |
Module | tei |
Used by | |
Members | abbr choice expan |
model.persStateLike groups elements describing changeable characteristics of a person which have a definite duration, for example occupation, residence, or name. | |
Module | tei |
Used by | |
Members | affiliation age education faith floruit gender occupation persName residence sex state trait |
Note |
These characteristics of an individual are typically a consequence of their own action or that of others. |
model.personPart groups elements which form part of the description of a person. [15.2.2. The Participant Description] | |
Module | tei |
Used by | |
Members | model.biblLike[bibl listBibl msDesc] model.eventLike[event listEvent] model.persStateLike[affiliation age education faith floruit gender occupation persName residence sex state trait] birth death idno name rs |
model.phrase groups elements which can occur at the level of individual words or phrases. [1.3. The TEI Class System] | |
Module | tei |
Used by | |
Members | model.graphicLike[graphic] model.highlighted[model.emphLike[code emph foreign gloss ident mentioned soCalled term title] model.hiLike[hi q]] model.lPart model.pPart.data[model.addressLike[affiliation email] model.dateLike[date] model.measureLike[geo] model.nameLike[model.nameLike.agent[name orgName persName] model.offsetLike model.persNamePart[addName forename genName roleName surname] model.placeStateLike[model.placeNamePart[district placeName region settlement] location population state trait] idno]] model.pPart.edit[model.pPart.editorial[abbr choice expan] model.pPart.transcriptional[corr orig reg sic unclear]] model.pPart.msdesc model.phrase.xml model.ptrLike[ptr ref] model.segLike[c cl m pc phr s w] model.specDescLike |
Note |
This class of elements can occur within paragraphs, list items, lines of verse, etc. |
model.placeNamePart groups elements which form part of a place name. [13.2.3. Place Names] | |
Module | tei |
Used by | |
Members | district placeName region settlement |
model.placeStateLike groups elements which describe changing states of a place. | |
Module | tei |
Used by | |
Members | model.placeNamePart[district placeName region settlement] location population state trait |
model.profileDescPart groups elements which may be used inside <profileDesc> and appear multiple times. | |
Module | tei |
Used by | |
Members | calendarDesc langUsage textClass |
model.ptrLike groups elements used for purposes of location and reference. [3.7. Simple Links and Cross-References] | |
Module | tei |
Used by | |
Members | ptr ref |
model.publicationStmtPart.agency groups the child elements of a <publicationStmt> element of the TEI header that indicate an authorising agent. [2.2.4. Publication, Distribution, Licensing, etc.] | |
Module | tei |
Used by | |
Members | authority publisher |
Note |
The ‘agency’ child elements, while not required, are required if one of the ‘detail’ child elements is to be used. It is not valid to have a ‘detail’ child element without a preceding ‘agency’ child element. See also model.publicationStmtPart.detail. |
model.publicationStmtPart.detail groups the agency-specific child elements of the <publicationStmt> element of the TEI header. [2.2.4. Publication, Distribution, Licensing, etc.] | |
Module | tei |
Used by | |
Members | model.ptrLike[ptr ref] date idno pubPlace |
Note |
A ‘detail’ child element may not occur unless an ‘agency’ child element precedes it. See also model.publicationStmtPart.agency. |
model.resource groups separate elements which constitute the content of a digital resource, as opposed to its metadata. [1.3. The TEI Class System] | |
Module | tei |
Used by | |
Members | standOff text |
model.segLike groups elements used for arbitrary segmentation. [16.3. Blocks, Segments, and Anchors 17.1. Linguistic Segment Categories] | |
Module | tei |
Used by | |
Members | c cl m pc phr s w |
Note |
The principles on which segmentation is carried out, and any special codes or attribute values used, should be defined explicitly in the <segmentation> element of the <encodingDesc> within the associated TEI header. |
model.standOffPart groups elements which may be used as children of <standOff>. | |
Module | tei |
Used by | |
Members | model.annotationLike[note] model.biblLike[bibl listBibl msDesc] model.global.meta[interp interpGrp link linkGrp span spanGrp] model.listLike[list listEvent listOrg listPerson listPlace listRelation table] zone |
model.teiHeaderPart groups high level elements which may appear more than once in a TEI header. | |
Module | tei |
Used by | |
Members | encodingDesc profileDesc |
att.anchoring (anchoring) provides attributes for use on annotations, e.g. notes and groups of notes describing the existence and position of an anchor for annotations. | |||||||||||||||||||
Module | tei | ||||||||||||||||||
Members | note | ||||||||||||||||||
Attributes |
|
||||||||||||||||||
Example |
<p>(...) tamen reuerendos dominos archiepiscopum et canonicos Leopolienses
necnon episcopum in duplicibus Quatuortemporibus<anchor xml:id="A55234"/> totaliter expediui...</p>
<!-- elsewhere in the document -->
<noteGrp targetEnd="#A55234">
<note xml:lang="en"> Quatuor Tempora, so called dry fast days.
</note>
<note xml:lang="pl"> Quatuor Tempora, tzw. Suche dni postne.
</note>
</noteGrp>
|
att.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] | |||||||||||
Module | tei | ||||||||||
Members | att.ascribed.directed[q] change | ||||||||||
Attributes |
|
att.ascribed.directed provides attributes for elements representing speech or action that can be directed at a group or individual. [3.3.3. Quotation 8.3. Elements Unique to Spoken Texts] | |||||||||||
Module | tei | ||||||||||
Members | q | ||||||||||
Attributes |
|
att.cReferencing provides attributes that may be used to supply a canonical reference as a means of identifying the target of a pointer. | |||||||||
Module | tei | ||||||||
Members | gloss ptr ref term | ||||||||
Attributes |
|
att.calendarSystem provides attributes for indicating calendar systems to which a date belongs. [3.6.4. Dates and Times 13.4. Dates] | |||||||||||||||
Module | tei | ||||||||||||||
Members | date | ||||||||||||||
Attributes |
|
att.canonical provides attributes that can be used to associate a representation such as a name or title with canonical information about the object being named or referenced. [13.1.1. Linking Names and Their Referents] | |||||||||||||||||||||
Module | tei | ||||||||||||||||||||
Members | att.naming[att.personal[addName forename genName name orgName persName placeName roleName surname] affiliation author birth death district editor education event occupation population pubPlace region repository residence settlement state trait] authority catDesc date faith funder publisher relation resp respStmt term title | ||||||||||||||||||||
Attributes |
|
||||||||||||||||||||
Example | In this contrived example, a canonical reference to the same organisation is provided
in four different ways.
<author n="1">
<name ref="http://nzetc.victoria.ac.nz/tm/scholarly/name-427308.html"
type="organisation">New Zealand Parliament, Legislative Council</name>
</author>
<author n="2">
<name ref="nzvn:427308"
type="organisation">New Zealand Parliament, Legislative Council</name>
</author>
<author n="3">
<name ref="./named_entities.xml#o427308"
type="organisation">New Zealand Parliament, Legislative Council</name>
</author>
<author n="4">
<name key="name-427308"
type="organisation">New Zealand Parliament, Legislative Council</name>
</author> The first presumes the availability of an internet connection and a processor that
can resolve a URI (most can). The second requires, in addition, a <prefixDef> that declares how the nzvm prefix should be interpreted. The third does not require an internet connection,
but does require that a file named named_entities.xml be in the same directory as the TEI document. The fourth requires that an entire
external system for key resolution be available. |
||||||||||||||||||||
Note |
The key attribute is more flexible and general-purpose, but its use in interchange requires that documentation about how the key is to be resolved be sent to the recipient of the TEI document. In contrast values of the ref attribute are resolved using the widely accepted protocols for a URI, and thus less documentation, if any, is likely required by the recipient in data interchange. These guidelines provide no semantic basis or suggested precedence when both key and ref are provided. For this reason simultaneous use of both is not recommended unless documentation explaining the use is provided, probably in an ODD customizaiton, for interchange. |
att.coordinated provides attributes that can be used to position their parent element within a two dimensional coordinate system. | |||||||||||||||||||||||||||||||||||||
Module | transcr | ||||||||||||||||||||||||||||||||||||
Members | surface zone | ||||||||||||||||||||||||||||||||||||
Attributes |
|
att.datable provides attributes for normalization of elements that contain dates, times, or datable events. [3.6.4. Dates and Times 13.4. Dates] | |||||||
Module | tei | ||||||
Members | affiliation age author birth change date death district editor education event faith floruit funder gender idno langKnown licence location name occupation orgName persName placeName population region relation residence resp settlement sex state title trait | ||||||
Attributes |
|
||||||
Note |
This ‘superclass’ provides attributes that can be used to provide normalized values of temporal information. By default, the attributes from the att.datable.w3c class are provided. If the module for names & dates is loaded, this class also provides attributes from the att.datable.iso and att.datable.custom classes. In general, the possible values of attributes restricted to the W3C datatypes form a subset of those values available via the ISO 8601 standard. However, the greater expressiveness of the ISO datatypes may not be needed, and there exists much greater software support for the W3C datatypes. |
att.datable.custom provides attributes for normalization of elements that contain datable events to a custom dating system (i.e. other than the Gregorian used by W3 and ISO). [13.4. Dates] | |||||||||||||||||||||||||||||||||||||||||||||||||||||
Module | namesdates | ||||||||||||||||||||||||||||||||||||||||||||||||||||
Members | att.datable[affiliation age author birth change date death district editor education event faith floruit funder gender idno langKnown licence location name occupation orgName persName placeName population region relation residence resp settlement sex state title trait] | ||||||||||||||||||||||||||||||||||||||||||||||||||||
Attributes |
|
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] | |||||||||||||||||||||||||||||||||||
Module | namesdates | ||||||||||||||||||||||||||||||||||
Members | att.datable[affiliation age author birth change date death district editor education event faith floruit funder gender idno langKnown licence location name occupation orgName persName placeName population region relation residence resp settlement sex state title trait] | ||||||||||||||||||||||||||||||||||
Attributes |
|
||||||||||||||||||||||||||||||||||
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. |
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] | |||||||||||||||||||||||||||||||||||||
Module | tei | ||||||||||||||||||||||||||||||||||||
Members | att.datable[affiliation age author birth change date death district editor education event faith floruit funder gender idno langKnown licence location name occupation orgName persName placeName population region relation residence resp settlement sex state title trait] | ||||||||||||||||||||||||||||||||||||
Attributes |
|
||||||||||||||||||||||||||||||||||||
Schematron |
<sch:rule context="tei:*[@when]">
<sch:report test="@notBefore|@notAfter|@from|@to"
role="nonfatal">The @when attribute cannot be used with any other att.datable.w3c
attributes.</sch:report>
</sch:rule>
|
||||||||||||||||||||||||||||||||||||
Schematron |
<sch:rule context="tei:*[@from]">
<sch:report test="@notBefore"
role="nonfatal">The @from and @notBefore attributes cannot be used together.</sch:report>
</sch:rule>
|
||||||||||||||||||||||||||||||||||||
Schematron |
<sch:rule context="tei:*[@to]">
<sch:report test="@notAfter"
role="nonfatal">The @to and @notAfter attributes cannot be used together.</sch:report>
</sch:rule>
|
||||||||||||||||||||||||||||||||||||
Example |
<date from="1863-05-28" to="1863-06-01">28 May through 1 June 1863</date>
|
||||||||||||||||||||||||||||||||||||
Note |
The value of these attributes should be a normalized representation of the date, time, or combined date & time intended, in any of the standard formats specified by XML Schema Part 2: Datatypes Second Edition, using the Gregorian calendar. The most commonly-encountered format for the date portion of a temporal attribute
is Note that this format does not currently permit use of the value 0000 to represent the year 1 BCE; instead the value -0001 should be used. |
att.datcat provides attributes that are used to align XML elements or attributes with the appropriate Data Categories (DCs) defined by an external taxonomy, in this way establishing the identity of information containers and values, and providing means of interpreting them. [9.5.2. Lexical View 18.3. Other Atomic Feature Values] | |||||||||||||||||||
Module | tei | ||||||||||||||||||
Members | att.segLike[c cl m pc phr s w] category taxonomy | ||||||||||||||||||
Attributes |
|
||||||||||||||||||
Example | The example below presents the TEI encoding of the name-value pair <part of speech, common noun> , where the name (key) ‘part of speech’ is abbreviated as ‘POS’, and the value, ‘common noun’ is symbolized by ‘NN’. The entire name-value pair is encoded by means of the element <f>. In TEI XML, that element acts as the container, labeled with the name attribute. Its contents may be complex or simple. In the case at hand, the content
is the symbol ‘NN’.The datcat attribute relates the feature name (i.e., the key) to the data category ‘part of speech’, while the attribute valueDatcat relates the feature value to the data category common noun. Both these data categories should be defined in an external and preferably open
reference taxonomy or ontology.
<fs>
<f name="POS"
datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3">
<symbol valueDatcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545"
value="NN"/>
</f>
<!-- ... -->
</fs> ‘NN’ is the symbol for common noun used e.g. in the CLAWS-7 tagset defined by the University Centre for Computer Corpus Research on Language at the
University of Lancaster. The very same data category used for tagging an early version
of the British National Corpus, and coming from the BNC Basic (C5) tagset, uses the symbol ‘NN0’ (rather than ‘NN’). Making these values semantically interoperable would be extremely difficult without
a human expert if they were not anchored in a single point of an established reference
taxonomy of morphosyntactic data categories. In the case at hand, the string ‘http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545’ is both a persistent identifier of the data category in question, as well as a pointer
to a shared definition of common noun.While the symbols ‘NN’, ‘NN0’, and many others (often coming from languages other than English) are implicitly
members of the container category ‘part of speech’, it is sometimes useful not to rely on such an implicit relationship but rather use
an explicit identifier for that data category, to distinguish it from other morphosyntactic
data categories, such as gender, tense, etc. For that purpose, the above example uses
the datcat attribute to reference a definition of part of speech. The reference taxonomy in this example is the CLARIN Concept Registry.If the feature structure markup exemplified above is to be repeated many times in
a single document, it is much more efficient to gather the persistent identifiers
in a single place and to only reference them, implicitly or directly, from feature
structure markup. The following example is much more concise than the one above and
relies on the concepts of feature structure declaration and feature value library,
discussed in chapter [[undefined FS]].
<fs>
<f name="POS" fVal="#commonNoun"/>
<!-- ... -->
</fs> The assumption here is that the relevant feature values are collected in a place that
the annotation document in question has access to — preferably, a single document
per linguistic resource, for example an <fsdDecl> that is XIncluded as a sibling of <text> or a child of <encodingDesc>; a <taxonomy> available resource-wide (e.g., in a shared header) is also an option.The example
below presents an <fvLib> element that collects the relevant feature values (most of them omitted). At the
same time, this example shows one way of encoding a tagset, i.e., an established inventory of values of (in the case at hand) morphosyntactic
categories.
<fvLib n="POS values">
<symbol xml:id="commonNoun" value="NN"
datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"/>
<symbol xml:id="properNoun" value="NP"
datcat="http://hdl.handle.net/11459/CCR_C-1371_fbebd9ec-a7f4-9a36-d6e9-88ee16b944ae"/>
<!-- ... -->
</fvLib> Note that these Guidelines do not prescribe a specific choice between datcat and valueDatcat in such cases. The former is the generic way of referencing a data category, whereas
the latter is more specific, in that it references a data category that represents
a value. The choice between them comes into play where a single element — or a tight
element complex, such as the <f>/<symbol> complex illustrated above — make it necessary or useful to distinguish between the
container data category and its value. |
||||||||||||||||||
Example | In the context of dictionaries designed with semantic interoperability in mind, the
following example ensures that the <pos> element is interpreted as the same information container as in the case of the example
of <f name="POS"> above.
<gramGrp>
<pos datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"
valueDatcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545">NN</pos>
</gramGrp> Efficiency of this type of interoperable markup demands that the references to the
particular data categories should best be provided in a single place within the dictionary
(or a single place within the project), rather than being repeated inside every entry.
For the container elements, this can be achieved at the level of <tagUsage>, although here, the valueDatcat attribute should be used, because it is not the <tagUsage> element that is associated with the relevant data category, but rather the element
<pos> (or <case>, etc.) that is described by <tagUsage>:
<tagsDecl partial="true">
<!-- ... -->
<namespace name="http://www.tei-c.org/ns/1.0">
<tagUsage gi="pos"
targetDatcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3">Contains the part of speech.</tagUsage>
<tagUsage gi="case"
targetDatcat="http://hdl.handle.net/11459/CCR_C-1840_9f4e319c-f233-6c90-9117-7270e215f039">Contains information about the grammatical case that the described form is inflected
for.</tagUsage>
<!-- ... -->
</namespace>
</tagsDecl> Another possibility is to shorten the URIs by means of the <prefixDef> mechanism, as illustrated below:
<listPrefixDef>
<prefixDef ident="ccr" matchPattern="pos"
replacementPattern="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"/>
<prefixDef ident="ccr" matchPattern="adj"
replacementPattern="http://hdl.handle.net/11459/CCR_C-1230_23653c21-fca1-edf8-fd7c-3df2d6499157"/>
</listPrefixDef>
<!-- ... -->
<entry>
<!--...-->
<form>
<orth>isotope</orth>
</form>
<gramGrp>
<pos datcat="ccr:pos"
valueDatcat="ccr:adj">adj</pos>
</gramGrp>
<!--...-->
</entry> This mechanism creates implications that are not always wanted, among others, in the
case at hand, suggesting that the identifiers ‘pos’ and ‘adj’ belong to a namespace associated with the CLARIN Concept Repository (CCR), whereas
that is solely a shorthand mechanism whose scope is the current resource. Documenting
this clearly in the header of the dictionary is therefore advised.Yet another possibility
is to associate the information about the relationship between a TEI markup element
and the data category that it is intended to model already at the level of modeling
the dictionary resource, that is, at the level of the ODD, in the <equiv> element that is a child of <elementSpec> or <attDef>. |
||||||||||||||||||
Example | The <taxonomy> element is a handy tool for encoding taxonomies that are later referenced by att.datcat attributes, but it can also act as an intermediary device, for example holding a
fragment of an external taxonomy (or ‘flattening’ an external ontology) that is relevant to the project or document at hand. (It is
also imaginable that, for the purpose of the project at hand, the local <taxonomy> element combines vocabularies that originate from more than one external taxonomy
or ontology.) In such cases, the <taxonomy> creates a local layer of indirection: the att.datcat attributes internal to the resource may reference the <category> elements stored in the header (as well as the <taxonomy> element itself), whereas these same <category> and <taxonomy> elements use att.datcat attributes to reference the original taxonomy or ontology.
<encodingDesc>
<!-- ... -->
<classDecl>
<!-- ... -->
<taxonomy xml:id="UD-SYN"
datcat="https://universaldependencies.org/u/dep/index.html">
<desc>
<term>UD syntactic relations</term>
</desc>
<category xml:id="acl"
valueDatcat="https://universaldependencies.org/u/dep/acl.html">
<catDesc>
<term>acl</term>: Clausal modifier of noun (adjectival clause)</catDesc>
</category>
<category xml:id="acl_relcl"
valueDatcat="https://universaldependencies.org/u/dep/acl-relcl.html">
<catDesc>
<term>acl:relcl</term>: relative clause modifier</catDesc>
</category>
<category xml:id="advcl"
valueDatcat="https://universaldependencies.org/u/dep/advcl.html">
<catDesc>
<term>advcl</term>: Adverbial clause modifier</catDesc>
</category>
<!-- ... -->
</taxonomy>
</classDecl>
</encodingDesc> The above fragment was excerpted from the GB subset of the ParlaMint project in April 2023, and enriched with att.datcat attributes for the purpose of illustrating the mechanism described here.Note that,
in the ideal case, the values of att.datcat attributes should be persistent identifiers, and that the addressing scheme of Universal
Dependencies is treated here as persistent for the sake of illustration. Note also
that the contrast between datcat used on <taxonomy> on the one hand, and the valueDatcat used on <category> on the other, is not mandatory: both kinds of relations could be encoded by means
of the generic datcat attribute, but using the former for the container and the latter for the content
is more user-friendly. |
||||||||||||||||||
Example | The targetDatcat attribute is designed to be used in, e.g., feature structure declarations, and is
analogous to the targetLang attribute of the att.pointing class, in that it describes the object that is being referenced, rather than the
referencing object.
<fDecl name="POS"
targetDatcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3">
<fDescr>part of speech (morphosyntactic category)</fDescr>
<vRange>
<vAlt>
<symbol value="NN"
datcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545"/>
<symbol value="NP"
datcat="http://hdl.handle.net/11459/CCR_C-1371_fbebd9ec-a7f4-9a36-d6e9-88ee16b944ae"/>
<!-- ... -->
</vAlt>
</vRange>
</fDecl> Above, the <fDecl> uses targetDatcat, because if it were to use datcat, it would be asserting that it is an instance of the container data category part of speech, whereas it is not — it models a container (<f>) that encodes a part of speech. Note also that it is the <f> that is modeled above, not its values, which are used as direct references to data
categories; hence the use of datcat in the <symbol> element. |
||||||||||||||||||
Example | The att.datcat attributes can be used for any sort of taxonomies. The example below illustrates
their usefulness for describing usage domain labels in dictionaries on the example
of the Diccionario da Lingua Portugueza by António de Morais Silva, retro-digitised in the MORDigital project.
<!-- in the dictionary header --><encodingDesc>
<classDecl>
<taxonomy xml:id="domains">
<!--...-->
<category xml:id="domain.medical_and_health_sciences">
<catDesc xml:lang="en">Medical and Health Sciences</catDesc>
<catDesc xml:lang="pt">Ciências Médicas e da Saúde</catDesc>
<category xml:id="domain.medical_and_health_sciences.medicine"
valueDatcat="https://vocabs.rossio.fcsh.unl.pt/pub/morais_domains/pt/page/0025">
<catDesc xml:lang="en">
<term>Medicine</term>
<gloss>
<!--...-->
</gloss>
</catDesc>
<catDesc xml:lang="pt">
<term>Medicina</term>
<gloss>
<!--...-->
</gloss>
</catDesc>
</category>
</category>
<!--...-->
</taxonomy>
</classDecl>
</encodingDesc>
<!--
inside an <entry> element: -->
<usg type="domain"
valueDatcat="#domain.medical_and_health_sciences.medicine">Med.</usg> In the Morais dictionary, the relevant domain labels are in the header, getting referenced
inside the dictionary, from <usg> elements. The vocabulary used for dictionary-internal labelling is in turn anchored
in the MorDigital controlled vocabulary service of the NOVA University of Lisbon – School of Social Sciences and Humanities (NOVA
FCSH). |
||||||||||||||||||
Note |
The TEI Abstract Model can be expressed as a hierarchy of attribute-value matrices (AVMs) of various types and of various levels of complexity, nested or grouped in various ways. At the most abstract level, an AVM consists of an information container and the value (contents) of that container. A simple example of an XML serialization of such structures is, on the one hand, the opening and closing tags that delimit and name the container, and, on the other, the content enclosed by the two tags that constitues the value. An analogous example is an attribute name and the value of that attribute. In a TEI XML example of two equivalent serializations expressing the name-value pair
The att.datcat class provides means of addressing the containers and their values, while at the same time providing a way to interpret them in the context of external taxonomies or ontologies. Aligning e.g. both the <pos> element and the pos attribute with the same value of an external reference point (i.e., an entry in an agreed taxonomy) affirms the identity of the concept serialised by both the element container and the attribute container, and optionally provides a definition of that concept (in the case at hand, the concept part of speech). The value of the att.datcat attributes should be a PID (persistent identifier) that points to a specific — and, ideally, shared — taxonomy or ontology. Among the resources that can, to a lesser or greater extent, be used as inventories of (more or less) standardized linguistic categories are the GOLD ontology, CLARIN CCR, OLiA, or TermWeb's DatCatInfo, and also the Universal Dependencies inventory, on the assumption that its URIs are going to persist. It is imaginable that a project may choose to address a local taxonomy store instead, but this risks losing the advantage of interchangeability with other projects. Historically, datcat and valueDatcat originate from the (now obsolete) ISO 12620:2009 standard, describing the data model and procedures for a Data Category Registry (DCR). The current version of that standard, ISO 12620-1, does not standardize the serialization of pointers, merely mentioning the TEI att.datcat as an example. Note that no constraint prevents the occurrence of a combination of att.datcat attributes: the <fDecl> element, which is a natural bearer of the targetDatcat attribute, is an instance of a specific modeling element, and, in principle, could be semantically fixed by an appropriate reference taxonomy of modeling devices. |
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] | |||||||||
Module | tei | ||||||||
Members | bibl editorialDecl langUsage listBibl listEvent listOrg listPerson listPlace projectDesc samplingDecl sourceDesc textClass | ||||||||
Attributes |
|
||||||||
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. |
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] | |||||||
Module | tei | ||||||
Members | back body div front geo gloss graphic msDesc p ptr ref standOff surface term text | ||||||
Attributes |
|
||||||
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. |
att.dimensions provides attributes for describing the size of physical objects. | |||||||||||||||||||||||||||||||||||||||
Module | tei | ||||||||||||||||||||||||||||||||||||||
Members | age birth date death floruit population state trait unclear | ||||||||||||||||||||||||||||||||||||||
Attributes |
|
att.divLike provides attributes common to all elements which behave in the same way as divisions. [4. Default Text Structure] | |||||||||||||||||
Module | tei | ||||||||||||||||
Members | div | ||||||||||||||||
Attributes |
|
att.docStatus provides attributes for use on metadata elements describing the status of a document. | |||||||||
Module | tei | ||||||||
Members | bibl change msDesc revisionDesc | ||||||||
Attributes |
|
||||||||
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>
|
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] | |||||||||||||||||
Module | tei | ||||||||||||||||
Members | affiliation age birth corr date death education event expan faith floruit gender langKnown location name occupation org orgName persName person place placeName population reg relation residence sex state trait unclear | ||||||||||||||||
Attributes |
|
||||||||||||||||
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. |
att.fragmentable provides attributes for representing fragmentation of a structural element, typically as a consequence of some overlapping hierarchy. | |||||||||||
Module | tei | ||||||||||
Members | att.divLike[div] att.segLike[c cl m pc phr s w] p | ||||||||||
Attributes |
|
att.global provides attributes common to all elements in the TEI encoding scheme. [1.3.1.1. Global Attributes] | |||||||||||||||||||||||||||||||||||||||||||||
Module | tei | ||||||||||||||||||||||||||||||||||||||||||||
Members | TEI abbr addName affiliation age author authority back bibl biblScope birth body c calendar calendarDesc catDesc catRef category cell change choice cit cl classDecl code corr date death desc district div divGen edition editionStmt editor editorialDecl education email emph encodingDesc event expan faith figDesc figure fileDesc floruit foreign forename front funder genName gender geo gloss graphic head hi ident idno interp interpGrp item label langKnown langUsage language licence link linkGrp list listBibl listEvent listOrg listPerson listPlace listPrefixDef listRelation location m mentioned msContents msDesc msIdentifier msName name note occupation org orgName orig p pc persName person phr place placeName population prefixDef profileDesc projectDesc ptr pubPlace publicationStmt publisher q quote ref reg region relatedItem relation repository residence resp respStmt revisionDesc roleName row s samplingDecl series settlement sex sic soCalled sourceDesc span spanGrp standOff state surface surname table tagsDecl taxonomy teiHeader term text textClass textLang title titleStmt trait unclear w zone | ||||||||||||||||||||||||||||||||||||||||||||
Attributes |
|
att.global.change provides attributes allowing its member elements to specify one or more states or revision campaigns with which they are associated. | |||||||
Module | transcr | ||||||
Members | att.global[TEI abbr addName affiliation age author authority back bibl biblScope birth body c calendar calendarDesc catDesc catRef category cell change choice cit cl classDecl code corr date death desc district div divGen edition editionStmt editor editorialDecl education email emph encodingDesc event expan faith figDesc figure fileDesc floruit foreign forename front funder genName gender geo gloss graphic head hi ident idno interp interpGrp item label langKnown langUsage language licence link linkGrp list listBibl listEvent listOrg listPerson listPlace listPrefixDef listRelation location m mentioned msContents msDesc msIdentifier msName name note occupation org orgName orig p pc persName person phr place placeName population prefixDef profileDesc projectDesc ptr pubPlace publicationStmt publisher q quote ref reg region relatedItem relation repository residence resp respStmt revisionDesc roleName row s samplingDecl series settlement sex sic soCalled sourceDesc span spanGrp standOff state surface surname table tagsDecl taxonomy teiHeader term text textClass textLang title titleStmt trait unclear w zone] | ||||||
Attributes |
|
att.global.facs provides attributes used to express correspondence between an element and all or part of a facsimile image or surface. [11.1. Digital Facsimiles] | |||||||
Module | transcr | ||||||
Members | att.global[TEI abbr addName affiliation age author authority back bibl biblScope birth body c calendar calendarDesc catDesc catRef category cell change choice cit cl classDecl code corr date death desc district div divGen edition editionStmt editor editorialDecl education email emph encodingDesc event expan faith figDesc figure fileDesc floruit foreign forename front funder genName gender geo gloss graphic head hi ident idno interp interpGrp item label langKnown langUsage language licence link linkGrp list listBibl listEvent listOrg listPerson listPlace listPrefixDef listRelation location m mentioned msContents msDesc msIdentifier msName name note occupation org orgName orig p pc persName person phr place placeName population prefixDef profileDesc projectDesc ptr pubPlace publicationStmt publisher q quote ref reg region relatedItem relation repository residence resp respStmt revisionDesc roleName row s samplingDecl series settlement sex sic soCalled sourceDesc span spanGrp standOff state surface surname table tagsDecl taxonomy teiHeader term text textClass textLang title titleStmt trait unclear w zone] | ||||||
Attributes |
|
att.global.linking provides a set of attributes for hypertextual linking. [16. Linking, Segmentation, and Alignment] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Module | linking | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Members | att.global[TEI abbr addName affiliation age author authority back bibl biblScope birth body c calendar calendarDesc catDesc catRef category cell change choice cit cl classDecl code corr date death desc district div divGen edition editionStmt editor editorialDecl education email emph encodingDesc event expan faith figDesc figure fileDesc floruit foreign forename front funder genName gender geo gloss graphic head hi ident idno interp interpGrp item label langKnown langUsage language licence link linkGrp list listBibl listEvent listOrg listPerson listPlace listPrefixDef listRelation location m mentioned msContents msDesc msIdentifier msName name note occupation org orgName orig p pc persName person phr place placeName population prefixDef profileDesc projectDesc ptr pubPlace publicationStmt publisher q quote ref reg region relatedItem relation repository residence resp respStmt revisionDesc roleName row s samplingDecl series settlement sex sic soCalled sourceDesc span spanGrp standOff state surface surname table tagsDecl taxonomy teiHeader term text textClass textLang title titleStmt trait unclear w zone] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Attributes |
|
att.global.rendition provides rendering attributes common to all elements in the TEI encoding scheme. [1.3.1.1.3. Rendition Indicators] | |||||||||||||||||||||||||||||||
Module | tei | ||||||||||||||||||||||||||||||
Members | att.global[TEI abbr addName affiliation age author authority back bibl biblScope birth body c calendar calendarDesc catDesc catRef category cell change choice cit cl classDecl code corr date death desc district div divGen edition editionStmt editor editorialDecl education email emph encodingDesc event expan faith figDesc figure fileDesc floruit foreign forename front funder genName gender geo gloss graphic head hi ident idno interp interpGrp item label langKnown langUsage language licence link linkGrp list listBibl listEvent listOrg listPerson listPlace listPrefixDef listRelation location m mentioned msContents msDesc msIdentifier msName name note occupation org orgName orig p pc persName person phr place placeName population prefixDef profileDesc projectDesc ptr pubPlace publicationStmt publisher q quote ref reg region relatedItem relation repository residence resp respStmt revisionDesc roleName row s samplingDecl series settlement sex sic soCalled sourceDesc span spanGrp standOff state surface surname table tagsDecl taxonomy teiHeader term text textClass textLang title titleStmt trait unclear w zone] | ||||||||||||||||||||||||||||||
Attributes |
|
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] | |||||||||||||||||
Module | tei | ||||||||||||||||
Members | att.global[TEI abbr addName affiliation age author authority back bibl biblScope birth body c calendar calendarDesc catDesc catRef category cell change choice cit cl classDecl code corr date death desc district div divGen edition editionStmt editor editorialDecl education email emph encodingDesc event expan faith figDesc figure fileDesc floruit foreign forename front funder genName gender geo gloss graphic head hi ident idno interp interpGrp item label langKnown langUsage language licence link linkGrp list listBibl listEvent listOrg listPerson listPlace listPrefixDef listRelation location m mentioned msContents msDesc msIdentifier msName name note occupation org orgName orig p pc persName person phr place placeName population prefixDef profileDesc projectDesc ptr pubPlace publicationStmt publisher q quote ref reg region relatedItem relation repository residence resp respStmt revisionDesc roleName row s samplingDecl series settlement sex sic soCalled sourceDesc span spanGrp standOff state surface surname table tagsDecl taxonomy teiHeader term text textClass textLang title titleStmt trait unclear w zone] | ||||||||||||||||
Attributes |
|
||||||||||||||||
Example |
Blessed are the
<choice>
<sic>cheesemakers</sic>
<corr resp="#editor" cert="high">peacemakers</corr>
</choice>: for they shall be called the children of God.
|
||||||||||||||||
Example |
<!-- 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>
|
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] | |||||||||||
Module | tei | ||||||||||
Members | att.global[TEI abbr addName affiliation age author authority back bibl biblScope birth body c calendar calendarDesc catDesc catRef category cell change choice cit cl classDecl code corr date death desc district div divGen edition editionStmt editor editorialDecl education email emph encodingDesc event expan faith figDesc figure fileDesc floruit foreign forename front funder genName gender geo gloss graphic head hi ident idno interp interpGrp item label langKnown langUsage language licence link linkGrp list listBibl listEvent listOrg listPerson listPlace listPrefixDef listRelation location m mentioned msContents msDesc msIdentifier msName name note occupation org orgName orig p pc persName person phr place placeName population prefixDef profileDesc projectDesc ptr pubPlace publicationStmt publisher q quote ref reg region relatedItem relation repository residence resp respStmt revisionDesc roleName row s samplingDecl series settlement sex sic soCalled sourceDesc span spanGrp standOff state surface surname table tagsDecl taxonomy teiHeader term text textClass textLang title titleStmt trait unclear w zone] | ||||||||||
Attributes |
|
||||||||||
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. |
att.internetMedia provides attributes for specifying the type of a computer resource using a standard taxonomy. | |||||||
Module | tei | ||||||
Members | att.media[graphic] ptr ref | ||||||
Attributes |
|
||||||
Example | In 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. |
att.interpLike provides attributes for elements which represent a formal analysis or interpretation. [17.2. Global Attributes for Simple Analyses] | |||||||||||||||||||||||||
Module | tei | ||||||||||||||||||||||||
Members | interp interpGrp span spanGrp | ||||||||||||||||||||||||
Attributes |
|
att.lexicographic.normalized provides attributes for usage within word-level elements in the analysis module and within lexicographic microstructure in the dictionaries module. | |||||||||||||||||||||||||||||||
Module | analysis | ||||||||||||||||||||||||||||||
Members | att.linguistic[pc w] | ||||||||||||||||||||||||||||||
Attributes |
|
||||||||||||||||||||||||||||||
Note |
It needs to be stressed that the two attributes in this class are meant for strictly lexicographic and linguistic uses, and not for editorial interventions. For the latter, the mechanism based on <choice>, <orig>, and <reg> needs to be employed. |
att.linguistic provides a set of attributes concerning linguistic features of tokens, for usage within token-level elements, specifically <w> and <pc> in the analysis module. [17.4.2. Lightweight Linguistic Annotation] | |||||||||||||||||||||||||||||||||||||||||||||||||||||
Module | analysis | ||||||||||||||||||||||||||||||||||||||||||||||||||||
Members | pc w | ||||||||||||||||||||||||||||||||||||||||||||||||||||
Attributes |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
Note |
These attributes make it possible to encode simple language corpora and to add a layer of linguistic information to any tokenized resource. See section 17.4.2. Lightweight Linguistic Annotation for discussion. |
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] | |||||||
Module | tei | ||||||
Members | event | ||||||
Attributes |
|
att.media provides attributes for specifying display and related properties of external media. | |||||||||||||||||||
Module | tei | ||||||||||||||||||
Members | graphic | ||||||||||||||||||
Attributes |
|
att.msClass provides attributes to indicate text type or classification. [10.6. Intellectual Content 10.6.1. The msItem and msItemStruct Elements] | |||||||
Module | msdescription | ||||||
Members | msContents | ||||||
Attributes |
|
att.msExcerpt (manuscript excerpt) provides attributes used to describe excerpts from a manuscript placed in a description thereof. [10.6. Intellectual Content] | |||||||
Module | msdescription | ||||||
Members | msContents quote | ||||||
Attributes |
|
||||||
Note |
In the case of an incipit, indicates whether the incipit as given is defective, i.e. the first words of the text as preserved, as opposed to the first words of the work itself. In the case of an explicit, indicates whether the explicit as given is defective, i.e. the final words of the text as preserved, as opposed to what the closing words would have been had the text of the work been whole. |
att.naming provides attributes common to elements which refer to named persons, places, organizations etc. [3.6.1. Referring Strings 13.3.7. Names and Nyms] | |||||||||||||||
Module | tei | ||||||||||||||
Members | att.personal[addName forename genName name orgName persName placeName roleName surname] affiliation author birth death district editor education event occupation population pubPlace region repository residence settlement state trait | ||||||||||||||
Attributes |
|
att.patternReplacement provides attributes for regular-expression matching and replacement. [16.2.3. Using Abbreviated Pointers 2.3.6.3. Milestone Method 2.3.6. The Reference System Declaration 2.3.6.2. Search-and-Replace Method] | |||||||||||||||||
Module | header | ||||||||||||||||
Members | prefixDef | ||||||||||||||||
Attributes |
|
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] | |||||||||||||||
Module | tei | ||||||||||||||
Members | addName forename genName name orgName persName placeName roleName surname | ||||||||||||||
Attributes |
|
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] | |||||||||||||
Module | tei | ||||||||||||
Members | figure head label note | ||||||||||||
Attributes |
|
att.pointing provides a set of attributes used by all elements which point to other elements by means of one or more URI references. [1.3.1.1.2. Language Indicators 3.7. Simple Links and Cross-References] | |||||||||||||||||||||||||||||||
Module | tei | ||||||||||||||||||||||||||||||
Members | att.pointing.group[linkGrp] calendar catRef gloss licence link note ptr ref span term | ||||||||||||||||||||||||||||||
Attributes |
|
att.ranging provides attributes for describing numerical ranges. | |||||||||||||||||||||||||||||||
Module | tei | ||||||||||||||||||||||||||||||
Members | att.dimensions[age birth date death floruit population state trait unclear] | ||||||||||||||||||||||||||||||
Attributes |
|
||||||||||||||||||||||||||||||
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.
|
att.resourced provides attributes by which a resource (such as an externally held media file) may be located. | |||||||
Module | tei | ||||||
Members | graphic | ||||||
Attributes |
|
att.segLike provides attributes for elements used for arbitrary segmentation. [16.3. Blocks, Segments, and Anchors 17.1. Linguistic Segment Categories] | |||||||||
Module | tei | ||||||||
Members | c cl m pc phr s w | ||||||||
Attributes |
|
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] | |||||||||||
Module | tei | ||||||||||
Members | bibl event idno item list listBibl listEvent listOrg listPerson listPlace listRelation msDesc org person place relation term | ||||||||||
Attributes |
|
att.tableDecoration provides attributes used to decorate rows or cells of a table. [14. Tables, Formulæ, Graphics, and Notated Music] | |||||||||||||||||||||||||||||||
Module | figures | ||||||||||||||||||||||||||||||
Members | cell row | ||||||||||||||||||||||||||||||
Attributes |
|
att.translatable provides attributes used to indicate the status of a translatable portion of an ODD document. | |||||||||
Module | tagdocs | ||||||||
Members | desc gloss | ||||||||
Attributes |
|
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] | |||||||||||||||||||
Module | tei | ||||||||||||||||||
Members | att.pointing.group[linkGrp] TEI abbr addName affiliation age bibl birth c calendar change cit cl corr date death desc district div divGen education event faith figure forename genName gender gloss graphic head ident idno label link list listBibl listEvent listOrg listPerson listPlace listRelation location m msDesc msName name note occupation org orgName pc persName phr place placeName population ptr quote ref reg region relatedItem relation residence roleName s settlement sex standOff state surface surname table term text title trait w zone | ||||||||||||||||||
Attributes |
|
||||||||||||||||||
Schematron |
<sch:rule context="tei:*[@subtype]">
<sch:assert test="@type">The <sch:name/> element should not be categorized in detail
with @subtype unless also categorized in general with @type</sch:assert>
</sch:rule>
|
||||||||||||||||||
Note |
When appropriate, values from an established typology should be used. Alternatively a typology may be defined in the associated TEI header. If values are to be taken from a project-specific list, this should be defined using the <valList> element in the project-specific schema description, as described in 23.3.1.3. Modification of Attribute and Attribute Value Lists . |
att.written provides attributes to indicate the hand in which the content of an element was written in the source being transcribed. [1.3.1. Attribute Classes] | |||||||
Module | tei | ||||||
Members | div figure head hi label note p text zone | ||||||
Attributes |
|
macro.limitedContent (paragraph content) defines the content of prose elements that are not used for transcription of extant materials. [1.3. The TEI Class System] | |
Module | tei |
Used by | |
Content model |
<content> <alternate minOccurs="0" maxOccurs="unbounded"> <textNode/> <classRef key="model.limitedPhrase"/> <classRef key="model.inter"/> </alternate> </content> ⚓ |
Declaration |
macro.limitedContent = ( text | model.limitedPhrase | model.inter )*⚓ |
macro.paraContent (paragraph content) defines the content of paragraphs and similar elements. [1.3. The TEI Class System] | |
Module | tei |
Used by | |
Content model |
<content> <alternate minOccurs="0" maxOccurs="unbounded"> <textNode/> <classRef key="model.paraPart"/> </alternate> </content> ⚓ |
Declaration |
macro.paraContent = ( text | model.paraPart )*⚓ |
macro.phraseSeq (phrase sequence) defines a sequence of character data and phrase-level elements. [1.4.1. Standard Content Models] | |
Module | tei |
Used by | |
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 )*⚓ |
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] | |
Module | tei |
Used by | |
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 )*⚓ |
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] | |
Module | tei |
Used by | |
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 )*⚓ |
teidata.certainty defines the range of attribute values expressing a degree of certainty. | |
Module | tei |
Used by | |
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. |
teidata.count defines the range of attribute values used for a non-negative integer value used as a count. | |
Module | tei |
Used by | |
Content model |
<content> <dataRef name="nonNegativeInteger"/> </content> ⚓ |
Declaration |
teidata.count = xsd:nonNegativeInteger⚓ |
Note |
Any positive integer value or zero is permitted |
teidata.duration.iso defines the range of attribute values available for representation of a duration in time using ISO 8601 standard formats | |
Module | tei |
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 For complete details, see ISO 8601 Data elements and interchange formats — Information interchange — Representation of dates and times. |
teidata.duration.w3c defines the range of attribute values available for representation of a duration in time using W3C datatypes. | |
Module | tei |
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 For complete details, see the W3C specification. |
teidata.enumerated defines the range of attribute values expressed as a single XML name taken from a list of documented possibilities. | |
Module | tei |
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. |
teidata.gender defines the range of attribute values used to represent the gender of a person, persona, or character. | |
Module | tei |
Used by | |
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). |
teidata.language defines the range of attribute values used to identify a particular combination of human language and writing system. [6.1. Language Identification] | |
Module | tei |
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.
There are two exceptions to the above format. First, there are language tags in the IANA registry that do not match the above syntax, but are present because they have been ‘grandfathered’ from previous specifications. Second, an entire language tag can consist of only a private use subtag. These tags
start with Examples include
The W3C Internationalization Activity has published a useful introduction to BCP 47, Language tags in HTML and XML. |
teidata.name defines the range of attribute values expressed as an XML Name. | |
Module | tei |
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. |
teidata.namespace defines the range of attribute values used to indicate XML namespaces as defined by the W3C Namespaces in XML Technical Recommendation. | |
Module | tei |
Used by | |
Content model |
<content> <dataRef restriction="\S+" name="anyURI"/> </content> ⚓ |
Declaration |
teidata.namespace = xsd:anyURI { pattern = "\S+" }⚓ |
Note |
The range of syntactically valid values is defined by RFC 3986 Uniform Resource Identifier (URI): Generic Syntax |
teidata.numeric defines the range of attribute values used for numeric values. | |
Module | tei |
Used by | |
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. |
teidata.outputMeasurement defines a range of values for use in specifying the size of an object that is intended for display. | |
Module | tei |
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. |
teidata.pattern defines attribute values which are expressed as a regular expression. | |
Module | tei |
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 WikipediaH(ä|ae?)ndel (or alternatively, it is said that the pattern H(ä|ae?)ndel matches each of the three strings)This TEI datatype is mapped to the XSD token datatype, and may therefore contain any string of characters. However, it is recommended that the value used conform to the particular flavour of regular expression syntax supported by XSD Schema. |
teidata.point defines the data type used to express a point in cartesian space. | |
Module | tei |
Used by | |
Content model |
<content> <dataRef name="token" restriction="(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)"/> </content> ⚓ |
Declaration |
teidata.point = token { pattern = "(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)" }⚓ |
Example |
<facsimile>
<surface ulx="0" uly="0" lrx="400" lry="280">
<zone points="220,100 300,210 170,250 123,234">
<graphic url="handwriting.png"/>
</zone>
</surface>
</facsimile>
|
Note |
A point is defined by two numeric values, which should be expressed as decimal numbers. Neither number can end in a decimal point. E.g., both 0.0,84.2 and 0,84 are allowed, but 0.,84. is not. |
teidata.pointer defines the range of attribute values used to provide a single URI, absolute or relative, pointing to some other resource, either within the current document or elsewhere. | |
Module | tei |
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, |
teidata.prefix defines a range of values that may function as a URI scheme name. | |
Module | tei |
Used by |
Element:
|
Content model |
<content> <dataRef name="token" restriction="[a-z][a-z0-9\+\.\-]*"/> </content> ⚓ |
Declaration |
teidata.prefix = token { pattern = "[a-z][a-z0-9\+\.\-]*" }⚓ |
Note |
This datatype is used to constrain a string of characters to one that can be used as a URI scheme name according to RFC 3986, section 3.1. Thus only the 26 lowercase letters a–z, the 10 digits 0–9, the plus sign, the period, and the hyphen are permitted, and the value must start with a letter. |
teidata.probCert defines a range of attribute values which can be expressed either as a numeric probability or as a coded certainty value. | |
Module | tei |
Used by | |
Content model |
<content> <alternate> <dataRef key="teidata.probability"/> <dataRef key="teidata.certainty"/> </alternate> </content> ⚓ |
Declaration |
teidata.probCert = teidata.probability | teidata.certainty⚓ |
teidata.probability defines the range of attribute values expressing a probability. | |
Module | tei |
Used by | |
Content model |
<content> <dataRef name="double"> <dataFacet name="minInclusive" value="0"/> <dataFacet name="maxInclusive" value="1"/> </dataRef> </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. |
teidata.sex defines the range of attribute values used to identify the sex of an organism. | |
Module | tei |
Used by | |
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. |
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. | |
Module | tei |
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. |
teidata.temporal.w3c defines the range of attribute values expressing a temporal expression such as a date, a time, or a combination of them, that conform to the W3C XML Schema Part 2: Datatypes Second Edition specification. | |
Module | tei |
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. |
teidata.temporal.working defines the range of values, conforming to the W3C XML Schema Part 2: Datatypes Second Edition specification, expressing a date or a date and a time within the working life of the document. | |
Module | tei |
Used by | |
Content model |
<content> <alternate> <dataRef name="date" restriction="(19[789][0-9]|[2-9][0-9]{3}).*"/> <dataRef name="dateTime" restriction="(19[789][0-9]|[2-9][0-9]{3}).*"/> </alternate> </content> ⚓ |
Declaration |
teidata.temporal.working = xsd:date { pattern = "(19[789][0-9]|[2-9][0-9]{3}).*" } | xsd:dateTime { pattern = "(19[789][0-9]|[2-9][0-9]{3}).*" }⚓ |
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. The earliest time expressable with this datatype is 01 January 1970 (the Unix Epoch), which could be written as either 1970-01-01 or 1970-01-01T00:00:00Z. |
teidata.text defines the range of attribute values used to express some kind of identifying string as a single sequence of Unicode characters possibly including whitespace. | |
Module | tei |
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. |
teidata.truthValue defines the range of attribute values used to express a truth value. | |
Module | tei |
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. |
teidata.unboundedCount defines the range of values used for a counting number or the string unbounded for infinity. | |
Module | tei |
Used by | |
Content model |
<content> <alternate> <dataRef name="nonNegativeInteger"/> <valList type="closed"> <valItem ident="unbounded"/> </valList> </alternate> </content> ⚓ |
Declaration |
teidata.unboundedCount = xsd:nonNegativeInteger | ( "unbounded" )⚓ |
teidata.version defines the range of attribute values which may be used to specify a TEI or Unicode version number. | |
Module | tei |
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 (https://unicode.org/versions/). A version number contains digits and fullstop characters only. The first number supplied identifies the major version number. A second and third number, for minor and sub-minor version numbers, may also be supplied. |
teidata.versionNumber defines the range of attribute values used for version numbers. | |
Module | tei |
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}" }⚓ |
teidata.word defines the range of attribute values expressed as a single word or token. | |
Module | tei |
Used by | |
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. |
teidata.xTruthValue (extended truth value) defines the range of attribute values used to express a truth value which may be unknown. | |
Module | tei |
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. |
teidata.xpath defines attribute values which contain an XPath expression. | |
Module | tei |
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. |
Schematron |
<sch:rule context="tei:linkGrp[@type='businesses']/tei:ptr">
<sch:let name="taxDoc"
value="if (doc-available('../taxonomies.xml')) then doc('../taxonomies.xml')
else if (doc-available('../data/taxonomies.xml')) then doc('../data/taxonomies.xml')
else doc('taxonomies.xml')"/>
<sch:let name="businesses"
value="for $c in $taxDoc//tei:taxonomy[@xml:id='businesses']/descendant::tei:category
return concat('bs:', $c/@xml:id)"/>
<sch:assert test="@target = $businesses"> ERROR: the value of @target must be one
of <sch:value-of select="string-join($businesses, ', ')"/>.
</sch:assert>
</sch:rule>
|
Schematron |
<sch:rule context="tei:event[not(@xml:id) or not(matches(@xml:id, '^ev_\d\d\d\d_\d+$'))]">
<sch:let name="year"
value="tokenize(ancestor::tei:TEI/@xml:id, '_')[2]"/>
<sch:let name="maxId"
value="max((for $i in //tei:event[@xml:id][matches(xs:string(@xml:id), '^ev_\d+_\d+$')]/@xml:id
return xs:integer(tokenize($i, '_')[3])))"/>
<sch:let name="nextId"
value="'ev_' || $year || '_' || xs:string($maxId + 1)"/>
<sch:assert test="@xml:id and matches(@xml:id, '^ev_\d\d\d\d_\d+$')"> ERROR: event
elements must have a unique xml:id. The next available id is <sch:value-of select="$nextId"/>
</sch:assert>
</sch:rule>
|
Schematron |
<sch:rule context="tei:TEI">
<sch:let name="fname"
value="concat(@xml:id, '.xml')"/>
<sch:assert test="ends-with(document-uri(/), $fname)"> ERROR: The @xml:id of your
document (<sch:value-of select="@xml:idid"/>)
does not match the document file name (<sch:value-of select="document-uri(/)"/>).
</sch:assert>
</sch:rule>
|
Schematron |
<sch:rule context="tei:listPerson/tei:person[@corresp]">
<sch:let name="ptr" value="@corresp"/>
<sch:assert test="not(following-sibling::tei:person[@corresp = $ptr])"> ERROR: The
person element pointing to <sch:value-of select="$ptr"/> is duplicated.
</sch:assert>
</sch:rule>
|
Schematron |
<sch:rule context="tei:*[text()][not(ancestor-or-self::tei:code or ancestor::tei:TEI[@xml:id='search'])]">
<sch:assert test="not(text()[matches(., $straightQuotes)])"> Do not use straight quotes
in text. Use the q or
title elements wherever possible; for apostrophes,
use the smart version (’).
</sch:assert>
</sch:rule>
|
Schematron |
<sch:rule context="tei:event/tei:listPerson/tei:person[@corresp]/tei:persName">
<sch:assert test="xs:string(.) = normalize-space(.)"> ERROR: Avoid leading, trailing,
and multiple spaces in persNames.
</sch:assert>
</sch:rule>
|
Schematron |
<sch:rule context="tei:biblScope[@unit='page']">
<sch:assert test="matches(., '^[ivxlcA-Z\d\s–;,]+$')"> ERROR: page ranges should contain
only digits, en dashes, and optionally semicolons or commas and spaces for disjoint
ranges.
</sch:assert>
<sch:let name="ranges"
value="tokenize(., ';\s+')"/>
<sch:assert test="every $r in $ranges satisfies matches($r, '^[ivxlcA-Z\d–]+$')">
ERROR: This page range does not seem to conform to our conventions. Use semi-colons
to separate distinct pages or ranges.
</sch:assert>
</sch:rule>
|
Schematron |
<sch:rule context="tei:person[@xml:id]">
<sch:assert test="matches(@xml:id, '^[a-z]{4,4}\d+$')"> ERROR: The @xml:id attribute
of a person element should conform to the pattern
xxxx1 (four lower-case letters + a number).
</sch:assert>
</sch:rule>
|
Schematron |
<sch:rule context="tei:person[not(@xml:id) and not(@corresp)]">
<sch:assert test="@xml:id"> ERROR: person elements must have a unique xml:id. Please
type the first four letters of the id you need, and the next available id will be
shown.
</sch:assert>
</sch:rule>
<sch:rule context="tei:person[matches(@xml:id, '^[a-z]{4,4}$')]">
<sch:let name="letters"
value="xs:string(@xml:id)"/>
<sch:let name="maxId"
value="max((0, for $i in //tei:person[@xml:id][matches(xs:string(@xml:id),
'^' || $letters || '\d+$')]/@xml:id return xs:integer(substring($i,
5))))"/>
<sch:let name="nextId"
value="$letters || xs:string($maxId + 1)"/>
<sch:assert test="@xml:id[string-length(.) gt 4]"> NOTE: <sch:value-of select="$nextId"/>
is the next available id for the letter prefix <sch:value-of select="$letters"/>.
</sch:assert>
</sch:rule>
|
Schematron |
<sch:rule context="tei:event/tei:listPerson/tei:listRelation/tei:relation">
<sch:assert test="starts-with(@active, 'pros:') and starts-with(@passive, 'pros:')">
ERROR: @passive and @active ids must start with the pros: prefix.
</sch:assert>
</sch:rule>
|
Schematron |
<sch:rule context="tei:event/tei:listPerson/tei:listRelation/tei:relation">
<sch:let name="personPtrs"
value="distinct-values(ancestor::tei:listPerson/tei:person/@corresp)"/>
<sch:assert test="xs:string(@active) = $personPtrs and xs:string(@passive = $personPtrs)">
ERROR: A relation element has a pointer to <sch:value-of select="."/>, but there is
no corresponding
person element in the listPerson.
</sch:assert>
</sch:rule>
|
Schematron |
<sch:ns uri="http://www.w3.org/1999/xhtml"
prefix="xh"/>
<sch:ns uri="http://hcmc.uvic.ca/ns"
prefix="hcmc"/>
<sch:pattern>
<sch:let name="smartDouble" value="'[“”]'"/>
<sch:let name="smartSingle" value="'[‘’]'"/>
<sch:let name="straightDouble" value="'"'"/>
<sch:let name="straightApos" value="''''"/>
<sch:let name="straightQuotes"
value="concat('[', $straightDouble, $straightApos, ']')"/>
</sch:pattern>
|