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.
Formal Definition
~ed-stamp
?, (~inclusion
| ( {[TAN-class-2 (~adjust-condition
):] {{[TAN-A-lm (~action-condition
):] {{{{[TAN-mor (~action-condition-attributes
):]~action-condition-attributes
}}}} OR {{{{[TAN-class-2 (~action-condition-attributes
):]~action-condition-attributes
}}}} OR {{{{[TAN-core (~action-condition-attributes
):] {empty}}}}}}} OR {{[TAN-core (~action-condition
):] ( {{{{[TAN-mor (~action-condition-attributes
):]~action-condition-attributes
}}}} OR {{{{[TAN-class-2 (~action-condition-attributes
):]~action-condition-attributes
}}}} OR {{{{[TAN-core (~action-condition-attributes
):] {empty}}}}} |<where>
+)}}} OR {[TAN-core (~adjust-condition
):] {empty}}, (<comment>
* & ({empty}, {[TAN-class-1 (~adjust-non-core
):] (<normalization>
* &<replace>
*)} OR {[TAN-class-2 (~adjust-non-core
):]~adjust-non-core
} OR {[TAN-class-3 (~adjust-non-core
):] ({empty} & {empty})} OR {[TAN-core (~adjust-non-core
):] {empty}}))))
Used by: ~adjustment-list
Caution | |
---|---|
Any range in either an |
Example 9.105. <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 9.106. <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 9.107. <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 9.108. <adjustments>
<head> ......... <redivision> ......... </redivision> <adjustments> <normalization which="no hyphens"/> </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.
Formal Definition
~entity-digital-nontan-id
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 an element's |
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 9.109. <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 9.110. <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 9.111. <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.
Formal Definition
~ed-stamp
?, ((@xml:id
|@id
),@idrefs
)
Used by: ~voc-key-core
Caution | |
---|---|
|
Example 9.112. <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 9.113. <alias>
<head> ......... <vocabulary-key> ......... <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"/> <work xml:id="ο.c" which="Explanationes de commentario graeco Olympiodori"/> <alias xml:id="ο.d" idrefs="ο ο.c"/> <work xml:id="η" which="Lemmata de commentario graeco Eliae"/> ......... </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.
Formal Definition
(~inclusion
| (~certainty-stamp
?,@bitext-relation
?,@reuse-type
?,@group
?, (<comment>
* & (<tok>
|<group>
)+)))
Used by: ~body-item
Example 9.114. <align>
<TAN-A-tok TAN-version="2020" 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.
Formal Definition
(~inclusion
| (~certainty-stamp
?,@lexicon
?,@morphology
?,~claimant-attributes
?,@group
?,@tok-pop
?, (<comment>
* & (( {[TAN-A-lm (~default-tok-element
):] (<tok>
|<tok>
)} OR {[TAN-class-2 (~default-tok-element
):]<tok>
} |<group>
)+,<lm>
+))))
Used by: ~body-item
Example 9.115. <ana>
<TAN-A-lm TAN-version="2020" 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 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.
Formal Definition
~entity-digital-tan-no-id
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 an element's |
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. |
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.
Formal Definition
~condition-pattern
Used by: ~element-rule
Example 9.116. <assert>
<TAN-mor TAN-version="2020" id="tag:kalvesmaki.com,2014:tan-r-mor:eng:penn"> ......... <body> <rule m-matches=".+"> <assert m-has-how-many-features="1">Features may not be combined.</assert> </rule> <rule m-has-features="$"> <assert tok-matches="$">Only $ may be tagged as a dollar sign.</assert> </rule> ......... </body> </TAN-mor>
Note | |
---|---|
Taken from eng.kalvesmaki.com,2014.2 |
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.
Formal Definition
~ed-stamp
?, (~multi-source-whole-div-textual-reference
|~single-source-partial-div-textual-reference
|~scriptum-reference
)
The element at-ref
specifies whether a verb uses <at-ref>
(default: disallowed).
Formal Definition
~ed-stamp
?,@status
Used by: ~element-claim
, ~constraints-on-verb
Example 9.117. <at-ref>
<TAN-A TAN-version="2020" 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"> <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>)”
Formal Definition
~entity-nondigital-id
Used by: ~voc-element-non-class-2
Example 9.118. <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 9.119. <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 9.120. <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.
Formal Definition
~ed-stamp
?, {[TAN-A-lm (~body-attributes-non-core
):]~body-attributes-non-core
} OR {[TAN-A-tok (~body-attributes-non-core
):]~body-attributes-non-core
} OR {[TAN-T (~body-attributes-non-core
):]@xml:lang
} OR {[TAN-voc (~body-attributes-non-core
):]~body-attributes-non-core
} OR {[TAN-core (~body-attributes-non-core
):] {empty}}, (<comment>
* & {[TAN-class-1 (~body-content-non-core
):] ({empty} & {{[TAN-T (~body-content-non-class-1
):] {{{[TAN-T (~body-item
):]<div>
}}} OR {{{[TAN-core (~body-item
):] {empty}}}}+}} OR {{[TAN-class-1 (~body-content-non-class-1
):] {empty}}})} OR {[TAN-class-2 (~body-content-non-core
):] (~claimant-attributes
? & {{[TAN-A (~body-content-non-class-2
):]~body-content-non-class-2
}} OR {{[TAN-class-2 (~body-content-non-class-2
):] (<group>
* & {{{[TAN-A-lm (~body-item
):]<ana>
}}} OR {{{[TAN-A-tok (~body-item
):]<align>
}}} OR {{{[TAN-core (~body-item
):] {empty}}}}*)}})} OR {[TAN-class-3 (~body-content-non-core
):] ({empty} & {{[TAN-mor (~body-content-non-class-3
):] (<category>
* &<rule>
*)}} OR {{[TAN-voc (~body-content-non-class-3
):] (<group>
* & {{{[TAN-voc (~body-item
):] (<item>
|<verb>
)}}} OR {{{[TAN-core (~body-item
):] {empty}}}}*)}} OR {{[TAN-class-3 (~body-content-non-class-3
):] {empty}}})} OR {[TAN-core (~body-content-non-core
):] {empty}})
Used by: ~TAN-root
Example 9.121. <body>
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2020"> <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 9.122. <body>
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:model-object-refs" TAN-version="2020"> <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 9.123. <body>
<TAN-T TAN-version="2020" 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 9.124. <body>
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.fra.1844.saint-hilaire:semantic-refs" TAN-version="2020"> <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 sequence 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.
Formal Definition
~ed-stamp
?, (~inclusion
| (@type
, (<comment>
* &<feature>
+)))
Used by: ~TAN-mor-body
Caution | |
---|---|
Features may not be repeated within a given category. |
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.
Formal Definition
~ed-stamp
?,@when
,@flag
?,@who
, text
Example 9.125. <change>
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2020"> <head> ......... <resp who="xslt1" roles="stylesheet1"/> <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> <to-do/> </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.
Formal Definition
((<IRI>
+,~metadata-human-readable
) |@which
),<value>
Used by: ~entity-digital-core-content
The element claim
makes one or more claims (assertions).
Formal Definition
(~inclusion
| (~ed-stamp
?,@xml:id
?,~certainty-claim
?,~claimant-attributes
?,@period
?,@adverb
?,@verb
?,@where
?, ( (@subject
|<subject>
+)? & (@object
| (<object>
|<claim>
+)+)? &<at-ref>
* & (@in-lang
|<in-lang>
+)?)))
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 9.126. <claim>
<TAN-A TAN-version="2020" 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"> <at-ref src="grc" ref="1 a 2"> ......... </at-ref> </claim> <claim subject="δ π" verb="shows" object="cl1a2a"/> <claim subject="comm-omnes" verb="attests"> <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 comment
discusses issues relevant to nearby data. Must credit someone, specified by @who
, and indicate when the comment was made, specified by @when.
.
Formal Definition
@when
,@who
, text
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 9.127. <comment>
<TEI TAN-version="2020" 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 |
Example 9.128. <comment>
<TAN-T id="tag:parkj@textalign.net,2015:patricius.confession.2003.eng" TAN-version="2020"> <head> ......... <vocabulary-key> ......... <div-type xml:id="para" which="paragraph"/> <comment when="2016-01-25-05:00" who="park">The following agents and roles apply only to the preparation of the TAN file, not the original TEI file that serves as the source. See the teiHeader for details on responsibility.</comment> <person xml:id="park"> ......... </person> ......... </vocabulary-key> ......... <to-do> <comment when="2018-08-09-04:00" who="park">File needs to be checked.</comment> </to-do> </head> ......... </TAN-T>
Note | |
---|---|
Taken from patricius.confessio.2003.eng.tan-t |
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.
Formal Definition
~entity-digital-tan-no-id
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. |
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>
.
Formal Definition
~ed-stamp
?, (<comment>
* &<subject>
? &<object>
? &<at-ref>
? &<in-lang>
? &<period>
? &<place>
?)
Used by: ~entity-nondigital-with-constraints-content
Example 9.129. <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> ......... </vocabulary-key> ......... </head>
Note | |
---|---|
Taken from ar.cat.TAN-A.claims |
Example 9.130. <constraints>
<group type="textual_subject"> ......... <group type="one_or_more_at_refs"> <verb group="zero_objects"> ......... <desc>At the <at-ref>, the textual entity referred to by the subject lacks any text. The claim takes no object.</desc> <constraints> <subject status="required" item-type="scriptum"/> <object status="disallowed"/> <at-ref status="required"/> </constraints> </verb> <verb group="one_object"> ......... <desc>At the <at-ref>, the textual entity referred to by the subject has the words contained in the object.</desc> <constraints> <subject status="required" item-type="scriptum work version"/> <object status="required" content-datatype="string"/> <at-ref status="required"/> </constraints> </verb> </group> ......... </group>
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.
Formal Definition
~metadata-human-readable-attributes
, text
Used by: ~metadata-human-readable
Caution | |
---|---|
All text must be normalized (Unicode NFC). |
Example 9.131. <desc>
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2020"> <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 9.132. <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 9.133. <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.
Formal Definition
~ed-stamp
?,@type
,@n
,<div>
*
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.
Formal Definition
~ed-stamp
?, (~inclusion
| (@type
,@n
,@xml:lang
?, (<div>
+ | text)))
Used by: ~element-div
, ~scriptum-reference
, ~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 |
Example 9.134. <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-ref
refers to one or more <div>
s.
<div-ref>
s are expanded against @src
/@work
and @ref.
. That is, a <div-ref>
points to every div of every source cited.
The sequence of consecutive <div-ref>
s is important, because they will be processed in document order. The effect of one <div-ref>
may affect the results of subsequent ones.
Formal Definition
~ed-stamp
?,@ref
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.
Formal Definition
~entity-nondigital-id
Used by: ~voc-element-tan-a
, ~voc-element-class-1
Example 9.135. <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 |
Formal Definition
~doc-attributes
, @[ANY]*, {[catalog.tan (~any-content
):] ( {{[catalog.tan (~any-element
):] <[ANY]>}} OR {{[TAN-core (~any-element
):] <[ANY]>}}* & text)} OR {[TAN-core (~any-content
):] ( {{[catalog.tan (~any-element
):] <[ANY]>}} OR {{[TAN-core (~any-element
):] <[ANY]>}}* & text)}
Used by: <collection>
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.
Formal Definition
~ed-stamp
?, (~inclusion
|@n
)
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 |
Note | |
---|---|
Taken from ar.cat.TAN-A |
Definition 1
Formal Definition
@type
,@code
Definition 2
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.
Formal Definition
~entity-nondigital-id
Used by: ~voc-element-non-class-3
, ~element-category
Caution | |
---|---|
Features may not be repeated within a given category. |
Caution | |
---|---|
Codes for features must be case-indifferently unique within a given category. |
Example 9.137. <feature>
<head> ......... <vocabulary-key ed-when="2015-03-03" ed-who="kalvesmaki"> ......... <alias id="''" idrefs="cl-quo"/> <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> <alias id="--" idrefs="dash"/> <feature xml:id="dash"> <IRI>http://dbpedia.org/resource/Dash</IRI> <name>dash</name> <desc>Examples: --</desc> </feature> <alias id="$" idrefs="x24"/> <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> <alias id="[" idrefs="x5B"/> <feature xml:id="x5B"> <IRI>tag:textalign.net,2015:morphology:option:bracket-opening</IRI> <name>opening bracket</name> <desc>Examples: ( [ {</desc> </feature> <alias id="]" idrefs="x5D"/> ......... </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.
.
Formal Definition
~ed-stamp
?, (~inclusion
|@who
)
Used by: ~resp-list
Example 9.138. <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 9.139. <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 9.140. <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 9.141. <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.
Formal Definition
language
Used by: ~decl-non-class-2
, ~decl-non-class-3
Example 9.142. <for-lang>
<head> ......... <license licensor="kalvesmaki"> ......... </license> <for-lang>eng</for-lang> <source> ......... </source> ......... </head>
Note | |
---|---|
Taken from eng.kalvesmaki.com,2014.2 |
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.
.
Formal Definition
((@val
|@rgx
) |@pos
| ((@val
|@rgx
),@pos
))
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.
.
Formal Definition
@ref
, ((@val
|@rgx
) |@pos
| ((@val
|@rgx
),@pos
))
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 9.143. <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.
Formal Definition
~ed-stamp
?, (~inclusion
| (~group-attributes
, {[TAN-A-lm (~default-tok-element
):] (<tok>
|<tok>
)} OR {[TAN-class-2 (~default-tok-element
):]<tok>
}+))
The element group
collects items that share a common property, defined by the <group-type>
to which it refers.
Formal Definition
~ed-stamp
?, (~inclusion
| (~group-attributes
, (<comment>
* & ( {[TAN-class-1 (~body-group
):] {empty}} OR {[TAN-core (~body-group
):]<group>
} | {[TAN-A-lm (~body-item
):]<ana>
} OR {[TAN-A-tok (~body-item
):]<align>
} OR {[TAN-T (~body-item
):]<div>
} OR {[TAN-voc (~body-item
):] (<item>
|<verb>
)} OR {[TAN-core (~body-item
):] {empty}})+)))
Used by: ~element-ana
, ~element-align
, ~body-group
Caution | |
---|---|
|
Caution | |
---|---|
|
Example 9.144. <group>
<TAN-voc TAN-version="2020" 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> <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.
Formal Definition
~entity-nondigital-id
Used by: ~voc-element-class-2
, ~voc-element-class-3
Example 9.145. <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 9.146. <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>)”
Formal Definition
~ed-stamp
?, (<comment>
* & (~entity-digital-tan-self-content
, ( (<license>
+ &<numerals>
?) & {{[TAN-class-1 (~declaration-non-core
):] ( (<work>
&<version>
? &<token-definition>
* &<n-alias>
?) & {empty})}} OR {{[TAN-class-2 (~declaration-non-core
):] (<token-definition>
* & {{{[TAN-A-lm (~decl-non-class-2
):]~decl-non-class-2
}}} OR {{{[TAN-class-2 (~decl-non-class-2
):] {empty}}}})}} OR {{[TAN-class-3 (~declaration-non-core
):] ({empty} & {{{[TAN-mor (~decl-non-class-3
):]<for-lang>
+}}} OR {{{[TAN-class-3 (~decl-non-class-3
):] {empty}}}})}} OR {{[TAN-core (~declaration-non-core
):] {empty}}}), ( (<inclusion>
* &<vocabulary>
* & {{{[TAN-A-lm (~source-list
):]<source>
*}}} OR {{{[TAN-A-tok (~source-list
):]~source-list
}}} OR {{{[TAN-A (~source-list
):]<source>
*}}} OR {{{[TAN-voc (~source-list
):] {empty}}}} OR {{{[TAN-class-3 (~source-list
):]<source>
*}}} OR {{{[TAN-core (~source-list
):]<source>
}}} &<see-also>
* &<predecessor>
* &<successor>
* &<companion-version>
*) & {{[TAN-class-1 (~networked-files-non-core
):] (<redivision>
* &<model>
? &<annotation>
*)}} OR {{[TAN-core (~networked-files-non-core
):] {empty}}}),<adjustments>
*,~vocabulary-list
, (<resp>
+ &<file-resp>
),<change>
++,<to-do>
))
Used by: ~TAN-root
Example 9.147. <head>
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2020"> <head> <name>Categories, Aristotle, English translation by E. M. Edghill</name> <master-location href="https://raw.githubusercontent.com/textalign/TAN-2020/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 9.148. <head>
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:model-object-refs" TAN-version="2020"> <head> <name>Categories, Aristotle, English translation by E. M. Edghill</name> <master-location href="https://raw.githubusercontent.com/textalign/TAN-2020/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 9.149. <head>
<TAN-T TAN-version="2020" 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-2020/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 9.150. <head>
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.fra.1844.saint-hilaire:semantic-refs" TAN-version="2020"> <head> <name>Categories, Aristotle, French translation by J. Barthélemy Saint-Hilaire</name> <master-location href="https://raw.githubusercontent.com/textalign/TAN-2020/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.
Formal Definition
~ed-stamp
?, language
The element in-lang
specifies whether a verb uses <in-lang>
(default: disallowed).
Formal Definition
~ed-stamp
?,@status
Used by: ~element-claim
, ~in-lang
, ~constraints-on-verb
Example 9.151. <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”
Formal Definition
~ed-stamp
?,@xml:id
, (<comment>
* & (@href
| ((<IRI>
+,~metadata-human-readable
,<checksum>
*,<location>
+) | (@which
&@accessed-when
))))
Used by: ~element-ana
, ~element-align
, ~element-claim
, ~element-category
, ~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 an element's |
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 9.152. <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 9.153. <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 9.154. <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)”.
Formal Definition
~ed-stamp
?, anyURI
(pattern [a-zA-Z][\-.+a-zA-Z0-9]+:\S+)
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, https://tools.ietf.org/html/rfc8141, and https://www.iana.org/assignments/urn-namespaces/urn-namespaces.xhtml |
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 9.155. <IRI>
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2020"> <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.
Formal Definition
~ed-stamp
?, (~inclusion
| (@affects-element
?,@group
?, (<comment>
* & ( (@href
| ((<IRI>
+,~metadata-human-readable
,<checksum>
*,<location>
+) | (@which
&@accessed-when
))) | ((<IRI>
+,~metadata-human-readable
) |@which
) | ((<IRI>
+,~metadata-human-readable
,<constraints>
?) |@which
) |~entity-tok-def
))))
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 9.156. <item>
<TAN-voc TAN-version="2020" id="tag:parkj@textalign.net,2015:TAN-key:ar.cat"> ......... <body affects-element="work"> <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> <IRI>tag:parkj@textalign.net,2015:work:ammonius:on-aristotles-categories:discussions</IRI> <name xml:lang="lat">Explanationes de commentario graeco Ammonii</name> <name xml:lang="eng">Discussions in Ammonius's commentary on Aristotle's Categories</name> </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.
Formal Definition
@lexicon
?,@def-ref
?,~certainty-stamp
?, text
Used by: ~element-lm
Example 9.157. <l>
<TAN-A-lm TAN-version="2020" 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> ......... <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.
Formal Definition
(~entity-digital-tan-id
|~entity-nondigital-id
)
Used by: ~voc-element-non-class-2
Example 9.158. <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 9.159. <lexicon>
<vocabulary-key> ......... <morphology xml:id="penn" ed-when="2015-08-20-04:00" ed-who="park"> ......... </morphology> <lexicon xml:id="english"> <IRI>tag:parkj@textalign.net,2015:lexicon:eng:test</IRI> <name>An English dictionary</name> </lexicon> <person xml:id="park"> ......... </person> ......... </vocabulary-key>
Note | |
---|---|
Taken from ring-o-roses.eng.1881.lm |
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>)”
Formal Definition
~ed-stamp
?, (~inclusion
| (@licensor
, (<comment>
* & ((<IRI>
+,~metadata-human-readable
) |@which
))))
Used by: ~declaration-core
Example 9.160. <license>
<head> ......... <master-location href="https://raw.githubusercontent.com/textalign/TAN-2020/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 9.161. <license>
<head> ......... <master-location href="https://raw.githubusercontent.com/textalign/TAN-2020/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 9.162. <license>
<head> ......... <master-location href="https://raw.githubusercontent.com/textalign/TAN-2020/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 9.163. <license>
<head> ......... <master-location href="https://raw.githubusercontent.com/textalign/TAN-2020/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> <work> ......... </work> ......... </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.
Formal Definition
~certainty-stamp
?,@lexicon
?,@morphology
?, (<comment>
* & ((<l>
+,<m>
*) | (<l>
*,<m>
+)))
Used by: ~element-ana
Example 9.164. <lm>
<TAN-A-lm TAN-version="2020" 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 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.
Formal Definition
~ed-stamp
?,@accessed-when
,@href
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 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 an element's |
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 9.165. <location>
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2020"> <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.
Formal Definition
~certainty-stamp
?,@morphology
?, string (pattern [^\+\s]+(\s+[^\+\s]+)*)
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.
Formal Definition
~ed-stamp
?,@href
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 | |
---|---|
No |
Important | |
---|---|
Files should match the version kept at |
Example 9.166. <master-location>
<head>
<name>Categories, Aristotle, English translation by E. M. Edghill</name>
<master-location href="https://raw.githubusercontent.com/textalign/TAN-2020/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 9.167. <master-location>
<head>
<name>Categories, Aristotle, English translation by E. M. Edghill</name>
<master-location href="https://raw.githubusercontent.com/textalign/TAN-2020/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 9.168. <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-2020/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 9.169. <master-location>
<head>
<name>Categories, Aristotle, French translation by J. Barthélemy Saint-Hilaire</name>
<master-location href="https://raw.githubusercontent.com/textalign/TAN-2020/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.
Formal Definition
~entity-nondigital-id
Used by: ~voc-element-tan-a
Example 9.170. <modal>
<vocabulary-key>
.........
<verb xml:id="attests">
.........
</verb>
<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.
Formal Definition
~entity-digital-tan-no-id
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 an element's |
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 | |
---|---|
Class 1 files must share the same work as any model, redivision, or companion version. |
Example 9.171. <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 9.172. <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 9.173. <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 9.174. <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 href="ring-o-roses.eng.1957.xml" accessed-when="2017-11-21T08:28:27.168-05:00"/> </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
Formal Definition
~entity-digital-tan-id
Used by: ~voc-element-non-class-2
Caution | |
---|---|
|
Example 9.175. <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="2017-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 9.176. <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.
Formal Definition
@div-type
Used by: ~decl-class-1
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.
Formal Definition
~metadata-human-readable-attributes
, text
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 9.177. <name>
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2020"> <head> <name>Categories, Aristotle, English translation by E. M. Edghill</name> <master-location href="https://raw.githubusercontent.com/textalign/TAN-2020/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”
Formal Definition
~entity-nondigital-no-id
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 |
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.
Formal Definition
@priority
Used by: ~declaration-core
Example 9.182. <numerals>
<head>
.........
<version>
.........
</version>
<numerals priority="letters"/>
<source>
.........
</source>
.........
</head>
Note | |
---|---|
Taken from ring-o-roses.deu.1897 |
Example 9.183. <numerals>
<head>
.........
<license licensor="park">
.........
</license>
<numerals priority="letters"/>
<source xml:id="grc">
.........
</source>
.........
</head>
Note | |
---|---|
Taken from ar.cat.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.
Formal Definition
~ed-stamp
?, (~nontextual-reference
| (~multi-source-whole-div-textual-reference
|~single-source-partial-div-textual-reference
|~scriptum-reference
))
The element object
specifies expectations on a verb's use of object. By default, an object is required.
Formal Definition
~ed-stamp
?,@status
, (@item-type
|~constraint-content
)?
Used by: ~element-claim
, ~complex-object
, ~constraints-on-verb
Caution | |
---|---|
Claims involving verbs whose constrained content requires specification of units must use |
Caution | |
---|---|
|
Example 9.184. <object>
<TAN-A TAN-version="2020" 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> ......... </vocabulary-key> ......... </head> <body claimant="park" claim-period="per2010s"> ......... <claim subject="comm-omnes" verb="attests"> <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.
Formal Definition
~entity-nondigital-id
Used by: ~voc-element-agent
The element passage
specifies a textual passage within a single <div>
that should be reassigned to another <div>
.
Formal Definition
~ed-stamp
?,@ref
,~text-passage-selector-no-ref
+
Used by: ~adj-element-reassign
Definition 1
The element period
as a constraint specifies expectations on a verb's use of period. By default, a period is optional.
Formal Definition
~ed-stamp
?,@status
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.
Formal Definition
(~entity-nondigital-id
| (~ed-stamp
?, (~inclusion
| (@xml:id
,@from
,@to
))))
Used by: ~constraints-on-verb
, ~voc-key-core
Example 9.185. <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-antiquty"> <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> </vocabulary-key> ......... </head>
Note | |
---|---|
Taken from ar.cat.TAN-A.claims |
The element person
contains an IRI + name pattern identifying an individual human being.
Formal Definition
~entity-nondigital-id
Used by: ~voc-element-agent
Example 9.186. <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 9.187. <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 9.188. <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 9.189. <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
Formal Definition
~entity-nondigital-id
The element place
specifies expectations on a verb's use of place. By default, an place is optional.
Formal Definition
~ed-stamp
?,@status
Used by: ~voc-element-tan-a
, ~constraints-on-verb
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.
Formal Definition
~entity-digital-tan-no-id
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 an element's |
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. |
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.
Formal Definition
~ed-stamp
?, (~inclusion
| (<passage>
+,<to>
))
Used by: ~adjust-class-2
Caution | |
---|---|
Any range in either an |
Caution | |
---|---|
No token may be adjusted by more than one |
Caution | |
---|---|
A |
Important | |
---|---|
If a |
Caution | |
---|---|
In 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.
Formal Definition
~entity-digital-tan-no-id
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 an element's |
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 9.190. <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 9.191. <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 9.192. <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 9.193. <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 relationship
specifies a relationship that one document has to another.
Formal Definition
~entity-nondigital-id
Used by: ~voc-key-core
Example 9.194. <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 9.195. <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.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>
.
Formal Definition
~ed-stamp
?, (~inclusion
| ( ((@n
,@new
) | (@ref
,@new
)) |~complex-rename
))
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 | |
---|---|
|
Important | |
---|---|
If a |
Example 9.196. <rename>
<adjustments src="ger">
<skip div-type="Gedicht"/>
<rename n="e" by="-1"/>
</adjustments>
Note | |
---|---|
Taken from ringoroses.div.1 |
Example 9.197. <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.
Formal Definition
~ed-stamp
?, (~inclusion
| (<comment>
* & (@pattern
,@replacement
,@flags
?)))
Used by: ~adjust-repl
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.
Formal Definition
~condition-pattern
Used by: ~element-rule
Example 9.198. <report>
<rule m-has-features="'' . ; :"> <report tok-matches="\w">Nothing marked as punctuation should have word characters.</report> </rule>
Note | |
---|---|
Taken from eng.kalvesmaki.com,2014.2 |
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.
Formal Definition
~ed-stamp
?, (~inclusion
| (@who
,@roles
,@period
?))
Used by: ~resp-list
Example 9.199. <resp>
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2020"> <head> ......... <file-resp who="kalvesmaki"/> <resp who="xslt2" roles="stylesheet1"/> <resp roles="editor" who="kalvesmaki"/> <resp who="xslt1" roles="stylesheet1"/> <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> ......... </head> ......... </TAN-T>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-logical |
Example 9.200. <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>)”
Formal Definition
~entity-nondigital-id
Used by: ~voc-element-non-class-2
Example 9.201. <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 9.202. <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 9.203. <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.
Formal Definition
~entity-nondigital-id
Used by: ~voc-key-core
Example 9.204. <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 9.205. <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"/> </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.
Formal Definition
~ed-stamp
?, (~inclusion
| ( ( {{{[TAN-mor (~action-condition-attributes
):]~action-condition-attributes
}}} OR {{{[TAN-class-2 (~action-condition-attributes
):]~action-condition-attributes
}}} OR {{{[TAN-core (~action-condition-attributes
):] {empty}}}} |<where>
+), (<assert>
|<report>
)+))
Used by: ~TAN-mor-body
Example 9.206. <rule>
<TAN-mor TAN-version="2020" id="tag:kalvesmaki.com,2014:tan-r-mor:eng:penn"> ......... <body> <rule m-matches=".+"> <assert m-has-how-many-features="1">Features may not be combined.</assert> </rule> <rule m-has-features="$"> <assert tok-matches="$">Only $ may be tagged as a dollar sign.</assert> </rule> <rule m-has-features="'' . ; :"> <report tok-matches="\w">Nothing marked as punctuation should have word characters.</report> </rule> </body> </TAN-mor>
Note | |
---|---|
Taken from eng.kalvesmaki.com,2014.2 |
The element scriptum
contains an IRI + name pattern identifying a text-bearing object.
Formal Definition
~entity-nondigital-id
Used by: ~voc-element-tan-a
Example 9.207. <scriptum>
<head> ......... <vocabulary-key> ......... <work xml:id="Γ"> ......... </work> <scriptum xml:id="n"> <IRI>tag:parkj@textalign.net,2015:scriptum:ita:milan:ambrosianus:L-93</IRI> <name>Ambrosianus L 93</name> <desc>saec. ix</desc> </scriptum> <scriptum xml:id="B"> <IRI>tag:parkj@textalign.net,2015:scriptum:ita:venezia:marcianus:201</IRI> <name>Marcianus 201</name> <desc>saec. x</desc> </scriptum> <work xml:id="π" which="Commentarium graecum Porphyrii"/> ......... </vocabulary-key> ......... </head>
Note | |
---|---|
Taken from ar.cat.TAN-A.claims |
Example 9.208. <scriptum>
<vocabulary-key> ......... <verb xml:id="resembles"> ......... </verb> <scriptum xml:id="böhme"> <IRI>http://www.worldcat.org/oclc/4574384</IRI> <name>Franz Magnus Böhme, Deutsches Kinderlied und Kinderspiel: Volksüberlieferungen aus allen Landen deutscher Zunge, gesammelt, geordnet und mit Angabe der Quellen. Leipzig, 1897.</name> </scriptum> <alias id="ring" idrefs="ger eng-us"/> </vocabulary-key>
Note | |
---|---|
Taken from ringoroses.div.1 |
The element see-also
identifies a file that is related to the current one.
The sequence of consecutive <see-also>
s is immaterial.
Formal Definition
~ed-stamp
?, (~inclusion
| (@relationship
, (<comment>
* & ( ((<IRI>
+,~metadata-human-readable
,<checksum>
*,<location>
+) | (@which
&@accessed-when
)) | (@href
| ((<IRI>
+,~metadata-human-readable
,<checksum>
*,<location>
+) | (@which
&@accessed-when
)))))))
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 an element's |
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 9.209. <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 9.210. <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.
Formal Definition
~ed-stamp
?, (~inclusion
| (@shallow
?, (@ref
| (@n
|@div-type
| (@n
&@div-type
)))))
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 9.211. <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 9.213. <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.
Formal Definition
{[TAN-A-lm (~source-content
):]~entity-digital-nontan-no-id
} OR {[TAN-class-1 (~source-content
):] (~entity-nondigital-no-id
|~entity-digital-nontan-no-id
)} OR {[TAN-class-2 (~source-content
):]~entity-digital-tan-id
} OR {[TAN-class-3 (~source-content
):] (~entity-nondigital-no-id
|~entity-digital-nontan-no-id
|~entity-digital-tan-no-id
)} OR {[TAN-core (~source-content
):] {empty}}
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 an element's |
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 9.214. <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 9.215. <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 9.216. <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 9.217. <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.
Formal Definition
~ed-stamp
?, (~nontextual-reference
| (~multi-source-whole-div-textual-reference
|~single-source-partial-div-textual-reference
|~scriptum-reference
))
The element subject
specifies expectations on a verb's use of subject. By default, a subject is required.
Formal Definition
~ed-stamp
?,@status
, (@item-type
|~constraint-content
)?
Used by: ~element-claim
, ~subject
, ~constraints-on-verb
Caution | |
---|---|
Claims involving verbs whose constrained content requires specification of units must use |
Caution | |
---|---|
|
Example 9.218. <subject>
<TAN-A TAN-version="2020" 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> ......... </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 |
Example 9.219. <subject>
<claim verb="concerns" object="predication">
<subject src="grc" ref="1 1"/>
</claim>
Note | |
---|---|
Taken from ar.cat.TAN-A |
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.
Formal Definition
~entity-digital-tan-no-id
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 an element's |
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. |
The element tail
permits any arbitrary content. This element is suitable as a placeholder for temporary data, especially to improve the efficiency of applications.
Formal Definition
{[catalog.tan (~any-content
):] ( {{[catalog.tan (~any-element
):] <[ANY]>}} OR {{[TAN-core (~any-element
):] <[ANY]>}}* & text)} OR {[TAN-core (~any-content
):] ( {{[catalog.tan (~any-element
):] <[ANY]>}} OR {{[TAN-core (~any-element
):] <[ANY]>}}* & text)}
Used by: ~TAN-root
The element TAN-A
specifies that the file is a general TAN alignment file. Root element.
Formal Definition
~TAN-root
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 http://textalign.net for details.” |
Important | |
---|---|
Users should be warned about TAN files whose last change was made by an algorithm. |
Example 9.220. <TAN-A>
<TAN-A TAN-version="2020" 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 9.221. <TAN-A>
<TAN-A TAN-version="2020" 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 9.222. <TAN-A>
<TAN-A TAN-version="2020" 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.
Formal Definition
~TAN-root
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 http://textalign.net for details.” |
Important | |
---|---|
Users should be warned about TAN files whose last change was made by an algorithm. |
Example 9.223. <TAN-A-lm>
<TAN-A-lm TAN-version="2020" 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 9.224. <TAN-A-lm>
<TAN-A-lm TAN-version="2020" 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.
Formal Definition
~TAN-root
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 http://textalign.net for details.” |
Important | |
---|---|
Users should be warned about TAN files whose last change was made by an algorithm. |
Example 9.225. <TAN-A-tok>
<TAN-A-tok TAN-version="2020" 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 9.226. <TAN-A-tok>
<TAN-A-tok TAN-version="2020" 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 9.227. <TAN-A-tok>
<TAN-A-tok TAN-version="2020" 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.
Formal Definition
~TAN-root
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 http://textalign.net for details.” |
Important | |
---|---|
Users should be warned about TAN files whose last change was made by an algorithm. |
Example 9.228. <TAN-mor>
<TAN-mor TAN-version="2020" id="tag:kalvesmaki.com,2014:tan-r-mor:eng:penn"> <head> ......... </head> <body> ......... </body> </TAN-mor>
Note | |
---|---|
Taken from eng.kalvesmaki.com,2014.2 |
The element TAN-T
specifies that the TAN file contains a transcription. Root element.
Formal Definition
~TAN-root
Formal Definition
{empty}
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 http://textalign.net for details.” |
Important | |
---|---|
Users should be warned about TAN files whose last change was made by an algorithm. |
Example 9.229. <TAN-T>
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2020"> <head> ......... </head> <body xml:lang="eng"> ......... </body> </TAN-T>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-logical |
Example 9.230. <TAN-T>
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:model-object-refs" TAN-version="2020"> <head> ......... </head> <body xml:lang="eng"> ......... </body> </TAN-T>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-scriptum |
Example 9.231. <TAN-T>
<TAN-T TAN-version="2020" 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 9.232. <TAN-T>
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.fra.1844.saint-hilaire:semantic-refs" TAN-version="2020"> <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.
Formal Definition
~TAN-root
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 http://textalign.net for details.” |
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 9.233. <TAN-voc>
<TAN-voc TAN-version="2020" 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 9.234. <TAN-voc>
<TAN-voc TAN-version="2020" id="tag:parkj@textalign.net,2015:TAN-voc:standard"> <head> ......... </head> <body> ......... </body> </TAN-voc>
Note | |
---|---|
Taken from park-projects.TAN-voc |
Example 9.235. <TAN-voc>
<TAN-voc TAN-version="2020" 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 9.236. <TAN-voc>
<TAN-voc TAN-version="2020" 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.
.
Formal Definition
((@val
|@rgx
) |@pos
| ((@val
|@rgx
),@pos
))
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.
.
Formal Definition
@ref
, ((@val
|@rgx
) |@pos
| ((@val
|@rgx
),@pos
))
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 9.237. <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.
Formal Definition
@ref
Used by: ~adj-element-reassign
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>
.
Formal Definition
~ed-stamp
?, (~inclusion
|<comment>
*)
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 9.238. <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 9.239. <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 9.240. <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 9.241. <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>
.
Formal Definition
~certainty-stamp
?, (@val
|@rgx
),@chars
?
Definition 1
The element tok
points to one or more tokens in the context source or reference.
Formal Definition
((@val
|@rgx
) |@pos
| ((@val
|@rgx
),@pos
)),@chars
?
Definition 2
The element tok
points to one or more tokens in the context source.
Formal Definition
@ref
, ((@val
|@rgx
) |@pos
| ((@val
|@rgx
),@pos
)),@chars
?
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>
.
Formal Definition
~ed-stamp
?, {[TAN-A-lm (~tok-sources-ref-opt
):] {empty}} OR {[TAN-class-2 (~tok-sources-ref-opt
):] {{[TAN-A-lm (~ptr-attr-src-many
):] {empty}}} OR {{[TAN-class-2 (~ptr-attr-src-many
):]@src
}}},@ref
, ((@val
|@rgx
) |@pos
| ((@val
|@rgx
),@pos
)), {[TAN-A (~tok-cert-opt
):] {empty}} OR {[TAN-class-2 (~tok-cert-opt
):]~certainty-claim
?},@chars
?
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 9.242. <tok>
<TAN-A TAN-version="2020" 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"> <at-ref src="grc" ref="1 a 2"> <tok pos="3-4"/> </at-ref> </claim> ......... <claim subject="comm-omnes" verb="attests"> <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.
Formal Definition
text
Used by: ~decl-non-class-2
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.
Formal Definition
text
Used by: ~decl-non-class-2
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>)”
Formal Definition
~ed-stamp
?, (~inclusion
| ( {[TAN-A-lm (~token-definition-attributes
):] {empty}} OR {[TAN-class-2 (~token-definition-attributes
):] {{[TAN-A-lm (~ptr-attr-src-many
):] {empty}}} OR {{[TAN-class-2 (~ptr-attr-src-many
):]@src
}}} OR {[TAN-core (~token-definition-attributes
):] {empty}}, (@which
| (@pattern
,@flags
?))))
Used by: ~decl-class-1
, ~decl-class-2
, ~entity-tok-def
Caution | |
---|---|
No source may be given more than one token definition. |
Example 9.243. <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 9.244. <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 9.245. <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 |
Example 9.246. <token-definition>
<head>
.........
<license licensor="park">
.........
</license>
<token-definition which="letters and punctuation"/>
<source>
.........
</source>
.........
</head>
Note | |
---|---|
Taken from ring-o-roses.eng.1881.lm |
The element topic
contains an IRI + name pattern identifying a topic.
Formal Definition
~entity-nondigital-id
Used by: ~voc-element-tan-a
Example 9.247. <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.
Formal Definition
~entity-nondigital-id
Used by: ~voc-element-tan-a
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.
Formal Definition
{[TAN-voc (~extra-verb-attrs
):]@group
} OR {[TAN-core (~extra-verb-attrs
):] {empty}}?,~entity-nondigital-constrained
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 9.248. <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> <modal which="possibly" xml:id="perhaps"/> ......... </vocabulary-key> ......... </head>
Note | |
---|---|
Taken from ar.cat.TAN-A.claims |
Example 9.249. <verb>
<vocabulary-key>
.........
<role xml:id="stylesheet1" which="stylesheet"/>
<verb which="is about" xml:id="concerns"/>
<topic xml:id="predication">
.........
</topic>
</vocabulary-key>
Note | |
---|---|
Taken from ar.cat.TAN-A |
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”
Formal Definition
~entity-nondigital-id
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”
Formal Definition
~entity-nondigital-no-id
Used by: ~voc-element-tan-a
, ~decl-class-1
Example 9.250. <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 9.251. <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 |
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.
Formal Definition
~entity-digital-tan-no-id
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 an element's |
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 9.252. <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 9.253. <vocabulary>
<TAN-T TAN-version="2020" 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 9.254. <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.
Formal Definition
~ed-stamp
?, (<comment>
* & ( (<person>
|<organization>
|<algorithm>
)* &<role>
* &<period>
* &<alias>
* &<relationship>
*) & {[TAN-class-1 (~voc-key-non-core
):] (<div-type>
* & {empty})} OR {[TAN-class-2 (~voc-key-non-core
):] (<group-type>
* & {{[TAN-A-lm (~voc-element-non-class-2
):] (<lexicon>
+ &<morphology>
+)}} OR {{[TAN-A-tok (~voc-element-non-class-2
):] (<bitext-relation>
+ &<reuse-type>
+)}} OR {{[TAN-A (~voc-element-non-class-2
):] (<work>
* &<place>
* &<unit>
* &<div-type>
* &<modal>
* &<version>
* &<scriptum>
* &<topic>
* &<verb>
*)}} OR {{[TAN-class-2 (~voc-element-non-class-2
):] {empty}}})} OR {[TAN-class-3 (~voc-key-non-core
):] (<group-type>
* & {{[TAN-mor (~voc-element-non-class-3
):]<feature>
*}} OR {{[TAN-class-3 (~voc-element-non-class-3
):] {empty}}})} OR {[TAN-core (~voc-key-non-core
):] {empty}})
Used by: ~vocabulary-list
Example 9.255. <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 9.256. <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 9.257. <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 9.258. <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 condition that permits the following adjustment actions to be performed.
The condition must be true for each attribute, for at least one value in that attribute.
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 easily processed.
Formal Definition
~ed-stamp
?, {[TAN-mor (~action-condition-attributes
):]~action-condition-attributes
} OR {[TAN-class-2 (~action-condition-attributes
):]~action-condition-attributes
} OR {[TAN-core (~action-condition-attributes
):] {empty}}
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”
Formal Definition
~entity-nondigital-id
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”
Formal Definition
~entity-nondigital-no-id
Used by: ~voc-element-tan-a
, ~decl-class-1
Example 9.259. <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 9.260. <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 9.261. <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 9.262. <work>
<head> ......... <license licensor="kalvesmaki"> ......... </license> <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 |