The element adjustments
declares alterations. In a class-1 file, it specifies alterations that have been made to the underlying source. In a class-2 file, it specifies alterations that should be made to the class-1 source(
s) before processing any claims in the <body>
.
The sequence of consecutive adjustments matters, in that their contents will be processed first by priority (<skip>
, <rename>
, <equate>
, <reassign>
), then in document order. The instructions in one <adjustment>
may render null an instruction in a lower-priority, or subsequent adjustment action.
Used by: ~adjustment-list
Caution | |
---|---|
Any range in either an |
Example 12.134. <adjustments>
<head> ......... <redivision> ......... </redivision> <adjustments> <normalization which="no hyphens"/> </adjustments> <vocabulary-key> ......... </vocabulary-key> ......... </head>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-logical |
Example 12.135. <adjustments>
<head> ......... <model> ......... </model> <adjustments> <normalization which="no hyphens"/> </adjustments> <vocabulary-key> ......... </vocabulary-key> ......... </head>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-scriptum |
Example 12.136. <adjustments>
<head> ......... <model> ......... </model> <adjustments> <normalization which="no hyphens"/> </adjustments> <vocabulary-key> ......... </vocabulary-key> ......... </head>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949 |
Example 12.137. <adjustments>
<head> ......... <redivision> ......... </redivision> <adjustments> <normalization which="no hyphens"/> <normalization which="no ligatures"/> </adjustments> <vocabulary-key> ......... </vocabulary-key> ......... </head>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.ref-logical |
The element algorithm
contains an IRI + name pattern identifying an algorithm.
The term "algorithm" covers any set of computational instructions. It does not include the hardware used to run the algorithm, nor does it identify any algorithms used to run an algorithm. For example, an algorithm might identify one or more XSLT stylesheets, but it does not identify the engine (e.g., Saxon), catalyzing software (e.g., oXygen), or operating system (e.g., Windows) used to run the algorithm.
Used by: ~voc-element-agent
Caution | |
---|---|
An element that has a |
Caution | |
---|---|
Every TAN file referred to by way of an element containing |
Caution | |
---|---|
No element may point to a TAN file that has an identical |
Important | |
---|---|
If a target file has children items in the |
Important | |
---|---|
If a target file has a |
Important | |
---|---|
If a target file points only to non-local locations and no internet is available, the following message will be returned. “No internet available.” |
Important | |
---|---|
If an element not essential to validation has no |
Example 12.138. <algorithm>
<head> ......... <vocabulary-key> <algorithm xml:id="xslt2"> <IRI>tag:textalign.net,2015:stylesheet:convert-tan2018-to-tan2020</IRI> <name>Stylesheet to create a TAN file.</name> <location href="../applications/convert/convert%20TAN%202018%20to%20TAN%202020.xsl" accessed-when="2018-08-04T23:55:36.096-04:00"/> </algorithm> <div-type xml:id="ch"> ......... </div-type> ......... <person xml:id="kalvesmaki"> ......... </person> <algorithm xml:id="xslt1"> <IRI>tag:textalign.net,2015:stylesheet:convert-tan2017-to-tan2018</IRI> <name>Stylesheet to populate a TAN-A file from collections.</name> <location href="../applications/convert/convert%20TAN%202017%20to%20TAN%202018.xsl" accessed-when="2018-08-05"/> </algorithm> <role xml:id="editor"> ......... </role> ......... </vocabulary-key> ......... </head>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-logical |
Example 12.139. <algorithm>
<vocabulary-key> ......... <person xml:id="kalvesmaki"> ......... </person> <algorithm xml:id="xslt1"> <IRI>tag:textalign.net,2015:stylesheet:convert-tan2017-to-tan2018</IRI> <name>Stylesheet to populate a TAN-A file from collections.</name> <location href="../applications/convert/convert%20TAN%202017%20to%20TAN%202018.xsl" accessed-when="2018-08-02"/> </algorithm> <role xml:id="editor"> ......... </role> ......... </vocabulary-key>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-scriptum |
Example 12.140. <algorithm>
<vocabulary-key> <algorithm xml:id="xslt2"> <IRI>tag:textalign.net,2015:stylesheet:convert-tan2018-to-tan2020</IRI> <name>Stylesheet to create a TAN file.</name> <location href="../applications/convert/convert%20TAN%202018%20to%20TAN%202020.xsl" accessed-when="2018-08-05T00:03:20.142-04:00"/> </algorithm> <div-type xml:id="ch"> ......... </div-type> ......... </vocabulary-key>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949 |
The element alias
assigns a single id (@xml:id
or @id
) to multiple idrefs. An <alias>
effectively groups multiple vocabulary items together. @xml:id
and @id
are equivalent alternatives. The latter supports characters disallowed by the former (e.g., colons).
This feature is useful for creating groups of persons, works, scripta, etc., and referring to them. It is inspired by the model of the critical edition, where multiple manuscripts, each of which have their own identifier, can be assigned a family that has its own special siglum.
Because ids and idrefs are encapsulated within a single file, and because <alias>
serves exclusively idrefs, this element may neither include nor be included.
The sequence of consecutive <alias>
es is immaterial.
Used by: ~voc-key-core
Caution | |
---|---|
|
Example 12.141. <alias>
<vocabulary-key>
.........
<div-type xml:id="v" which="verse (scripture)"/>
<alias xml:id="test" idrefs="ch v"/>
</vocabulary-key>
Note | |
---|---|
Taken from matt.eng.kjv.1760 |
Example 12.142. <alias>
<head> ......... <vocabulary-key> <alias xml:id="all" idrefs="grc eng"/> <algorithm xml:id="xslt1"> ......... </algorithm> ......... <work xml:id="α.c" which="Explanationes de commentario graeco Ammonii"/> <alias xml:id="α.d" idrefs="α α.c"/> <work xml:id="φ" which="Lemmata de commentario graeco Ioannis Philoponi"/> <work xml:id="φ.c" which="Explanationes de commentario graeco Ioannis Philoponi"/> <alias xml:id="φ.d" idrefs="φ φ.c"/> <work xml:id="ο" which="Lemmata de commentario graeco Olympiodori"/> ......... </vocabulary-key> ......... </head>
Note | |
---|---|
Taken from ar.cat.TAN-A.claims |
The element align
declares one or more groups of word-tokens that should be aligned with each other. <align>
specifies that all the tokens invoked for one source collectively align with the tokens in the other. No special meaning is attached to sequences of <tok>
s that do not follow the source order.
The sequence of consecutive <align>
s is immaterial.
Used by: ~body-item
Example 12.143. <align>
<TAN-A-tok TAN-version="2021" id="tag:parkj@textalign.net,2015:TAN-A-tok,ring01+ring02"> ......... <body bitext-relation="B-descends-from-A" reuse-type="adaptation"> <align> <tok src="ring1881" ref="1" pos="1"/> <tok src="ring1987" ref="1" pos="1"/> </align> <align> <tok src="ring1881" ref="1" pos="2"/> <tok src="ring1987" ref="1" pos="2"/> </align> <align> <tok src="ring1881" ref="1" pos="3"/> <tok src="ring1987" ref="1" pos="3"/> </align> <align> <tok src="ring1881" ref="1" pos="4"/> <tok src="ring1987" ref="1" pos="4"/> </align> <align> ......... </align> ......... </body> </TAN-A-tok>
Note | |
---|---|
Taken from ringoroses.01+02.token.1 |
The element ana
contains a one or more assertions about the lexical or morphological properties of one or more tokens.
Claims within an <ana>
are distributive. That is, every combination of <l>
and <m>
within an <lm>
is claimed to be true for every <tok>
.
The sequence of consecutive <ana>
s is immaterial.
Used by: ~body-item
Example 12.144. <ana>
<TAN-A-lm TAN-version="2021" id="tag:kalvesmaki.com,2014:tan-t:ar.cat.grc.1949.minio-paluello:semantic-refs:TAN-A-lm:2016-04-05T07:07:40.033-04:00"> ......... <body lexicon="LSJ Lampe new" morphology="Perseus" claimant="xslt2"> <ana tok-pop="2"> <tok ref="11 2 1 1" pos="1"/> <lm> ......... </lm> </ana> <ana> <tok ref="10 6 3 2" pos="4"/> <tok ref="10 6 3 3" pos="15"/> <tok ref="10 6 4 2" pos="37"/> ......... </ana> <ana> <tok ref="8 3 5 4" pos="6"/> <tok ref="8 3 7 3" pos="7"/> <lm> ......... </lm> </ana> <ana> <tok ref="7 1 2 1" pos="12"/> <tok ref="7 3 1 3" pos="22"/> <tok ref="7 3 1 3" pos="24"/> ......... </ana> <ana> ......... </ana> ......... </body> </TAN-A-lm>
Note | |
---|---|
Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-A-lm-sample |
The element annotation
identifies a class-2 file that is an annotation on (and therefore a dependent of) the current file.
The sequence of consecutive <annotation>
s is immaterial.
Used by: ~networked-files-non-core
Caution | |
---|---|
|
Caution | |
---|---|
An element that has a |
Caution | |
---|---|
Every TAN file referred to by way of an element containing |
Caution | |
---|---|
No element may point to a TAN file that has an identical |
Important | |
---|---|
If a target file has children items in the |
Important | |
---|---|
If a target file has a |
Important | |
---|---|
If a target file points only to non-local locations and no internet is available, the following message will be returned. “No internet available.” |
Caution | |
---|---|
If a linking element points to a file that must be resolved, that file must be a TAN file. |
Example 12.145. <annotation>
<head> ......... <redivision> ......... </redivision> <annotation> <IRI>tag:parkj@textalign.net,2015:ar.cat.tan-a:claims</IRI> <name>Comments and claims on Aristotle's Categories</name> <location accessed-when="2021-04-29T11:29:58.992-04:00" href="TAN-A/ar.cat.TAN-A.claims.xml"/> </annotation> <adjustments> ......... </adjustments> ......... </head>
Note | |
---|---|
Taken from ar.cat.grc.1949.minio-paluello.ref-scriptum |
The element assert
names a pattern that, if found to be false in any <m>
in a dependent TAN-A-lm file, will return the enclosed message upon validation of the dependent file, along with an error or warning. Modeled on Schematron <report>
.
The sequence of consecutive <assert>
s is immaterial.
Used by: ~element-rule
Example 12.146. <assert>
<TAN-mor TAN-version="2021" id="tag:kalvesmaki.com,2014:tan-r-mor:eng:penn"> ......... <body> <rule m-matches=".+"> <assert m-has-how-many-codes="1">Features may not be combined.</assert> </rule> <rule> <where m-has-codes="$"/> <assert tok-matches="$">Only $ may be tagged as a dollar sign.</assert> </rule> ......... </body> </TAN-mor>
Note | |
---|---|
Taken from eng.kalvesmaki.com,2014.2 |
Example 12.147. <assert>
<rule m-matches="^. i"> <assert m-matches="^[dp]">An interrogative must be either a determiner (d) or a pronoun (p).</assert> </rule>
Note | |
---|---|
Taken from grc.perseus.tan-mor |
The element at-ref
restricts a claim to a particular abstract textual reference.
<at-ref>
was designed primarily to serve claims related to apparatus critici. In traditional critical editions, the main text has an apparatus at the bottom of the page, indicating variations in the manuscript, e.g., "A om." or "A: γάρ". These terse statements are shorthand for: "Manuscript A omits the passage at line X word Y" and "Manuscript A reads γάρ in place of the passage at line X word Y." In those statements, the siglum A refers to the subject, and the reading (or lack thereof) is the object. The qualifier "at line X word Y" is the phrase that corresponds to <at-ref>
. It functions much like <where>
, but the geography is textual rather than spatial.
<at-ref>
is special, and must be explicitly allowed or required by each <verb>
or @verb
's IRI + name pattern plus constraints.
<at-ref>
contains a textual reference, and will look similar to <subject>
or <object>
built as a texutal reference.
The sequence of consecutive <at-ref>
s is immaterial.
The element at-ref
specifies whether a verb uses <at-ref>
(default: disallowed).
Used by: ~element-claim
, ~constraints-on-verb
Example 12.148. <at-ref>
<TAN-A TAN-version="2021" id="tag:parkj@textalign.net,2015:ar.cat.tan-a:claims"> <head> ......... <vocabulary-key> ......... <verb xml:id="om"> ......... <constraints> <subject status="required" item-type="person work version scriptum"/> <at-ref status="required"/> <object status="disallowed"/> </constraints> </verb> ......... </vocabulary-key> ......... </head> <body claimant="park" claim-period="per2010s"> ......... <claim subject="andronicus boethus" adverb="perhaps" verb="om" xml:id="cl1a2a" claim-when="2017-03-10" claimant="park"> <at-ref src="grc" ref="1 a 2"> <tok pos="3-4"/> </at-ref> </claim> ......... <claim subject="B" verb="reads"> <at-ref src="grc" ref="1 a 5"> <tok pos="1-2"/> </at-ref> <object>τις ἀποδιδῷ</object> </claim> <claim subject="Λ" adverb="perhaps" verb="reads"> <at-ref src="grc" ref="1 a 5"> <tok pos="1-2"/> </at-ref> <object>τις ἀποδιδῷ</object> </claim> ......... </body> </TAN-A>
Note | |
---|---|
Taken from ar.cat.TAN-A.claims |
The element bitext-relation
identifies how the text of one text-bearing object relates to that of another by specifying a relationship, e.g., B is a direct copy of A; B and A descend from a commont parent, etc. See the section called “Token-based annotations and alignments (<TAN-A-tok>)” for theoretical background.
In most cases, there will be need for only one of these elements as a vocabulary item. But multiple values may be helpful for cases where a bitext has a complex history, for example, a textual object that was created over time, and in different phases.
This element should not be used to describe any activities (e.g., translation, copying), reserved for <reuse-type>
.
For examples see the section called “TAN keywords for types of bitext relations (<bitext-relation>)”
Used by: ~voc-element-non-class-2
Example 12.149. <bitext-relation>
<vocabulary-key> <algorithm xml:id="xslt2"> ......... </algorithm> <bitext-relation xml:id="B-descends-from-A"> <IRI>tag:textalign.net,2015:bitext-relation:a/x+/b</IRI> <name>B descends directly from A, unknown number of intermediaries</name> <desc>The 1987 versions is hypothesized to descend somehow from the 1881 version, mainly for the sake of illustration.</desc> </bitext-relation> <reuse-type xml:id="adaptation"> ......... </reuse-type> ......... </vocabulary-key>
Note | |
---|---|
Taken from ringoroses.01+02.token.1 |
Example 12.150. <bitext-relation>
<vocabulary-key> <algorithm xml:id="xslt2"> ......... </algorithm> <bitext-relation xml:id="unclear"> <IRI>tag:kalvesmaki@gmail.com,2014:bitext-relation:unclear</IRI> <name>The German and English versions bear some relationship, but what exactly is unclear.</name> </bitext-relation> <reuse-type xml:id="correlationGeneral"> ......... </reuse-type> ......... </vocabulary-key>
Note | |
---|---|
Taken from ringoroses.01+03.token.1 |
Example 12.151. <bitext-relation>
<vocabulary-key> <algorithm xml:id="xslt2"> ......... </algorithm> <bitext-relation xml:id="unclear"> <IRI>tag:kalvesmaki@gmail.com,2014:bitext-relation:unclear</IRI> <name>The German and English versions bear some relationship, but what exactly is unclear.</name> </bitext-relation> <reuse-type xml:id="correlationGeneral"> ......... </reuse-type> ......... </vocabulary-key>
Note | |
---|---|
Taken from ringoroses.01+03.token.2 |
The element body
contains the data of a TAN file.
Used by: ~TAN-root
Example 12.152. <body>
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2021"> <head> ......... </head> <body xml:lang="eng"> <div type="ch" n="1"> ......... </div> <div type="ch" n="2"> ......... </div> <div type="ch" n="3"> ......... </div> ......... </body> </TAN-T>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-logical |
Example 12.153. <body>
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:model-object-refs" TAN-version="2021"> <head> ......... </head> <body xml:lang="eng"> <div type="p" n="1"> ......... </div> <div type="p" n="2"> ......... </div> <div type="p" n="3"> ......... </div> ......... </body> </TAN-T>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-scriptum |
Example 12.154. <body>
<TAN-T TAN-version="2021" id="tag:kalvesmaki.com,2014:tan-t:ar.cat.fra.1844.saint-hilaire:semantic-refs-realigned"> <head> ......... </head> <body xml:lang="fra"> <div n="ti_1" type="ti"> ......... </div> <div n="1" type="ch"> ......... </div> <div n="2" type="ch"> ......... </div> ......... </body> </TAN-T>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949 |
Example 12.155. <body>
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.fra.1844.saint-hilaire:semantic-refs" TAN-version="2021"> <head> ......... </head> <body xml:lang="fra"> <div type="ti" n="ti">CATÉGORIES</div> <div type="sec" n="1"> ......... </div> <div type="sec" n="2"> ......... </div> ......... </body> </TAN-T>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.ref-logical |
The element category
groups a set of features that share a common grammatical trait such as gender, number, etc.
The order of consecutive <category>
s is important, dictating the sequence in which codes should appear in the values of <m>
in a dependent TAN-A-lm file.
Used by: ~features-categorized
Example 12.156. <category>
<TAN-mor TAN-version="2021" id="tag:kalvesmaki.com,2014:tan-r-mor:grc:perseus"> ......... <body> ......... <rule m-matches="^. v"> ......... </rule> <category feature="morphosyntactic_category"> <code feature="adjective"> ......... </code> <code feature="conjunction"> ......... </code> <code feature="adverb"> ......... </code> ......... </category> <category feature="secondary_morphosyntactic_category"> <code feature="article"> ......... </code> <code feature="adjectival_adverb"> ......... </code> <code feature="pronoun_reciprocal"> ......... </code> ......... </category> <category feature="feature_person"> <code feature="first"> ......... </code> <code feature="second"> ......... </code> <code feature="third"> ......... </code> </category> <category feature="feature_number"> <code feature="dual"> ......... </code> <code feature="plural"> ......... </code> <code feature="singular"> ......... </code> </category> <category feature="feature_tense"> ......... </category> ......... </body> </TAN-mor>
Note | |
---|---|
Taken from grc.perseus.tan-mor |
The element change
declares a change made to the current file. Must credit/blame someone, specified by @who
, and indicate when the change was made, specified by @when.
.
Collectively, <change>
elements are called the changelog, the revision history of the document.
The editor has discretion as to how long or detailed a <change>
should be, or how many should be retained in a changelog. Ideally, <change>
s documenting every published version should be retained.
<change>
elements may appear in any order, but it is good practice to put the most recent at the top.
Example 12.157. <change>
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2021"> <head> ......... <resp who="xslt1" roles="stylesheet1"/> <change when="2020-12-31" who="kalvesmaki">Added new reference-system declaration.</change> <change when="2016-06-22T08:04:25.003-04:00" who="kalvesmaki">Reformatted according to first model found. Backup made at file:/C:/Users/jdkalv/Dropbox/TAN/library/TAN-2018/examples/ar.cat.eng.1926.edghill.sem-201606220804250030400.xml.</change> <change when="2016-01-26-04:00" who="kalvesmaki">Started new file.</change> <change who="xslt1" when="2017-11-02T22:29:17.742-04:00">TAN file updated to 2018 schemas.</change> <change who="xslt2" when="2018-08-04T23:55:36.096-04:00">Converted from 2018 to 2019 schemas.</change> ......... </head> ......... </TAN-T>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-logical |
The element checksum
specifies some checksum value of a digital file. This element contains other elements that define the type and value of the checksum. Must begin with an IRI + name pattern that identifies the type of checksum being used (e.g., SHA-1).
This element allows other users to check to see if copies of a file are identical.
No checksums will be generated, checked, or validated by TAN schemas.
Used by: ~entity-digital-core-content
Example 12.158. <checksum>
<source> ......... <name>The Saint Patrick's Confessio Hypertext Stack Project edition</name> <checksum> <IRI>http://dbpedia.org/resource/Sha-1</IRI> <name>SHA-1</name> <value>91D95564ABDF2B2C1B9EEF016CBA51E8179646CC</value> </checksum> <location href="http://www.confessio.ie/sites/confessio.ie/files/downloads/confessio_english.xml" accessed-when="2015-01-25"/> </source>
Note | |
---|---|
Taken from patricius.confessio.2003.eng |
The element claim
makes one or more claims (assertions).
Used by: ~body-content-non-class-2
, ~complex-object
Caution | |
---|---|
Claims involving verbs whose constrained content requires specification of units must use |
Caution | |
---|---|
A claim with a verb that has content constraints must not allow other verbs. |
Caution | |
---|---|
Every |
Caution | |
---|---|
Every |
Caution | |
---|---|
No |
Example 12.159. <claim>
<TAN-A TAN-version="2021" id="tag:parkj@textalign.net,2015:ar.cat.tan-a:claims"> ......... <body claimant="park" claim-period="per2010s"> <comment when="2017-03-10-05:00" who="park">The next two claims interpret Minio-Paluello's apparatus criticus entry for 1a2, which claims that Andronicus and Boethus might have omitted τῆς οὐσίας (based on what Porphyry and Dexippus say) and asserts that the reading adopted is found in the seven commentators. The interpretation below sticks close to M-P's original, and does not fill in important gaps. For example, Dexippus's remark comes from his commentary, 1.18 (p. 21.20) and is reliant wholly on a fragment of Porphyry preserved in Simplicius's commentary, p. 30.1-2. Furthermore, a careful reading of these texts shows that Porphyry claimed not that Andronicus and Boethus omitted the text, or relied on sources that had omitted it, but that they observed that there were manuscripts that had done so.</comment> <claim subject="andronicus boethus" adverb="perhaps" verb="om" xml:id="cl1a2a" claim-when="2017-03-10" claimant="park"> <at-ref src="grc" ref="1 a 2"> ......... </at-ref> </claim> <claim subject="δ π" verb="shows" object="cl1a2a"/> <claim subject="comm-omnes" verb="attests" period="late_antiquity"> <object src="grc" ref="1 a 2"> ......... </object> </claim> <claim subject="comm-omnes" verb="attests" xml:id="cl1a2b"> <object src="grc" ref="1 a 2"> ......... </object> </claim> <claim subject="π" verb="shows" object="cl1a2b"/> ......... </body> </TAN-A>
Note | |
---|---|
Taken from ar.cat.TAN-A.claims |
The element code
attaches a grammatical feature to a code, and makes it available to a TAN-A-lm file.
Because vocabulary item for a grammatical feature is language-agnostic, and because a TAN-mor code is language-specific, guidance to the editor of a TAN-A-lm file may be important. Ihildren <desc>
s can be used to provide examples or other guidance.
Used by: ~element-category
, ~features-uncategorized
Caution | |
---|---|
Codes for features must be case-indifferently unique. |
Example 12.160. <code>
<TAN-mor TAN-version="2021" id="tag:kalvesmaki.com,2014:tan-r-mor:eng:penn"> ......... <body> ......... <rule m-has-codes="'' . ; :"> ......... </rule> <code feature="closing_quotation_mark"> <desc>Examples: ' ''</desc> <val>''</val> </code> <code feature="dash"> <desc>Example: --</desc> <val>--</val> </code> <code feature="dollar"> <desc>Examples: Examples: $ -$ --$ A$ C$ HK$ M$ NZ$ S$ U.S.$ US$</desc> <val>$</val> </code> <code feature="opening_parenthetical_punctuation"> <desc>Examples: ( [ {</desc> <val>[</val> </code> <code feature="closing_parenthetical_punctuation"> ......... </code> ......... </body> </TAN-mor>
Note | |
---|---|
Taken from eng.kalvesmaki.com,2014.2 |
The element comment
discusses issues relevant to nearby data. Must credit someone, specified by @who
, and indicate when the comment was made, specified by @when.
.
Used by: ~element-ana
, ~element-lm
, ~element-align
, ~element-category
, ~element-item
, ~element-replace
, ~element-adjustments
, ~element-group
, ~element-head
, ~element-license
, ~element-to-do
, ~element-vocabulary-key
, ~link-element-inclusion
, ~link-element-see-also
, ~body-content-core
, ~constraints-on-verb
, ~entity-digital-nontan-id
, ~entity-digital-nontan-no-id
, ~entity-digital-tan-id
, ~entity-digital-tan-no-id
, ~entity-nondigital-constrained
, ~entity-nondigital-id
, ~entity-nondigital-no-id
Example 12.161. <comment>
<redivision> ......... <location href="ar.cat.eng.1926.edghill.ref-logical.xml" accessed-when="2016-07-07T16:36:28.867-04:00"/> <comment who="kalvesmaki" when="2021-02-12">A scan is available here: https://ia600908.us.archive.org/33/items/worksofaristotle01arisuoft/worksofaristotle01arisuoft.pdf</comment> </redivision>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-scriptum |
Example 12.162. <comment>
<to-do> <comment when="2020-04-25" who="kalvesmaki">Text needs to be proofread</comment> </to-do>
Note | |
---|---|
Taken from ar.cat.lat.1961.minio-paluello.ref-scriptum |
Example 12.163. <comment>
<TEI TAN-version="2021" id="tag:parkj@textalign.net,2015:gomme.1898.ring-o-roses"> ......... <head> ......... <source> ......... <name>The traditional games of England, Scotland, and Ireland : with tunes, singing-rhymes, and methods of playing according to the variants extant and recorded in different parts of the Kingdom</name> <comment when="2015-03-10" who="park">This work is to be found at vol. 2, pp. 108-111.</comment> </source> ......... <to-do> <comment when="2018-08-09-04:00" who="park">Finish file.</comment> </to-do> </head> ......... </TEI>
Note | |
---|---|
Taken from gomme.1989.ring-o-roses |
The element companion-version
identifies a file closely associated with the current one.
In a class 1 file, <companion-version>
points to another class 1 file that has a different version of the same work found in the same scriptum.
In class 2 and class 3 files, <companion-version>
points to a file of the same type, but the nature of the relationship between the two files is not stipulated. It can be used to point to a continuation of a dataset, or to competing one.
The sequence of consecutive <companion-version>
s is immaterial.
Used by: ~networked-files-core
Caution | |
---|---|
|
Caution | |
---|---|
Class 1 files must share the same source as any redivision or companion version. |
Caution | |
---|---|
Class 1 files must share the same work as any model, redivision, or companion version. |
Example 12.164. <companion-version>
<head> ......... <source xml:id="eng"> ......... </source> <companion-version> <IRI>tag:parkj@textalign.net,2015:ar.cat.tan-a:claims</IRI> <name>Comments and claims on Aristotle's Categories</name> <location accessed-when="2021-04-29T11:41:57.716-04:00" href="ar.cat.TAN-A.claims.xml"/> </companion-version> <adjustments src="fra"> ......... </adjustments> ......... </head>
Note | |
---|---|
Taken from ar.cat.TAN-A |
The element constraints
specifies the expectations for a given verb. Any verb without constraints is presumed to be transitive, requiring a subject and an object, allowing adverbs, but disallowing opt-in elements, e.g., <in-lang>
.
Used by: ~entity-nondigital-with-constraints-content
Example 12.165. <constraints>
<head> ......... <vocabulary-key> ......... <verb xml:id="om"> ......... <desc>This verb is similar to the standard TAN verb "lacks", but expands the definition to persons.</desc> <constraints> <subject status="required" item-type="person work version scriptum"/> <at-ref status="required"/> <object status="disallowed"/> </constraints> </verb> <verb xml:id="attests"> ......... <desc>This verb is similar to the standard TAN verb "matches", but expands the definition to persons.</desc> <constraints> <subject status="required" item-type="person work version scriptum"/> <object status="required" item-type="ref"/> </constraints> </verb> <verb xml:id="has-length"> ......... <desc>This verb is used to describe the how many pages or folios a scriptum is.</desc> <constraints> <subject status="required" item-type="scriptum"/> <object status="required" content-datatype="integer" content-lexical-constraint="\d+"/> </constraints> </verb> ......... </vocabulary-key> ......... </head>
Note | |
---|---|
Taken from ar.cat.TAN-A.claims |
Example 12.166. <constraints>
<item> ......... <name>wrote</name> <constraints> <subject status="required" item-type="person"/> <object status="required" item-type="work version"/> </constraints> </item>
Note | |
---|---|
Taken from verbs.TAN-voc |
The element desc
provides a human-readable description of a concept, person, or thing referred to by the parent element (or the current document, if the parent element is <head>
). <desc>
is, in effect, a <comment>
about that concept, person, or thing.
Used by: ~element-code
, ~metadata-human-readable
Caution | |
---|---|
All text must be normalized (Unicode NFC). |
Example 12.167. <desc>
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2021"> <head> ......... <license licensor="kalvesmaki"> ......... <name>Creative Commons Attribution 4.0 International License</name> <desc>Exclusive of rights held and licenses offered by rightsholders of the source or sources listed below, this data file, insofar as it constitutes an independent work, is licensed under a Creative Commons Attribution 4.0 International License.</desc> </license> ......... <vocabulary-key> ......... <div-type xml:id="ic"> ......... <name>independent clause</name> <desc>used to identify two or more sentence parts that have a subject and predicate and function as a sentence.</desc> </div-type> ......... </vocabulary-key> ......... </head> ......... </TAN-T>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-logical |
Example 12.168. <desc>
<license licensor="kalvesmaki"> ......... <name>Creative Commons Attribution 4.0 International License</name> <desc>Exclusive of rights held and licenses offered by rightsholders of the source or sources listed below, this data file, insofar as it constitutes an independent work, is licensed under a Creative Commons Attribution 4.0 International License.</desc> </license>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-scriptum |
Example 12.169. <desc>
<license licensor="kalvesmaki"> ......... <name>Creative Commons Attribution 4.0 International License</name> <desc>Exclusive of rights held and licenses offered by rightsholders of the source or sources listed below, this data file, insofar as it constitutes an independent work, is licensed under a Creative Commons Attribution 4.0 International License.</desc> </license>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949 |
The element div
restricts a claim to a particular passage in a subject or object. In this context <div>
is especially useful for clarifying which part of a scriptum is meant, e.g., page ranges.
Unlike class-1 <div>
s, this one takes no text and no inclusions.
The sequence of consecutive <div>
s in a <subject>
or <object>
is important. A <div>
specifies not only which parts of an <object>
or <subject>
are relevant, but the sequence of those parts.
The element div
marks a textual unit. Contains other <div>
s or text, but not both (i.e., no mixed content).
TAN's <div>
differs from the TEI's, in that the latter is intended for the first level or levels of subdivision in the front, body, or back of a text, but not for paragraphs or anonymous blocks. The TAN <div>
better resembles HTML's, and can be applied to any kind of textual division, even a single character.
Used by: ~element-div
, ~scriptum-filter
, ~body-item
Caution | |
---|---|
All text must be normalized (Unicode NFC). |
Important | |
---|---|
Most div references are unique. |
Caution | |
---|---|
An |
Caution | |
---|---|
Every leaf div must have at least some non-space text. |
Caution | |
---|---|
No text may begin with a modifying character. |
Caution | |
---|---|
No text may have a spacing character followed by a modifying character. |
Caution | |
---|---|
No text may have Unicode characters that are disallowed, e.g., U+A0, NO BREAK SPACE. |
Caution | |
---|---|
No reference may point to a mixture of leaf and non-leaf |
Important | |
---|---|
An |
Important | |
---|---|
A |
Caution | |
---|---|
Each value in |
Example 12.170. <div>
<body xml:lang="eng"> <div type="ch" n="1"> <div type="par" n="1"> <div type="s" n="1"> <div type="ic" n="1">Things are said to be named 'equivocally' when, though they have a common name, the definition corresponding with the name differs for each. Thus, a real man and a figure in a picture can both lay claim to the name 'animal';</div> <div type="ic" n="2">yet these are equivocally so named, for, though they have a common name, the definition corresponding with the name differs for each.</div> <div type="ic" n="3">For should any one define in what sense each is an animal, his definition in the one case will be appropriate to that case only.</div> </div> <div type="s" n="2"> ......... </div> <div type="s" n="3"> ......... </div> </div> </div> <div type="ch" n="2"> ......... </div> ......... </body>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-logical |
The element div-type
declares a type of textual division (e.g., title, paragraph, stanza).
For more information, see the section called “One reference system” and the section called “TAN keywords for types of divisions (<div-type>)” for standard TAN values.
Used by: ~voc-element-tan-a
, ~voc-element-class-1
Example 12.171. <div-type>
<head> ......... <vocabulary-key> <algorithm xml:id="xslt2"> ......... </algorithm> <div-type xml:id="ch"> <IRI>http://dbpedia.org/resource/Chapter_(books)</IRI> <name>chapter</name> </div-type> <div-type xml:id="par"> <IRI>http://dbpedia.org/resource/Paragraph</IRI> <name xml:lang="eng">paragraph</name> </div-type> <div-type xml:id="s"> <IRI>http://dbpedia.org/resource/Sentence_(linguistics)</IRI> <name>sentence</name> </div-type> <div-type xml:id="ic"> <IRI>https://en.wikipedia.org/wiki/Independent_clause</IRI> <name>independent clause</name> <desc>used to identify two or more sentence parts that have a subject and predicate and function as a sentence.</desc> </div-type> <div-type xml:id="pt" which="part"/> ......... </vocabulary-key> ......... </head>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-logical |
The element equate
declares an ad hoc equivalence in @n
values. It behaves like <alias>
but has scope only over a particular source. For example, <equate n="pr pref preface introduction"/> specifies that sources with <div>
@n
values of either "pr", "pref", "preface", or "introduction" should be treated as equivalent. Hence, in the <body>
any @ref
="pr" will also match a <div n="introduction"/>
This element does not imply that the @n
values are the same. It merely states that, for the purposes of this class-2 file, they should be treated as equivalent.
Only the first <equate>
applying to a <div>
in a given source will be applied.
Used by: ~adjust-class-2
Important | |
---|---|
Only the first of multiple adjustment actions will be applied. Action priority: skip, ref-based rename, then for every |
Caution | |
---|---|
In adjustment actions involving |
Important | |
---|---|
At least one |
Example 12.172. <equate>
<adjustments src="fra">
<skip div-type="summ" shallow="false"/>
<equate n="ti title"/>
<reassign>
.........
</reassign>
</adjustments>
Note | |
---|---|
Taken from ar.cat.TAN-A |
The element feature
names, through its IRI + name pattern, a grammatical feature or concept (e.g., plural, subjunctive, 1st person) that is part of a language. In the context of <category>
a @code
is always included. The first <feature>
of a <category>
, however, never has a @code
, because it describes the grammatical class of the <category>
.
The sequence of consecutive <feature>
s is immaterial.
See the section called “TAN keywords for features (<feature>)” for a list of standard features.
Used by: ~voc-element-non-class-3
Example 12.173. <feature>
<head> ......... <vocabulary-key ed-when="2015-03-03" ed-who="kalvesmaki"> ......... <algorithm xml:id="xslt1"> ......... </algorithm> <feature xml:id="cl-quo"> <IRI>tag:textalign.net,2015:morphology:option:quotation-mark-closing</IRI> <name>closing quotation mark</name> <desc>Examples: ' ''</desc> </feature> <feature xml:id="dash"> <IRI>http://dbpedia.org/resource/Dash</IRI> <name>dash</name> <desc>Examples: --</desc> </feature> <feature xml:id="x24"> <IRI>http://dbpedia.org/resource/Dollar_sign</IRI> <name>dollar</name> <desc>Examples: $ -$ --$ A$ C$ HK$ M$ NZ$ S$ U.S.$ US$</desc> </feature> <feature xml:id="x2E"> <IRI>tag:textalign.net,2015:morphology:option:punctuation:sentence-closer</IRI> <name>sentence closer</name> <desc>Examples: ; . ! ?</desc> </feature> <feature xml:id="x3A"> ......... </feature> ......... </vocabulary-key> ......... </head>
Note | |
---|---|
Taken from eng.kalvesmaki.com,2014.2 |
The element file-resp
specifies the persons, organizations, or algorithms that are primarily responsible for the file. Any unattributed claims or assertions made in the file will be credited to/blamed upon these agents. At least one of these agents must be given an IRI in the namespace of the file @id.
.
Used by: ~resp-list
Example 12.174. <file-resp>
<head>
.........
<vocabulary-key>
.........
</vocabulary-key>
<file-resp who="kalvesmaki"/>
<resp who="xslt2" roles="stylesheet1"/>
.........
</head>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-logical |
Example 12.175. <file-resp>
<head>
.........
<vocabulary-key>
.........
</vocabulary-key>
<file-resp who="kalvesmaki"/>
<resp roles="editor" who="kalvesmaki"/>
.........
</head>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-scriptum |
Example 12.176. <file-resp>
<head>
.........
<vocabulary-key>
.........
</vocabulary-key>
<file-resp who="kalvesmaki"/>
<resp who="xslt2" roles="stylesheet1"/>
.........
</head>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949 |
Example 12.177. <file-resp>
<head>
.........
<vocabulary-key>
.........
</vocabulary-key>
<file-resp who="kalvesmaki"/>
<resp who="xslt2" roles="stylesheet1"/>
.........
</head>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.ref-logical |
The element for-lang
specifies a language that is being discussed. This element does not identify the language of the text enclosed by the parent element (one must use @xml:lang
for that purpose).
Values should adhere to BCP (Best Common Practices) 47, http://www.rfc-editor.org/rfc/bcp/bcp47.txt
. For more details see the section called “Languages”.
Examples: 'eng' (English), 'grc' (classical Greek), 'lat' (Latin). For more see the section called “Languages”
The sequence of consecutive <for-lang>
s is immaterial.
Used by: ~decl-non-class-2
, ~decl-non-class-3
Example 12.178. <for-lang>
<head> ......... <license which="Attribution-ShareAlike 3.0 Unported" licensor="perseus"/> <for-lang>grc</for-lang> <tok-is>ἆ</tok-is> ......... </head>
Note | |
---|---|
Taken from grc-tan-a-lm-%CE%B1 |
Example 12.179. <for-lang>
<head> ......... <license which="Attribution-ShareAlike 3.0 Unported" licensor="perseus"/> <for-lang>grc</for-lang> <tok-starts-with>αʹ</tok-starts-with> ......... </head>
Note | |
---|---|
Taken from grc-tan-a-lm-%CE%B1%CA%B9 |
Example 12.180. <for-lang>
<head> ......... <license licensor="kalvesmaki"> ......... </license> <for-lang>eng</for-lang> <source> ......... </source> ......... </head>
Note | |
---|---|
Taken from eng.kalvesmaki.com,2014.2 |
Example 12.181. <for-lang>
<head> ......... <license licensor="kalvesmaki"> ......... </license> <for-lang>grc</for-lang> <source> ......... </source> ......... </head>
Note | |
---|---|
Taken from grc.perseus.tan-mor |
Definition 1
The element from-tok
points to a single token that is the start of a range of tokens to be selected from a source, but without @ref.
.
Definition 2
The element from-tok
points to a single token that is the start of a range of tokens to be selected from a source, in the context of @ref.
.
Used by: ~text-passage-selector-no-ref
, ~text-passage-selector-with-ref
Caution | |
---|---|
Every token must be locatable in every cited ref in every source. |
Caution | |
---|---|
In a |
Example 12.182. <from-tok>
<passage ref="5 4 7 2">
<from-tok val=":" pos="1"/>
<through-tok val=":" pos="1"/>
</passage>
Note | |
---|---|
Taken from ar.cat.TAN-A |
Example 12.183. <from-tok>
<subject src="eng-uk">
<tok ref="2" pos="2-3" chars="3-4"/>
<from-tok ref="1" pos="3"/>
<through-tok ref="2" pos="1"/>
</subject>
Note | |
---|---|
Taken from ringoroses.div.1 |
The element group
groups token references that should be treated as referring to but a single token.
The element group
collects items that share a common property, defined by the <group-type>
to which it refers.
Used by: ~element-ana
, ~element-align
, ~body-group
Caution | |
---|---|
|
Caution | |
---|---|
|
Example 12.184. <group>
<ana> <group> <tok ref="1" pos="1 - last-1"/> </group> <lm> ......... </lm> </ana>
Note | |
---|---|
Taken from ring-o-roses.eng.1881.lm |
Example 12.185. <group>
<TAN-voc TAN-version="2021" id="tag:parkj@textalign.net,2015:TAN-key:ar.cat"> ......... <body affects-element="work"> ......... <item> ......... </item> <group> <item> ......... </item> <item> ......... </item> </group> <group> <item> ......... </item> <item> ......... </item> </group> <group> <item> ......... </item> <item> ......... </item> </group> <group> ......... </group> ......... </body> </TAN-voc>
Note | |
---|---|
Taken from ar.cat.TAN-voc |
The element group-type
names types of <group>
s. See the section called “TAN keywords for types of groups (<group-type>)” for standard TAN values.
Used by: ~voc-element-class-2
, ~voc-element-class-3
Example 12.186. <group-type>
<vocabulary-key>
.........
<morphology xml:id="Perseus">
.........
</morphology>
<group-type xml:id="status" which="status"/>
<person include="rel"/>
.........
</vocabulary-key>
Note | |
---|---|
Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-A-lm-sample |
Example 12.187. <group-type>
<head> ......... <vocabulary-key> <group-type xml:id="inline-start" which="no new line start"/> <group-type xml:id="inline-end" which="no new line end"/> <group-type xml:id="line-start" which="new line start"/> <group-type xml:id="line-end" which="new line end"/> ......... </vocabulary-key> ......... </head>
Note | |
---|---|
Taken from div-types.TAN-voc |
The element head
contains the metadata (data about the data in the <body>
)
For more see the section called “Metadata (<head>)”
Used by: ~TAN-root
Example 12.188. <head>
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2021"> <head> <name>Categories, Aristotle, English translation by E. M. Edghill</name> <master-location href="https://raw.githubusercontent.com/textalign/TAN-2021/master/examples/ar.cat.eng.1926.edghill.ref-logical.xml"/> <license licensor="kalvesmaki"> ......... </license> ......... </head> <body xml:lang="eng"> ......... </body> </TAN-T>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-logical |
Example 12.189. <head>
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:model-object-refs" TAN-version="2021"> <head> <name>Categories, Aristotle, English translation by E. M. Edghill</name> <master-location href="https://raw.githubusercontent.com/textalign/TAN-2021/master/examples/ar.cat.eng.1926.edghill.ref-scriptum.xml"/> <license licensor="kalvesmaki"> ......... </license> ......... </head> <body xml:lang="eng"> ......... </body> </TAN-T>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-scriptum |
Example 12.190. <head>
<TAN-T TAN-version="2021" id="tag:kalvesmaki.com,2014:tan-t:ar.cat.fra.1844.saint-hilaire:semantic-refs-realigned"> <head> <name>Realignment of Categories, Aristotle, French translation by J. Barthélemy Saint-Hilaire</name> <master-location href="https://raw.githubusercontent.com/textalign/TAN-2021/master/examples/ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949.xml"/> <license licensor="kalvesmaki"> ......... </license> ......... </head> <body xml:lang="fra"> ......... </body> </TAN-T>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949 |
Example 12.191. <head>
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.fra.1844.saint-hilaire:semantic-refs" TAN-version="2021"> <head> <name>Categories, Aristotle, French translation by J. Barthélemy Saint-Hilaire</name> <master-location href="https://raw.githubusercontent.com/textalign/TAN-2021/master/examples/ar.cat.fra.1844.saint-hilaire.ref-logical-after.xml"/> <license licensor="kalvesmaki"> ......... </license> ......... </head> <body xml:lang="fra"> ......... </body> </TAN-T>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.ref-logical |
The element in-lang
restricts a claim to a particular language; used with only certain verbs, e.g., "translates".
Multiple values of <in-lang>
are interpreted to mean "and", resulting in distribution of the claim.
By default, <in-lang>
is disallowed. A verb's constrained IRI + name pattern must explicitly require or allow it.
The element in-lang
specifies whether a verb uses <in-lang>
(default: disallowed).
Used by: ~element-claim
, ~in-lang
, ~constraints-on-verb
Example 12.192. <in-lang>
<constraints>
.........
<object status="required" item-type="ref scriptum work version source"/>
<in-lang status="allowed"/>
</constraints>
Note | |
---|---|
Taken from verbs.TAN-voc |
The element inclusion
specifies a TAN file that is available for inclusion. An inclusion occurs whenever an element X points to this inclusion by means of @include.
. TAN-compliant validators and processors will find every element X that is found in the included file (checked recursively, against any inclusions of X adopted by the inclusion) and insert them at that place in the dependent document.
Only select elements will be included, not the entire inclusion file. Exactly which elements are included is dictated by @include
placed in select empty elements.
The presence of an <inclusion>
does not require its use, although it may add time to the validation process.
The sequence of consecutive <inclusion>
s is immaterial.
For more, see the section called “Networked Files”
Used by: ~element-ana
, ~element-align
, ~element-claim
, ~element-category
, ~element-code
, ~element-rule
, ~element-div
, ~element-item
, ~element-replace
, ~adj-element-equate
, ~adj-element-reassign
, ~adj-element-rename
, ~adj-element-skip
, ~element-group-for-tok
, ~element-adjustments
, ~element-file-resp
, ~element-group
, ~element-license
, ~element-resp
, ~element-to-do
, ~element-token-definition
, ~link-element-see-also
, ~voc-element-period
, ~entity-digital-nontan-id
, ~entity-digital-nontan-no-id
, ~entity-digital-tan-id
, ~entity-digital-tan-no-id
, ~entity-nondigital-constrained
, ~entity-nondigital-id
, ~entity-nondigital-no-id
, ~networked-files-core
Caution | |
---|---|
An inclusion must point to a TAN file |
Caution | |
---|---|
For any element with |
Caution | |
---|---|
Inclusions are integral parts of any TAN file. Access to at least one copy is absolutely mandatory. |
Caution | |
---|---|
Inclusions/vocabularies may not be invoked circularly. |
Caution | |
---|---|
The vocabulary of a file may not include it. |
Important | |
---|---|
The |
Caution | |
---|---|
An element that has a |
Caution | |
---|---|
Every TAN file referred to by way of an element containing |
Caution | |
---|---|
No element may point to a TAN file that has an identical |
Important | |
---|---|
If a target file has children items in the |
Important | |
---|---|
If a target file has a |
Important | |
---|---|
If a target file points only to non-local locations and no internet is available, the following message will be returned. “No internet available.” |
Caution | |
---|---|
If a linking element points to a file that must be resolved, that file must be a TAN file. |
Important | |
---|---|
If |
Example 12.193. <inclusion>
<head> ......... <work which="matthew"/> <inclusion xml:id="serm-mount"> <IRI>tag:parkj@textalign.net,2015:bible:matthew:sermon-on-the-mount</IRI> <name>Sermon on the Mount, King James Version of the Bible, 1760 edition</name> <location accessed-when="2019-10-09T02:09:11.163-04:00" href="sermon-on-the-mount.eng.kjv.1760.xml"/> </inclusion> <vocabulary which="bible eng" accessed-when="2019-10-08"/> ......... </head>
Note | |
---|---|
Taken from matt.eng.kjv.1760 |
Example 12.194. <inclusion>
<head> ......... <source which="kjv 1760"/> <inclusion xml:id="lords-prayer"> <IRI>tag:parkj@textalign.net,2015:bible:matthew:lords-prayer</IRI> <name>Matthew's version of the Lord's Prayer, King James Version of the Bible, 1760 edition</name> <location accessed-when="2019-10-09T02:32:50.973-04:00" href="lords-prayer.eng.kjv.1760.xml"/> </inclusion> <vocabulary-key> ......... </vocabulary-key> ......... </head>
Note | |
---|---|
Taken from sermon-on-the-mount.eng.kjv.1760 |
Example 12.195. <inclusion>
<head> ......... <token-definition pattern="[\w]+"/> <inclusion xml:id="rel"> <IRI>tag:kalvesmaki.com,2014:tan-t:ar.cat.grc.1949.minio-paluello:object-refs</IRI> <name>Categories, Aristotle, Greek text by Minio-Paluello</name> <location href="../ar.cat.grc.1949.minio-paluello.ref-scriptum.xml" accessed-when="2016-09-28T08:50:23.457-04:00"/> </inclusion> <source> ......... </source> ......... </head>
Note | |
---|---|
Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-A-lm-sample |
The element IRI
contains an International Resource Identifier that names the concept, person, or thing referred to by the parent element.
Any kind of IRIs are allowed: URLs, tag URNs, UUIDs, etc. For names of well-known resources, an HTTP URL identifier might be preferred, to facilitate linked data. If an entity/resource lacks a suitable URL-type name, you may use or coin any other valid IRI, such as a UUID, a tag URN, or an OID. Some concepts may be difficult to find IRIs for.
Sibling <IRI>
s are to be treated as names for the same thing, not as names of different things. Loosely, sibling <IRI>
s can be thought of as synonymous, but technically the are only poecilonymic. In the terms of Web Ontology Language (http://www.w3.org/TR/owl-ref/),
sibling <IRI>
s cannot be assumed to share the relationship owl:sameAs, because they will draw from independent vocabularies that may identify similar concepts differently.
An element given multiple <IRI>
s refers to one or more items within the intersection, not the union, of the target concepts. Nevertheless, most interpretations of TAN files will draw inferences based upon the union. That is, if item A is assigned IRI X, item B IRIs X and Y, and item C IRI Y, it is likely that users of the data will infer identity between items A and C.
The sequence of consecutive <IRI>
s is immaterial.
The element is named IRI instead of URI to encourage internationalization, and the use of alphabets other than Latin.
An <IRI>
from the standard TAN vocabulary may be overridden locally.
For more see the section called “Identifiers and their use (IRIs, URIs, URLs, URNs, UUIDs)”.
Used by: ~entity-digital-core-content
, ~entity-nondigital-content
, ~entity-nondigital-with-constraints-content
Caution | |
---|---|
An IRI may appear no more than once in a TAN document. |
Caution | |
---|---|
An IRI that names a TAN file must match that file's |
Caution | |
---|---|
Any IRI beginning urn: must continue with a name that is part of the official IANA Registry of URN Namespaces. See RFC 2414, |
Caution | |
---|---|
No file may import vocabularies with items that have duplicate IRIs. |
Caution | |
---|---|
All text must be normalized (Unicode NFC). |
Caution | |
---|---|
Every item in a reserved TAN-voc must have at least one IRI with a tag URN in the TAN namespace |
Example 12.196. <IRI>
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2021"> <head> ......... <license licensor="kalvesmaki"> <IRI>http://creativecommons.org/licenses/by/4.0/deed.en_US</IRI> <name>Creative Commons Attribution 4.0 International License</name> ......... </license> <work> <IRI>http://dbpedia.org/resource/Categories_(Aristotle)</IRI> <name>Aristotle, Categories</name> </work> <source> <IRI>http://id.lib.harvard.edu/aleph/007901738/catalog</IRI> <name>Aristotle: Categoriae & De interpretatione by E.M. Edghill. Analytica priora / by A.J. Jenkinson. Analytica posteriora / by G.R.G. Mure. Oxford : Clarendon Press, 1926. </name> </source> <model> <IRI>tag:kalvesmaki.com,2014:tan-t:ar.cat.grc.1949.minio-paluello:semantic-refs</IRI> <name>Categories, Aristotle, Greek text by Minio-Paluello</name> ......... </model> ......... </head> ......... </TAN-T>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-logical |
The element item
provides a container for IRI, names, and descriptions of something. The item is assumed to be a type (or types) of thing indicated by the values of the closest @affects-attribute
or @affects-element.
.
An <item>
does not describe verbs, which have special constraints. Use <verb>
instead.
Used by: ~body-item
Caution | |
---|---|
Names must be unique for vocabulary items assigned to a given element name. |
Caution | |
---|---|
|
Caution | |
---|---|
|
Caution | |
---|---|
Every item in a reserved TAN-voc must have at least one IRI with a tag URN in the TAN namespace |
Example 12.197. <item>
<TAN-voc TAN-version="2021" id="tag:parkj@textalign.net,2015:TAN-key:ar.cat"> ......... <body affects-element="work"> <item> <IRI>http://dbpedia.org/resource/Categories_(Aristotle)</IRI> <name xml:lang="fra">Aristote, Catégories</name> <name xml:lang="eng">Aristotle, Categories</name> </item> <item> <IRI>tag:parkj@textalign.net,2015:work:porphyry:on-aristotles-categories</IRI> <name xml:lang="lat">Commentarium graecum Porphyrii</name> <name xml:lang="eng">Porphyry's commentary on Aristotle's Categories</name> </item> <item> <IRI>tag:parkj@textalign.net,2015:work:dexippus:on-aristotles-categories</IRI> <name xml:lang="lat">Commentarium graecum Dexippi</name> <name xml:lang="eng">Dexippus's commentary on Aristotle's Categories</name> </item> <group> <item> <IRI>tag:parkj@textalign.net,2015:work:ammonius:on-aristotles-categories:lemmata</IRI> <name xml:lang="lat">Lemmata de commentario graeco Ammonii</name> <name xml:lang="eng">Lemmata from Ammonius's commentary on Aristotle's Categories</name> </item> <item> ......... </item> </group> ......... </body> </TAN-voc>
Note | |
---|---|
Taken from ar.cat.TAN-voc |
The element l
names a lexeme, by pointing to the main word entry in the lexicon identified by the element's inherited value(
s) of @lexicon.
. This element should not be used to point to roots, only to lexical headwords.
In many languages, especially those that are lightly inflected, the lexeme will be identical to the word token itself. If <l>
is omitted, the calculated value of <tok>
is to be inferred as its value.
The sequence of consecutive <l>
s is immaterial.
Used by: ~element-lm
Example 12.198. <l>
<TAN-A-lm TAN-version="2021" id="tag:kalvesmaki.com,2014:tan-t:ar.cat.grc.1949.minio-paluello:semantic-refs:TAN-A-lm:2016-04-05T07:07:40.033-04:00"> ......... <body lexicon="LSJ Lampe new" morphology="Perseus" claimant="xslt2"> <ana tok-pop="2"> ......... <lm> <l>Δῆλος</l> <m>n e - s - - - f a -</m> </lm> </ana> <ana> ......... <lm> <l>Σωκράτης</l> <m>n e - s - - - m g -</m> </lm> </ana> <ana> ......... <lm> <l>αἰσχύνω</l> <m>v - - - a n p - - -</m> </lm> </ana> <ana> ......... <lm> <l>αἴσθησις</l> <m>n - - s - - - f n -</m> </lm> </ana> <ana> ......... <lm> <l>αἴσθησις</l> <m>n - - s - - - f g -</m> </lm> </ana> ......... </body> </TAN-A-lm>
Note | |
---|---|
Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-A-lm-sample |
The element lexicon
names a lexicographical authority.
Used by: ~voc-element-non-class-2
Example 12.199. <lexicon>
<head> ......... <vocabulary-key> <algorithm xml:id="xslt2"> ......... </algorithm> <lexicon xml:id="LSJ"> <IRI>http://lccn.loc.gov/95032369</IRI> <name xml:lang="eng">Liddell-Scott-Jones, 9th ed. plus rev. supplement</name> </lexicon> <lexicon xml:id="Lampe"> <IRI>http://lccn.loc.gov/77372171</IRI> <name xml:lang="eng">G.H.W. Lampe, A Patristic Greek Lexicon, Oxford 1961.</name> </lexicon> <lexicon xml:id="new"> <IRI>urn:uuid:d6558d00-8f68-11e3-950a-425861b86ab6</IRI> <name xml:lang="eng">Lexicon generated from words in this document not to be found in any other lexicon.</name> </lexicon> <morphology xml:id="Perseus"> ......... </morphology> ......... </vocabulary-key> ......... </head>
Note | |
---|---|
Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-A-lm-sample |
Example 12.200. <lexicon>
<vocabulary-key> ......... <algorithm xml:id="xslt1"> ......... </algorithm> <lexicon xml:id="LSJ"> <IRI>http://lccn.loc.gov/95032369</IRI> <name>Liddell-Scott-Jones 9+</name> <name xml:lang="eng">Liddell-Scott-Jones, 9th ed. plus rev. supplement</name> </lexicon> <morphology xml:id="perseus-dik"> ......... </morphology> ......... </vocabulary-key>
Note | |
---|---|
Taken from grc-tan-a-lm-%CE%B1 |
The element license
states the license under which the data is distributed and the rights associated with it, exclusive of any rights attached to the source.
Diligently check to ensure that the license you have claimed respects the rights of your sources' rightsholders. It is recommended that you license your data under a license that is similar to or more liberal than the one under which your sources have been released.
For more discussion, see the section called “Key Declarations” and for a list of standard TAN vocabulary, the section called “TAN keywords for types of rights (<license>)”
Used by: ~declaration-core
Example 12.201. <license>
<head> ......... <master-location href="https://raw.githubusercontent.com/textalign/TAN-2021/master/examples/ar.cat.eng.1926.edghill.ref-logical.xml"/> <license licensor="kalvesmaki"> <IRI>http://creativecommons.org/licenses/by/4.0/deed.en_US</IRI> <name>Creative Commons Attribution 4.0 International License</name> <desc>Exclusive of rights held and licenses offered by rightsholders of the source or sources listed below, this data file, insofar as it constitutes an independent work, is licensed under a Creative Commons Attribution 4.0 International License.</desc> </license> <work> ......... </work> ......... </head>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-logical |
Example 12.202. <license>
<head> ......... <master-location href="https://raw.githubusercontent.com/textalign/TAN-2021/master/examples/ar.cat.eng.1926.edghill.ref-scriptum.xml"/> <license licensor="kalvesmaki"> <IRI>http://creativecommons.org/licenses/by/4.0/deed.en_US</IRI> <name>Creative Commons Attribution 4.0 International License</name> <desc>Exclusive of rights held and licenses offered by rightsholders of the source or sources listed below, this data file, insofar as it constitutes an independent work, is licensed under a Creative Commons Attribution 4.0 International License.</desc> </license> <work> ......... </work> ......... </head>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-scriptum |
Example 12.203. <license>
<head> ......... <master-location href="https://raw.githubusercontent.com/textalign/TAN-2021/master/examples/ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949.xml"/> <license licensor="kalvesmaki"> <IRI>http://creativecommons.org/licenses/by/4.0/deed.en_US</IRI> <name>Creative Commons Attribution 4.0 International License</name> <desc>Exclusive of rights held and licenses offered by rightsholders of the source or sources listed below, this data file, insofar as it constitutes an independent work, is licensed under a Creative Commons Attribution 4.0 International License.</desc> </license> <work> ......... </work> ......... </head>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949 |
Example 12.204. <license>
<head> ......... <master-location href="https://raw.githubusercontent.com/textalign/TAN-2021/master/examples/ar.cat.fra.1844.saint-hilaire.ref-logical-after.xml"/> <license licensor="kalvesmaki"> <IRI>http://creativecommons.org/licenses/by/4.0/deed.en_US</IRI> <name>Creative Commons Attribution 4.0 International License</name> <desc>Exclusive of rights held and licenses offered by rightsholders of the source or sources listed below, this data file, insofar as it constitutes an independent work, is licensed under a Creative Commons Attribution 4.0 International License.</desc> </license> <reference-system type="logical" wf-ready="true"/> ......... </head>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.ref-logical |
The element lm
groups lexical or morphological data.
Components within <lm>
combine with each other and with all sibling <tok>
s. That is, every <l>
is asserted against every <m>
within an <lm>
is asserted of every <tok>
.
The sequence of consecutive <lm>
s is immaterial.
Used by: ~element-ana
Example 12.205. <lm>
<TAN-A-lm TAN-version="2021" id="tag:kalvesmaki.com,2014:tan-t:ar.cat.grc.1949.minio-paluello:semantic-refs:TAN-A-lm:2016-04-05T07:07:40.033-04:00"> ......... <body lexicon="LSJ Lampe new" morphology="Perseus" claimant="xslt2"> <ana tok-pop="2"> <tok ref="11 2 1 1" pos="1"/> <lm> <l>Δῆλος</l> <m>n e - s - - - f a -</m> </lm> </ana> <ana> ......... <tok ref="10 6 4 2" pos="37"/> <lm> <l>Σωκράτης</l> <m>n e - s - - - m g -</m> </lm> </ana> <ana> ......... <tok ref="8 3 7 3" pos="7"/> <lm> <l>αἰσχύνω</l> <m>v - - - a n p - - -</m> </lm> </ana> <ana> ......... <tok ref="7 4 9 2" pos="4"/> <lm> <l>αἴσθησις</l> <m>n - - s - - - f n -</m> </lm> </ana> ......... </body> </TAN-A-lm>
Note | |
---|---|
Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-A-lm-sample |
The element location
declares where an electronic file was found and when.
The URL may be absolute or relative to the current document.
The sequence of consecutive <location>
s is important. During TAN validation, the first <location>
with an available document will be used, and the following sibling <location>
s will be ignored.
Used by: ~entity-digital-core-content
Caution | |
---|---|
|
Important | |
---|---|
If an |
Important | |
---|---|
If an |
Important | |
---|---|
If the internet is available, and an |
Caution | |
---|---|
The only |
Caution | |
---|---|
No |
Caution | |
---|---|
An |
Caution | |
---|---|
An element that has a |
Caution | |
---|---|
Every TAN file referred to by way of an element containing |
Caution | |
---|---|
No element may point to a TAN file that has an identical |
Important | |
---|---|
If a target file has children items in the |
Important | |
---|---|
If a target file has a |
Important | |
---|---|
If a target file points only to non-local locations and no internet is available, the following message will be returned. “No internet available.” |
Caution | |
---|---|
If a linking element points to a file that must be resolved, that file must be a TAN file. |
Important | |
---|---|
If an element not essential to validation has no |
Important | |
---|---|
If |
Example 12.206. <location>
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2021"> <head> ......... <model> ......... <name>Categories, Aristotle, Greek text by Minio-Paluello</name> <location href="ar.cat.grc.1949.minio-paluello.ref-logical.xml" accessed-when="2016-02-10T14:08:52.058-05:00"/> </model> <see-also relationship="alt"> ......... <name>Categories, Aristotle, Greek text by Minio-Paluello</name> <location href="ar.cat.grc.1949.minio-paluello.ref-scriptum.xml" accessed-when="2016-02-11T12:40:42.823-05:00"/> </see-also> <redivision> ......... <name>Categories, Aristotle, English translation by E. M. Edghill</name> <location href="ar.cat.eng.1926.edghill.ref-scriptum.xml" accessed-when="2016-06-22T08:13:35.791-04:00"/> </redivision> ......... <vocabulary-key> <algorithm xml:id="xslt2"> ......... <name>Stylesheet to create a TAN file.</name> <location href="../applications/convert/convert%20TAN%202018%20to%20TAN%202020.xsl" accessed-when="2018-08-04T23:55:36.096-04:00"/> </algorithm> ......... </vocabulary-key> ......... </head> ......... </TAN-T>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-logical |
The element m
carries a morphological code that conforms to the rules or patterns defined in the TAN-mor file upon which the data depends.
Codes are space-delimited. If a value of <m>
violates the rules established by the dependency TAN-mor file, an error will be generated. For more about how codes are built, and how they function, see the section called “Lexico-morphology (<TAN-A-lm>)”.
The sequence of consecutive <m>
s is immaterial.
Used by: ~element-lm
Caution | |
---|---|
When using a category-based morphology, the number of feature codes in an |
Caution | |
---|---|
Every feature code in an |
The element master-location
points to a location where a master copy of the file is to be found. Use of this element entails a commitment to updating the TAN file in that location.
The URL may be absolute or relative to the current document.
<master-location>
does not disallow the file from being kept, published, or distributed elsewhere. It merely indicates where an authoritative version of the file is to be found.
Used by: ~entity-digital-tan-self-content
Caution | |
---|---|
Any TAN file without a to-do list will be treated as being no longer in progress and should have at least one master-location. |
Caution | |
---|---|
|
Important | |
---|---|
If an |
Important | |
---|---|
If an |
Important | |
---|---|
If the internet is available, and an |
Caution | |
---|---|
The only |
Caution | |
---|---|
No |
Caution | |
---|---|
An |
Caution | |
---|---|
No |
Important | |
---|---|
Files should match the version kept at |
Example 12.207. <master-location>
<head>
<name>Categories, Aristotle, English translation by E. M. Edghill</name>
<master-location href="https://raw.githubusercontent.com/textalign/TAN-2021/master/examples/ar.cat.eng.1926.edghill.ref-logical.xml"/>
<license licensor="kalvesmaki">
.........
</license>
.........
</head>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-logical |
Example 12.208. <master-location>
<head>
<name>Categories, Aristotle, English translation by E. M. Edghill</name>
<master-location href="https://raw.githubusercontent.com/textalign/TAN-2021/master/examples/ar.cat.eng.1926.edghill.ref-scriptum.xml"/>
<license licensor="kalvesmaki">
.........
</license>
.........
</head>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-scriptum |
Example 12.209. <master-location>
<head>
<name>Realignment of Categories, Aristotle, French translation by J. Barthélemy
Saint-Hilaire</name>
<master-location href="https://raw.githubusercontent.com/textalign/TAN-2021/master/examples/ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949.xml"/>
<license licensor="kalvesmaki">
.........
</license>
.........
</head>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949 |
Example 12.210. <master-location>
<head>
<name>Categories, Aristotle, French translation by J. Barthélemy Saint-Hilaire</name>
<master-location href="https://raw.githubusercontent.com/textalign/TAN-2021/master/examples/ar.cat.fra.1844.saint-hilaire.ref-logical-after.xml"/>
<license licensor="kalvesmaki">
.........
</license>
.........
</head>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.ref-logical |
The element modal
contains an IRI + name pattern identifying a modal or adverb that qualifies the verb of an assertion.
See the section called “TAN keywords for types of modals (<modal>)” for standard TAN vocabulary.
Used by: ~voc-element-tan-a
Example 12.211. <modal>
<vocabulary-key>
.........
<unit xml:id="folio">
.........
</unit>
<modal which="possibly" xml:id="perhaps"/>
<person xml:id="park">
.........
</person>
.........
</vocabulary-key>
Note | |
---|---|
Taken from ar.cat.TAN-A.claims |
The element model
identifies a class-1 file has been used as a model for how the current file has been segmented and labeled.
A file need not follow its model exactly. Upon verbose validation, differences between the file and its model will be reported only as warnings.
Used by: ~networked-files-non-core
Caution | |
---|---|
|
Caution | |
---|---|
An element that has a |
Caution | |
---|---|
Every TAN file referred to by way of an element containing |
Caution | |
---|---|
No element may point to a TAN file that has an identical |
Important | |
---|---|
If a target file has children items in the |
Important | |
---|---|
If a target file has a |
Important | |
---|---|
If a target file points only to non-local locations and no internet is available, the following message will be returned. “No internet available.” |
Caution | |
---|---|
If a linking element points to a file that must be resolved, that file must be a TAN file. |
Important | |
---|---|
If a class 1 file diverges from the structure of its model a warning will be generated specifying where differences exist. |
Caution | |
---|---|
A class 1 file with a |
Caution | |
---|---|
Class 1 files must share the same work as any model, redivision, or companion version. |
Example 12.212. <model>
<head> ......... <source> ......... </source> <model> <IRI>tag:kalvesmaki.com,2014:tan-t:ar.cat.grc.1949.minio-paluello:semantic-refs</IRI> <name>Categories, Aristotle, Greek text by Minio-Paluello</name> <location href="ar.cat.grc.1949.minio-paluello.ref-logical.xml" accessed-when="2016-02-10T14:08:52.058-05:00"/> </model> <see-also relationship="alt"> ......... </see-also> ......... </head>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-logical |
Example 12.213. <model>
<head> ......... <redivision> ......... </redivision> <model> <IRI>tag:kalvesmaki.com,2014:tan-t:ar.cat.grc.1949.minio-paluello:object-refs</IRI> <name>Categories, Aristotle, Greek text by Minio-Paluello</name> <location href="ar.cat.grc.1949.minio-paluello.ref-scriptum.xml" accessed-when="2016-07-07T16:36:28.867-04:00"/> </model> <adjustments> ......... </adjustments> ......... </head>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-scriptum |
Example 12.214. <model>
<head> ......... <redivision> ......... </redivision> <model> <IRI>tag:kalvesmaki.com,2014:tan-t:ar.cat.grc.1949.minio-paluello:semantic-refs</IRI> <name>Categories, Aristotle, Greek text by Minio-Paluello</name> <location href="ar.cat.grc.1949.minio-paluello.ref-logical.xml" accessed-when="2016-07-14T11:38:29.251-04:00"/> </model> <adjustments> ......... </adjustments> ......... </head>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949 |
Example 12.215. <model>
<head> ......... <vocabulary> ......... </vocabulary> <model> <IRI>tag:parkj@textalign.net,2015:ring04</IRI> <name>TAN transcription of 1790 version of Ring around the Rosie reported by Newell in 1883</name> <location accessed-when="2021-04-27-04:00" href="ring-o-roses.eng.1951.xml"/> </model> <adjustments> ......... </adjustments> ......... </head>
Note | |
---|---|
Taken from ring-o-roses.eng.1987 |
The element morphology
identifies a dependency <TAN-mor>
file that defines the parts of speech for a language, the codes for those parts, and the rules for combining them
Used by: ~voc-element-non-class-2
Caution | |
---|---|
|
Example 12.216. <morphology>
<vocabulary-key> ......... <lexicon xml:id="new"> ......... </lexicon> <morphology xml:id="Perseus"> <IRI>tag:kalvesmaki.com,2014:tan-r-mor:grc:perseus</IRI> <name xml:lang="eng">Perseus Greek morphology</name> <location href="../../../library-lm/grc/grc.perseus.tan-mor.xml" accessed-when="2021-01-11"/> </morphology> <group-type xml:id="status" which="status"/> ......... </vocabulary-key>
Note | |
---|---|
Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-A-lm-sample |
Example 12.217. <morphology>
<vocabulary-key> ......... <lexicon xml:id="LSJ"> ......... </lexicon> <morphology xml:id="perseus-dik"> <IRI>tag:kalvesmaki.com,2014:tan-r-mor:grc:perseus</IRI> <name xml:lang="eng">Perseus Greek morphology</name> <location accessed-when="2020-03-05" href="../TAN-mor/grc.perseus.tan-mor.xml"/> </morphology> <organization xml:id="perseus"> ......... </organization> ......... </vocabulary-key>
Note | |
---|---|
Taken from grc-tan-a-lm-%CE%B1 |
Example 12.218. <morphology>
<vocabulary-key> ......... <lexicon xml:id="LSJ"> ......... </lexicon> <morphology xml:id="perseus-dik"> <IRI>tag:kalvesmaki.com,2014:tan-r-mor:grc:perseus</IRI> <name xml:lang="eng">Perseus Greek morphology</name> <location accessed-when="2020-03-05" href="../TAN-mor/grc.perseus.tan-mor.xml"/> </morphology> <organization xml:id="perseus"> ......... </organization> ......... </vocabulary-key>
Note | |
---|---|
Taken from grc-tan-a-lm-%CE%B1%CA%B9 |
Example 12.219. <morphology>
<vocabulary-key> <algorithm xml:id="xslt2"> ......... </algorithm> <morphology xml:id="penn" ed-when="2015-08-20-04:00" ed-who="park"> <IRI>tag:kalvesmaki.com,2014:tan-r-mor:eng:penn</IRI> <name>Penn Treebank tag set</name> <location href="../TAN-mor/eng.kalvesmaki.com%2C2014.2.xml" accessed-when="2015-11-03-05:00"/> </morphology> <lexicon xml:id="english"> ......... </lexicon> ......... </vocabulary-key>
Note | |
---|---|
Taken from ring-o-roses.eng.1881.lm |
The element n-alias
specifies whether aliases for n should be applied selectively. For files that use <vocabulary>
with @which
, for extra @n
vocabulary, this element improves the efficiency of validation.
Used by: ~decl-class-1
Example 12.220. <n-alias>
<head>
.........
<reference-system type="logical" wf-ready="true"/>
<n-alias div-type="book"/>
<work which="matthew"/>
.........
</head>
Note | |
---|---|
Taken from matt.eng.kjv.1760 |
The element name
provides a human-readable name of a concept, person, or thing referred to by the parent element (or the current document, if the parent element is <head>
).
A name must be unique within a file for a given class of items. That is, if "page" is the name of a div type, there must be no other div type vocabulary item with that name, but "page" could still be used as the <name>
of a verb or person.
The sequence of consecutive <name>
s is immaterial. Some applications may adopt the first <name>
as the primary one.
Used by: ~metadata-human-readable
Caution | |
---|---|
All text must be normalized (Unicode NFC). |
Caution | |
---|---|
Names must be unique for vocabulary items assigned to a given element name. |
Caution | |
---|---|
Names may not duplicate names reserved by standard TAN vocabulary for the affected element. |
Caution | |
---|---|
Names may not be duplicates of, case-variants of, or hyphen variants of other names for the same element. |
Caution | |
---|---|
Each |
Example 12.221. <name>
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2021"> <head> <name>Categories, Aristotle, English translation by E. M. Edghill</name> <master-location href="https://raw.githubusercontent.com/textalign/TAN-2021/master/examples/ar.cat.eng.1926.edghill.ref-logical.xml"/> <license licensor="kalvesmaki"> <IRI>http://creativecommons.org/licenses/by/4.0/deed.en_US</IRI> <name>Creative Commons Attribution 4.0 International License</name> <desc>Exclusive of rights held and licenses offered by rightsholders of the source or sources listed below, this data file, insofar as it constitutes an independent work, is licensed under a Creative Commons Attribution 4.0 International License.</desc> </license> <work> <IRI>http://dbpedia.org/resource/Categories_(Aristotle)</IRI> <name>Aristotle, Categories</name> </work> <source> <IRI>http://id.lib.harvard.edu/aleph/007901738/catalog</IRI> <name>Aristotle: Categoriae & De interpretatione by E.M. Edghill. Analytica priora / by A.J. Jenkinson. Analytica posteriora / by G.R.G. Mure. Oxford : Clarendon Press, 1926. </name> </source> ......... <redivision> <IRI>tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:model-object-refs</IRI> <name>Categories, Aristotle, English translation by E. M. Edghill</name> <location href="ar.cat.eng.1926.edghill.ref-scriptum.xml" accessed-when="2016-06-22T08:13:35.791-04:00"/> </redivision> ......... </head> ......... </TAN-T>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-logical |
The element normalization
specifies an alteration that has been made to a source file to bring the transcription into conformity with standards or common expectations. This element is used typically for minor corrections, e.g., suppression of discretionary hyphenation. You should declare every normalizing change you have made to the source.
<normalization>
is especially helpful in reference to nondigital sources, but it may be made also for digital sources, to declare global changes that would be cumbersome, difficult, or impossible to describe via regular expressions in <replace>
.
The sequence of consecutive <normalization>
is immaterial.
See the section called “TAN keywords for types of normalizations (<normalization>)” for standard TAN vocabulary for normalizations. For general discussion see the section called “Normalizing transcriptions”
Used by: ~adjust-non-core
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-logical |
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-scriptum |
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949 |
Example 12.225. <normalization>
<adjustments> <normalization which="no hyphens"/> <normalization which="no ligatures"/> </adjustments>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.ref-logical |
The element numerals
specifies how nonarabic numerals should be interpreted, as letter numerals or as Roman numerals.
If <numerals>
is not present, any ambiguous numerical values are assumed to be Roman.
Used by: ~declaration-core
Example 12.226. <numerals>
<head>
.........
<version>
.........
</version>
<numerals priority="letters"/>
<source>
.........
</source>
.........
</head>
Note | |
---|---|
Taken from ring-o-roses.deu.1897-prev |
Example 12.227. <numerals>
<head>
.........
<version>
.........
</version>
<numerals priority="letters"/>
<source>
.........
</source>
.........
</head>
Note | |
---|---|
Taken from ring-o-roses.deu.1897 |
Example 12.228. <numerals>
<head>
.........
<license licensor="park">
.........
</license>
<numerals priority="letters"/>
<token-definition src="fra" pattern="\S+"/>
.........
</head>
Note | |
---|---|
Taken from ar.cat.TAN-A |
Example 12.229. <numerals>
<head>
.........
<license licensor="park" which="by 4.0"/>
<numerals priority="letters"/>
<source xml:id="conf">
.........
</source>
.........
</head>
Note | |
---|---|
Taken from patricius.confessio.TAN-A |
The element object
points to text references that act as the object of the claim.
Unlike @object
, which points to any entity via idrefs, <subject>
is intended exclusively to point to data content or a textual subject.
Each textual <object>
is interpreted as a single entity, with all textual references encoded by the element treated as a single, grouped passage. The sequence of its contents is therefore significant.
The element object
specifies expectations on a verb's use of object. By default, an object is required.
Used by: ~element-claim
, ~complex-object
, ~constraints-on-verb
Caution | |
---|---|
Claims involving verbs whose constrained content requires specification of units must use |
Caution | |
---|---|
|
Example 12.230. <object>
<TAN-A TAN-version="2021" id="tag:parkj@textalign.net,2015:ar.cat.tan-a:claims"> <head> ......... <vocabulary-key> ......... <verb xml:id="om"> ......... <constraints> ......... <at-ref status="required"/> <object status="disallowed"/> </constraints> </verb> <verb xml:id="attests"> ......... <constraints> <subject status="required" item-type="person work version scriptum"/> <object status="required" item-type="ref"/> </constraints> </verb> <verb xml:id="has-length"> ......... <constraints> <subject status="required" item-type="scriptum"/> <object status="required" content-datatype="integer" content-lexical-constraint="\d+"/> </constraints> </verb> ......... </vocabulary-key> ......... </head> <body claimant="park" claim-period="per2010s"> ......... <claim subject="comm-omnes" verb="attests" period="late_antiquity"> <object src="grc" ref="1 a 2"> <tok pos="3-4"/> </object> </claim> <claim subject="comm-omnes" verb="attests" xml:id="cl1a2b"> <object src="grc" ref="1 a 2"> <tok pos="3-4"/> </object> </claim> ......... </body> </TAN-A>
Note | |
---|---|
Taken from ar.cat.TAN-A.claims |
The element organization
contains an IRI + name pattern identifying an organization: a group of persons, whether formally incorporated or not.
This term is taken in its loosest sense. "Organization" and "person" are treated as mutually exclusive and exhaustive categories of all human beings, real or fictive. Therefore a tribe or clan, which ordinarily might dislike being thought of as an organization, are nevertheless so classified here.
Used by: ~voc-element-agent
Example 12.231. <organization>
<vocabulary-key> ......... <morphology xml:id="perseus-dik"> ......... </morphology> <organization xml:id="perseus"> <IRI>http://dbpedia.org/resource/Perseus_Project</IRI> <name>Perseus Project</name> </organization> <person xml:id="dik"> ......... </person> ......... </vocabulary-key>
Note | |
---|---|
Taken from grc-tan-a-lm-%CE%B1 |
Example 12.232. <organization>
<vocabulary-key> ......... <morphology xml:id="perseus-dik"> ......... </morphology> <organization xml:id="perseus"> <IRI>http://dbpedia.org/resource/Perseus_Project</IRI> <name>Perseus Project</name> </organization> <person xml:id="dik"> ......... </person> ......... </vocabulary-key>
Note | |
---|---|
Taken from grc-tan-a-lm-%CE%B1%CA%B9 |
Example 12.233. <organization>
<vocabulary-key>
<person which="Jenny Park" xml:id="park"/>
<organization xml:id="pt" which="Project_team_for_TAN_examples"/>
</vocabulary-key>
Note | |
---|---|
Taken from park-projects.TAN-voc |
The element passage
specifies a textual passage within a single <div>
that should be reassigned to another <div>
.
Used by: ~adj-element-reassign
Example 12.234. <passage>
<reassign> <passage ref="5 4 7 2"> <from-tok val=":" pos="1"/> <through-tok val=":" pos="1"/> </passage> <to ref="5 4 7 1"/> </reassign>
Note | |
---|---|
Taken from ar.cat.TAN-A |
Definition 1
The element period
as a constraint specifies expectations on a verb's use of period. By default, a period is optional.
Definition 2
The element period
identifies or defines a period of time, either through specific dates or dateTimes, or to a vocabulary item that names a more generic period of time.
Used by: ~constraints-on-verb
, ~voc-key-core
Example 12.235. <period>
<head> ......... <vocabulary-key> ......... <role xml:id="creator"> ......... </role> <period xml:id="per2010s" from="2010-01-01" to="2019-12-31"/> <period xml:id="late-antiquity"> <IRI>tag:parkj@textalign.net,2015:period:late-antiquity</IRI> <name>late antiquity</name> <desc>Roughly starting in the second to fourth century and finishing from the sixth to ninth, depending upon the context. Late antiquity tends to be later than you think.</desc> </period> <place xml:id="pavia"> ......... </place> </vocabulary-key> ......... </head>
Note | |
---|---|
Taken from ar.cat.TAN-A.claims |
The element person
contains an IRI + name pattern identifying an individual human being.
Used by: ~voc-element-agent
Example 12.236. <person>
<vocabulary-key> ......... <div-type xml:id="pt" which="part"/> <person xml:id="kalvesmaki"> <IRI>http://viaf.org/viaf/299582703</IRI> <IRI>tag:kalvesmaki.com,2014:self</IRI> <name xml:lang="eng">Joel Kalvesmaki</name> </person> <algorithm xml:id="xslt1"> ......... </algorithm> ......... </vocabulary-key>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-logical |
Example 12.237. <person>
<vocabulary-key> ......... <div-type xml:id="l"> ......... </div-type> <person xml:id="kalvesmaki"> <IRI>http://viaf.org/viaf/299582703</IRI> <IRI>tag:kalvesmaki.com,2014:self</IRI> <name xml:lang="eng">Joel Kalvesmaki</name> </person> <algorithm xml:id="xslt1"> ......... </algorithm> ......... </vocabulary-key>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-scriptum |
Example 12.238. <person>
<vocabulary-key> ......... <div-type xml:id="pt" which="part"/> <person xml:id="kalvesmaki"> <IRI>http://viaf.org/viaf/299582703</IRI> <IRI>tag:kalvesmaki.com,2014:self</IRI> <name xml:lang="eng">Joel Kalvesmaki</name> </person> <role xml:id="editor"> ......... </role> ......... </vocabulary-key>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949 |
Example 12.239. <person>
<vocabulary-key> ......... <div-type xml:id="pt" which="part"/> <person xml:id="kalvesmaki"> <IRI>http://viaf.org/viaf/299582703</IRI> <IRI>tag:kalvesmaki.com,2014:self</IRI> <name xml:lang="eng">Joel Kalvesmaki</name> </person> <role xml:id="editor"> ......... </role> ......... </vocabulary-key>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.ref-logical |
The element place
contains an IRI + name pattern identifying a spatial location, usually somewhere on earth
The element place
specifies expectations on a verb's use of place. By default, an place is optional.
Used by: ~voc-element-tan-a
, ~constraints-on-verb
Example 12.240. <place>
<vocabulary-key> ......... <period xml:id="late-antiquity"> ......... </period> <place xml:id="pavia"> <IRI>http://dbpedia.org/resource/Pavia</IRI> <name>Pavia</name> </place> </vocabulary-key>
Note | |
---|---|
Taken from ar.cat.TAN-A.claims |
The element predecessor
identifies a file that the current file succeeds. Predecessors may or may not have the same @id
value.
The sequence of consecutive <predecessor>
s is immaterial.
Used by: ~networked-files-core
Caution | |
---|---|
An element that has a |
Caution | |
---|---|
Every TAN file referred to by way of an element containing |
Caution | |
---|---|
No element may point to a TAN file that has an identical |
Important | |
---|---|
If a target file has children items in the |
Important | |
---|---|
If a target file has a |
Important | |
---|---|
If a target file points only to non-local locations and no internet is available, the following message will be returned. “No internet available.” |
Caution | |
---|---|
If a linking element points to a file that must be resolved, that file must be a TAN file. |
Important | |
---|---|
If an element not essential to validation has no |
Example 12.241. <predecessor>
<head> ......... <source> ......... </source> <predecessor> <IRI>tag:hans@beispiel.com,2014:ringel</IRI> <name>TAN Transkription, Ringelreihen mit Riederfallen</name> <location accessed-when="2021-04-29T11:46:36.281-04:00" href="ring-o-roses.deu.1897-prev.xml"/> </predecessor> <adjustments> ......... </adjustments> ......... </head>
Note | |
---|---|
Taken from ring-o-roses.deu.1897 |
The element reassign
identifies words and phrases that should be moved from one <div>
to another in a given source.
Only the first <reassign>
applying to a <div>
in a given source will be applied.
Used by: ~adjust-class-2
Caution | |
---|---|
Any range in either an |
Caution | |
---|---|
No token may be adjusted by more than one |
Caution | |
---|---|
A |
Caution | |
---|---|
In a |
Example 12.242. <reassign>
<adjustments src="fra"> ......... <equate n="ti title"/> <reassign> <passage ref="5 4 7 2"> ......... </passage> <to ref="5 4 7 1"/> </reassign> </adjustments>
Note | |
---|---|
Taken from ar.cat.TAN-A |
The element redivision
identifies a class-1 file that has the same work, scriptum, and version, but is segmented according to a different reference system.
The normalized transcriptions of redivided texts must be identical.
The sequence of consecutive <redivision>
s is immaterial.
Used by: ~networked-files-non-core
Caution | |
---|---|
|
Caution | |
---|---|
An element that has a |
Caution | |
---|---|
Every TAN file referred to by way of an element containing |
Caution | |
---|---|
No element may point to a TAN file that has an identical |
Important | |
---|---|
If a target file has children items in the |
Important | |
---|---|
If a target file has a |
Important | |
---|---|
If a target file points only to non-local locations and no internet is available, the following message will be returned. “No internet available.” |
Caution | |
---|---|
If a linking element points to a file that must be resolved, that file must be a TAN file. |
Caution | |
---|---|
Class 1 files must share the same source as any redivision or companion version. |
Caution | |
---|---|
Class 1 files must share the same work-version, if supplied, as any redivision. |
Caution | |
---|---|
Class 1 files must have identical transcriptions, after TAN normalization, as any redivision. |
Caution | |
---|---|
Class 1 files must share the same work as any model, redivision, or companion version. |
Example 12.243. <redivision>
<head> ......... <see-also relationship="alt"> ......... </see-also> <redivision> <IRI>tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:model-object-refs</IRI> <name>Categories, Aristotle, English translation by E. M. Edghill</name> <location href="ar.cat.eng.1926.edghill.ref-scriptum.xml" accessed-when="2016-06-22T08:13:35.791-04:00"/> </redivision> <adjustments> ......... </adjustments> ......... </head>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-logical |
Example 12.244. <redivision>
<head> ......... <source> ......... </source> <redivision> <IRI>tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs</IRI> <name>Categories, Aristotle, English translation by E. M. Edghill</name> <location href="ar.cat.eng.1926.edghill.ref-logical.xml" accessed-when="2016-07-07T16:36:28.867-04:00"/> ......... </redivision> <model> ......... </model> ......... </head>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-scriptum |
Example 12.245. <redivision>
<head> ......... <source> ......... </source> <redivision> <IRI>tag:kalvesmaki.com,2014:tan-t:ar.cat.fra.1844.saint-hilaire:semantic-refs</IRI> <name>Categories, Aristotle, French translation by J. Barthélemy Saint-Hilaire</name> <location href="ar.cat.fra.1844.saint-hilaire.ref-logical.xml" accessed-when="2016-07-14T11:38:29.251-04:00"/> </redivision> <model> ......... </model> ......... </head>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949 |
Example 12.246. <redivision>
<head> ......... <source> ......... </source> <redivision> <IRI>tag:kalvesmaki.com,2014:tan-t:ar.cat.fra.1844.saint-hilaire:semantic-refs-realigned</IRI> <name>Realignment of Categories, Aristotle, French translation by J. Barthélemy Saint-Hilaire</name> <location href="ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949.xml" accessed-when="2016-07-13T15:08:34.397-04:00"/> </redivision> <adjustments> ......... </adjustments> ......... </head>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.ref-logical |
The element reference-system
specifies the type of reference system and its basis. The attributes of this element specify the type of reference system (material or logical); point to one or more reference scripta that form the basis of the reference system, and stipulate whether the scripta use that reference system as their key material or logical reference system.
In the absence of this element or any individual attribute, the following values are presumed:
The default reference type, material (i.e., scriptum-based: pages, columns, lines) or logical (based on conceptual divisions), is determined by the types of text units in the topmost tier of <div>
s.
The default reference scriptum is <source>
. The reference system is assumed not to be the primary one.
For a class 1 file to be a candidate for Literature Fragid URIs, whether as a target or as a source of creating LF URIs, the reference system must be the key reference system of its type in the reference scriptum.
Used by: ~decl-class-1
Caution | |
---|---|
A class 1 file with a |
Example 12.247. <reference-system>
<head>
.........
<license licensor="kalvesmaki">
.........
</license>
<reference-system type="logical" wf-ready="true"/>
<work>
.........
</work>
.........
</head>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.ref-logical |
Example 12.248. <reference-system>
<head>
.........
<work>
.........
</work>
<reference-system type="logical" wf-ready="true"/>
<source>
.........
</source>
.........
</head>
Note | |
---|---|
Taken from ar.cat.grc.1949.minio-paluello.ref-logical |
Example 12.249. <reference-system>
<head>
.........
<work>
.........
</work>
<reference-system type="material" wf-ready="true" scriptum="bekker"/>
<source>
.........
</source>
.........
</head>
Note | |
---|---|
Taken from ar.cat.grc.1949.minio-paluello.ref-scriptum |
Example 12.250. <reference-system>
<head>
.........
<work>
.........
</work>
<reference-system type="material" wf-ready="true"/>
<source>
.........
</source>
.........
</head>
Note | |
---|---|
Taken from ar.cat.lat.1961.minio-paluello.ref-scriptum |
The element relationship
specifies a relationship that one document has to another.
Used by: ~voc-key-core
Example 12.251. <relationship>
<vocabulary-key> ......... <role xml:id="stylesheet1" which="stylesheet"/> <relationship xml:id="alt"> <IRI>tag:kalvesmaki.com,2014:relationship:diff-work-version</IRI> <name>different work version</name> </relationship> </vocabulary-key>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-logical |
Example 12.252. <relationship>
<vocabulary-key> ......... <role xml:id="stylesheet1" which="stylesheet"/> <relationship xml:id="alt"> <IRI>tag:kalvesmaki.com,2014:relationship:diff-work-version</IRI> <name>different work version</name> </relationship> <scriptum xml:id="bekker"> ......... </scriptum> </vocabulary-key>
Note | |
---|---|
Taken from ar.cat.lat.1961.minio-paluello.ref-scriptum |
The element rename
provisionally reassigns values of @n
's in class 1 sources, or their calculated ref value, to another value.
A <rename>
may be applied on the basis of either @n
or @ref
, but a ref-based <rename>
always supersedes an n-based rename. Only the first matching <rename>
will be applied to a given <div>
in a source.
A ref-based rename eliminates any alternative values of @n
, inherited or native. That is, if a <div>
has @n
="prol pref" and the rename has @ref
="prol" and @new
="prologue" then the alternative value "pref" will be ignored.
Renames override any equate actions. An exception is made when an n-based rename affects one value of @n
but an equate affects another value. Ref-based renames always override any equate action.
If a <div>
is renamed such that it needs to be moved elsewhere in the hierarchy, and it matches the reference of another <div>
, the text from the renamed <div>
will be added to the end of the target <div>
.
Used by: ~adjust-class-2
Caution | |
---|---|
Any range in either an |
Important | |
---|---|
Only the first of multiple adjustment actions will be applied. Action priority: skip, ref-based rename, then for every |
Caution | |
---|---|
In adjustment actions involving |
Caution | |
---|---|
|
Example 12.253. <rename>
<adjustments src="ger">
<skip div-type="Gedicht"/>
<rename n="e" by="-1"/>
</adjustments>
Note | |
---|---|
Taken from ringoroses.div.1 |
Example 12.254. <rename>
<adjustments src="ger">
<skip div-type="Gedicht"/>
<rename ref="1 e" new="4"/>
</adjustments>
Note | |
---|---|
Taken from ringoroses.01+03.token.2 |
The element replace
contains the equivalent of the XPath replace()
function plus parameters, indicating a replacement operation that should be, or has been, applied to a digital file.
Multiple <replace>
s will be assumed to have been implemented in the given order.
The conventions of this element and its children parallel the XPath function replace()
. See http://www.w3.org/TR/xpath-functions-30/#func-replace
The sequence of consecutive <replace>
s is important, reflecting the order in which replacements occured. Results may differ depending upon the order of replace operations.
Used by: ~adjust-repl
Example 12.255. <replace>
<adjustments>
.........
<normalization>
.........
</normalization>
<replace pattern="--" replacement="—" flags="i"/>
</adjustments>
Note | |
---|---|
Taken from gomme.1989.ring-o-roses |
The element report
names a pattern that, if found to be true in any <m>
in a dependent TAN-A-lm file, will return the enclosed message upon validation of the dependent file, along with an error or warning. Modeled on Schematron <report>
.
The sequence of consecutive <report>
s is immaterial.
Used by: ~element-rule
Example 12.256. <report>
<rule m-has-codes="'' . ; :"> <report tok-matches="\w">Nothing marked as punctuation should have word characters.</report> </rule>
Note | |
---|---|
Taken from eng.kalvesmaki.com,2014.2 |
Example 12.257. <report>
<body> <rule m-has-how-many-codes="2-10"> <report m-matches="^c">A conjunction has no other inflectional properties.</report> <report m-matches="^r">A preposition has no other inflectional properties.</report> <report m-matches="^i">An interjection has no other inflectional properties.</report> <report m-matches="^y">An acronym has no other inflectional properties.</report> </rule> ......... </body>
Note | |
---|---|
Taken from grc.perseus.tan-mor |
The element resp
specifies a role held by one or more persons, organizations, or algorithms, perhaps during a specified time period.
The sequence of consecutive <resp>
s is immaterial.
Used by: ~resp-list
Example 12.258. <resp>
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2021"> <head> ......... <file-resp who="kalvesmaki"/> <resp who="xslt2" roles="stylesheet1"/> <resp roles="editor" who="kalvesmaki"/> <resp who="xslt1" roles="stylesheet1"/> <change when="2020-12-31" who="kalvesmaki">Added new reference-system declaration.</change> ......... </head> ......... </TAN-T>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-logical |
Example 12.259. <resp>
<head> ......... <file-resp who="kalvesmaki"/> <resp roles="editor" who="kalvesmaki"/> <resp who="xslt1" roles="stylesheet1"/> ......... </head>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-scriptum |
The element reuse-type
identifies a category of text reuse (e.g., translation, mistranslation, paraphrase, ridicule). See the section called “Token-based annotations and alignments (<TAN-A-tok>)” for theoretical background.
For standard TAN vocabulary items see the section called “TAN keywords for types of bitext reuse (<reuse-type>)”
Used by: ~voc-element-non-class-2
Example 12.260. <reuse-type>
<vocabulary-key> ......... <bitext-relation xml:id="B-descends-from-A"> ......... </bitext-relation> <reuse-type xml:id="adaptation"> <IRI>tag:textalign.net,2015:reuse-type:adaptation:general</IRI> <name>general adaptation</name> </reuse-type> <person xml:id="park"> ......... </person> ......... </vocabulary-key>
Note | |
---|---|
Taken from ringoroses.01+02.token.1 |
Example 12.261. <reuse-type>
<vocabulary-key> ......... <bitext-relation xml:id="unclear"> ......... </bitext-relation> <reuse-type xml:id="correlationGeneral"> <IRI>tag:kalvesmaki@gmail.com,2014:reuse-type:correlation-general</IRI> <name>Texts are generally correlated, but without specifying the relation</name> </reuse-type> <comment when="2016-02-22-05:00" who="park">The following is equivalent to @which = 'letters'</comment> ......... </vocabulary-key>
Note | |
---|---|
Taken from ringoroses.01+03.token.1 |
Example 12.262. <reuse-type>
<vocabulary-key> ......... <bitext-relation xml:id="unclear"> ......... </bitext-relation> <reuse-type xml:id="correlationGeneral"> <IRI>tag:kalvesmaki@gmail.com,2014:reuse-type:correlation-general</IRI> <name>Texts are generally correlated, but without specifying the relation</name> </reuse-type> <person xml:id="park"> ......... </person> ......... </vocabulary-key>
Note | |
---|---|
Taken from ringoroses.01+03.token.2 |
The element role
specifies a role (responsibility, task, or activity) that one or more <agent>
s had in creating or editing the data.
A role may be any activity, e.g., editor, funder, supervisor, data-processor, peer reviewer, patron, identified through the enclosed IRI + name pattern.
See the section called “TAN keywords for types of roles (<role>)” for standard TAN vocabulary.
Used by: ~voc-key-core
Example 12.263. <role>
<head> ......... <vocabulary-key> ......... <algorithm xml:id="xslt1"> ......... </algorithm> <role xml:id="editor"> <IRI>http://schema.org/editor</IRI> <name xml:lang="eng">Editor</name> </role> <role xml:id="stylesheet1" which="stylesheet"/> <relationship xml:id="alt"> ......... </relationship> </vocabulary-key> ......... </head>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-logical |
Example 12.264. <role>
<head> ......... <vocabulary-key> ......... <algorithm xml:id="xslt1"> ......... </algorithm> <role xml:id="editor"> <IRI>http://schema.org/editor</IRI> <name xml:lang="eng">Editor</name> </role> <role xml:id="stylesheet1" which="stylesheet"/> <scriptum xml:id="bekker"> ......... </scriptum> </vocabulary-key> ......... </head>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-scriptum |
The element rule
encloses asserts and reports that should be evaluated provided that the conditions specified in the attributes (or children <where>
attributes) are true.
The sequence of consecutive <rule>
s is immaterial.
Used by: ~TAN-mor-body
Example 12.265. <rule>
<TAN-mor TAN-version="2021" id="tag:kalvesmaki.com,2014:tan-r-mor:eng:penn"> ......... <body> <rule m-matches=".+"> <assert m-has-how-many-codes="1">Features may not be combined.</assert> </rule> <rule> <where m-has-codes="$"/> <assert tok-matches="$">Only $ may be tagged as a dollar sign.</assert> </rule> <rule m-has-codes="'' . ; :"> <report tok-matches="\w">Nothing marked as punctuation should have word characters.</report> </rule> <code feature="closing_quotation_mark"> ......... </code> ......... </body> </TAN-mor>
Note | |
---|---|
Taken from eng.kalvesmaki.com,2014.2 |
Example 12.266. <rule>
<body> <rule m-has-how-many-codes="2-10"> <report m-matches="^c">A conjunction has no other inflectional properties.</report> <report m-matches="^r">A preposition has no other inflectional properties.</report> <report m-matches="^i">An interjection has no other inflectional properties.</report> ......... </rule> <rule m-matches="^e"> ......... </rule> ......... </body>
Note | |
---|---|
Taken from grc.perseus.tan-mor |
The element scriptum
contains an IRI + name pattern identifying a text-bearing object.
Used by: ~voc-element-tan-a
, ~voc-element-class-1
Example 12.267. <scriptum>
<vocabulary-key> ......... <role xml:id="stylesheet1" which="stylesheet"/> <scriptum xml:id="bekker"> <IRI>http://id.lib.harvard.edu/alma/990017941240203941/catalog</IRI> <IRI>http://www.worldcat.org/oclc/490107033</IRI> <name>Bekker</name> ......... </scriptum> </vocabulary-key>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-scriptum |
Example 12.268. <scriptum>
<vocabulary-key> ......... <role xml:id="stylesheet1" which="stylesheet"/> <scriptum xml:id="bekker"> <IRI>http://id.lib.harvard.edu/alma/990017941240203941/catalog</IRI> <IRI>http://www.worldcat.org/oclc/490107033</IRI> <name>Bekker</name> ......... </scriptum> </vocabulary-key>
Note | |
---|---|
Taken from ar.cat.grc.1949.minio-paluello.ref-logical |
Example 12.269. <scriptum>
<vocabulary-key> ......... <role xml:id="stylesheet1" which="stylesheet"/> <scriptum xml:id="bekker"> <IRI>http://id.lib.harvard.edu/alma/990017941240203941/catalog</IRI> <IRI>http://www.worldcat.org/oclc/490107033</IRI> <name>Bekker</name> ......... </scriptum> </vocabulary-key>
Note | |
---|---|
Taken from ar.cat.grc.1949.minio-paluello.ref-scriptum |
Example 12.270. <scriptum>
<vocabulary-key> ......... <relationship xml:id="alt"> ......... </relationship> <scriptum xml:id="bekker"> <IRI>http://id.lib.harvard.edu/alma/990017941240203941/catalog</IRI> <IRI>http://www.worldcat.org/oclc/490107033</IRI> <name>Bekker</name> ......... </scriptum> </vocabulary-key>
Note | |
---|---|
Taken from ar.cat.lat.1961.minio-paluello.ref-scriptum |
The element see-also
identifies a file that is related to the current one.
The sequence of consecutive <see-also>
s is immaterial.
Used by: ~networked-files-core
Caution | |
---|---|
An element that has a |
Caution | |
---|---|
Every TAN file referred to by way of an element containing |
Caution | |
---|---|
No element may point to a TAN file that has an identical |
Important | |
---|---|
If a target file has children items in the |
Important | |
---|---|
If a target file has a |
Important | |
---|---|
If a target file points only to non-local locations and no internet is available, the following message will be returned. “No internet available.” |
Important | |
---|---|
If an element not essential to validation has no |
Important | |
---|---|
If |
Example 12.271. <see-also>
<head> ......... <model> ......... </model> <see-also relationship="alt"> <IRI>tag:kalvesmaki.com,2014:tan-t:ar.cat.grc.1949.minio-paluello:object-refs</IRI> <name>Categories, Aristotle, Greek text by Minio-Paluello</name> <location href="ar.cat.grc.1949.minio-paluello.ref-scriptum.xml" accessed-when="2016-02-11T12:40:42.823-05:00"/> </see-also> <redivision> ......... </redivision> ......... </head>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-logical |
Example 12.272. <see-also>
<head> ......... <source> ......... </source> <see-also relationship="alt"> <IRI>tag:kalvesmaki.com,2014:tan-t:ar.cat.grc.1949.minio-paluello:semantic-refs</IRI> <name>Categories, Aristotle, Greek text by Minio-Paluello</name> <location accessed-when="2018-12-11-05:00" href="ar.cat.grc.1949.minio-paluello.ref-logical.xml"/> </see-also> <vocabulary-key> ......... </vocabulary-key> ......... </head>
Note | |
---|---|
Taken from ar.cat.lat.1961.minio-paluello.ref-scriptum |
The element skip
marks parts of a source that have been ignored or should be skipped, either shallowly (default) or deeply.
Note, the shallow skip of a <div>
may result in the creation of empty <div>
s, which will be ignored during validation.
This element is useful for ignoring extraneous divs, e.g., where a source has introduced divs that do not exist in other versions of the same work. For example, a transcription may group the topmost divisions of a text into parts, or may adopt superfluous divisions (e.g., introducing a <div>
for chapter in the New Testament book Philemon, which does not have more than one chapter, and can be identified purely by verse).
Only the first <skip>
applying to a <div>
in a given source will be applied.
Used by: ~adjust-class-2
Caution | |
---|---|
Any range in either an |
Important | |
---|---|
Only the first of multiple adjustment actions will be applied. Action priority: skip, ref-based rename, then for every |
Caution | |
---|---|
In adjustment actions involving |
Caution | |
---|---|
Every div type reference must be valid in every source |
Example 12.273. <skip>
<adjustments src="fra">
<skip div-type="summ" shallow="false"/>
<equate n="ti title"/>
.........
</adjustments>
Note | |
---|---|
Taken from ar.cat.TAN-A |
Example 12.274. <skip>
<adjustments src="ger">
<skip div-type="Gedicht"/>
<rename n="e" by="-1"/>
</adjustments>
Note | |
---|---|
Taken from ringoroses.div.1 |
Note | |
---|---|
Taken from ringoroses.01+03.token.1 |
Example 12.276. <skip>
<adjustments src="ger">
<skip div-type="Gedicht"/>
<rename ref="1 e" new="4"/>
</adjustments>
Note | |
---|---|
Taken from ringoroses.01+03.token.2 |
The element source
identifies the source upon which the data in the <body>
of the current file depends.
TAN-T and TAN-A-lm allow only one <source>
. TAN-A-tok allows exactly two. All other TAN formats require one or more.
The sequence of consecutive <source>
s is immaterial, but it does dictate the order in which sources are validated and processed.
Used by: ~source-list
Caution | |
---|---|
An element that has a |
Caution | |
---|---|
Every TAN file referred to by way of an element containing |
Caution | |
---|---|
No element may point to a TAN file that has an identical |
Important | |
---|---|
If a target file has children items in the |
Important | |
---|---|
If a target file has a |
Important | |
---|---|
If a target file points only to non-local locations and no internet is available, the following message will be returned. “No internet available.” |
Caution | |
---|---|
If a linking element points to a file that must be resolved, that file must be a TAN file. |
Important | |
---|---|
If |
Caution | |
---|---|
A class 1 |
Caution | |
---|---|
Sources are integral parts of a class 2 TAN file. Access to at least one non-faulty copy is absolutely mandatory. |
Example 12.277. <source>
<head> ......... <work> ......... </work> <source> <IRI>http://id.lib.harvard.edu/aleph/007901738/catalog</IRI> <name>Aristotle: Categoriae & De interpretatione by E.M. Edghill. Analytica priora / by A.J. Jenkinson. Analytica posteriora / by G.R.G. Mure. Oxford : Clarendon Press, 1926. </name> </source> <model> ......... </model> ......... </head>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-logical |
Example 12.278. <source>
<head> ......... <work> ......... </work> <source> <IRI>http://id.lib.harvard.edu/aleph/007901738/catalog</IRI> <name>Aristotle: Categoriae & De interpretatione by E.M. Edghill. Analytica priora / by A.J. Jenkinson. Analytica posteriora / by G.R.G. Mure. Oxford : Clarendon Press, 1926. </name> </source> <redivision> ......... </redivision> ......... </head>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-scriptum |
Example 12.279. <source>
<head> ......... <work> ......... </work> <source> <IRI>http://id.lib.harvard.edu/aleph/002773288/catalog</IRI> <name>Logique d'Aristote: Traduite en français pour la première fois et accompagnée de notes perpétuelles par J. Barthélemy Saint-Hilaire. Paris : Ladrange, 1839-1844. </name> </source> <redivision> ......... </redivision> ......... </head>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949 |
Example 12.280. <source>
<head> ......... <work> ......... </work> <source> <IRI>http://id.lib.harvard.edu/aleph/002773288/catalog</IRI> <name>Logique d'Aristote: Traduite en français pour la première fois et accompagnée de notes perpétuelles par J. Barthélemy Saint-Hilaire. Paris : Ladrange, 1839-1844. </name> </source> <redivision> ......... </redivision> ......... </head>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.ref-logical |
The element subject
points to text references that act as the subject of the claim.
Unlike @subject
, which points to any entity via idrefs, <subject>
is intended exclusively to point to data content or a textual subject.
Each textual <subject>
is interpreted as a single entity, with all textual references encoded by the element treated as a single, grouped passage. The sequence of its contents is therefore significant.
The element subject
specifies expectations on a verb's use of subject. By default, a subject is required.
Used by: ~element-claim
, ~subject
, ~constraints-on-verb
Caution | |
---|---|
Claims involving verbs whose constrained content requires specification of units must use |
Caution | |
---|---|
|
Example 12.281. <subject>
<TAN-A TAN-version="2021" id="tag:parkj@textalign.net,2015:ar.cat.tan-a:claims"> <head> ......... <vocabulary-key> ......... <verb xml:id="om"> ......... <constraints> <subject status="required" item-type="person work version scriptum"/> <at-ref status="required"/> ......... </constraints> </verb> <verb xml:id="attests"> ......... <constraints> <subject status="required" item-type="person work version scriptum"/> <object status="required" item-type="ref"/> </constraints> </verb> <verb xml:id="has-length"> ......... <constraints> <subject status="required" item-type="scriptum"/> <object status="required" content-datatype="integer" content-lexical-constraint="\d+"/> </constraints> </verb> ......... </vocabulary-key> ......... </head> <body claimant="park" claim-period="per2010s"> ......... <claim verb="refers-to"> <subject src="grc" ref="1 b 25"/> <object work="grc" ref="1 a 16"/> </claim> ......... </body> </TAN-A>
Note | |
---|---|
Taken from ar.cat.TAN-A.claims |
The element successor
identifies a file that succeeds the current file. Successors may or may not have the same document @id
value.
The sequence of consecutive <successor>
s is immaterial.
Used by: ~networked-files-core
Caution | |
---|---|
|
Caution | |
---|---|
An element that has a |
Caution | |
---|---|
Every TAN file referred to by way of an element containing |
Caution | |
---|---|
No element may point to a TAN file that has an identical |
Important | |
---|---|
If a target file has children items in the |
Important | |
---|---|
If a target file has a |
Important | |
---|---|
If a target file points only to non-local locations and no internet is available, the following message will be returned. “No internet available.” |
Caution | |
---|---|
If a linking element points to a file that must be resolved, that file must be a TAN file. |
Example 12.282. <successor>
<head> ......... <source> ......... </source> <successor> <IRI>tag:hans@beispiel.com,2014:ringel</IRI> <name>TAN Transkription, Ringelreihen mit Riederfallen</name> <location accessed-when="2021-04-29T11:46:04.656-04:00" href="ring-o-roses.deu.1897.xml"/> </successor> <adjustments> ......... </adjustments> ......... </head>
Note | |
---|---|
Taken from ring-o-roses.deu.1897-prev |
The element tail
permits any arbitrary content. This element is suitable as a placeholder for temporary data, especially to improve the efficiency of applications.
Used by: ~TAN-root
Example 12.283. <tail>
<TAN-T TAN-version="2021" id="tag:hans@beispiel.com,2014:ringel"> ......... <body xml:lang="deu"> ......... </body> <tail> </tail> </TAN-T>
Note | |
---|---|
Taken from ring-o-roses.deu.1897-prev |
The element TAN-A
specifies that the file is a general TAN alignment file. Root element.
Important | |
---|---|
Users should be warned about versions of TAN that are under development. “This version of TAN is under development, and is subject to change. Participants in developing the TAN schemas, functions, and guidelines are welcome. See |
Important | |
---|---|
Users should be warned about TAN files whose last change was made by an algorithm. |
Example 12.284. <TAN-A>
<TAN-A TAN-version="2021" id="tag:parkj@textalign.net,2015:ar.cat.tan-a:claims"> <head> ......... </head> <body claimant="park" claim-period="per2010s"> ......... </body> </TAN-A>
Note | |
---|---|
Taken from ar.cat.TAN-A.claims |
Example 12.285. <TAN-A>
<TAN-A TAN-version="2021" id="tag:parkj@textalign.net,2015:ar.cat.tan-a"> <head> ......... </head> <body claimant="park"> ......... </body> </TAN-A>
Note | |
---|---|
Taken from ar.cat.TAN-A |
Example 12.286. <TAN-A>
<TAN-A TAN-version="2021" id="tag:parkj@textalign.net,2015:patricius.confessio.tan-a"> <head> ......... </head> <body claimant="park"> ......... </body> </TAN-A>
Note | |
---|---|
Taken from patricius.confessio.TAN-A |
Example 12.287. <TAN-A>
<TAN-A TAN-version="2021" id="tag:parkj@textalign.net,2015:ring01-TAN-A-ring02"> <head> ......... </head> <body claimant="park"> ......... </body> </TAN-A>
Note | |
---|---|
Taken from ringoroses.div.1 |
The element TAN-A-lm
specifies that the file is a TAN file containing lexico-morphology data about a class-1 source or a language in general. Root element.
Important | |
---|---|
Users should be warned about versions of TAN that are under development. “This version of TAN is under development, and is subject to change. Participants in developing the TAN schemas, functions, and guidelines are welcome. See |
Important | |
---|---|
Users should be warned about TAN files whose last change was made by an algorithm. |
Example 12.288. <TAN-A-lm>
<TAN-A-lm TAN-version="2021" id="tag:kalvesmaki.com,2014:tan-t:ar.cat.grc.1949.minio-paluello:semantic-refs:TAN-A-lm:2016-04-05T07:07:40.033-04:00"> <head> ......... </head> <body lexicon="LSJ Lampe new" morphology="Perseus" claimant="xslt2"> ......... </body> </TAN-A-lm>
Note | |
---|---|
Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-A-lm-sample |
Example 12.289. <TAN-A-lm>
<TAN-A-lm TAN-version="2021" id="tag:kalvesmaki.com,2015:tan-a-lm:grc:perseusα"> <head> ......... </head> <body lexicon="LSJ" morphology="perseus-dik" claimant="xslt2"> ......... </body> </TAN-A-lm>
Note | |
---|---|
Taken from grc-tan-a-lm-%CE%B1 |
Example 12.290. <TAN-A-lm>
<TAN-A-lm TAN-version="2021" id="tag:kalvesmaki.com,2015:tan-a-lm:grc:perseusαʹ"> <head> ......... </head> <body lexicon="LSJ" morphology="perseus-dik" claimant="xslt2"> ......... </body> </TAN-A-lm>
Note | |
---|---|
Taken from grc-tan-a-lm-%CE%B1%CA%B9 |
Example 12.291. <TAN-A-lm>
<TAN-A-lm TAN-version="2021" id="tag:parkj@textalign.net,2015:ring01-lm"> <head> ......... </head> <body lexicon="english" morphology="penn" claimant="xslt2"> ......... </body> </TAN-A-lm>
Note | |
---|---|
Taken from ring-o-roses.eng.1881.lm |
The element TAN-A-tok
specifies that the file is contains token-to-token alignments between two sources. Root element.
Important | |
---|---|
Users should be warned about versions of TAN that are under development. “This version of TAN is under development, and is subject to change. Participants in developing the TAN schemas, functions, and guidelines are welcome. See |
Important | |
---|---|
Users should be warned about TAN files whose last change was made by an algorithm. |
Example 12.292. <TAN-A-tok>
<TAN-A-tok TAN-version="2021" id="tag:parkj@textalign.net,2015:TAN-A-tok,ring01+ring02"> <head> ......... </head> <body bitext-relation="B-descends-from-A" reuse-type="adaptation"> ......... </body> </TAN-A-tok>
Note | |
---|---|
Taken from ringoroses.01+02.token.1 |
Example 12.293. <TAN-A-tok>
<TAN-A-tok TAN-version="2021" id="tag:parkj@textalign.net,2015:TAN-A-tok,ring01+ring03"> <head> ......... </head> <body reuse-type="correlationGeneral" bitext-relation="unclear" claimant="xslt2"> ......... </body> </TAN-A-tok>
Note | |
---|---|
Taken from ringoroses.01+03.token.1 |
Example 12.294. <TAN-A-tok>
<TAN-A-tok TAN-version="2021" id="tag:parkj@textalign.net,2015:TAN-A-tok,ring01+ring03:alt"> <head> ......... </head> <body reuse-type="correlationGeneral" bitext-relation="unclear" claimant="xslt2"> ......... </body> </TAN-A-tok>
Note | |
---|---|
Taken from ringoroses.01+03.token.2 |
The element TAN-mor
specifies that the TAN file contains codes and rules for the parts of speech for a language, the codes for those parts, and the rules for combining them. Root element.
Important | |
---|---|
Users should be warned about versions of TAN that are under development. “This version of TAN is under development, and is subject to change. Participants in developing the TAN schemas, functions, and guidelines are welcome. See |
Important | |
---|---|
Users should be warned about TAN files whose last change was made by an algorithm. |
Example 12.295. <TAN-mor>
<TAN-mor TAN-version="2021" id="tag:kalvesmaki.com,2014:tan-r-mor:eng:penn"> <head> ......... </head> <body> ......... </body> </TAN-mor>
Note | |
---|---|
Taken from eng.kalvesmaki.com,2014.2 |
Example 12.296. <TAN-mor>
<TAN-mor TAN-version="2021" id="tag:kalvesmaki.com,2014:tan-r-mor:grc:perseus"> <head> ......... </head> <body> ......... </body> </TAN-mor>
Note | |
---|---|
Taken from grc.perseus.tan-mor |
The element TAN-T
specifies that the TAN file contains a transcription. Root element.
Important | |
---|---|
Users should be warned about versions of TAN that are under development. “This version of TAN is under development, and is subject to change. Participants in developing the TAN schemas, functions, and guidelines are welcome. See |
Important | |
---|---|
Users should be warned about TAN files whose last change was made by an algorithm. |
Example 12.297. <TAN-T>
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2021"> <head> ......... </head> <body xml:lang="eng"> ......... </body> </TAN-T>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-logical |
Example 12.298. <TAN-T>
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:model-object-refs" TAN-version="2021"> <head> ......... </head> <body xml:lang="eng"> ......... </body> </TAN-T>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-scriptum |
Example 12.299. <TAN-T>
<TAN-T TAN-version="2021" id="tag:kalvesmaki.com,2014:tan-t:ar.cat.fra.1844.saint-hilaire:semantic-refs-realigned"> <head> ......... </head> <body xml:lang="fra"> ......... </body> </TAN-T>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949 |
Example 12.300. <TAN-T>
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.fra.1844.saint-hilaire:semantic-refs" TAN-version="2021"> <head> ......... </head> <body xml:lang="fra"> ......... </body> </TAN-T>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.ref-logical |
The element TAN-voc
specifies a TAN file that contains vocabulary items. Root element.
Important | |
---|---|
Users should be warned about versions of TAN that are under development. “This version of TAN is under development, and is subject to change. Participants in developing the TAN schemas, functions, and guidelines are welcome. See |
Important | |
---|---|
Users should be warned about TAN files whose last change was made by an algorithm. |
Caution | |
---|---|
The vocabulary of a file may not include it. |
Example 12.301. <TAN-voc>
<TAN-voc TAN-version="2021" id="tag:parkj@textalign.net,2015:TAN-key:ar.cat"> <head> ......... </head> <body affects-element="work"> ......... </body> </TAN-voc>
Note | |
---|---|
Taken from ar.cat.TAN-voc |
Example 12.302. <TAN-voc>
<TAN-voc TAN-version="2021" id="tag:parkj@textalign.net,2015:TAN-voc:standard"> <head> ......... </head> <body> ......... </body> </TAN-voc>
Note | |
---|---|
Taken from park-projects.TAN-voc |
Example 12.303. <TAN-voc>
<TAN-voc TAN-version="2021" id="tag:textalign.net,2015:tan-voc:bitext-relation"> <head> ......... </head> <body affects-element="bitext-relation"> ......... </body> </TAN-voc>
Note | |
---|---|
Taken from bitext-relations.TAN-voc |
Example 12.304. <TAN-voc>
<TAN-voc TAN-version="2021" id="tag:textalign.net,2015:tan-voc:div-types"> <head> ......... </head> <body affects-element="div-type"> ......... </body> </TAN-voc>
Note | |
---|---|
Taken from div-types.TAN-voc |
Definition 1
The element through-tok
points to a single token that is the end of a range of tokens to be selected from a source, but without @ref.
.
Definition 2
The element through-tok
points to a single token in a single reference that is the end of a range of tokens to be selected from a source, in the context of @ref.
.
Used by: ~text-passage-selector-no-ref
, ~text-passage-selector-with-ref
Caution | |
---|---|
Every token must be locatable in every cited ref in every source. |
Caution | |
---|---|
In a |
Example 12.305. <through-tok>
<passage ref="5 4 7 2">
<from-tok val=":" pos="1"/>
<through-tok val=":" pos="1"/>
</passage>
Note | |
---|---|
Taken from ar.cat.TAN-A |
Example 12.306. <through-tok>
<subject src="eng-uk">
.........
<from-tok ref="1" pos="3"/>
<through-tok ref="2" pos="1"/>
</subject>
Note | |
---|---|
Taken from ringoroses.div.1 |
The element to
indicates a ref to which the preceding <tok>
s should be moved.
Used by: ~adj-element-reassign
Example 12.307. <to>
<reassign>
<passage ref="5 4 7 2">
.........
</passage>
<to ref="5 4 7 1"/>
</reassign>
Note | |
---|---|
Taken from ar.cat.TAN-A |
The element to-do
lists tasks that remain to be done (via <comment>
children). Lack of content in <to-do>
suggests that the file is no longer considered a work in progress, but it does not guarantee that the file will not be changed in the future.
An empty <to-do>
implies stability, so requires a file to have a <master-location>
.
Used by: ~element-head
Caution | |
---|---|
Any TAN file without a to-do list will be treated as being no longer in progress and should have at least one master-location. |
Example 12.308. <to-do>
<head>
.........
<change who="xslt2" when="2018-08-04T23:55:36.096-04:00">Converted from 2018 to 2019 schemas.</change>
<to-do/>
</head>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-logical |
Example 12.309. <to-do>
<head>
.........
<change when="2018-07-30-04:00" who="kalvesmaki">updated to 2019 schemas</change>
<to-do/>
</head>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-scriptum |
Example 12.310. <to-do>
<head>
.........
<change who="xslt2" when="2018-08-05T00:03:20.142-04:00">Converted from 2018 to 2019 schemas.</change>
<to-do/>
</head>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949 |
Example 12.311. <to-do>
<head>
.........
<change who="xslt2" when="2018-08-05T00:05:17.879-04:00">Converted from 2018 to 2019 schemas.</change>
<to-do/>
</head>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.ref-logical |
The element tok
points to a token in the abstract, no matter where it is found, either in the source (if there is one) or the language (if there is no source).
The sequence of consecutive <tok>
s is immaterial, except in the context of <group>
.
Definition 1
The element tok
points to one or more tokens in the context source or reference.
Definition 2
The element tok
points to one or more tokens in the context source.
The element tok
identifies one or more tokens (words or word fragments). Used by class-2 files to make claims about specific words.
In TAN-A and TAN-A-tok files, <tok>
does not necessarily carry linguistic connotations; in TAN-A-lm, it normally does.
Most <tok>
s are restricted to a single token, or a portion of a single token, perhaps filtered by the value of @chars.
. But they can refer to multiple tokens through multiple values of @src
, @ref
, and @pos
, to save space and perhaps enhance legibility. For example, <tok src="a b" ref="1.1 - 1.3" pos="1-4"> would point to 24 tokens (assuming that the two sources each have at least four tokens in the three references 1.1, 1.2, and 1.3).
If you wish to treat multiple word fragments as a single token, use <group>
.
The sequence of consecutive <tok>
s is immaterial in the context of TAN-A-lm, and TAN-A-tok, except in the context of <group>
, where the sequence dictates how the new token is to be constructed.
The sequence of consecutive <tok>
s is important in the context of TAN-A, where the sequence specifies the order in which word tokens should be supplied in the context of the <claim>
.
Used by: ~default-tok-element
, ~single-div-partial-textual-reference
, ~multi-div-partial-textual-reference
Caution | |
---|---|
Every token must be locatable in every cited ref in every source. |
Caution | |
---|---|
Every character must be locatable in every token in every ref in every source. |
Example 12.312. <tok>
<TAN-A TAN-version="2021" id="tag:parkj@textalign.net,2015:ar.cat.tan-a:claims"> ......... <body claimant="park" claim-period="per2010s"> ......... <claim subject="andronicus boethus" adverb="perhaps" verb="om" xml:id="cl1a2a" claim-when="2017-03-10" claimant="park"> <at-ref src="grc" ref="1 a 2"> <tok pos="3-4"/> </at-ref> </claim> ......... <claim subject="comm-omnes" verb="attests" period="late_antiquity"> <object src="grc" ref="1 a 2"> <tok pos="3-4"/> </object> </claim> <claim subject="comm-omnes" verb="attests" xml:id="cl1a2b"> <object src="grc" ref="1 a 2"> <tok pos="3-4"/> </object> </claim> ......... <claim subject="B" verb="reads"> <at-ref src="grc" ref="1 a 5"> <tok pos="1-2"/> </at-ref> ......... </claim> <claim subject="Λ" adverb="perhaps" verb="reads"> <at-ref src="grc" ref="1 a 5"> <tok pos="1-2"/> </at-ref> ......... </claim> <claim subject="π α φ ο" verb="matches"> <object src="grc" ref="1 a 5"> <tok pos="1-2"/> </object> </claim> ......... </body> </TAN-A>
Note | |
---|---|
Taken from ar.cat.TAN-A.claims |
The element tok-is
specifies an exact value of @val
of <tok>
s in the file. Collectively, every <tok>
should point to at least one <tok-is>
.
This element is an optional way to improve the efficiency of validation and applications.
The sequence of consecutive <tok-is>
s is immaterial.
Used by: ~decl-non-class-2
Example 12.313. <tok-is>
<TAN-A-lm TAN-version="2021" id="tag:kalvesmaki.com,2015:tan-a-lm:grc:perseusα"> <head> ......... <for-lang>grc</for-lang> <tok-is>ἆ</tok-is> <tok-is>ἁ</tok-is> <tok-is>ἅ</tok-is> <tok-is>ἃ</tok-is> <tok-is>ᾇ</tok-is> ......... </head> ......... </TAN-A-lm>
Note | |
---|---|
Taken from grc-tan-a-lm-%CE%B1 |
The element tok-starts-with
specifies one opening string that characterizes the @val
of <tok>
s in the file.
This element is an optional way to improve the efficiency of validation and applications.
The sequence of consecutive <tok-is>
s is immaterial.
Used by: ~decl-non-class-2
Example 12.314. <tok-starts-with>
<TAN-A-lm TAN-version="2021" id="tag:kalvesmaki.com,2015:tan-a-lm:grc:perseusαʹ"> <head> ......... <for-lang>grc</for-lang> <tok-starts-with>αʹ</tok-starts-with> <tok-starts-with>Αʹ</tok-starts-with> <vocabulary-key> ......... </vocabulary-key> ......... </head> ......... </TAN-A-lm>
Note | |
---|---|
Taken from grc-tan-a-lm-%CE%B1%CA%B9 |
The element token-definition
defines a word token via a regular expression. The pattern in this element is used to split a string into tokens and non-tokens.
The attributes of this element mirror the parameters for the function xsl:analyze-string (see https://www.w3.org/TR/xslt-30/#element-analyze-string
).
For more see the section called “Defining words and tokens” and for standard TAN vocabulary items see the section called “TAN keywords for types of token definitions (<token-definition>)”
Used by: ~decl-class-1
, ~decl-class-2
, ~entity-tok-def
Caution | |
---|---|
No source may be given more than one token definition. |
Example 12.315. <token-definition>
<head>
.........
<license licensor="park">
.........
</license>
<token-definition src="*" which="letters only"/>
<vocabulary>
.........
</vocabulary>
.........
</head>
Note | |
---|---|
Taken from ar.cat.TAN-A.claims |
Example 12.316. <token-definition>
<head>
.........
<numerals priority="letters"/>
<token-definition src="fra" pattern="\S+"/>
<source xml:id="grc">
.........
</source>
.........
</head>
Note | |
---|---|
Taken from ar.cat.TAN-A |
Example 12.317. <token-definition>
<head>
.........
<license which="by_4.0" licensor="park"/>
<token-definition src="eng-us" pattern="[-\w]+"/>
<source xml:id="eng-uk">
.........
</source>
.........
</head>
Note | |
---|---|
Taken from ringoroses.div.1 |
Example 12.318. <token-definition>
<head>
.........
<license licensor="kalvesmaki">
.........
</license>
<token-definition pattern="[\w]+"/>
<inclusion xml:id="rel">
.........
</inclusion>
.........
</head>
Note | |
---|---|
Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-A-lm-sample |
The element topic
contains an IRI + name pattern identifying a topic.
Used by: ~voc-element-tan-a
Example 12.319. <topic>
<vocabulary-key> ......... <verb which="is about" xml:id="concerns"/> <topic xml:id="predication"> <IRI>tag:parkj@textalign.net,2015:topic:predication</IRI> <name>predication</name> <desc>The act of asserting something about a grammatical subject.</desc> </topic> </vocabulary-key>
Note | |
---|---|
Taken from ar.cat.TAN-A |
The element unit
contains an IRI + name pattern identifying a unit type (e.g., millimeters, seconds, Euros), to be used in conjunction with <object>
to specify what quantities measure.
Used by: ~voc-element-tan-a
Example 12.320. <unit>
<vocabulary-key> ......... <verb xml:id="has-length"> ......... </verb> <unit xml:id="folio"> <IRI>http://dbpedia.org/resource/Folio</IRI> <name>folio</name> </unit> <modal which="possibly" xml:id="perhaps"/> ......... </vocabulary-key>
Note | |
---|---|
Taken from ar.cat.TAN-A.claims |
The element val
contains the expected value for a morphological code
Used by: ~element-code
Example 12.321. <val>
<TAN-mor TAN-version="2021" id="tag:kalvesmaki.com,2014:tan-r-mor:eng:penn"> ......... <body> ......... <code feature="closing_quotation_mark"> <desc>Examples: ' ''</desc> <val>''</val> </code> <code feature="dash"> <desc>Example: --</desc> <val>--</val> </code> <code feature="dollar"> <desc>Examples: Examples: $ -$ --$ A$ C$ HK$ M$ NZ$ S$ U.S.$ US$</desc> <val>$</val> </code> <code feature="opening_parenthetical_punctuation"> <desc>Examples: ( [ {</desc> <val>[</val> </code> ......... </body> </TAN-mor>
Note | |
---|---|
Taken from eng.kalvesmaki.com,2014.2 |
The element value
states the value of a <checksum>
Used by: <checksum>
Example 12.322. <value>
<checksum> ......... <name>SHA-1</name> <value>91D95564ABDF2B2C1B9EEF016CBA51E8179646CC</value> </checksum>
Note | |
---|---|
Taken from patricius.confessio.2003.eng |
The element verb
contains an IRI + name pattern identifying a property, relationship, action, or something else that is used to say something about something.
The preferred term "verb" is equivalent to RDF "predicate." The latter term is avoided, since in regular usage "predicate" signifies both a verb and all the words it governs.
See the section called “TAN keywords for verbs (<verb>)” for standard TAN vocabulary items.
Used by: ~voc-element-tan-a
, ~body-item
Caution | |
---|---|
Claims involving verbs whose constrained content requires specification of units must use |
Caution | |
---|---|
A claim with a verb that has content constraints must not allow other verbs. |
Example 12.323. <verb>
<head> ......... <vocabulary-key> ......... <alias xml:id="comm-omnes" idrefs="π δ α.d φ.d ο.d η.d σ.d"/> <verb which="refers or alludes to" xml:id="refers-to"/> <verb xml:id="om"> <IRI>tag:parkj@textalign.net,2015:verb:omits</IRI> <name>omits</name> <name>omits text</name> ......... </verb> <verb xml:id="attests"> <IRI>tag:parkj@textalign.net,2015:verb:attests-to</IRI> <name>attests</name> <name>attests to</name> ......... </verb> <verb xml:id="has-length"> <IRI>tag:parkj@textalign.net,2015:verb:scriptum-has-length</IRI> <name>has length</name> <desc>This verb is used to describe the how many pages or folios a scriptum is.</desc> ......... </verb> <unit xml:id="folio"> ......... </unit> ......... </vocabulary-key> ......... </head>
Note | |
---|---|
Taken from ar.cat.TAN-A.claims |
The element version
identifies the version of a work. Applicable to sources that contain multiple versions, e.g., original text and facing translations. Like <work>
, <version>
points to a conceptual entity, not a physical one.
Very few work-versions have their own URNs. It is advisable to assign a tag URN or a UUID. If you have used an IRI for <work>
that you are entitled to modify, you may wish to add a suffix that will name the version. If you need to specify exactly where on a text-bearing object a version appears, <desc>
or <comment>
should be used.
For background, see the section called “One Work”
The element version
identifies the version of a work. Applicable to sources that contain multiple versions, e.g., original text and facing translations. Like <work>
, <version>
points to a conceptual entity, not a physical one.
In the context of a class 1 file, the entity identified by <version>
is assumed to be a version of the entity defined in <work>
.
Very few work-versions have their own URN names. It is advisable to assign a tag URN or a UUID. If you have used an IRI for <work>
that you are entitled to modify, you may wish to add a suffix that will name the version. If you need to specify exactly where on a text-bearing object a version appears, <desc>
or <comment>
should be used.
For more, see the section called “One Work”
Used by: ~voc-element-tan-a
, ~decl-class-1
Example 12.324. <version>
<head> ......... <work> ......... </work> <version> <IRI>tag:parkj@textalign.net,2015:version:matthews-version-of-the-lords-prayer</IRI> <name>Matthew's version of the Lord's Prayer</name> </version> <vocabulary> ......... </vocabulary> ......... </head>
Note | |
---|---|
Taken from lords-prayer.eng.kjv.1760 |
Example 12.325. <version>
<head> ......... <work> ......... </work> <version> <IRI>urn:uuid:31648039-3dbb-49b9-b66e-9bd2cd11630e</IRI> <name>zweite Version</name> </version> <numerals priority="letters"/> ......... </head>
Note | |
---|---|
Taken from ring-o-roses.deu.1897-prev |
Example 12.326. <version>
<head> ......... <work> ......... </work> <version> <IRI>urn:uuid:31648039-3dbb-49b9-b66e-9bd2cd11630e</IRI> <name>zweite Version</name> </version> <numerals priority="letters"/> ......... </head>
Note | |
---|---|
Taken from ring-o-roses.deu.1897 |
Example 12.327. <version>
<head> ......... <work> ......... </work> <version> <IRI>tag:parkj@textalign.net,2015:work:ring:version:newell-reported</IRI> <name>Ring around the Rosie, second version</name> <name>Ring around the Rosie, version reported by Newell</name> </version> <source> ......... </source> ......... </head>
Note | |
---|---|
Taken from ring-o-roses.eng.1951 |
The element vocabulary
specifies a TAN-voc file that supplies vocabulary items for the host file. For more discussion, see the section called “Vocabulary (TAN-voc
)”
The sequence of consecutive <vocabulary>
s is immaterial.
Used by: ~networked-files-core
, ~vocabulary-list
Caution | |
---|---|
No file may import vocabularies with items that have duplicate IRIs. |
Caution | |
---|---|
|
Caution | |
---|---|
Inclusions/vocabularies may not be invoked circularly. |
Caution | |
---|---|
The vocabulary of a file may not include it. |
Important | |
---|---|
The |
Caution | |
---|---|
An element that has a |
Caution | |
---|---|
Every TAN file referred to by way of an element containing |
Caution | |
---|---|
No element may point to a TAN file that has an identical |
Important | |
---|---|
If a target file has children items in the |
Important | |
---|---|
If a target file has a |
Important | |
---|---|
If a target file points only to non-local locations and no internet is available, the following message will be returned. “No internet available.” |
Caution | |
---|---|
If a linking element points to a file that must be resolved, that file must be a TAN file. |
Important | |
---|---|
If |
Caution | |
---|---|
An element's |
Caution | |
---|---|
A |
Caution | |
---|---|
Vocabularies are integral parts of a document. Access to at least one version is absolutely mandatory. |
Example 12.328. <vocabulary>
<head> ......... <version> ......... </version> <vocabulary> <IRI>tag:parkj@textalign.net,2015:TAN-voc:standard</IRI> <name>Keywords for TAN files edited by Jenny Park</name> <location href="TAN-voc/park-projects.TAN-voc.xml" accessed-when="2019-10-08"/> </vocabulary> <source which="kjv 1760"/> ......... </head>
Note | |
---|---|
Taken from lords-prayer.eng.kjv.1760 |
Example 12.329. <vocabulary>
<TAN-T TAN-version="2021" id="tag:parkj@textalign.net,2015:bible:matthew"> <head> ......... <inclusion xml:id="serm-mount"> ......... </inclusion> <vocabulary which="bible eng" accessed-when="2019-10-08"/> <vocabulary> <IRI>tag:parkj@textalign.net,2015:TAN-voc:standard</IRI> <name>Keywords for TAN files edited by Jenny Park</name> <location href="TAN-voc/park-projects.TAN-voc.xml" accessed-when="2019-10-08"/> </vocabulary> <source which="kjv 1760"/> ......... </head> ......... </TAN-T>
Note | |
---|---|
Taken from matt.eng.kjv.1760 |
Example 12.330. <vocabulary>
<head> ......... <source> ......... </source> <vocabulary> <IRI>tag:parkj@textalign.net,2015:TAN-voc:standard</IRI> <name>Vocabulary for TAN files edited by Jenny Park</name> <location href="TAN-voc/park-projects.TAN-voc.xml" accessed-when="2020-01-10"/> </vocabulary> <model> ......... </model> ......... </head>
Note | |
---|---|
Taken from ring-o-roses.eng.1987 |
The element vocabulary-key
contains vocabulary items for the immediate file.
Used by: ~vocabulary-list
Example 12.331. <vocabulary-key>
<head> ......... <adjustments> ......... </adjustments> <vocabulary-key> <algorithm xml:id="xslt2"> ......... </algorithm> <div-type xml:id="ch"> ......... </div-type> <div-type xml:id="par"> ......... </div-type> ......... </vocabulary-key> <file-resp who="kalvesmaki"/> ......... </head>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-logical |
Example 12.332. <vocabulary-key>
<head> ......... <adjustments> ......... </adjustments> <vocabulary-key> <div-type xml:id="p"> ......... </div-type> <div-type xml:id="c"> ......... </div-type> <div-type xml:id="l"> ......... </div-type> ......... </vocabulary-key> <file-resp who="kalvesmaki"/> ......... </head>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-scriptum |
Example 12.333. <vocabulary-key>
<head> ......... <adjustments> ......... </adjustments> <vocabulary-key> <algorithm xml:id="xslt2"> ......... </algorithm> <div-type xml:id="ch"> ......... </div-type> <div-type xml:id="par"> ......... </div-type> ......... </vocabulary-key> <file-resp who="kalvesmaki"/> ......... </head>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949 |
Example 12.334. <vocabulary-key>
<head> ......... <adjustments> ......... </adjustments> <vocabulary-key> <algorithm xml:id="xslt2"> ......... </algorithm> <div-type xml:id="ch"> ......... </div-type> <div-type xml:id="par"> ......... </div-type> ......... </vocabulary-key> <file-resp who="kalvesmaki"/> ......... </head>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.ref-logical |
The element where
identifies a set of conditions that must be met for any actions to be performed or rules to be evaluated.
For a <where>
to be considered true, each attribute must evaluate as true for the target context. That is, multiple attributes are evaluated as intersection operators (and), not union (or).
Sibling <where>
s provide alternative conditions. If the first <where>
evaluates as true, the condition is considered true. If it does not, then the process is applied again to the second <where>
. The sequence of consecutive <where>
s is immaterial, although they will be processed in document order. It is advisable to start with <where>
s that are most likely to make a match.
Used by: ~action-complex-condition
Example 12.335. <where>
<rule>
<where m-has-codes="$"/>
<assert tok-matches="$">Only $ may be tagged as a dollar sign.</assert>
</rule>
Note | |
---|---|
Taken from eng.kalvesmaki.com,2014.2 |
The element work
identifies a creative textual work, understood conceptually, not physically (e.g., Homer's Iliad, not a particular version or copy of it).
The term "work" is only loosely defined in TAN. Any text that has enough unity to be referred to in ordinary conversation as a single entity may be identified as a work. A work may be composed of other works, be a part of other works, or even overlap with other works. E.g., the Lord's Prayer, the Gospel of Luke, the Tetravengelion, the New Testament, and the Bible are all valid works, despite the complex relationship between each of them.
This element takes the IRI + name pattern. For more, see the section called “One Work”
The element work
identifies a creative textual work, understood conceptually, not physically (e.g., Homer's Iliad, not a particular version or copy of it).
The term "work" is only loosely defined in TAN. Any text that has enough unity to be referred to in ordinary conversation as a single entity may be identified as a work. A work may be composed of other works, be a part of other works, or even overlap with other works. E.g., Q, the Lord's Prayer, the Gospel of Luke, the Tetravengelion, the New Testament, and the Bible are all valid works, despite their complex interrelationships of nesting and spanning one another.
This element takes the IRI + name pattern. For more, see the section called “One Work”
Used by: ~voc-element-tan-a
, ~decl-class-1
, ~voc-element-class-1
Example 12.336. <work>
<head> ......... <license licensor="kalvesmaki"> ......... </license> <work> <IRI>http://dbpedia.org/resource/Categories_(Aristotle)</IRI> <name>Aristotle, Categories</name> </work> <source> ......... </source> ......... </head>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-logical |
Example 12.337. <work>
<head> ......... <license licensor="kalvesmaki"> ......... </license> <work> <IRI>http://dbpedia.org/resource/Categories_(Aristotle)</IRI> <name>Aristotle, Categories</name> </work> <source> ......... </source> ......... </head>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-scriptum |
Example 12.338. <work>
<head> ......... <license licensor="kalvesmaki"> ......... </license> <work> <IRI>http://dbpedia.org/resource/Categories_(Aristotle)</IRI> <name>Aristotle, Categories</name> </work> <source> ......... </source> ......... </head>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949 |
Example 12.339. <work>
<head> ......... <reference-system type="logical" wf-ready="true"/> <work> <IRI>http://dbpedia.org/resource/Categories_(Aristotle)</IRI> <name xml:lang="fra">Aristote, Catégories</name> <name xml:lang="eng">Aristotle, Categories</name> </work> <source> ......... </source> ......... </head>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.ref-logical |