Table of Contents
@accessed-when
@adverb
@affects-attribute
@affects-element
@bitext-relation
@by
@cert
@cert2
@chars
@claim-period
@claim-when
@claimant
@content-datatype
@content-lexical-constraint
@def-ref
@div-type
@ed-when
@ed-who
@exceptions
@feature
@flag
@flags
@from
@group
@href
@id
@idrefs
@in-lang
@include
@item-type
@lexicon
@licensor
@m-has-codes
@m-has-how-many-codes
@m-matches
@metadata-resolved
@morphology
@n
@new
@object
@pattern
@period
@pos
@priority
@ref
@ref-alias
@relationship
@replacement
@reuse-type
@rgx
@roles
@root
@scriptum
@shallow
@src
@stable
@status
@subject
@TAN-version
@to
@tok-matches
@tok-pop
@type
@units
@val
@verb
@wf-ready
@when
@where
@which
@who
@work
@xml:id
@xml:lang
<adjustments>
<algorithm>
<alias>
<align>
<ana>
<annotation>
<assert>
<at-ref>
<bitext-relation>
<body>
<category>
<change>
<checksum>
<claim>
<code>
<collection>
<comment>
<companion-version>
<constraints>
<desc>
<div>
<div-type>
<doc>
<equate>
<feature>
<file-resp>
<for-lang>
<from-tok>
<group>
<group-type>
<head>
<in-lang>
<inclusion>
<IRI>
<item>
<l>
<lexicon>
<license>
<lm>
<location>
<m>
<master-location>
<modal>
<model>
<morphology>
<n-alias>
<name>
<normalization>
<numerals>
<object>
<organization>
<passage>
<period>
<person>
<place>
<predecessor>
<reassign>
<redivision>
<reference-system>
<relationship>
<rename>
<replace>
<report>
<resp>
<reuse-type>
<role>
<rule>
<scriptum>
<see-also>
<skip>
<source>
<subject>
<successor>
<tail>
<TAN-A>
<TAN-A-lm>
<TAN-A-tok>
<TAN-mor>
<TAN-T>
<TAN-voc>
<through-tok>
<to>
<to-do>
<tok>
<tok-is>
<tok-starts-with>
<token-definition>
<topic>
<unit>
<val>
<value>
<verb>
<version>
<vocabulary>
<vocabulary-key>
<where>
<work>
~action-complex-condition
~action-condition
~action-condition-attributes
~action-simple-condition
~adj-element-equate
~adj-element-reassign
~adj-element-rename
~adj-element-skip
~adjust-class-2
~adjust-class-3
~adjust-condition
~adjust-core
~adjust-non-class-2
~adjust-non-class-3
~adjust-non-core
~adjust-repl
~adjustment-list
~any-attribute
~any-content
~any-element
~attr-accessed-when
~attr-by
~attr-cert
~attr-cert2
~attr-chars
~attr-claim-period
~attr-claim-when
~attr-content-datatype
~attr-content-lexical-constraint
~attr-def-ref
~attr-ed-when
~attr-flags-for-errors
~attr-flags-for-functions
~attr-href
~attr-id-alias
~attr-id-tan
~attr-id-xml
~attr-in-lang
~attr-item-type
~attr-lang-xml
~attr-n
~attr-new-name
~attr-new-ref
~attr-pattern
~attr-pos-many
~attr-pos-one
~attr-priority
~attr-ref-alias
~attr-ref-many
~attr-ref-one
~attr-replacement
~attr-rgx
~attr-scriptum
~attr-shallow
~attr-status
~attr-TAN-ver
~attr-tok-pop
~attr-type-ref-system
~attr-val
~attr-wf-ready
~attr-when
~attribute-scope
~body-attributes-non-core
~body-content-class-1
~body-content-class-2
~body-content-class-3
~body-content-core
~body-content-non-class-1
~body-content-non-class-2
~body-content-non-class-3
~body-content-non-core
~body-group
~body-item
~certainty-claim
~certainty-stamp
~claimant-attributes
~complex-object
~complex-rename
~cond-attr-m-has-codes
~cond-attr-m-has-how-many-codes
~cond-attr-m-matches
~cond-attr-tok-matches
~condition-pattern
~constraint-content
~constraint-item-type
~constraints-on-verb
~data-certainty
~data-div-item-ref
~data-div-range-ref
~data-IRI
~data-picker-item
~data-picker-sequence
~data-tag-uri
~decl-class-1
~decl-class-2
~decl-class-3
~decl-non-class-1
~decl-non-class-2
~decl-non-class-3
~declaration-core
~declaration-list
~declaration-non-core
~default-tok-element
~doc-attributes
~ed-stamp
~element-adjustments
~element-align
~element-ana
~element-assert
~element-at-ref
~element-at-ref-constraint
~element-body
~element-category
~element-change
~element-checksum
~element-claim
~element-code
~element-comment
~element-desc
~element-div
~element-file-resp
~element-for-lang
~element-from-tok-no-ref
~element-from-tok-with-ref
~element-group
~element-group-for-tok
~element-head
~element-in-lang
~element-in-lang-constraint
~element-IRI
~element-item
~element-l
~element-license
~element-lm
~element-location
~element-m
~element-master-location
~element-n-alias
~element-name
~element-normalization
~element-numerals
~element-object
~element-object-constraint
~element-passage
~element-period-constraint
~element-place-constraint
~element-reference-system
~element-replace
~element-report
~element-resp
~element-rule
~element-scope
~element-subject
~element-subject-constraint
~element-tail
~element-through-tok-no-ref
~element-through-tok-with-ref
~element-to
~element-to-do
~element-tok-abstract
~element-tok-for-claim-no-ref
~element-tok-for-claim-with-ref
~element-tok-is
~element-tok-standard
~element-tok-starts-with
~element-token-definition
~element-val
~element-version
~element-vocabulary-key
~element-where
~element-work
~entity-digital-core-content
~entity-digital-nontan-id
~entity-digital-nontan-no-id
~entity-digital-tan-id
~entity-digital-tan-no-id
~entity-digital-tan-other-content
~entity-digital-tan-self-content
~entity-nondigital-constrained
~entity-nondigital-content
~entity-nondigital-id
~entity-nondigital-no-id
~entity-nondigital-with-constraints-content
~entity-tok-def
~extra-verb-attrs
~features-categorized
~features-uncategorized
~group-attributes
~group-attributes-core
~group-attributes-non-core
~in-lang
~inclusion
~link-element-annotation
~link-element-companion-version
~link-element-inclusion
~link-element-model
~link-element-predecessor
~link-element-redivision
~link-element-see-also
~link-element-source
~link-element-successor
~link-element-vocabulary
~metadata-human-readable
~metadata-human-readable-attributes
~multi-div-partial-textual-reference
~multi-source-whole-div-textual-reference
~networked-files
~networked-files-core
~networked-files-non-core
~nondoc-attributes
~nontextual-reference
~object
~ptr-attr-bitext-relation
~ptr-attr-claimant
~ptr-attr-div-type
~ptr-attr-ed-who
~ptr-attr-feature
~ptr-attr-group
~ptr-attr-idrefs
~ptr-attr-include
~ptr-attr-lexicon
~ptr-attr-licensor
~ptr-attr-modal
~ptr-attr-morphology
~ptr-attr-object
~ptr-attr-period
~ptr-attr-place
~ptr-attr-relationship
~ptr-attr-reuse-type
~ptr-attr-role
~ptr-attr-scriptum
~ptr-attr-src-many
~ptr-attr-src-one
~ptr-attr-subject
~ptr-attr-type
~ptr-attr-units
~ptr-attr-verb
~ptr-attr-which
~ptr-attr-who
~ptr-attr-work
~resp-list
~scriptum-filter
~scriptum-reference
~simple-rename
~single-div-partial-textual-reference
~single-source-partial-div-textual-reference
~source-content
~source-list
~subject
~TAN-mor-body
~TAN-root
~text-passage-selector-no-ref
~text-passage-selector-with-ref
~textual-reference
~tok-cert-opt
~tok-selector-attributes-many
~tok-selector-attributes-one
~tok-sources-ref-opt
~token-definition-attributes
~voc-element-agent
~voc-element-alg
~voc-element-alias
~voc-element-brel
~voc-element-class-1
~voc-element-class-2
~voc-element-class-3
~voc-element-div-type
~voc-element-feature
~voc-element-group-type
~voc-element-lexicon
~voc-element-modal
~voc-element-morphology
~voc-element-non-class-1
~voc-element-non-class-2
~voc-element-non-class-3
~voc-element-org
~voc-element-period
~voc-element-person
~voc-element-place
~voc-element-relationship
~voc-element-reus
~voc-element-role
~voc-element-scri
~voc-element-tan-a
~voc-element-topic
~voc-element-unit
~voc-element-verb
~voc-element-vers
~voc-element-work
~voc-key-core
~voc-key-non-core
~vocabulary-list
~work-version-reference
Each entry below begins with a description of the attribute, element, or pattern, followed by a formal definition and the name of the master file(s) that should be consulted. Dependencies are listed, along with relevant rules that would trigger errors, and examples (if any).
The contents of this chapter have been generated automatically from the RELAX-NG schemas (XML syntax), the error database, and local examples.
The 97 elements and 74 attributes defined in TAN, excluding TEI, are the following:
TAN-core@accessed-when
<adjustments>
<algorithm>
<alias>
<at-ref>
<body>
@cert
@cert2
<change>
<checksum>
<comment>
<companion-version>
<constraints>
@content-datatype
@content-lexical-constraint
<desc>
@div-type
<div-type>
@ed-when
@ed-who
@exceptions
<file-resp>
@flag
@flags
<for-lang>
@from
@group
<group>
<group-type>
<head>
@href
@id
@idrefs
<in-lang>
@include
<inclusion>
<IRI>
@item-type
<license>
@licensor
<location>
<master-location>
@n
<name>
<numerals>
<object>
<organization>
@pattern
@period
<period>
<person>
<place>
<predecessor>
@priority
@relationship
<relationship>
<resp>
<role>
@roles
<scriptum>
<see-also>
<source>
@status
<subject>
<successor>
<tail>
<TAN-T>
@TAN-version
@to
<to-do>
<token-definition>
@type
<value>
<verb>
<vocabulary>
<vocabulary-key>
@when
<where>
@which
@who
<work>
@xml:id
@xml:lang
TAN-class-1<annotation>
<model>
<n-alias>
<normalization>
<redivision>
@ref-alias
<reference-system>
<replace>
@replacement
@scriptum
@type
<version>
@wf-ready
<work>
TAN-class-2@by
@chars
@claim-period
@claim-when
@claimant
<equate>
<from-tok>
<group>
@new
<passage>
@pos
@priority
<reassign>
@ref
<rename>
@rgx
@shallow
<skip>
@src
<through-tok>
<to>
<tok>
@val
TAN-A@adverb
<at-ref>
<claim>
<div>
@in-lang
<in-lang>
<modal>
@object
<object>
<place>
@scriptum
@subject
<subject>
<TAN-A>
<tok>
<topic>
<unit>
@units
@verb
<version>
@where
@work
TAN-A-tok<align>
@bitext-relation
<bitext-relation>
@reuse-type
<reuse-type>
<TAN-A-tok>
TAN-A-lm<ana>
@def-ref
<l>
@lexicon
<lexicon>
<lm>
<m>
@morphology
<morphology>
<TAN-A-lm>
<tok>
<tok-is>
@tok-pop
<tok-starts-with>
TAN-class-3
TAN-voc@affects-attribute
@affects-element
<item>
<TAN-voc>
TAN-mor<assert>
<category>
<code>
@feature
<feature>
@m-has-codes
@m-has-how-many-codes
@m-matches
<report>
<rule>
<TAN-mor>
@tok-matches
<val>
catalog.tan<collection>
<doc>
@href
@id
@metadata-resolved
@root
@stable
The attribute accessed-when
specifies when an electronic file was last examined
Used by: ~element-location
, ~entity-digital-core-content
Important | |
---|---|
If |
Caution | |
---|---|
Future dates are not permitted. |
Example 12.1. @accessed-when
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2021"> <head> ......... <model> ......... <name>Categories, Aristotle, Greek text by Minio-Paluello</name> <location href="ar.cat.grc.1949.minio-paluello.ref-logical.xml" accessed-when="2016-02-10T14:08:52.058-05:00"/> </model> <see-also relationship="alt"> ......... <name>Categories, Aristotle, Greek text by Minio-Paluello</name> <location href="ar.cat.grc.1949.minio-paluello.ref-scriptum.xml" accessed-when="2016-02-11T12:40:42.823-05:00"/> </see-also> <redivision> ......... <name>Categories, Aristotle, English translation by E. M. Edghill</name> <location href="ar.cat.eng.1926.edghill.ref-scriptum.xml" accessed-when="2016-06-22T08:13:35.791-04:00"/> </redivision> ......... <vocabulary-key> <algorithm xml:id="xslt2"> ......... <name>Stylesheet to create a TAN file.</name> <location href="../applications/convert/convert%20TAN%202018%20to%20TAN%202020.xsl" accessed-when="2018-08-04T23:55:36.096-04:00"/> </algorithm> ......... </vocabulary-key> ......... </head> ......... </TAN-T>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-logical |
The attribute adverb
names a <modal>
that qualifies the claim.
Multiple values of @adverb
are interpreted to mean "and" with intersection. No distribution takes place. @adverb
="X Y" specifies that the claim is expressed in both X and Y modes. For example, adverb="not probably" means that the claim is probably not true.
The sequence of multiple values of @adverb
is immaterial. This attribute is not inheritable.
Takes IDrefs to vocabulary items <modal>
, <modal>
Used by: ~element-claim
Caution | |
---|---|
Every idref in an attribute must point to a vocabulary item (by |
Caution | |
---|---|
All idrefs in an attribute must be unique. |
Caution | |
---|---|
Multiple idrefs in a single attribute should not point to the same entity. |
Example 12.2. @adverb
<TAN-A TAN-version="2021" id="tag:parkj@textalign.net,2015:ar.cat.tan-a:claims"> ......... <body claimant="park" claim-period="per2010s"> <comment when="2017-03-10-05:00" who="park">The next two claims interpret Minio-Paluello's apparatus criticus entry for 1a2, which claims that Andronicus and Boethus might have omitted τῆς οὐσίας (based on what Porphyry and Dexippus say) and asserts that the reading adopted is found in the seven commentators. The interpretation below sticks close to M-P's original, and does not fill in important gaps. For example, Dexippus's remark comes from his commentary, 1.18 (p. 21.20) and is reliant wholly on a fragment of Porphyry preserved in Simplicius's commentary, p. 30.1-2. Furthermore, a careful reading of these texts shows that Porphyry claimed not that Andronicus and Boethus omitted the text, or relied on sources that had omitted it, but that they observed that there were manuscripts that had done so.</comment> <claim subject="andronicus boethus" adverb="perhaps" verb="om" xml:id="cl1a2a" claim-when="2017-03-10" claimant="park"> <at-ref src="grc" ref="1 a 2"> ......... </at-ref> </claim> <claim subject="δ π" verb="shows" object="cl1a2a"/> ......... <claim subject="B" verb="reads"> ......... </claim> <claim subject="Λ" adverb="perhaps" verb="reads"> <at-ref src="grc" ref="1 a 5"> ......... </at-ref> <object>τις ἀποδιδῷ</object> </claim> <claim subject="π α φ ο" verb="matches"> ......... </claim> ......... </body> </TAN-A>
Note | |
---|---|
Taken from ar.cat.TAN-A.claims |
The attribute affects-attribute
names one or more TAN attributes that an item applies to.
This attribute is weakly inheritable. An element will be affected only by the values of the closest @affects-attribute.
.
Currently this attribute may be applied only to @n.
.
Used by: ~body-attributes-non-core
, ~group-attributes-non-core
, ~element-item
Example 12.3. @affects-attribute
<TAN-voc TAN-version="2021" id="tag:textalign.net,2015:tan-voc:n:eng:bible">
<head>
.........
</head>
<body affects-attribute="n" affects-element="work">
<item>
.........
</item>
<item>
.........
</item>
<item>
.........
</item>
.........
</body>
</TAN-voc>
Note | |
---|---|
Taken from n.bible.eng.tan-voc |
Example 12.4. @affects-attribute
<TAN-voc TAN-version="2021" id="tag:textalign.net,2015:tan-voc:n:spa:bible">
<head>
.........
</head>
<body affects-attribute="n" affects-element="work">
<item>
.........
</item>
<item>
.........
</item>
<item>
.........
</item>
.........
</body>
</TAN-voc>
Note | |
---|---|
Taken from n.bible.spa.tan-voc |
Example 12.5. @affects-attribute
<TAN-voc TAN-version="2021" id="tag:textalign.net,2015:tan-voc:n:eng-ara:quran">
<head>
.........
</head>
<body affects-attribute="n" affects-element="work">
<item>
.........
</item>
<item>
.........
</item>
<item>
.........
</item>
.........
</body>
</TAN-voc>
Note | |
---|---|
Taken from n.quran.eng-ara.tan-voc |
Example 12.6. @affects-attribute
<TAN-voc TAN-version="2021" id="tag:textalign.net,2015:tan-voc:n:eng:unlabeled-divs-1">
<head>
.........
</head>
<body affects-attribute="n">
<item>
.........
</item>
<item>
.........
</item>
<item>
.........
</item>
</body>
</TAN-voc>
Note | |
---|---|
Taken from n.unlabeled-divs-1.eng.tan-voc |
The attribute affects-element
names one or more TAN elements that an item applies to.
This attribute is weakly inheritable. An element is be affected only by the values of the closest @affects-element.
.
Used by: ~body-attributes-non-core
, ~group-attributes-non-core
, ~element-item
Caution | |
---|---|
|
Caution | |
---|---|
|
Example 12.7. @affects-element
<TAN-voc TAN-version="2021" id="tag:parkj@textalign.net,2015:TAN-key:ar.cat">
<head>
.........
</head>
<body affects-element="work">
<item>
.........
</item>
<item>
.........
</item>
<item>
.........
</item>
.........
</body>
</TAN-voc>
Note | |
---|---|
Taken from ar.cat.TAN-voc |
Example 12.8. @affects-element
<TAN-voc TAN-version="2021" id="tag:parkj@textalign.net,2015:TAN-voc:standard"> ......... <body> <group affects-element="person"> <item> ......... </item> </group> <item affects-element="work"> <IRI>http://dbpedia.org/resource/Ring_a_Ring_o%27_Roses</IRI> <name>Ring a Ring o' Roses</name> <name>Ring Around the Rosie</name> </item> <item affects-element="organization"> <IRI>tag:parkj@textalign.net,2015:example-project</IRI> <name>Project team for TAN examples</name> </item> <group affects-element="scriptum source"> ......... </group> </body> </TAN-voc>
Note | |
---|---|
Taken from park-projects.TAN-voc |
The attribute bitext-relation
points via idrefs to one or more bitext-relations. Multiple values are combinatory.
This attribute is weakly inheritable. See the section called “Attribute inheritability and priority”
See the section called “TAN keywords for types of bitext relations (<bitext-relation>)” for standard TAN values.
Takes IDrefs to vocabulary items <bitext-relation>
Used by: ~body-attributes-non-core
, ~element-align
Caution | |
---|---|
Every idref in an attribute must point to a vocabulary item (by |
Caution | |
---|---|
All idrefs in an attribute must be unique. |
Caution | |
---|---|
Multiple idrefs in a single attribute should not point to the same entity. |
Example 12.9. @bitext-relation
<TAN-A-tok TAN-version="2021" id="tag:parkj@textalign.net,2015:TAN-A-tok,ring01+ring02">
<head>
.........
</head>
<body bitext-relation="B-descends-from-A" reuse-type="adaptation">
<align>
.........
</align>
<align>
.........
</align>
<align>
.........
</align>
.........
</body>
</TAN-A-tok>
Note | |
---|---|
Taken from ringoroses.01+02.token.1 |
Example 12.10. @bitext-relation
<TAN-A-tok TAN-version="2021" id="tag:parkj@textalign.net,2015:TAN-A-tok,ring01+ring03">
<head>
.........
</head>
<body reuse-type="correlationGeneral" bitext-relation="unclear" claimant="xslt2">
<align>
.........
</align>
<align>
.........
</align>
<align>
.........
</align>
.........
</body>
</TAN-A-tok>
Note | |
---|---|
Taken from ringoroses.01+03.token.1 |
Example 12.11. @bitext-relation
<TAN-A-tok TAN-version="2021" id="tag:parkj@textalign.net,2015:TAN-A-tok,ring01+ring03:alt">
<head>
.........
</head>
<body reuse-type="correlationGeneral" bitext-relation="unclear" claimant="xslt2">
<align>
.........
</align>
<align>
.........
</align>
<align>
.........
</align>
.........
</body>
</TAN-A-tok>
Note | |
---|---|
Taken from ringoroses.01+03.token.2 |
The attribute by
specifies an amount by which an series of @n
values or the last component in a series of @ref
values should be incremented or decremented.
Used by: ~complex-rename
Example 12.12. @by
<adjustments src="ger">
<skip div-type="Gedicht"/>
<rename n="e" by="-1"/>
</adjustments>
Note | |
---|---|
Taken from ringoroses.div.1 |
The attribute cert
indicates how certain the claimant is of the claims, expressed as a real number from 0 (no certainty) to 1 (complete certainty).
This attribute is taken into account before all other attributes except @claimant.
. That is, @cert
is to be interpreted to mean: "@claimant
has @cert
confidence about the following assertion:...."
@cert
is cumulatively inheritable. Any @cert
value should be multiplied against all ancestors' values of @cert.
. For example, in a TAN-A-tok file, if an <align>
has a certainty of 0.6 and a child <tok>
has a certainty of 0.3, then that <tok>
's calculated certainty is 0.18. See the section called “Attribute inheritability and priority”
Any claim inherits as its value of @cert
the product of every component @cert.
. For example, if an <l>
and an <m>
in a TAN-A-lm file each have a certainty of 0.5, then the lexico-morphological claim that involves them both has a certainty of 0.25.
Used by: ~certainty-claim
Example 12.13. @cert
<TAN-A-lm TAN-version="2021" id="tag:kalvesmaki.com,2015:tan-a-lm:grc:perseusα"> ......... <body lexicon="LSJ" morphology="perseus-dik" claimant="xslt2"> <ana> <tok val="Α" cert="0.2"/> <tok val="α" cert="0.083333333333333333"/> <tok val="ἆ"/> ......... </ana> <ana> <tok val="α" cert="0.083333333333333333"/> <tok val="ἁ"/> <tok val="ἃ" cert="0.142857142857142857"/> <tok val="ἅ" cert="0.166666666666666667"/> ......... </ana> ......... <ana> <tok val="α" cert="0.083333333333333333"/> <tok val="ᾇ"/> ......... </ana> <ana> <tok val="α" cert="0.083333333333333333"/> <tok val="ἃ" cert="0.142857142857142857"/> <lm> ......... </lm> </ana> ......... <ana> <tok val="ά"/> <tok val="α" cert="0.083333333333333333"/> <tok val="ὰ"/> ......... </ana> </body> </TAN-A-lm>
Note | |
---|---|
Taken from grc-tan-a-lm-%CE%B1 |
The attribute cert2
provides a second measure of certainty. The value is taken along with @cert
as being the low or high limit to the range of certainty. See documentation on @cert.
.
Used by: ~certainty-claim
Example 12.14. @cert2
<align>
<tok src="eng" ref="1" pos="5" cert="0.3" cert2="0.2"/>
<tok src="ger" ref="1" pos="3" cert="0.3"/>
</align>
Note | |
---|---|
Taken from ringoroses.01+03.token.1 |
The attribute chars
identifies one or more characters, specified through Arabic numerals, or the keywords 'last' or 'last-X' (where X is a valid number), joined with commas or hyphens.
Examples: '1', 'last', 'last-3 - last-1', '1, 3, 5, 7 - 11, last-8, last'
Used by: ~element-tok-abstract
, ~element-tok-for-claim-no-ref
, ~element-tok-for-claim-with-ref
, ~element-tok-standard
Caution | |
---|---|
Sequences may not include values less than 1. |
Caution | |
---|---|
Sequences may not include values greater than the maximum allowed. |
Caution | |
---|---|
Ranges in sequences must go from a lesser value to a greater. |
Caution | |
---|---|
Every character must be locatable in every token in every ref in every source. |
Example 12.15. @chars
<subject src="eng-uk">
<tok ref="2" pos="2-3" chars="3-4"/>
<from-tok ref="1" pos="3"/>
.........
</subject>
Note | |
---|---|
Taken from ringoroses.div.1 |
The attribute claim-period
names a vocabulary item that identifies a time when a claim was made.
Takes IDrefs to vocabulary items <period>
Used by: ~claimant-attributes
Example 12.16. @claim-period
<TAN-A TAN-version="2021" id="tag:parkj@textalign.net,2015:ar.cat.tan-a:claims">
<head>
.........
</head>
<body claimant="park" claim-period="per2010s">
<comment when="2017-03-10-05:00" who="park">The next two claims interpret Minio-Paluello's
apparatus criticus entry for 1a2, which claims that Andronicus and Boethus might have
omitted τῆς οὐσίας (based on what Porphyry and Dexippus say) and asserts that the
reading adopted is found in the seven commentators. The interpretation below sticks
close to M-P's original, and does not fill in important gaps. For example, Dexippus's
remark comes from his commentary, 1.18 (p. 21.20) and is reliant wholly on a fragment of
Porphyry preserved in Simplicius's commentary, p. 30.1-2. Furthermore, a careful reading
of these texts shows that Porphyry claimed not that Andronicus and Boethus omitted the
text, or relied on sources that had omitted it, but that they observed that there were
manuscripts that had done so.</comment>
<claim subject="andronicus boethus" adverb="perhaps" verb="om" xml:id="cl1a2a" claim-when="2017-03-10" claimant="park">
.........
</claim>
<claim subject="δ π" verb="shows" object="cl1a2a"/>
.........
</body>
</TAN-A>
Note | |
---|---|
Taken from ar.cat.TAN-A.claims |
The attribute claim-when
identifies a time when a claim was made.
Used by: ~claimant-attributes
Example 12.17. @claim-when
<body claimant="park" claim-period="per2010s">
<comment when="2017-03-10-05:00" who="park">The next two claims interpret Minio-Paluello's
apparatus criticus entry for 1a2, which claims that Andronicus and Boethus might have
omitted τῆς οὐσίας (based on what Porphyry and Dexippus say) and asserts that the
reading adopted is found in the seven commentators. The interpretation below sticks
close to M-P's original, and does not fill in important gaps. For example, Dexippus's
remark comes from his commentary, 1.18 (p. 21.20) and is reliant wholly on a fragment of
Porphyry preserved in Simplicius's commentary, p. 30.1-2. Furthermore, a careful reading
of these texts shows that Porphyry claimed not that Andronicus and Boethus omitted the
text, or relied on sources that had omitted it, but that they observed that there were
manuscripts that had done so.</comment>
<claim subject="andronicus boethus" adverb="perhaps" verb="om" xml:id="cl1a2a" claim-when="2017-03-10" claimant="park">
<at-ref src="grc" ref="1 a 2">
.........
</at-ref>
</claim>
<claim subject="δ π" verb="shows" object="cl1a2a"/>
.........
</body>
Note | |
---|---|
Taken from ar.cat.TAN-A.claims |
The attribute claimant
points to a <person>
, <organization>
, or <algorithm>
who makes a claim. @claimant
within <body>
indicates the default persons to be credited or blamed for an assertion. If <body>
's @claimant
is absent, the default claimant would be the key agents of the file.
This attribute is taken into account before all other attributes. That is, @claimant
is to be interpreted to mean: "@claimant
states the following:...." Multiple values of @claimant
are interpreted to mean "and", resulting in distribution of the claim (e.g., claimant="x y" becomes "x claims that..." and "y claims that...").
In a TAN-A file, nested @claimants
mean that claimant X claims that claimant Y claims that... and so forth.
In other class-2 files, a nested @claimant
cancels out any inherited @claimants.
.
This attribute is weakly inheritable. See the section called “Attribute inheritability and priority”
Takes IDrefs to vocabulary items <person>
, <organization>
, <algorithm>
Used by: ~claimant-attributes
Example 12.18. @claimant
<TAN-A TAN-version="2021" id="tag:parkj@textalign.net,2015:ar.cat.tan-a:claims"> <head> ......... </head> <body claimant="park" claim-period="per2010s"> <comment when="2017-03-10-05:00" who="park">The next two claims interpret Minio-Paluello's apparatus criticus entry for 1a2, which claims that Andronicus and Boethus might have omitted τῆς οὐσίας (based on what Porphyry and Dexippus say) and asserts that the reading adopted is found in the seven commentators. The interpretation below sticks close to M-P's original, and does not fill in important gaps. For example, Dexippus's remark comes from his commentary, 1.18 (p. 21.20) and is reliant wholly on a fragment of Porphyry preserved in Simplicius's commentary, p. 30.1-2. Furthermore, a careful reading of these texts shows that Porphyry claimed not that Andronicus and Boethus omitted the text, or relied on sources that had omitted it, but that they observed that there were manuscripts that had done so.</comment> <claim subject="andronicus boethus" adverb="perhaps" verb="om" xml:id="cl1a2a" claim-when="2017-03-10" claimant="park"> <at-ref src="grc" ref="1 a 2"> ......... </at-ref> </claim> <claim subject="δ π" verb="shows" object="cl1a2a"/> ......... </body> </TAN-A>
Note | |
---|---|
Taken from ar.cat.TAN-A.claims |
Example 12.19. @claimant
<TAN-A TAN-version="2021" id="tag:parkj@textalign.net,2015:ar.cat.tan-a">
<head>
.........
</head>
<body claimant="park">
<claim verb="concerns" object="predication">
.........
</claim>
</body>
</TAN-A>
Note | |
---|---|
Taken from ar.cat.TAN-A |
Example 12.20. @claimant
<TAN-A TAN-version="2021" id="tag:parkj@textalign.net,2015:patricius.confessio.tan-a">
<head>
.........
</head>
<body claimant="park">
<claim verb="quotes">
.........
</claim>
</body>
</TAN-A>
Note | |
---|---|
Taken from patricius.confessio.TAN-A |
The attribute content-datatype
specifies a type of data. This attribute is used in TAN-A claims, and restricts the kind of object a particular verb governs to raw units, not entities definable by the IRI + name pattern. Use this attribute if and only if the verb may not govern objects defined as a vocabulary item.
Used by: ~constraint-content
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 | |
---|---|
|
Example 12.21. @content-datatype
<constraints>
<subject status="required" item-type="scriptum"/>
<object status="required" content-datatype="integer" content-lexical-constraint="\d+"/>
</constraints>
Note | |
---|---|
Taken from ar.cat.TAN-A.claims |
Example 12.22. @content-datatype
<constraints>
<subject status="required" item-type="scriptum work version"/>
<object status="required" content-datatype="string"/>
<at-ref status="required"/>
</constraints>
Note | |
---|---|
Taken from verbs.TAN-voc |
The attribute content-lexical-constraint
specifies a regular expression that constrains the value of any <object>
.
Note that the regular expression will be strictly followed, e.g., "\d+" will be satisfied by "a1" (because there is at least one digit). If you wish to constrain the entire value, be sure to use ^ and $, e.g., "^\d+$".
Used by: ~constraint-content
Caution | |
---|---|
Claims involving verbs whose constrained content requires specification of units must use |
Caution | |
---|---|
A claim with a verb that has content constraints must not allow other verbs. |
Example 12.23. @content-lexical-constraint
<constraints>
<subject status="required" item-type="scriptum"/>
<object status="required" content-datatype="integer" content-lexical-constraint="\d+"/>
</constraints>
Note | |
---|---|
Taken from ar.cat.TAN-A.claims |
The attribute def-ref
identifies which lexical definition is meant. This attribute is essential in cases where a lexicon has multiple entries for lexemes (lexical headwords) that are identical.
Because there is no TAN format for lexicons, assertions about lexica will not be validated.
Used by: ~element-l
Note | |
---|---|
Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-A-lm-sample |
The attribute div-type
is used by class-2 files to point to one or more <div-type>
s in class-1 files or by class-1 files to point to div type vocabulary items. Permits multiple values separated by spaces.
Takes IDrefs to vocabulary items <div-type>
Used by: ~element-n-alias
, ~action-condition-attributes
, ~adj-element-skip
Caution | |
---|---|
Every div type reference must be valid in every source |
Example 12.25. @div-type
<head>
.........
<reference-system type="logical" wf-ready="true"/>
<n-alias div-type="book"/>
<work which="matthew"/>
.........
</head>
Note | |
---|---|
Taken from matt.eng.kjv.1760 |
Example 12.26. @div-type
<adjustments src="fra">
<skip div-type="summ" shallow="false"/>
<equate n="ti title"/>
.........
</adjustments>
Note | |
---|---|
Taken from ar.cat.TAN-A |
Example 12.27. @div-type
<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 |
The attribute ed-when
marks the date or time when an element or its content was edited (added or modified)
The value of must always conform to an ISO date or dateTime pattern. See the section called “Dates and times”.
Along with @ed-who
, this forms the Edit Stamp pattern. See the section called “Edit stamp”
This attribute is weakly inheritable. See the section called “Attribute inheritability and priority”
Used by: ~ed-stamp
Caution | |
---|---|
Future dates are not permitted. |
Example 12.29. @ed-when
<head>
.........
<adjustments>
.........
</adjustments>
<vocabulary-key ed-who="park" ed-when="2015-10-31">
<algorithm xml:id="xslt1">
.........
</algorithm>
<div-type xml:id="l">
.........
</div-type>
<person xml:id="park">
.........
</person>
.........
</vocabulary-key>
<file-resp who="park"/>
.........
</head>
Note | |
---|---|
Taken from ring-o-roses.eng.1987 |
Example 12.30. @ed-when
<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 |
Example 12.31. @ed-when
<head>
.........
<comment when="2015-03-10" who="kalvesmaki">Codes developed as a synthesis of
ftp://ftp.cis.upenn.edu/pub/treebank/doc/tagguide.ps.gz and
http://www.comp.leeds.ac.uk/amalgam/tagsets/upenn.html</comment>
<vocabulary-key ed-when="2015-03-03" ed-who="kalvesmaki">
<algorithm xml:id="xslt2">
.........
</algorithm>
<person xml:id="kalvesmaki">
.........
</person>
<algorithm xml:id="xslt1">
.........
</algorithm>
.........
</vocabulary-key>
<file-resp who="kalvesmaki"/>
.........
</head>
Note | |
---|---|
Taken from eng.kalvesmaki.com,2014.2 |
Example 12.32. @ed-when
<head>
.........
<source>
.........
</source>
<vocabulary-key ed-when="2016-03-31" ed-who="kalvesmaki">
<person xml:id="kalvesmaki">
.........
</person>
<algorithm xml:id="xslt2">
.........
</algorithm>
<feature xml:id="c2">
.........
</feature>
.........
</vocabulary-key>
<file-resp who="kalvesmaki"/>
.........
</head>
Note | |
---|---|
Taken from grc.perseus.tan-mor |
The attribute ed-who
refers to one or more <agent>
s who have edited (added or modified) an element or its content.
Along with @ed-when
, this forms the Edit Stamp pattern. See the section called “Edit stamp”
This attribute is weakly inheritable. See the section called “Attribute inheritability and priority”
Takes IDrefs to vocabulary items <person>
, <organization>
, <algorithm>
Used by: ~ed-stamp
Caution | |
---|---|
Every idref in an attribute must point to a vocabulary item (by |
Caution | |
---|---|
All idrefs in an attribute must be unique. |
Caution | |
---|---|
Multiple idrefs in a single attribute should not point to the same entity. |
Example 12.33. @ed-who
<head>
.........
<adjustments>
.........
</adjustments>
<vocabulary-key ed-who="park" ed-when="2015-10-31">
<algorithm xml:id="xslt1">
.........
</algorithm>
<div-type xml:id="l">
.........
</div-type>
<person xml:id="park">
.........
</person>
.........
</vocabulary-key>
<file-resp who="park"/>
.........
</head>
Note | |
---|---|
Taken from ring-o-roses.eng.1987 |
Example 12.34. @ed-who
<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 |
Example 12.35. @ed-who
<head>
.........
<comment when="2015-03-10" who="kalvesmaki">Codes developed as a synthesis of
ftp://ftp.cis.upenn.edu/pub/treebank/doc/tagguide.ps.gz and
http://www.comp.leeds.ac.uk/amalgam/tagsets/upenn.html</comment>
<vocabulary-key ed-when="2015-03-03" ed-who="kalvesmaki">
<algorithm xml:id="xslt2">
.........
</algorithm>
<person xml:id="kalvesmaki">
.........
</person>
<algorithm xml:id="xslt1">
.........
</algorithm>
.........
</vocabulary-key>
<file-resp who="kalvesmaki"/>
.........
</head>
Note | |
---|---|
Taken from eng.kalvesmaki.com,2014.2 |
Example 12.36. @ed-who
<head>
.........
<source>
.........
</source>
<vocabulary-key ed-when="2016-03-31" ed-who="kalvesmaki">
<person xml:id="kalvesmaki">
.........
</person>
<algorithm xml:id="xslt2">
.........
</algorithm>
<feature xml:id="c2">
.........
</feature>
.........
</vocabulary-key>
<file-resp who="kalvesmaki"/>
.........
</head>
Note | |
---|---|
Taken from grc.perseus.tan-mor |
The attribute exceptions
lists strings that should not be interpreted as numerics; this is most commonly used in rare cases where a string label for @n
or @ref
might be interpreted as a Roman numeral or a letter numeral
Expected is a space delimited list of atomic values of @n.
. Because @n
is not case-sensitive, every item in @exceptions
is as well.
Used by: <numerals>
Takes IDrefs to vocabulary items <feature>
Used by: ~element-category
, ~element-code
Caution | |
---|---|
Every idref in an attribute must point to a vocabulary item (by |
Caution | |
---|---|
All idrefs in an attribute must be unique. |
Caution | |
---|---|
Multiple idrefs in a single attribute should not point to the same entity. |
Caution | |
---|---|
Codes for features must be case-indifferently unique. |
Example 12.37. @feature
<TAN-mor TAN-version="2021" id="tag:kalvesmaki.com,2014:tan-r-mor:eng:penn"> ......... <body> ......... <rule m-has-codes="'' . ; :"> ......... </rule> <code feature="closing_quotation_mark"> <desc>Examples: ' ''</desc> <val>''</val> </code> <code feature="dash"> <desc>Example: --</desc> <val>--</val> </code> <code feature="dollar"> <desc>Examples: Examples: $ -$ --$ A$ C$ HK$ M$ NZ$ S$ U.S.$ US$</desc> <val>$</val> </code> <code feature="opening_parenthetical_punctuation"> <desc>Examples: ( [ {</desc> <val>[</val> </code> <code feature="closing_parenthetical_punctuation"> ......... </code> ......... </body> </TAN-mor>
Note | |
---|---|
Taken from eng.kalvesmaki.com,2014.2 |
The attribute flag
indicates the level of error to be attached to the enclosed message. This attribute is similar to Schematron's @role
, but under a different name, to avoid confusion with TAN @roles.
.
This attribute is non-inheritable.
Used by: ~condition-pattern
, ~element-change
Example 12.38. @flag
<head>
.........
<change when="2014-10-28" who="park">Created new TAN-TEI file.</change>
<change when="2017-10-21" who="park" flag="error">The unnecessary top-level div, poem, has been removed.</change>
<change who="xslt1" when="2017-11-02T22:05:03.898-04:00">TAN file updated to 2018 schemas.</change>
.........
</head>
Note | |
---|---|
Taken from ring-o-roses.eng.1951 |
The attribute flags
specifies flags to be applied in an XPath function that uses regular expressions.
s = dot-all mode; m = multi-line mode; i = case-insensitive mode; x = remove whitespace characters from regular expression; q = no metacharacters
For more see http://www.w3.org/TR/xpath-functions-30/#flags
This attribute is non-inheritable.
Used by: ~element-replace
, ~element-token-definition
Example 12.39. @flags
<adjustments>
.........
<normalization>
.........
</normalization>
<replace pattern="--" replacement="—" flags="i"/>
</adjustments>
Note | |
---|---|
Taken from gomme.1989.ring-o-roses |
The attribute from
specifies the beginning of a period of time.
Used by: <period>
Caution | |
---|---|
Future dates are not permitted. |
Example 12.40. @from
<vocabulary-key>
.........
<role xml:id="creator">
.........
</role>
<period xml:id="per2010s" from="2010-01-01" to="2019-12-31"/>
<period xml:id="late-antiquity">
.........
</period>
.........
</vocabulary-key>
Note | |
---|---|
Taken from ar.cat.TAN-A.claims |
The attribute group
identifies one or more <group-type>
s under which the parent element, and its children, should be grouped.
This attribute is cumulatively inheritable. An <item>
is to be associated by all values of @group
in itself and its ancestors.
Takes IDrefs to vocabulary items <group-type>
, <group-type>
Used by: ~element-ana
, ~element-align
, ~extra-verb-attrs
, ~element-item
Caution | |
---|---|
Every idref in an attribute must point to a vocabulary item (by |
Caution | |
---|---|
All idrefs in an attribute must be unique. |
Caution | |
---|---|
Multiple idrefs in a single attribute should not point to the same entity. |
Example 12.41. @group
<body affects-element="div-type"> <group type="logical"> <item group="line-start line-end leading-start leading-end"> <IRI>tag:textalign.net,2015:div-type:abstract</IRI> <IRI>tag:textalign.net,2015:div-type:equiv:tei:abstract</IRI> <IRI>http://dbpedia.org/resource/Abstract_(summary)</IRI> ......... </item> <item> ......... </item> ......... <item> ......... </item> <item group="page-start page-end"> <IRI>tag:textalign.net,2015:div-type:afterword</IRI> <IRI>http://dbpedia.org/resource/Afterword</IRI> <name>afterword</name> </item> <item> ......... </item> ......... <item> ......... </item> <item group="annotation"> <IRI>tag:textalign.net,2015:div-type:apparatus_criticus</IRI> <IRI>http://dbpedia.org/resource/Critical_apparatus</IRI> <name>apparatus criticus</name> ......... </item> <item group="annotation"> <IRI>tag:textalign.net,2015:div-type:apparatus_fontium</IRI> <name>apparatus fontium</name> <desc>Section of a critical edition, usually at the bottom of the page, indicating parallel textual sources</desc> </item> <item group="line-start line-end"> ......... </item> ......... </group> ......... </body>
Note | |
---|---|
Taken from div-types.TAN-voc |
The attribute href
points to the location of a file. In some contexts, this attribute is permitted only as a temporary measure, to assist editing via Schematron Quick Fixes.
Used by: <doc>
, ~element-location
, ~element-master-location
, ~entity-digital-tan-other-content
Caution | |
---|---|
|
Important | |
---|---|
If an |
Important | |
---|---|
If an |
Important | |
---|---|
If the internet is available, and an |
Caution | |
---|---|
The only |
Caution | |
---|---|
No |
Caution | |
---|---|
An |
Caution | |
---|---|
No |
Caution | |
---|---|
Every |
Important | |
---|---|
|
Example 12.42. @href
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2021"> <head> <name>Categories, Aristotle, English translation by E. M. Edghill</name> <master-location href="https://raw.githubusercontent.com/textalign/TAN-2021/master/examples/ar.cat.eng.1926.edghill.ref-logical.xml"/> <license licensor="kalvesmaki"> ......... </license> ......... <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> ......... </head> ......... </TAN-T>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-logical |
Definition 1
Definition 2
Definition 1
The attribute id
provides a unique identifier for an <alias>
. Must be unique within a given file. Must consist only of non-spacing characters.
Definition 2
The attribute id
contains a tag URN that permanently and uniquely names the current file.
For more on the syntax of tag URNs see the section called “Tag URNs”
Used by: <collection>
, <doc>
, ~voc-element-alias
, ~TAN-root
Caution | |
---|---|
Every TAN file must have at least one organization or person with an |
Caution | |
---|---|
|
Important | |
---|---|
Different TAN files should have unique |
Important | |
---|---|
If a local catalog.tan.xml file lacks a reference to a TAN file being validated, a warning will appear. |
Example 12.43. @id
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2021">
<head>
.........
</head>
<body xml:lang="eng">
.........
</body>
</TAN-T>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-logical |
Example 12.44. @id
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:model-object-refs" TAN-version="2021">
<head>
.........
</head>
<body xml:lang="eng">
.........
</body>
</TAN-T>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-scriptum |
Example 12.45. @id
<TAN-T TAN-version="2021" id="tag:kalvesmaki.com,2014:tan-t:ar.cat.fra.1844.saint-hilaire:semantic-refs-realigned">
<head>
.........
</head>
<body xml:lang="fra">
.........
</body>
</TAN-T>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949 |
Example 12.46. @id
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.fra.1844.saint-hilaire:semantic-refs" TAN-version="2021">
<head>
.........
</head>
<body xml:lang="fra">
.........
</body>
</TAN-T>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.ref-logical |
The attribute idrefs
contains references to one or more values of @xml:id
or @id
in the file
Used by: ~voc-element-alias
Caution | |
---|---|
|
Example 12.47. @idrefs
<vocabulary-key>
.........
<div-type xml:id="v" which="verse (scripture)"/>
<alias xml:id="test" idrefs="ch v"/>
</vocabulary-key>
Note | |
---|---|
Taken from matt.eng.kjv.1760 |
Example 12.48. @idrefs
<head> ......... <vocabulary-key> <alias xml:id="all" idrefs="grc eng"/> <algorithm xml:id="xslt1"> ......... </algorithm> ......... <work xml:id="α.c" which="Explanationes de commentario graeco Ammonii"/> <alias xml:id="α.d" idrefs="α α.c"/> <work xml:id="φ" which="Lemmata de commentario graeco Ioannis Philoponi"/> <work xml:id="φ.c" which="Explanationes de commentario graeco Ioannis Philoponi"/> <alias xml:id="φ.d" idrefs="φ φ.c"/> <work xml:id="ο" which="Lemmata de commentario graeco Olympiodori"/> ......... </vocabulary-key> ......... </head>
Note | |
---|---|
Taken from ar.cat.TAN-A.claims |
The attribute in-lang
restricts a claim to a particular language; used with only certain verbs, e.g., "translates"
By default, this feature is disallowed. A verb's <constraint>
must explicitly require or allow it.
Used by: ~element-claim
, ~in-lang
Example 12.49. @in-lang
<body claimant="park">
.........
<claim verb="lacks_text" subject="böhme">
.........
</claim>
<claim subject="ger" verb="translates" object="eng-uk" in-lang="deu"/>
</body>
Note | |
---|---|
Taken from ringoroses.div.1 |
The attribute include
signals that the parent element is to be replaced by all elements of the same name found in the referred <inclusion>
.
A slight exception is made in the case of <div include=""/>, where only the rootmost <div>
s are included (which come with all descendant <div>
s preserved intact).
Takes IDrefs to vocabulary items <inclusion>
Used by: ~inclusion
Caution | |
---|---|
Every idref in an attribute must point to a vocabulary item (by |
Caution | |
---|---|
All idrefs in an attribute must be unique. |
Caution | |
---|---|
Multiple idrefs in a single attribute should not point to the same entity. |
Caution | |
---|---|
For any element with |
Caution | |
---|---|
Inclusions are integral parts of any TAN file. Access to at least one copy is absolutely mandatory. |
Example 12.50. @include
<body xml:lang="eng">
.........
<div n="4" type="ch">
.........
</div>
<div include="serm-mount"/>
<div n="8" type="ch">
.........
</div>
.........
</body>
Note | |
---|---|
Taken from matt.eng.kjv.1760 |
Example 12.51. @include
<div n="6" type="chapter">
.........
<div n="9" type="v">After this manner therefore pray ye:</div>
<div include="lords-prayer"/>
<div n="14" type="v">For if ye forgive men their trespasses, your heavenly Father will also
forgive you:</div>
.........
</div>
Note | |
---|---|
Taken from sermon-on-the-mount.eng.kjv.1760 |
Example 12.52. @include
<TAN-A-lm TAN-version="2021" id="tag:kalvesmaki.com,2014:tan-t:ar.cat.grc.1949.minio-paluello:semantic-refs:TAN-A-lm:2016-04-05T07:07:40.033-04:00"> <head> ......... <vocabulary-key> ......... <group-type xml:id="status" which="status"/> <person include="rel"/> <person xml:id="stylesheet"> ......... </person> ......... </vocabulary-key> <file-resp include="rel"/> <resp who="xslt2" roles="stylesheet1"/> ......... </head> ......... </TAN-A-lm>
Note | |
---|---|
Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-A-lm-sample |
The attribute item-type
specifies what type of item a verb's object or subject must be. Expected values are names of elements allowed in any vocabulary.
To bind the type to a textual reference in a class-1 source, let the value of @item-type
be 'ref'; this anticipates a claim with object/subject element with @ref
(and either @src
or @work
).
Used by: ~constraint-item-type
Example 12.53. @item-type
<head> ......... <vocabulary-key> ......... <verb xml:id="om"> ......... <constraints> <subject status="required" item-type="person work version scriptum"/> <at-ref status="required"/> ......... </constraints> </verb> <verb xml:id="attests"> ......... <constraints> <subject status="required" item-type="person work version scriptum"/> <object status="required" item-type="ref"/> </constraints> </verb> <verb xml:id="has-length"> ......... <constraints> <subject status="required" item-type="scriptum"/> <object status="required" content-datatype="integer" content-lexical-constraint="\d+"/> </constraints> </verb> ......... </vocabulary-key> ......... </head>
Note | |
---|---|
Taken from ar.cat.TAN-A.claims |
The attribute lexicon
points via idrefs to one or more lexicons, persons, organizations, or algorithms.
This attribute is weakly inheritable. See the section called “Attribute inheritability and priority”
Takes IDrefs to vocabulary items <lexicon>
Used by: ~group-attributes-non-core
, ~body-attributes-non-core
, ~element-ana
, ~element-l
, ~element-lm
Caution | |
---|---|
Every idref in an attribute must point to a vocabulary item (by |
Caution | |
---|---|
All idrefs in an attribute must be unique. |
Caution | |
---|---|
Multiple idrefs in a single attribute should not point to the same entity. |
Example 12.54. @lexicon
<TAN-A-lm TAN-version="2021" id="tag:kalvesmaki.com,2014:tan-t:ar.cat.grc.1949.minio-paluello:semantic-refs:TAN-A-lm:2016-04-05T07:07:40.033-04:00">
<head>
.........
</head>
<body lexicon="LSJ Lampe new" morphology="Perseus" claimant="xslt2">
<ana tok-pop="2">
.........
</ana>
<ana>
.........
</ana>
<ana>
.........
</ana>
.........
</body>
</TAN-A-lm>
Note | |
---|---|
Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-A-lm-sample |
Example 12.55. @lexicon
<TAN-A-lm TAN-version="2021" id="tag:kalvesmaki.com,2015:tan-a-lm:grc:perseusα">
<head>
.........
</head>
<body lexicon="LSJ" morphology="perseus-dik" claimant="xslt2">
<ana>
.........
</ana>
<ana>
.........
</ana>
<ana>
.........
</ana>
.........
</body>
</TAN-A-lm>
Note | |
---|---|
Taken from grc-tan-a-lm-%CE%B1 |
Example 12.56. @lexicon
<TAN-A-lm TAN-version="2021" id="tag:kalvesmaki.com,2015:tan-a-lm:grc:perseusαʹ">
<head>
.........
</head>
<body lexicon="LSJ" morphology="perseus-dik" claimant="xslt2">
<ana>
.........
</ana>
</body>
</TAN-A-lm>
Note | |
---|---|
Taken from grc-tan-a-lm-%CE%B1%CA%B9 |
Example 12.57. @lexicon
<TAN-A-lm TAN-version="2021" id="tag:parkj@textalign.net,2015:ring01-lm">
<head>
.........
</head>
<body lexicon="english" morphology="penn" claimant="xslt2">
<ana>
.........
</ana>
<ana>
.........
</ana>
<ana>
.........
</ana>
.........
</body>
</TAN-A-lm>
Note | |
---|---|
Taken from ring-o-roses.eng.1881.lm |
The attribute licensor
specifies one or more persons or organizations who hold the rights over the material specified by the parent element (either the data of the current file, or of the source that forms the basis for the data).
For more, see the section called “Key Declarations”
Takes IDrefs to vocabulary items <person>
, <organization>
Used by: ~element-license
Caution | |
---|---|
Every idref in an attribute must point to a vocabulary item (by |
Caution | |
---|---|
All idrefs in an attribute must be unique. |
Caution | |
---|---|
Multiple idrefs in a single attribute should not point to the same entity. |
Example 12.58. @licensor
<head>
.........
<master-location href="https://raw.githubusercontent.com/textalign/TAN-2021/master/examples/ar.cat.eng.1926.edghill.ref-logical.xml"/>
<license licensor="kalvesmaki">
<IRI>http://creativecommons.org/licenses/by/4.0/deed.en_US</IRI>
<name>Creative Commons Attribution 4.0 International License</name>
<desc>Exclusive of rights held and licenses offered by rightsholders of the source or
sources listed below, this data file, insofar as it constitutes an independent work, is
licensed under a Creative Commons Attribution 4.0 International License.</desc>
</license>
<work>
.........
</work>
.........
</head>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-logical |
Example 12.59. @licensor
<head>
.........
<master-location href="https://raw.githubusercontent.com/textalign/TAN-2021/master/examples/ar.cat.eng.1926.edghill.ref-scriptum.xml"/>
<license licensor="kalvesmaki">
<IRI>http://creativecommons.org/licenses/by/4.0/deed.en_US</IRI>
<name>Creative Commons Attribution 4.0 International License</name>
<desc>Exclusive of rights held and licenses offered by rightsholders of the source or
sources listed below, this data file, insofar as it constitutes an independent work, is
licensed under a Creative Commons Attribution 4.0 International License.</desc>
</license>
<work>
.........
</work>
.........
</head>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-scriptum |
Example 12.60. @licensor
<head>
.........
<master-location href="https://raw.githubusercontent.com/textalign/TAN-2021/master/examples/ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949.xml"/>
<license licensor="kalvesmaki">
<IRI>http://creativecommons.org/licenses/by/4.0/deed.en_US</IRI>
<name>Creative Commons Attribution 4.0 International License</name>
<desc>Exclusive of rights held and licenses offered by rightsholders of the source or
sources listed below, this data file, insofar as it constitutes an independent work, is
licensed under a Creative Commons Attribution 4.0 International License.</desc>
</license>
<work>
.........
</work>
.........
</head>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949 |
Example 12.61. @licensor
<head>
.........
<master-location href="https://raw.githubusercontent.com/textalign/TAN-2021/master/examples/ar.cat.fra.1844.saint-hilaire.ref-logical-after.xml"/>
<license licensor="kalvesmaki">
<IRI>http://creativecommons.org/licenses/by/4.0/deed.en_US</IRI>
<name>Creative Commons Attribution 4.0 International License</name>
<desc>Exclusive of rights held and licenses offered by rightsholders of the source or
sources listed below, this data file, insofar as it constitutes an independent work, is
licensed under a Creative Commons Attribution 4.0 International License.</desc>
</license>
<reference-system type="logical" wf-ready="true"/>
.........
</head>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.ref-logical |
The attribute m-has-codes
specifies one or more features. Values must be separated by spaces or the padded + (a plus sign with surrounding spaces). A plain space is treated as meaning "or" and the padded + as meaning "and." If there is at least one match between the list and the value of the codes in an <m>
then the condition will be treated as true. The padded plus sign specifies that all the items need to be found in the <m>
.
For example, feature-test="A B + C D + E" means that the condition will be true for a given <m>
only if that <m>
has A or (B and C) or (D and E) present as values. This is one of four tests for determining whether to process a <report>
or <assert>
Used by: ~action-condition-attributes
Example 12.62. @m-has-codes
<TAN-mor TAN-version="2021" id="tag:kalvesmaki.com,2014:tan-r-mor:eng:penn"> ......... <body> ......... <rule> <where m-has-codes="$"/> <assert tok-matches="$">Only $ may be tagged as a dollar sign.</assert> </rule> <rule m-has-codes="'' . ; :"> <report tok-matches="\w">Nothing marked as punctuation should have word characters.</report> </rule> <code feature="closing_quotation_mark"> ......... </code> ......... </body> </TAN-mor>
Note | |
---|---|
Taken from eng.kalvesmaki.com,2014.2 |
The attribute m-has-how-many-codes
specifies a range or sequence of integers (e.g., 2-4). If the quantity of features in an <m>
matches a number from that sequence, the condition is true, and false otherwise. If the keyword 'last' or 'max' is used, the total number of features will be substituted.
This test is useful for non-category based grammars to put a limit on the number of features that can be declared in an <m>
. This is one of four tests for determining whether to process a <report>
or <assert>
Used by: ~action-condition-attributes
Example 12.63. @m-has-how-many-codes
<rule m-matches=".+">
<assert m-has-how-many-codes="1">Features may not be combined.</assert>
</rule>
Note | |
---|---|
Taken from eng.kalvesmaki.com,2014.2 |
Example 12.64. @m-has-how-many-codes
<body>
<rule m-has-how-many-codes="2-10">
<report m-matches="^c">A conjunction has no other inflectional
properties.</report>
<report m-matches="^r">A preposition has no other inflectional
properties.</report>
<report m-matches="^i">An interjection has no other inflectional
properties.</report>
.........
</rule>
<rule m-matches="^e">
.........
</rule>
.........
</body>
Note | |
---|---|
Taken from grc.perseus.tan-mor |
The attribute m-matches
takes a regular expression. The condition is true only if an <m>
matches the pattern.
This is one of four tests for determining whether to process a <report>
or <assert>
Used by: ~action-condition-attributes
Example 12.65. @m-matches
<body>
<rule m-matches=".+">
<assert m-has-how-many-codes="1">Features may not be combined.</assert>
</rule>
<rule>
.........
</rule>
.........
</body>
Note | |
---|---|
Taken from eng.kalvesmaki.com,2014.2 |
Example 12.66. @m-matches
<body> <rule m-has-how-many-codes="2-10"> <report m-matches="^c">A conjunction has no other inflectional properties.</report> <report m-matches="^r">A preposition has no other inflectional properties.</report> <report m-matches="^i">An interjection has no other inflectional properties.</report> <report m-matches="^y">An acronym has no other inflectional properties.</report> </rule> ......... </body>
Note | |
---|---|
Taken from grc.perseus.tan-mor |
Used by: <collection>
Example 12.67. @metadata-resolved
<collection stable="true" metadata-resolved="false">
<doc href="ar.cat.eng.1926.edghill.ref-logical.xml" id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2021" xml:lang="eng" root="TAN-T">
.........
</doc>
<doc href="ar.cat.eng.1926.edghill.ref-scriptum.xml" id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:model-object-refs" TAN-version="2021" xml:lang="eng" root="TAN-T">
.........
</doc>
<doc href="ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949.xml" TAN-version="2021" id="tag:kalvesmaki.com,2014:tan-t:ar.cat.fra.1844.saint-hilaire:semantic-refs-realigned" xml:lang="fra" root="TAN-T">
.........
</doc>
.........
</collection>
Note | |
---|---|
Taken from catalog.tan |
Example 12.68. @metadata-resolved
<collection stable="true" metadata-resolved="false">
<doc href="ar.cat.TAN-voc.xml" TAN-version="2020" id="tag:parkj@textalign.net,2015:TAN-key:ar.cat" affects-element="work" root="TAN-voc">
.........
</doc>
<doc href="park-projects.TAN-voc.xml" TAN-version="2020" id="tag:parkj@textalign.net,2015:TAN-voc:standard" root="TAN-voc">
.........
</doc>
</collection>
Note | |
---|---|
Taken from catalog.tan |
The attribute morphology
points to one or more <morphology>
IDs
This attribute is inheritable. See the section called “Attribute inheritability and priority”
Takes IDrefs to vocabulary items <morphology>
Used by: ~group-attributes-non-core
, ~body-attributes-non-core
, ~element-ana
, ~element-lm
, ~element-m
Caution | |
---|---|
Every idref in an attribute must point to a vocabulary item (by |
Caution | |
---|---|
All idrefs in an attribute must be unique. |
Caution | |
---|---|
Multiple idrefs in a single attribute should not point to the same entity. |
Example 12.69. @morphology
<TAN-A-lm TAN-version="2021" id="tag:kalvesmaki.com,2014:tan-t:ar.cat.grc.1949.minio-paluello:semantic-refs:TAN-A-lm:2016-04-05T07:07:40.033-04:00">
<head>
.........
</head>
<body lexicon="LSJ Lampe new" morphology="Perseus" claimant="xslt2">
<ana tok-pop="2">
.........
</ana>
<ana>
.........
</ana>
<ana>
.........
</ana>
.........
</body>
</TAN-A-lm>
Note | |
---|---|
Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-A-lm-sample |
Example 12.70. @morphology
<TAN-A-lm TAN-version="2021" id="tag:kalvesmaki.com,2015:tan-a-lm:grc:perseusα">
<head>
.........
</head>
<body lexicon="LSJ" morphology="perseus-dik" claimant="xslt2">
<ana>
.........
</ana>
<ana>
.........
</ana>
<ana>
.........
</ana>
.........
</body>
</TAN-A-lm>
Note | |
---|---|
Taken from grc-tan-a-lm-%CE%B1 |
Example 12.71. @morphology
<TAN-A-lm TAN-version="2021" id="tag:kalvesmaki.com,2015:tan-a-lm:grc:perseusαʹ">
<head>
.........
</head>
<body lexicon="LSJ" morphology="perseus-dik" claimant="xslt2">
<ana>
.........
</ana>
</body>
</TAN-A-lm>
Note | |
---|---|
Taken from grc-tan-a-lm-%CE%B1%CA%B9 |
Example 12.72. @morphology
<TAN-A-lm TAN-version="2021" id="tag:parkj@textalign.net,2015:ring01-lm">
<head>
.........
</head>
<body lexicon="english" morphology="penn" claimant="xslt2">
<ana>
.........
</ana>
<ana>
.........
</ana>
<ana>
.........
</ana>
.........
</body>
</TAN-A-lm>
Note | |
---|---|
Taken from ring-o-roses.eng.1881.lm |
The attribute n
names a <div>
or <group>
, or refers to a <div>
's @n.
.
@n
may consist of one or more values, space delimited, which are to be treated as synonyms.
Any itemized value of @n
may be numerical on non-numerical. A numerical value follows one of the supported TAN numeration systems, with commas and hyphens to refer to build sequences or ranges. The order of numerical items in an @n
are significant. For example n="6, 8" signifies that the text straddles reference 6 then 8. But n="8, 6" signifies the converse. In the context of a <div>
, the implication is that in neither case can the text be securely disentangled so as to create one <div>
for 6 and another for 8.
The hyphen-minus, - (U+002D, the most common form of hyphen), is reserved to specify a range. This feature is useful for cases where a <div>
straddles more than one standard reference number (e.g., a translation of Aristotle that cannot be easily tied to Bekker numbers).
If you need to use a hyphen-like character in an @n
that does not specify a range, consider ‐ (U+2010 HYPHEN), ‑ (U+2011 NON-BREAKING HYPHEN), ‒ (U+2012 FIGURE DASH), – (U+2013 EN DASH), or − (U+2212 MINUS SIGN).
The comma is reserved to delimit items in a sequence of references.
The space is reserved to separate synonymous values, or to pad commas and hyphens. If you wish to use a value of @n
that should not be split at the space, use the underbar, _, instead.
@n
does not permit non-word characters, e.g., the period/full stop or colon. Such non-word characters need to be used by @ref
to connect @n
's.
Because @n
is used to construct @ref
, it is indirectly cumulatively inheritable. See the section called “Attribute inheritability and priority”.
Extra TAN vocabulary is available for @n
, to provide built-in aliases. For more on this feature see the section called “Extra @n
vocabulary”. For specific extra vocabulary see the section called “commonly used vocabulary for the bible (<work>@n)” the section called “vocabulario de uso común para la biblia (<work>@n)” the section called “Commonly used names for Surahs in the Quran, incorporating English and Arabic. (<work>@n)” the section called “Commonly used vocabulary in English for divs that are unnamed, first system (@n)”
Used by: ~element-div
, ~adj-element-equate
, ~adj-element-skip
, ~simple-rename
, ~complex-rename
, ~group-attributes-core
Important | |
---|---|
Most div references are unique. |
Caution | |
---|---|
An |
Important | |
---|---|
An |
Important | |
---|---|
A |
Caution | |
---|---|
Any range in either an |
Caution | |
---|---|
In adjustment actions involving |
Important | |
---|---|
At least one |
Example 12.73. @n
<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 |
Definition 1
The attribute new
provides the new name for an @n
that is to be renamed.
Definition 2
The attribute new
provides the new ref for a <div>
that is to be renamed.
Used by: ~simple-rename
, ~complex-rename
Caution | |
---|---|
|
Example 12.74. @new
<adjustments src="ger">
<skip div-type="Gedicht"/>
<rename ref="1 e" new="4"/>
</adjustments>
Note | |
---|---|
Taken from ringoroses.01+03.token.2 |
The attribute object
takes one or more ID refs of vocabulary items that serve as the grammatical object of a claim. For example, if you wish to say that work A is a commentary on work B, then @object
would have the ID ref for work B. @object
is used for simple idrefs. For complex objects such as data content or textual references you must use <object>
.
Multiple values of @object
are interpreted to mean "and", resulting in distribution of the claim. E.g., object="X Y" means the claim is true about X and about Y.
In RDF, the concept of object (the third element of a triple) is required. In TAN, the object is not required, since some <verb>
s may be intransitive (e.g., "Charlie slept.").
The sequence of multiple values of @object
are immaterial.
Takes IDrefs to vocabulary items <algorithm>
, <organization>
, <person>
, <work>
, <version>
, <scriptum>
, <topic>
, <source>
, <claim>
Used by: ~body-content-non-class-2
, ~element-claim
, ~object
Caution | |
---|---|
Every idref in an attribute must point to a vocabulary item (by |
Caution | |
---|---|
All idrefs in an attribute must be unique. |
Caution | |
---|---|
Multiple idrefs in a single attribute should not point to the same entity. |
Example 12.75. @object
<TAN-A TAN-version="2021" id="tag:parkj@textalign.net,2015:ar.cat.tan-a:claims"> ......... <body claimant="park" claim-period="per2010s"> ......... <claim subject="andronicus boethus" adverb="perhaps" verb="om" xml:id="cl1a2a" claim-when="2017-03-10" claimant="park"> ......... </claim> <claim subject="δ π" verb="shows" object="cl1a2a"/> <claim subject="comm-omnes" verb="attests" period="late_antiquity"> ......... </claim> <claim subject="comm-omnes" verb="attests" xml:id="cl1a2b"> ......... </claim> <claim subject="π" verb="shows" object="cl1a2b"/> <comment when="2017-03-10" who="park">The next three claims assert that the reading, ἀποδιδῷ τις, is attested to by π α φ ο but B transposes the words, and perhaps Boethius does as well. The claim sticks close to M-P's syntax, and does not fill in statements he would expect an intelligent reader to supply, e.g., that the claim is not that Boethius's translation perhaps transposed the words, but that Boethius was perhaps following one or more Greek manuscripts that did.</comment> ......... <claim verb="refers-to"> ......... </claim> <claim subject="boethius" verb="wrote" object="Λ" where="Pavia"/> <claim subject="n" verb="has_length"> ......... </claim> </body> </TAN-A>
Note | |
---|---|
Taken from ar.cat.TAN-A.claims |
Example 12.76. @object
<body claimant="park">
<claim verb="concerns" object="predication">
<subject src="grc" ref="1 1"/>
</claim>
</body>
Note | |
---|---|
Taken from ar.cat.TAN-A |
The attribute pattern
specifies a regular expression pattern to be searched for or matched. TAN regular expressions support the special escape character \u{}.
For more see the section called “Regular expressions” and https://www.w3.org/TR/xpath-functions-30/#regex-syntax
Used by: ~element-replace
, ~element-token-definition
Example 12.77. @pattern
<adjustments>
.........
<normalization>
.........
</normalization>
<replace pattern="--" replacement="—" flags="i"/>
</adjustments>
Note | |
---|---|
Taken from gomme.1989.ring-o-roses |
Example 12.78. @pattern
<head>
.........
<numerals priority="letters"/>
<token-definition src="fra" pattern="\S+"/>
<source xml:id="grc">
.........
</source>
.........
</head>
Note | |
---|---|
Taken from ar.cat.TAN-A |
Example 12.79. @pattern
<head>
.........
<license which="by_4.0" licensor="park"/>
<token-definition src="eng-us" pattern="[-\w]+"/>
<source xml:id="eng-uk">
.........
</source>
.........
</head>
Note | |
---|---|
Taken from ringoroses.div.1 |
Example 12.80. @pattern
<head>
.........
<license licensor="kalvesmaki">
.........
</license>
<token-definition pattern="[\w]+"/>
<inclusion xml:id="rel">
.........
</inclusion>
.........
</head>
Note | |
---|---|
Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-A-lm-sample |
The attribute period
names via idrefs one or more <period>
s.
Takes IDrefs to vocabulary items <period>
Used by: ~element-claim
, ~element-resp
Caution | |
---|---|
Every idref in an attribute must point to a vocabulary item (by |
Caution | |
---|---|
All idrefs in an attribute must be unique. |
Caution | |
---|---|
Multiple idrefs in a single attribute should not point to the same entity. |
Example 12.81. @period
<body claimant="park" claim-period="per2010s">
.........
<claim subject="δ π" verb="shows" object="cl1a2a"/>
<claim subject="comm-omnes" verb="attests" period="late_antiquity">
<object src="grc" ref="1 a 2">
.........
</object>
</claim>
<claim subject="comm-omnes" verb="attests" xml:id="cl1a2b">
.........
</claim>
.........
</body>
Note | |
---|---|
Taken from ar.cat.TAN-A.claims |
Definition 1
The attribute pos
lists one or more items by position, specified through Arabic numerals or the keywords 'last' or 'last-X' (where X is a valid number), joined with commas or hyphens.
Examples: '1', 'last', 'last-3 - last-1', '1, 3, 5, 7 - 11, last-8, last'
For more see the section called “Referencing tokens: @pos and @val”
Definition 2
The attribute pos
lists the position of one item, specified through Arabic numerals and the keyword 'last' or 'last-X' (where X is a valid number).
Examples: '1', 'last', 'last-3 - last-1'
For more see the section called “Referencing tokens: @pos and @val”
Used by: ~tok-selector-attributes-one
, ~tok-selector-attributes-many
Caution | |
---|---|
Sequences may not include values less than 1. |
Caution | |
---|---|
Sequences may not include values greater than the maximum allowed. |
Caution | |
---|---|
Ranges in sequences must go from a lesser value to a greater. |
Caution | |
---|---|
Every token must be locatable in every cited ref in every source. |
Example 12.82. @pos
<TAN-A TAN-version="2021" id="tag:parkj@textalign.net,2015:ar.cat.tan-a:claims"> ......... <body claimant="park" claim-period="per2010s"> ......... <claim subject="andronicus boethus" adverb="perhaps" verb="om" xml:id="cl1a2a" claim-when="2017-03-10" claimant="park"> <at-ref src="grc" ref="1 a 2"> <tok pos="3-4"/> </at-ref> </claim> ......... <claim subject="comm-omnes" verb="attests" period="late_antiquity"> <object src="grc" ref="1 a 2"> <tok pos="3-4"/> </object> </claim> <claim subject="comm-omnes" verb="attests" xml:id="cl1a2b"> <object src="grc" ref="1 a 2"> <tok pos="3-4"/> </object> </claim> ......... <claim subject="B" verb="reads"> <at-ref src="grc" ref="1 a 5"> <tok pos="1-2"/> </at-ref> ......... </claim> <claim subject="Λ" adverb="perhaps" verb="reads"> <at-ref src="grc" ref="1 a 5"> <tok pos="1-2"/> </at-ref> ......... </claim> <claim subject="π α φ ο" verb="matches"> <object src="grc" ref="1 a 5"> <tok pos="1-2"/> </object> </claim> ......... </body> </TAN-A>
Note | |
---|---|
Taken from ar.cat.TAN-A.claims |
The attribute priority
specifies where a renamed div or reassigned passage should be placed relative to the target and other renamed divs or reassigned passages. The target is presumed to be a value of 0. The higher the value of @priority
, the earlier the passage is placed. Negative integers specify the material should come after the base target.
The attribute priority
specifies whether roman numerals should have interpretive priority over letter numerals. For example, should "c" be interpreted as 3 or 100? Default is roman.
Used by: <numerals>
, ~adj-element-reassign
, ~adj-element-rename
Example 12.83. @priority
<head>
.........
<version>
.........
</version>
<numerals priority="letters"/>
<source>
.........
</source>
.........
</head>
Note | |
---|---|
Taken from ring-o-roses.deu.1897-prev |
Example 12.84. @priority
<head>
.........
<version>
.........
</version>
<numerals priority="letters"/>
<source>
.........
</source>
.........
</head>
Note | |
---|---|
Taken from ring-o-roses.deu.1897 |
Example 12.85. @priority
<head>
.........
<license licensor="park">
.........
</license>
<numerals priority="letters"/>
<token-definition src="fra" pattern="\S+"/>
.........
</head>
Note | |
---|---|
Taken from ar.cat.TAN-A |
Example 12.86. @priority
<head>
.........
<license licensor="park" which="by 4.0"/>
<numerals priority="letters"/>
<source xml:id="conf">
.........
</source>
.........
</head>
Note | |
---|---|
Taken from patricius.confessio.TAN-A |
Definition 1
The attribute ref
lists references to one or more <div>
s. It consists of one or more simple references joined by commas or hyphens. A simple reference is a string value that points to a single <div>
by joining one of its values of @n
with those of its ancestors, e.g., "1 1".
Truncation is allowed. For example, 1 1 - 3 will be interpreted first as 1.1 through 1.3; if that is invalid, it will be interpeted as 1.1 through 3. Another example: '2.4 - 7, 9' and 'ii iv - vii, 9' will be treated as identical, to mean 2.4 through 2.7 and 2.9.
In a range with members of uneven depth, those complete <div>
s that are closest to the shallowest member are retrieved. For example, 2 - 4 2 2 might fetch 2, 3, 4.1, and 4.2.1, 4.2.2 (and not 4 as a whole).
For more, see the section called “Referencing textual divisions: @ref”
Definition 2
The attribute ref
refers to a single <div>
. It consists of one simple reference e.g., "1 1".
Used by: ~element-tok-for-claim-with-ref
, ~multi-source-whole-div-textual-reference
, ~single-div-partial-textual-reference
, ~adj-element-skip
, ~element-from-tok-with-ref
, ~element-passage
, ~element-to
, ~element-tok-standard
, ~element-through-tok-with-ref
, ~simple-rename
, ~complex-rename
Important | |
---|---|
If a reference to a work is not found in some sources for that work, a warning will be returned. |
Caution | |
---|---|
In a |
Caution | |
---|---|
Any range in either an |
Example 12.87. @ref
<TAN-A TAN-version="2021" id="tag:parkj@textalign.net,2015:ar.cat.tan-a:claims"> ......... <body claimant="park" claim-period="per2010s"> ......... <claim subject="andronicus boethus" adverb="perhaps" verb="om" xml:id="cl1a2a" claim-when="2017-03-10" claimant="park"> <at-ref src="grc" ref="1 a 2"> <tok pos="3-4"/> </at-ref> </claim> ......... <claim subject="comm-omnes" verb="attests" period="late_antiquity"> <object src="grc" ref="1 a 2"> <tok pos="3-4"/> </object> </claim> <claim subject="comm-omnes" verb="attests" xml:id="cl1a2b"> <object src="grc" ref="1 a 2"> <tok pos="3-4"/> </object> </claim> ......... <claim subject="B" verb="reads"> <at-ref src="grc" ref="1 a 5"> <tok pos="1-2"/> </at-ref> <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 attribute ref-alias
contains one or more supplemental references to a <div>
. Each reference must have the same number of @n
values as the <div>
is deep in the body hierarchy. Each atomic @n
value inherits the corresponding div type. For example, in <div type="letter" n="1"> <div type="section" n="1" ref-alias="3 4">text</div> </div> the @ref-alias
ensures that the innermost <div>
is assigned both 1 1 and 3 4 as references, each typed to letter, section. The values of @ref-alias
are strongly inheritable by any children <div>
s.
This feature is intended for parts of a transcription that correspond to more than one section of a work.
Used by: ~element-div
Caution | |
---|---|
Each value in |
Example 12.88. @ref-alias
<div n="43" type="letter">
<div n="3" type="section" ref-alias="59 3">Ἦν ὅτε οὐκ ἦν κακία καὶ ἔσται ὅτε οὐκ ἔσται· οὐκ ἦν δὲ ὅτε οὐκ ἦν
ἀρετή, οὐδὲ ἔσται ὅτε οὐκ ἔσται· ἀνεξάλειπτα γὰρ τὰ σπέρματα τῆς ἀρετῆς. Πείθει δέ με
καὶ οὗτος παρ' ὀλίγον καὶ οὐ τελείως ἐν παντὶ κακῷ γεγονὼς καὶ ὁ πλούσιος ἐν τῷ ᾅδῃ διὰ
κακίαν κρινόμενος καὶ οἰκτείρων τοὺς ἀδελφούς. Τὸ δὲ ἐλεεῖν σπέρμα τυγχάνει τὸ κάλλιστον
τῆς ἀρετῆς.</div>
</div>
Note | |
---|---|
Taken from cpg2437.43.grc.1987.gehin |
The attribute relationship
names via idrefs one or more <relationship>
s
Takes IDrefs to vocabulary items <relationship>
Used by: ~link-element-see-also
Caution | |
---|---|
Every idref in an attribute must point to a vocabulary item (by |
Caution | |
---|---|
All idrefs in an attribute must be unique. |
Caution | |
---|---|
Multiple idrefs in a single attribute should not point to the same entity. |
Example 12.89. @relationship
<head>
.........
<model>
.........
</model>
<see-also relationship="alt">
<IRI>tag:kalvesmaki.com,2014:tan-t:ar.cat.grc.1949.minio-paluello:object-refs</IRI>
<name>Categories, Aristotle, Greek text by Minio-Paluello</name>
<location href="ar.cat.grc.1949.minio-paluello.ref-scriptum.xml" accessed-when="2016-02-11T12:40:42.823-05:00"/>
</see-also>
<redivision>
.........
</redivision>
.........
</head>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-logical |
Example 12.90. @relationship
<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 attribute replacement
contains a string used to replace any occurrence of @pattern
Used by: ~element-replace
Example 12.91. @replacement
<adjustments>
.........
<normalization>
.........
</normalization>
<replace pattern="--" replacement="—" flags="i"/>
</adjustments>
Note | |
---|---|
Taken from gomme.1989.ring-o-roses |
The attribute reuse-type
points via idrefs to one or more reuse-types. Multiple values are combinatory.
This attribute is weakly inheritable. See the section called “Attribute inheritability and priority”
Takes IDrefs to vocabulary items <reuse-type>
Used by: ~body-attributes-non-core
, ~element-align
Caution | |
---|---|
Every idref in an attribute must point to a vocabulary item (by |
Caution | |
---|---|
All idrefs in an attribute must be unique. |
Caution | |
---|---|
Multiple idrefs in a single attribute should not point to the same entity. |
Example 12.92. @reuse-type
<TAN-A-tok TAN-version="2021" id="tag:parkj@textalign.net,2015:TAN-A-tok,ring01+ring02">
<head>
.........
</head>
<body bitext-relation="B-descends-from-A" reuse-type="adaptation">
<align>
.........
</align>
<align>
.........
</align>
<align>
.........
</align>
.........
</body>
</TAN-A-tok>
Note | |
---|---|
Taken from ringoroses.01+02.token.1 |
Example 12.93. @reuse-type
<TAN-A-tok TAN-version="2021" id="tag:parkj@textalign.net,2015:TAN-A-tok,ring01+ring03">
<head>
.........
</head>
<body reuse-type="correlationGeneral" bitext-relation="unclear" claimant="xslt2">
<align>
.........
</align>
<align>
.........
</align>
<align>
.........
</align>
.........
</body>
</TAN-A-tok>
Note | |
---|---|
Taken from ringoroses.01+03.token.1 |
Example 12.94. @reuse-type
<TAN-A-tok TAN-version="2021" id="tag:parkj@textalign.net,2015:TAN-A-tok,ring01+ring03:alt">
<head>
.........
</head>
<body reuse-type="correlationGeneral" bitext-relation="unclear" claimant="xslt2">
<align>
.........
</align>
<align>
.........
</align>
<align>
.........
</align>
.........
</body>
</TAN-A-tok>
Note | |
---|---|
Taken from ringoroses.01+03.token.2 |
The attribute rgx
contains a regular expression. In the context of <tok>
it is an alternative to @val
and points to a particular word token according to a match on its string value. Values of @rgx
are case-sensitive. The TAN extension character class \u{} may be used.
For more see the section called “Referencing tokens: @pos and @val”
Used by: ~element-tok-abstract
, ~tok-selector-attributes-one
, ~tok-selector-attributes-many
Caution | |
---|---|
Attributes that take regular expressions must use escape sequences recognized by XML schema or TAN escape extensions (\u{}). See |
Caution | |
---|---|
Every token must be locatable in every cited ref in every source. |
Example 12.95. @rgx
<align>
<tok src="eng" ref="4" val="all"/>
<tok src="ger" ref="4" rgx="alle"/>
</align>
Note | |
---|---|
Taken from ringoroses.01+03.token.2 |
The attribute roles
refers via idrefs one or more <role>
s
Takes IDrefs to vocabulary items <role>
Used by: ~element-resp
Caution | |
---|---|
Every idref in an attribute must point to a vocabulary item (by |
Caution | |
---|---|
All idrefs in an attribute must be unique. |
Caution | |
---|---|
Multiple idrefs in a single attribute should not point to the same entity. |
Example 12.96. @roles
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2021"> <head> ......... <file-resp who="kalvesmaki"/> <resp who="xslt2" roles="stylesheet1"/> <resp roles="editor" who="kalvesmaki"/> <resp who="xslt1" roles="stylesheet1"/> <change when="2020-12-31" who="kalvesmaki">Added new reference-system declaration.</change> ......... </head> ......... </TAN-T>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-logical |
Example 12.97. @roles
<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 attribute scriptum
points to one or more ID refs of vocabulary items that are scripta (text-bearing objects).
Multiple values of @scriptum
are interpreted to mean "and", resulting in distribution of the claim.
The sequence of multiple values of @scriptum
is immaterial.
The attribute scriptum
points to a text-bearing object that forms the basis of the reference system. The reference system must be the primary one used in the scriptum for the type indicated, material or logical. Many scripta have both a primary material system (e.g., pages, columns, lines) as well as a logical one (e.g., chapters, sections, paragraphs).
Takes IDrefs to vocabulary items <scriptum>
Used by: ~scriptum-reference
, ~element-reference-system
Example 12.98. @scriptum
<head>
.........
<work>
.........
</work>
<reference-system type="material" wf-ready="true" scriptum="bekker"/>
<source>
.........
</source>
.........
</head>
Note | |
---|---|
Taken from ar.cat.grc.1949.minio-paluello.ref-scriptum |
The attribute shallow
indicates whether skipping should be done shallowly (default) or deeply
Used by: ~adj-element-skip
Example 12.99. @shallow
<adjustments src="fra">
<skip div-type="summ" shallow="false"/>
<equate n="ti title"/>
.........
</adjustments>
Note | |
---|---|
Taken from ar.cat.TAN-A |
Definition 1
The attribute src
refers via idref to only one <source>
Definition 2
The attribute src
refers via idrefs to one or more <source>
s
Takes IDrefs to vocabulary items <source>
Used by: ~multi-source-whole-div-textual-reference
, ~single-source-partial-div-textual-reference
, ~token-definition-attributes
, ~action-condition-attributes
, ~tok-sources-ref-opt
Caution | |
---|---|
Every idref in an attribute must point to a vocabulary item (by |
Caution | |
---|---|
All idrefs in an attribute must be unique. |
Caution | |
---|---|
Multiple idrefs in a single attribute should not point to the same entity. |
Example 12.100. @src
<TAN-A TAN-version="2021" id="tag:parkj@textalign.net,2015:ar.cat.tan-a:claims"> <head> ......... <license licensor="park"> ......... </license> <token-definition src="*" which="letters only"/> <vocabulary> ......... </vocabulary> ......... </head> <body claimant="park" claim-period="per2010s"> ......... <claim subject="andronicus boethus" adverb="perhaps" verb="om" xml:id="cl1a2a" claim-when="2017-03-10" claimant="park"> <at-ref src="grc" ref="1 a 2"> <tok pos="3-4"/> </at-ref> </claim> ......... <claim subject="comm-omnes" verb="attests" period="late_antiquity"> <object src="grc" ref="1 a 2"> <tok pos="3-4"/> </object> </claim> <claim subject="comm-omnes" verb="attests" xml:id="cl1a2b"> <object src="grc" ref="1 a 2"> <tok pos="3-4"/> </object> </claim> ......... </body> </TAN-A>
Note | |
---|---|
Taken from ar.cat.TAN-A.claims |
Used by: <collection>
Example 12.101. @stable
<collection stable="true" metadata-resolved="false">
<doc href="ar.cat.eng.1926.edghill.ref-logical.xml" id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2021" xml:lang="eng" root="TAN-T">
.........
</doc>
<doc href="ar.cat.eng.1926.edghill.ref-scriptum.xml" id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:model-object-refs" TAN-version="2021" xml:lang="eng" root="TAN-T">
.........
</doc>
<doc href="ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949.xml" TAN-version="2021" id="tag:kalvesmaki.com,2014:tan-t:ar.cat.fra.1844.saint-hilaire:semantic-refs-realigned" xml:lang="fra" root="TAN-T">
.........
</doc>
.........
</collection>
Note | |
---|---|
Taken from catalog.tan |
Example 12.102. @stable
<collection stable="true" metadata-resolved="false">
<doc href="ar.cat.TAN-voc.xml" TAN-version="2020" id="tag:parkj@textalign.net,2015:TAN-key:ar.cat" affects-element="work" root="TAN-voc">
.........
</doc>
<doc href="park-projects.TAN-voc.xml" TAN-version="2020" id="tag:parkj@textalign.net,2015:TAN-voc:standard" root="TAN-voc">
.........
</doc>
</collection>
Note | |
---|---|
Taken from catalog.tan |
Example 12.103. @stable
<collection stable="true">
<doc href="bitext-relations.TAN-voc.xml" id="tag:textalign.net,2015:tan-voc:bitext-relation" root="TAN-voc">
.........
</doc>
<doc href="div-types.TAN-voc.xml" id="tag:textalign.net,2015:tan-voc:div-types" root="TAN-voc">
.........
</doc>
<doc href="extra/n.bible.eng.tan-voc.xml" id="tag:textalign.net,2015:tan-voc:n:eng:bible" root="TAN-voc">
.........
</doc>
.........
</collection>
Note | |
---|---|
Taken from catalog.tan |
Example 12.104. @stable
<collection stable="true">
<doc href="bitext-relations.TAN-voc.xml"/>
<doc href="catalog.tan.xml"/>
<doc href="div-types.TAN-voc.xml"/>
.........
</collection>
Note | |
---|---|
Taken from collection |
The attribute status
specifies whether an element is required by in any <claim>
that uses the <verb>
in question.
Used by: ~element-at-ref-constraint
, ~element-in-lang-constraint
, ~element-object-constraint
, ~element-period-constraint
, ~element-place-constraint
, ~element-subject-constraint
Example 12.105. @status
<sourceDesc default="false">
<bibl default="false" status="draft">
<title type="main">My Name is Patrick</title>
<title type="subtitle">The Confessio of St Patrick and his Letter to the Soldiers of
Coroticus</title>
<author>
.........
</author>
.........
</bibl>
</sourceDesc>
Note | |
---|---|
Taken from patricius.confessio.2003.eng |
Example 12.106. @status
<teiHeader> <fileDesc> ......... </fileDesc> <revisionDesc status="draft"> <change when-iso="2015-05-14T16:30:25.958-04:00" status="draft"/> </revisionDesc> </teiHeader>
Note | |
---|---|
Taken from ring-o-roses.eng.1951 |
Example 12.107. @status
<constraints> <subject status="required" item-type="person work version scriptum"/> <at-ref status="required"/> ......... </constraints>
Note | |
---|---|
Taken from ar.cat.TAN-A.claims |
The attribute subject
points to one or more ID refs of vocabulary items in <head>
that serve as the grammatical subject of a claim. @subject
within <body>
indicates the default subject(
s) for <claim>
s. @subject
is used for idrefs; data content, textual references, or complex objects must be encoded with <subject>
.
Multiple values of @subject
are interpreted to mean "and", resulting in distribution of the claim. E.g., subject="X Y" means the claim is true about X and about Y.
The sequence of multiple values is immaterial.
Takes IDrefs to vocabulary items <algorithm>
, <organization>
, <person>
, <work>
, <version>
, <scriptum>
, <topic>
, <source>
Used by: ~body-content-non-class-2
, ~element-claim
, ~subject
Caution | |
---|---|
Every idref in an attribute must point to a vocabulary item (by |
Caution | |
---|---|
All idrefs in an attribute must be unique. |
Caution | |
---|---|
Multiple idrefs in a single attribute should not point to the same entity. |
Example 12.108. @subject
<TAN-A TAN-version="2021" id="tag:parkj@textalign.net,2015:ar.cat.tan-a:claims"> ......... <body claimant="park" claim-period="per2010s"> <comment when="2017-03-10-05:00" who="park">The next two claims interpret Minio-Paluello's apparatus criticus entry for 1a2, which claims that Andronicus and Boethus might have omitted τῆς οὐσίας (based on what Porphyry and Dexippus say) and asserts that the reading adopted is found in the seven commentators. The interpretation below sticks close to M-P's original, and does not fill in important gaps. For example, Dexippus's remark comes from his commentary, 1.18 (p. 21.20) and is reliant wholly on a fragment of Porphyry preserved in Simplicius's commentary, p. 30.1-2. Furthermore, a careful reading of these texts shows that Porphyry claimed not that Andronicus and Boethus omitted the text, or relied on sources that had omitted it, but that they observed that there were manuscripts that had done so.</comment> <claim subject="andronicus boethus" adverb="perhaps" verb="om" xml:id="cl1a2a" claim-when="2017-03-10" claimant="park"> <at-ref src="grc" ref="1 a 2"> ......... </at-ref> </claim> <claim subject="δ π" verb="shows" object="cl1a2a"/> <claim subject="comm-omnes" verb="attests" period="late_antiquity"> <object src="grc" ref="1 a 2"> ......... </object> </claim> <claim subject="comm-omnes" verb="attests" xml:id="cl1a2b"> <object src="grc" ref="1 a 2"> ......... </object> </claim> <claim subject="π" verb="shows" object="cl1a2b"/> ......... </body> </TAN-A>
Note | |
---|---|
Taken from ar.cat.TAN-A.claims |
The attribute TAN-version
specifies a version of TAN.
Used by: ~TAN-root
Important | |
---|---|
TAN files using a version other than the current version will be marked with a warning. |
Important | |
---|---|
The |
Example 12.109. @TAN-version
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2021">
<head>
.........
</head>
<body xml:lang="eng">
.........
</body>
</TAN-T>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-logical |
Example 12.110. @TAN-version
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:model-object-refs" TAN-version="2021">
<head>
.........
</head>
<body xml:lang="eng">
.........
</body>
</TAN-T>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-scriptum |
Example 12.111. @TAN-version
<TAN-T TAN-version="2021" id="tag:kalvesmaki.com,2014:tan-t:ar.cat.fra.1844.saint-hilaire:semantic-refs-realigned">
<head>
.........
</head>
<body xml:lang="fra">
.........
</body>
</TAN-T>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949 |
Example 12.112. @TAN-version
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.fra.1844.saint-hilaire:semantic-refs" TAN-version="2021">
<head>
.........
</head>
<body xml:lang="fra">
.........
</body>
</TAN-T>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.ref-logical |
The attribute to
specifies the end of a period of time.
Used by: <period>
Caution | |
---|---|
Future dates are not permitted. |
Example 12.113. @to
<vocabulary-key>
.........
<role xml:id="creator">
.........
</role>
<period xml:id="per2010s" from="2010-01-01" to="2019-12-31"/>
<period xml:id="late-antiquity">
.........
</period>
.........
</vocabulary-key>
Note | |
---|---|
Taken from ar.cat.TAN-A.claims |
The attribute tok-matches
takes a regular expression. When validating a given <m>
, a test will be made against each companion <tok>
(i.e., those <tok>
s that have the same ancestral <ana>
). The condition will be treated as true only for those matches with the resolved token value.
This is one of four tests for determining whether to process a <report>
or <assert>
Used by: ~action-condition-attributes
Example 12.114. @tok-matches
<TAN-mor TAN-version="2021" id="tag:kalvesmaki.com,2014:tan-r-mor:eng:penn"> ......... <body> ......... <rule> <where m-has-codes="$"/> <assert tok-matches="$">Only $ may be tagged as a dollar sign.</assert> </rule> <rule m-has-codes="'' . ; :"> <report tok-matches="\w">Nothing marked as punctuation should have word characters.</report> </rule> ......... </body> </TAN-mor>
Note | |
---|---|
Taken from eng.kalvesmaki.com,2014.2 |
The attribute tok-pop
specifies the quantity of tokens that are the subject of the <ana>
. This attribute is useful for language-specific TAN-A-lm files, where the total number of tokens that formed the set might be lost. It is also useful for calculating the relative probability of token-to-lm combinations.
This attribute is weakly inheritable. See the section called “Attribute inheritability and priority”
Used by: ~element-ana
Example 12.115. @tok-pop
<body lexicon="LSJ Lampe new" morphology="Perseus" claimant="xslt2">
<ana tok-pop="2">
<tok ref="11 2 1 1" pos="1"/>
<lm>
.........
</lm>
</ana>
<ana>
.........
</ana>
.........
</body>
Note | |
---|---|
Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-A-lm-sample |
The attribute type
declares the main type of reference system is being used: material (based on the material features of a scriptum, e.g., page, column, line) or logical (e.g., chapter, paragraph, stanza). This is evaluated primarily against the top level of the reference system
The attribute type
indicates the type of its parent element. In the context of <div>
it specifies a type of textual unit, identified by a <div-type>
. In the context of <group>
it specifies a kind of group identified by a <group-type>
. In the context of <category>
it specifies a kind of grammatical feature identified by <feature>
.
Takes IDrefs to vocabulary items <div-type>
, <group-type>
, <feature>
Used by: ~element-div
, ~element-reference-system
, ~group-attributes-core
Caution | |
---|---|
Every idref in an attribute must point to a vocabulary item (by |
Caution | |
---|---|
All idrefs in an attribute must be unique. |
Caution | |
---|---|
Multiple idrefs in a single attribute should not point to the same entity. |
Example 12.116. @type
<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 attribute units
points to the ID ref of a <unit>
, identifying the type of unit.
Takes IDrefs to vocabulary items <unit>
, <div-type>
Used by: ~nontextual-reference
Caution | |
---|---|
Every idref in an attribute must point to a vocabulary item (by |
Caution | |
---|---|
All idrefs in an attribute must be unique. |
Caution | |
---|---|
Multiple idrefs in a single attribute should not point to the same entity. |
Caution | |
---|---|
Claims involving verbs whose constrained content requires specification of units must use |
Example 12.117. @units
<claim subject="n" verb="has_length">
<object units="folio">160</object>
</claim>
Note | |
---|---|
Taken from ar.cat.TAN-A.claims |
The attribute val
contains a string that points to a word token by its value. Matches are case-, space-, and accent-sensitive.
For more see the section called “Referencing tokens: @pos and @val”
Used by: ~element-tok-abstract
, ~tok-selector-attributes-one
, ~tok-selector-attributes-many
Caution | |
---|---|
Every token must be locatable in every cited ref in every source. |
Example 12.118. @val
<reassign> <passage ref="5 4 7 2"> <from-tok val=":" pos="1"/> <through-tok val=":" pos="1"/> </passage> ......... </reassign>
Note | |
---|---|
Taken from ar.cat.TAN-A |
Example 12.119. @val
<body lexicon="LSJ" morphology="perseus-dik" claimant="xslt2"> <ana> <tok val="Α" cert="0.2"/> <tok val="α" cert="0.083333333333333333"/> <tok val="ἆ"/> ......... </ana> <ana> <tok val="α" cert="0.083333333333333333"/> <tok val="ἁ"/> ......... </ana> ......... <ana> <tok val="α" cert="0.083333333333333333"/> <tok val="ᾇ"/> ......... </ana> <ana> <tok val="α" cert="0.083333333333333333"/> <tok val="ἃ" cert="0.142857142857142857"/> ......... </ana> ......... <ana> <tok val="ά"/> <tok val="α" cert="0.083333333333333333"/> <tok val="ὰ"/> ......... </ana> </body>
Note | |
---|---|
Taken from grc-tan-a-lm-%CE%B1 |
The attribute verb
points to one or more <verb>
s that serve to assert something of the subject.
The TAN term "verb" is the preferred equivalent to RDF "predicate."
Multiple values of @verb
are interpreted to mean "and", resulting in distribution of the claim. E.g., verb="X Y" means the claim is true for verb X and verb Y. Any claim with multiple verbs must observe the constraints of each verb.
Takes IDrefs to vocabulary items <verb>
Used by: ~body-content-non-class-2
, ~element-claim
Caution | |
---|---|
Every idref in an attribute must point to a vocabulary item (by |
Caution | |
---|---|
All idrefs in an attribute must be unique. |
Caution | |
---|---|
Multiple idrefs in a single attribute should not point to the same entity. |
Caution | |
---|---|
Every |
Caution | |
---|---|
Every |
Caution | |
---|---|
No |
Example 12.120. @verb
<TAN-A TAN-version="2021" id="tag:parkj@textalign.net,2015:ar.cat.tan-a:claims"> ......... <body claimant="park" claim-period="per2010s"> <comment when="2017-03-10-05:00" who="park">The next two claims interpret Minio-Paluello's apparatus criticus entry for 1a2, which claims that Andronicus and Boethus might have omitted τῆς οὐσίας (based on what Porphyry and Dexippus say) and asserts that the reading adopted is found in the seven commentators. The interpretation below sticks close to M-P's original, and does not fill in important gaps. For example, Dexippus's remark comes from his commentary, 1.18 (p. 21.20) and is reliant wholly on a fragment of Porphyry preserved in Simplicius's commentary, p. 30.1-2. Furthermore, a careful reading of these texts shows that Porphyry claimed not that Andronicus and Boethus omitted the text, or relied on sources that had omitted it, but that they observed that there were manuscripts that had done so.</comment> <claim subject="andronicus boethus" adverb="perhaps" verb="om" xml:id="cl1a2a" claim-when="2017-03-10" claimant="park"> <at-ref src="grc" ref="1 a 2"> ......... </at-ref> </claim> <claim subject="δ π" verb="shows" object="cl1a2a"/> <claim subject="comm-omnes" verb="attests" period="late_antiquity"> <object src="grc" ref="1 a 2"> ......... </object> </claim> <claim subject="comm-omnes" verb="attests" xml:id="cl1a2b"> <object src="grc" ref="1 a 2"> ......... </object> </claim> <claim subject="π" verb="shows" object="cl1a2b"/> ......... </body> </TAN-A>
Note | |
---|---|
Taken from ar.cat.TAN-A.claims |
The attribute wf-ready
specifies whether the class 1 file's reference system is suited for Writing Fragid URIs. Default is false. If @wf-ready
is true, the class 1 file can be parsed against, and be used to generate, Writing Fragid URIs. A value of true may be supplied only if the following are true:
The scriptum used for the reference system has no more than one logical and no more than one material reference system (the "key reference system," defined by the specifications for Writing Fragids, version 0).
The division of a text unit should result in a unique numbered sequence. That is, in any given enumerable text division sequence (sibling <div>
s whose values of @n
can be converted to integers or integer-qualified integers, e.g., 3b), Arabic numerals, Roman numerals, and alphabetic numerals may not be mixed.
It is permitted to divide a key reference system more finely, but only in its innermost (leafmost) structures, not at the branch or root levels.
Used by: ~element-reference-system
Example 12.121. @wf-ready
<head>
.........
<license licensor="kalvesmaki">
.........
</license>
<reference-system type="logical" wf-ready="true"/>
<work>
.........
</work>
.........
</head>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.ref-logical |
Example 12.122. @wf-ready
<head>
.........
<work>
.........
</work>
<reference-system type="logical" wf-ready="true"/>
<source>
.........
</source>
.........
</head>
Note | |
---|---|
Taken from ar.cat.grc.1949.minio-paluello.ref-logical |
Example 12.123. @wf-ready
<head>
.........
<work>
.........
</work>
<reference-system type="material" wf-ready="true" scriptum="bekker"/>
<source>
.........
</source>
.........
</head>
Note | |
---|---|
Taken from ar.cat.grc.1949.minio-paluello.ref-scriptum |
Example 12.124. @wf-ready
<head>
.........
<work>
.........
</work>
<reference-system type="material" wf-ready="true"/>
<source>
.........
</source>
.........
</head>
Note | |
---|---|
Taken from ar.cat.lat.1961.minio-paluello.ref-scriptum |
The attribute when
indicates a date or date and time
This attribute is weakly inheritable. See the section called “Attribute inheritability and priority”
Used by: ~element-change
, ~element-comment
Caution | |
---|---|
Future dates are not permitted. |
Example 12.125. @when
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2021"> <head> ......... <resp who="xslt1" roles="stylesheet1"/> <change when="2020-12-31" who="kalvesmaki">Added new reference-system declaration.</change> <change when="2016-06-22T08:04:25.003-04:00" who="kalvesmaki">Reformatted according to first model found. Backup made at file:/C:/Users/jdkalv/Dropbox/TAN/library/TAN-2018/examples/ar.cat.eng.1926.edghill.sem-201606220804250030400.xml.</change> <change when="2016-01-26-04:00" who="kalvesmaki">Started new file.</change> <change who="xslt1" when="2017-11-02T22:29:17.742-04:00">TAN file updated to 2018 schemas.</change> <change who="xslt2" when="2018-08-04T23:55:36.096-04:00">Converted from 2018 to 2019 schemas.</change> ......... </head> ......... </TAN-T>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-logical |
The attribute where
restricts the domain of a <claim>
to a specific <place>
.
Multiple values of @where
are interpreted to mean "or" with union. Unlike most other attributes for <claim>
, no distribution takes place. For example, where="X Y" means the claim occured in either X or Y or both.
The sequence of multiple values of @where
is immaterial.
Takes IDrefs to vocabulary items <place>
Used by: ~element-claim
Caution | |
---|---|
Every idref in an attribute must point to a vocabulary item (by |
Caution | |
---|---|
All idrefs in an attribute must be unique. |
Caution | |
---|---|
Multiple idrefs in a single attribute should not point to the same entity. |
Example 12.126. @where
<body claimant="park" claim-period="per2010s">
.........
<claim verb="refers-to">
.........
</claim>
<claim subject="boethius" verb="wrote" object="Λ" where="Pavia"/>
<claim subject="n" verb="has_length">
.........
</claim>
</body>
Note | |
---|---|
Taken from ar.cat.TAN-A.claims |
The attribute which
points to a single vocabulary item. Reference is made either via idref or <name>
. Because this attribute points to only one vocabulary item, spaces are permitted, if using a vocabulary's <name>
. Before evaluation @which
will be name-normalized: spaces, hyphens, and underscores will be treated as identical, and text will be rendered lowercase.
Used by: ~element-token-definition
, ~entity-digital-core-content
, ~entity-nondigital-content
, ~entity-nondigital-with-constraints-content
Caution | |
---|---|
An element's |
Caution | |
---|---|
A |
Example 12.127. @which
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2021"> <head> ......... <adjustments> <normalization which="no hyphens"/> </adjustments> <vocabulary-key> ......... <div-type xml:id="ic"> ......... </div-type> <div-type xml:id="pt" which="part"/> <person xml:id="kalvesmaki"> ......... </person> ......... <role xml:id="editor"> ......... </role> <role xml:id="stylesheet1" which="stylesheet"/> <relationship xml:id="alt"> ......... </relationship> </vocabulary-key> ......... </head> ......... </TAN-T>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-logical |
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-scriptum |
The attribute who
refers via idrefs to a person, organization, or algorithm.
Takes IDrefs to vocabulary items <person>
, <organization>
, <algorithm>
Used by: ~element-change
, ~element-comment
, ~element-file-resp
, ~element-resp
Caution | |
---|---|
Every idref in an attribute must point to a vocabulary item (by |
Caution | |
---|---|
All idrefs in an attribute must be unique. |
Caution | |
---|---|
Multiple idrefs in a single attribute should not point to the same entity. |
Example 12.129. @who
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2021"> <head> ......... <vocabulary-key> ......... </vocabulary-key> <file-resp who="kalvesmaki"/> <resp who="xslt2" roles="stylesheet1"/> <resp roles="editor" who="kalvesmaki"/> <resp who="xslt1" roles="stylesheet1"/> <change when="2020-12-31" who="kalvesmaki">Added new reference-system declaration.</change> ......... </head> ......... </TAN-T>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-logical |
The attribute work
refers via idrefs to one or more works. The ensuing claim(
s) will be considerd to be true of any sources that share the same work.
If you wish to avoid making a claim applying to all other versions of a work, use @src
instead.
Multiple values of @work
are interpreted to mean "and", resulting in distribution of the claim. E.g., work="X Y" means the claim is true for both work X and work Y.
Takes IDrefs to vocabulary items <source>
, <work>
Used by: ~multi-source-whole-div-textual-reference
, ~work-version-reference
Caution | |
---|---|
Every idref in an attribute must point to a vocabulary item (by |
Caution | |
---|---|
All idrefs in an attribute must be unique. |
Caution | |
---|---|
Multiple idrefs in a single attribute should not point to the same entity. |
Important | |
---|---|
If a reference to a work is not found in some sources for that work, a warning will be returned. |
Example 12.130. @work
<claim verb="refers-to">
<subject src="grc" ref="1 b 25"/>
<object work="grc" ref="1 a 16"/>
</claim>
Note | |
---|---|
Taken from ar.cat.TAN-A.claims |
Example 12.131. @work
<TAN-A TAN-version="2021" id="tag:parkj@textalign.net,2015:ring01-TAN-A-ring02"> ......... <body claimant="park"> ......... <claim verb="resembles"> <subject src="eng-uk"> ......... </subject> <object work="eng-uk" ref="3-4"/> </claim> <claim verb="quotes"> <subject work="ring" ref="1"/> <object work="ring" ref="2"/> </claim> ......... </body> </TAN-A>
Note | |
---|---|
Taken from ringoroses.div.1 |
The attribute xml:id
identifies an entity described within an element. Must be unique within a given file. Must consist only of word characters.
Used by: ~element-claim
, ~link-element-inclusion
, ~voc-element-alias
, ~voc-element-period
, ~entity-digital-nontan-id
, ~entity-digital-tan-id
, ~entity-nondigital-constrained
, ~entity-nondigital-id
Caution | |
---|---|
|
Example 12.132. @xml:id
<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"> <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"> ......... </div-type> ......... </vocabulary-key> ......... </head>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.ref-logical |
The attribute xml:lang
specifies a language code that names the language of the text enclosed by the parent element. Values are inherited by all descendants except for those that have an @xml:lang
and their descendants.
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)
Used by: ~nontextual-reference
, ~body-attributes-non-core
, ~element-div
, ~metadata-human-readable-attributes
Example 12.133. @xml:lang
<TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2021"> <head> ......... <vocabulary-key> ......... <div-type xml:id="par"> <IRI>http://dbpedia.org/resource/Paragraph</IRI> <name xml:lang="eng">paragraph</name> </div-type> ......... <person xml:id="kalvesmaki"> ......... <IRI>tag:kalvesmaki.com,2014:self</IRI> <name xml:lang="eng">Joel Kalvesmaki</name> </person> ......... <role xml:id="editor"> <IRI>http://schema.org/editor</IRI> <name xml:lang="eng">Editor</name> </role> ......... </vocabulary-key> ......... </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 |