TAN patterns, elements, and attributes defined

TAN patterns, elements, and attributes definedEach 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-T<div> <TAN-T> 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-3TAN-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

TAN attributes

<code>@accessed-when</code>TAN-core.rngThe attribute accessed-when specifies when an electronic file was last examined Used by: ~element-location, ~entity-digital-core-contentIf @accessed-when predates one or more dates in a target file, a warning will be returned.Future dates are not permitted.<code>@accessed-when</code><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> Taken from ar.cat.eng.1926.edghill.ref-logical

<code>@adverb</code>TAN-A.rngThe 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-claimEvery idref in an attribute must point to a vocabulary item (by @xml:id or name) that is of the appropriate corresponding element.All idrefs in an attribute must be unique.Multiple idrefs in a single attribute should not point to the same entity.<code>@adverb</code><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> Taken from ar.cat.TAN-A.claims

<code>@affects-attribute</code>TAN-voc.rngThe 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<code>@affects-attribute</code><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> Taken from n.bible.eng.tan-voc<code>@affects-attribute</code><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> Taken from n.bible.spa.tan-voc<code>@affects-attribute</code><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> Taken from n.quran.eng-ara.tan-voc<code>@affects-attribute</code><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> Taken from n.unlabeled-divs-1.eng.tan-voc

<code>@affects-element</code>TAN-voc.rngThe 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@affects-element may take names only of those TAN elements that accept @which@affects-element may take the value "vocabulary" only in official TAN-voc files.<code>@affects-element</code><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> Taken from ar.cat.TAN-voc<code>@affects-element</code><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> Taken from park-projects.TAN-voc

<code>@bitext-relation</code>TAN-A-tok.rngThe attribute bitext-relation points via idrefs to one or more bitext-relations. Multiple values are combinatory.This attribute is weakly inheritable. See See for standard TAN values. Takes IDrefs to vocabulary items <bitext-relation>Used by: ~body-attributes-non-core, ~element-alignEvery idref in an attribute must point to a vocabulary item (by @xml:id or name) that is of the appropriate corresponding element.All idrefs in an attribute must be unique.Multiple idrefs in a single attribute should not point to the same entity.<code>@bitext-relation</code><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> Taken from ringoroses.01+02.token.1<code>@bitext-relation</code><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> Taken from ringoroses.01+03.token.1<code>@bitext-relation</code><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> Taken from ringoroses.01+03.token.2

<code>@by</code>TAN-class-2.rngThe 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@by may be applied only to those @n and @ref values that are calculable as integers.<code>@by</code> <adjustments src="ger"> <skip div-type="Gedicht"/> <rename n="e" by="-1"/> </adjustments> Taken from ringoroses.div.1

<code>@cert</code>TAN-core.rngThe 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 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<code>@cert</code><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> Taken from grc-tan-a-lm-%CE%B1

<code>@cert2</code>TAN-core.rngThe 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<code>@cert2</code> <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> Taken from ringoroses.01+03.token.1

<code>@chars</code>TAN-class-2.rngThe 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-standardSequences may not include values less than 1.Sequences may not include values greater than the maximum allowed.Ranges in sequences must go from a lesser value to a greater.Every character must be locatable in every token in every ref in every source.<code>@chars</code> <subject src="eng-uk"> <tok ref="2" pos="2-3" chars="3-4"/> <from-tok ref="1" pos="3"/> ......... </subject> Taken from ringoroses.div.1

<code>@claim-period</code>TAN-class-2.rngThe 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<code>@claim-period</code><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> Taken from ar.cat.TAN-A.claims

<code>@claim-when</code>TAN-class-2.rngThe attribute claim-when identifies a time when a claim was made. Used by: ~claimant-attributes<code>@claim-when</code> <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> Taken from ar.cat.TAN-A.claims

<code>@claimant</code>TAN-class-2.rngThe 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 Takes IDrefs to vocabulary items <person>, <organization>, <algorithm>Used by: ~claimant-attributes<code>@claimant</code><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> Taken from ar.cat.TAN-A.claims<code>@claimant</code><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> Taken from ar.cat.TAN-A<code>@claimant</code><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> Taken from patricius.confessio.TAN-A

<code>@content-datatype</code>TAN-core.rngThe 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-contentClaims involving verbs whose constrained content requires specification of units must use <object> or <subject> with @units..<object> or <subject> with @units may be used only with verbs with constrained content.A claim with a verb that has content constraints must not allow other verbs.<subject>s' and <object>s' content must be castable to any datatype constraints defined by the verb.<code>@content-datatype</code> <constraints> <subject status="required" item-type="scriptum"/> <object status="required" content-datatype="integer" content-lexical-constraint="\d+"/> </constraints> Taken from ar.cat.TAN-A.claims<code>@content-datatype</code> <constraints> <subject status="required" item-type="scriptum work version"/> <object status="required" content-datatype="string"/> <at-ref status="required"/> </constraints> Taken from verbs.TAN-voc

<code>@content-lexical-constraint</code>TAN-core.rngThe 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-contentClaims involving verbs whose constrained content requires specification of units must use <object> or <subject> with @units..<object> or <subject> with @units may be used only with verbs with constrained content.A claim with a verb that has content constraints must not allow other verbs.<subject>s' and <object>s' content must match any lexical constraints defined by the verb.<code>@content-lexical-constraint</code> <constraints> <subject status="required" item-type="scriptum"/> <object status="required" content-datatype="integer" content-lexical-constraint="\d+"/> </constraints> Taken from ar.cat.TAN-A.claims

<code>@def-ref</code>TAN-A-lm.rngThe 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<code>@def-ref</code> <lm> <l def-ref="1">εἰμί</l> <m>v c - - p n a - - -</m> </lm> Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-A-lm-sample

<code>@div-type</code>TAN-core.rngThe 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-skipEvery div type reference must be valid in every source<code>@div-type</code> <head> ......... <reference-system type="logical" wf-ready="true"/> <n-alias div-type="book"/> <work which="matthew"/> ......... </head> Taken from matt.eng.kjv.1760<code>@div-type</code> <adjustments src="fra"> <skip div-type="summ" shallow="false"/> <equate n="ti title"/> ......... </adjustments> Taken from ar.cat.TAN-A<code>@div-type</code> <adjustments src="ger"> <skip div-type="Gedicht"/> <rename n="e" by="-1"/> </adjustments> Taken from ringoroses.div.1<code>@div-type</code> <adjustments src="ger"> <skip div-type="Gedicht"/> </adjustments> Taken from ringoroses.01+03.token.1

<code>@ed-when</code>TAN-core.rngThe 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 .Along with @ed-who, this forms the Edit Stamp pattern. See This attribute is weakly inheritable. See Used by: ~ed-stampFuture dates are not permitted.<code>@ed-when</code> <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> Taken from ring-o-roses.eng.1987<code>@ed-when</code> <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> Taken from ring-o-roses.eng.1881.lm<code>@ed-when</code> <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> Taken from eng.kalvesmaki.com,2014.2<code>@ed-when</code> <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> Taken from grc.perseus.tan-mor

<code>@ed-who</code>TAN-core.rngThe 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 This attribute is weakly inheritable. See Takes IDrefs to vocabulary items <person>, <organization>, <algorithm>Used by: ~ed-stampEvery idref in an attribute must point to a vocabulary item (by @xml:id or name) that is of the appropriate corresponding element.All idrefs in an attribute must be unique.Multiple idrefs in a single attribute should not point to the same entity.<code>@ed-who</code> <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> Taken from ring-o-roses.eng.1987<code>@ed-who</code> <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> Taken from ring-o-roses.eng.1881.lm<code>@ed-who</code> <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> Taken from eng.kalvesmaki.com,2014.2<code>@ed-who</code> <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> Taken from grc.perseus.tan-mor

<code>@exceptions</code>TAN-core.rngThe 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 numeralExpected 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>

<code>@feature</code>TAN-mor.rng Takes IDrefs to vocabulary items <feature>Used by: ~element-category, ~element-codeEvery idref in an attribute must point to a vocabulary item (by @xml:id or name) that is of the appropriate corresponding element.All idrefs in an attribute must be unique.Multiple idrefs in a single attribute should not point to the same entity.Codes for features must be case-indifferently unique.<code>@feature</code><TAN-mor TAN-version="2021" id="tag:kalvesmaki.com,2014:tan-r-mor:eng:penn"> ......... <body> ......... <rule m-has-codes="'' . ; :"> ......... </rule> <code feature="closing_quotation_mark"> <desc>Examples: ' ''</desc> <val>''</val> </code> <code feature="dash"> <desc>Example: --</desc> <val>--</val> </code> <code feature="dollar"> <desc>Examples: Examples: $ -$ --$ A$ C$ HK$ M$ NZ$ S$ U.S.$ US$</desc> <val>$</val> </code> <code feature="opening_parenthetical_punctuation"> <desc>Examples: ( [ {</desc> <val>[</val> </code> <code feature="closing_parenthetical_punctuation"> ......... </code> ......... </body> </TAN-mor> Taken from eng.kalvesmaki.com,2014.2

<code>@flag</code>TAN-core.rngThe 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<code>@flag</code> <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> Taken from ring-o-roses.eng.1951

<code>@flags</code>TAN-core.rngThe 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/#flagsThis attribute is non-inheritable. Used by: ~element-replace, ~element-token-definition<code>@flags</code> <adjustments> ......... <normalization> ......... </normalization> <replace pattern="--" replacement="—" flags="i"/> </adjustments> Taken from gomme.1989.ring-o-roses

<code>@from</code>TAN-core.rngThe attribute from specifies the beginning of a period of time. Used by: <period>Future dates are not permitted.@from must predate @to<code>@from</code> <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> Taken from ar.cat.TAN-A.claims

<code>@group</code>TAN-core.rngThe 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-itemEvery idref in an attribute must point to a vocabulary item (by @xml:id or name) that is of the appropriate corresponding element.All idrefs in an attribute must be unique.Multiple idrefs in a single attribute should not point to the same entity.<code>@group</code> <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> Taken from div-types.TAN-voc

<code>@href</code>catalog.tan.rng TAN-core.rngThe 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@href must have <location> or <master-location> as a parent; any other parent will trigger a quick fix to populate the element with the IRI + name pattern of the target file.If an @href points to a local file that is not available, a warning will be returned. @href points to file that is either (1) not available or (2) not valid XMLIf an @href points to a file that is not local, and no internet is available, a warning will be returned. No internet access.If the internet is available, and an @href points to a non-local file that is not available, a warning will be returned. @href points to non-local file that is either (1) not available, (2) not valid XML, or (3) at a server not trusted by the validation engine.The only @href in a TAN document that may point to another document with the same document id is that of <master-location> or <see-also>No @href should point to the URI of the document itself.An @href that points to a local drive should have "file:/" prepended.No <master-location> may have an @href that points to a compressed archive.Every @href in a catalog.tan.xml file must point to a document that is available.@href values in catalog.tan.xml should be unique<code>@href</code><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> Taken from ar.cat.eng.1926.edghill.ref-logical

<code>@id</code>catalog.tan.rngDefinition 1Definition 2 TAN-core.rngDefinition 1The attribute id provides a unique identifier for an <alias>. Must be unique within a given file. Must consist only of non-spacing characters.Definition 2The attribute id contains a tag URN that permanently and uniquely names the current file.For more on the syntax of tag URNs see Used by: <collection>, <doc>, ~voc-element-alias, ~TAN-rootEvery TAN file must have at least one organization or person with an <IRI> that is a tag URI whose namespace matches the namespaces of @id in the root element.@xml:id values may not be repeated in the same document.An @xml:id on a vocabulary item need not duplicate a <name> (except in a TAN-mor file).In a catalog.tan.xml, @id should match the target's root element @idDifferent TAN files should have unique @ids..If a local catalog.tan.xml file lacks a reference to a TAN file being validated, a warning will appear.<code>@id</code><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> Taken from ar.cat.eng.1926.edghill.ref-logical<code>@id</code><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> Taken from ar.cat.eng.1926.edghill.ref-scriptum<code>@id</code><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> Taken from ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949<code>@id</code><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> Taken from ar.cat.fra.1844.saint-hilaire.ref-logical

<code>@idrefs</code>TAN-core.rngThe attribute idrefs contains references to one or more values of @xml:id or @id in the file Used by: ~voc-element-alias<alias> references must not be circular.Every value in @idrefs must correspond to an @id or @xml:id in the file.<code>@idrefs</code> <vocabulary-key> ......... <div-type xml:id="v" which="verse (scripture)"/> <alias xml:id="test" idrefs="ch v"/> </vocabulary-key> Taken from matt.eng.kjv.1760<code>@idrefs</code> <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> Taken from ar.cat.TAN-A.claims

<code>@in-lang</code>TAN-A.rngThe 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<code>@in-lang</code> <body claimant="park"> ......... <claim verb="lacks_text" subject="böhme"> ......... </claim> <claim subject="ger" verb="translates" object="eng-uk" in-lang="deu"/> </body> Taken from ringoroses.div.1

<code>@include</code>TAN-core.rngThe 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: ~inclusionEvery idref in an attribute must point to a vocabulary item (by @xml:id or name) that is of the appropriate corresponding element.All idrefs in an attribute must be unique.Multiple idrefs in a single attribute should not point to the same entity.For any element with @include, at least one element of the same name must be found in target inclusion document.Inclusions are integral parts of any TAN file. Access to at least one copy is absolutely mandatory.<code>@include</code> <body xml:lang="eng"> ......... <div n="4" type="ch"> ......... </div> <div include="serm-mount"/> <div n="8" type="ch"> ......... </div> ......... </body> Taken from matt.eng.kjv.1760<code>@include</code> <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> Taken from sermon-on-the-mount.eng.kjv.1760<code>@include</code><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> Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-A-lm-sample

<code>@item-type</code>TAN-core.rngThe 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<code>@item-type</code> <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> Taken from ar.cat.TAN-A.claims

<code>@lexicon</code>TAN-A-lm.rngThe attribute lexicon points via idrefs to one or more lexicons, persons, organizations, or algorithms.This attribute is weakly inheritable. See Takes IDrefs to vocabulary items <lexicon>Used by: ~group-attributes-non-core, ~body-attributes-non-core, ~element-ana, ~element-l, ~element-lmEvery idref in an attribute must point to a vocabulary item (by @xml:id or name) that is of the appropriate corresponding element.All idrefs in an attribute must be unique.Multiple idrefs in a single attribute should not point to the same entity.<code>@lexicon</code><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> Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-A-lm-sample<code>@lexicon</code><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> Taken from grc-tan-a-lm-%CE%B1<code>@lexicon</code><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> Taken from grc-tan-a-lm-%CE%B1%CA%B9<code>@lexicon</code><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> Taken from ring-o-roses.eng.1881.lm

<code>@licensor</code>TAN-core.rngThe 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 Takes IDrefs to vocabulary items <person>, <organization>Used by: ~element-licenseEvery idref in an attribute must point to a vocabulary item (by @xml:id or name) that is of the appropriate corresponding element.All idrefs in an attribute must be unique.Multiple idrefs in a single attribute should not point to the same entity.<code>@licensor</code> <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> Taken from ar.cat.eng.1926.edghill.ref-logical<code>@licensor</code> <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> Taken from ar.cat.eng.1926.edghill.ref-scriptum<code>@licensor</code> <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> Taken from ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949<code>@licensor</code> <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> Taken from ar.cat.fra.1844.saint-hilaire.ref-logical

<code>@m-has-codes</code>TAN-mor.rngThe 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<code>@m-has-codes</code><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> Taken from eng.kalvesmaki.com,2014.2

<code>@m-has-how-many-codes</code>TAN-mor.rngThe 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<code>@m-has-how-many-codes</code> <rule m-matches=".+"> <assert m-has-how-many-codes="1">Features may not be combined.</assert> </rule> Taken from eng.kalvesmaki.com,2014.2<code>@m-has-how-many-codes</code> <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> Taken from grc.perseus.tan-mor

<code>@m-matches</code>TAN-mor.rngThe 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<code>@m-matches</code> <body> <rule m-matches=".+"> <assert m-has-how-many-codes="1">Features may not be combined.</assert> </rule> <rule> ......... </rule> ......... </body> Taken from eng.kalvesmaki.com,2014.2<code>@m-matches</code> <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> Taken from grc.perseus.tan-mor

<code>@metadata-resolved</code>catalog.tan.rng Used by: <collection><code>@metadata-resolved</code><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> Taken from catalog.tan<code>@metadata-resolved</code><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> Taken from catalog.tan

<code>@morphology</code>TAN-A-lm.rngThe attribute morphology points to one or more <morphology> IDsThis attribute is inheritable. See Takes IDrefs to vocabulary items <morphology>Used by: ~group-attributes-non-core, ~body-attributes-non-core, ~element-ana, ~element-lm, ~element-mEvery idref in an attribute must point to a vocabulary item (by @xml:id or name) that is of the appropriate corresponding element.All idrefs in an attribute must be unique.Multiple idrefs in a single attribute should not point to the same entity.<code>@morphology</code><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> Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-A-lm-sample<code>@morphology</code><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> Taken from grc-tan-a-lm-%CE%B1<code>@morphology</code><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> Taken from grc-tan-a-lm-%CE%B1%CA%B9<code>@morphology</code><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> Taken from ring-o-roses.eng.1881.lm

<code>@n</code>TAN-core.rngThe 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 .Extra TAN vocabulary is available for @n, to provide built-in aliases. For more on this feature see . For specific extra vocabulary see Used by: ~element-div, ~adj-element-equate, ~adj-element-skip, ~simple-rename, ~complex-rename, ~group-attributes-coreMost div references are unique.An @n taking digit values should not begin with 0.An @n's value should not appear in the text.A <div>'s reference (self and ancestor @ns, concatenated) should not appear in the text.Any range in either an @n or in a @ref in an adjustment action must be predictably calculated.In adjustment actions involving @n, at least one value should be found in each source.The values of @n in <equate> should not have duplicates.At least one @n value in an equate should be found in every source.<code>@n</code> <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> Taken from ar.cat.eng.1926.edghill.ref-logical

<code>@new</code>TAN-class-2.rngDefinition 1The attribute new provides the new name for an @n that is to be renamed.Definition 2The attribute new provides the new ref for a <div> that is to be renamed. Used by: ~simple-rename, ~complex-renameIn a <rename> the quantity of values in @ref and @new must be identical.@new may not take the same value as what it replaces.No adjustment action should result in the mixing of leaf <div>s and non-leaf <div>s.<code>@new</code> <adjustments src="ger"> <skip div-type="Gedicht"/> <rename ref="1 e" new="4"/> </adjustments> Taken from ringoroses.01+03.token.2

<code>@object</code>TAN-A.rngThe 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, ~objectEvery idref in an attribute must point to a vocabulary item (by @xml:id or name) that is of the appropriate corresponding element.All idrefs in an attribute must be unique.Multiple idrefs in a single attribute should not point to the same entity.<code>@object</code><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> Taken from ar.cat.TAN-A.claims<code>@object</code> <body claimant="park"> <claim verb="concerns" object="predication"> <subject src="grc" ref="1 1"/> </claim> </body> Taken from ar.cat.TAN-A

<code>@pattern</code>TAN-core.rngThe 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 and https://www.w3.org/TR/xpath-functions-30/#regex-syntax Used by: ~element-replace, ~element-token-definition<code>@pattern</code> <adjustments> ......... <normalization> ......... </normalization> <replace pattern="--" replacement="—" flags="i"/> </adjustments> Taken from gomme.1989.ring-o-roses<code>@pattern</code> <head> ......... <numerals priority="letters"/> <token-definition src="fra" pattern="\S+"/> <source xml:id="grc"> ......... </source> ......... </head> Taken from ar.cat.TAN-A<code>@pattern</code> <head> ......... <license which="by_4.0" licensor="park"/> <token-definition src="eng-us" pattern="[-\w]+"/> <source xml:id="eng-uk"> ......... </source> ......... </head> Taken from ringoroses.div.1<code>@pattern</code> <head> ......... <license licensor="kalvesmaki"> ......... </license> <token-definition pattern="[\w‍]+"/> <inclusion xml:id="rel"> ......... </inclusion> ......... </head> Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-A-lm-sample

<code>@period</code>TAN-core.rngThe attribute period names via idrefs one or more <period>s. Takes IDrefs to vocabulary items <period>Used by: ~element-claim, ~element-respEvery idref in an attribute must point to a vocabulary item (by @xml:id or name) that is of the appropriate corresponding element.All idrefs in an attribute must be unique.Multiple idrefs in a single attribute should not point to the same entity.<code>@period</code> <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> Taken from ar.cat.TAN-A.claims

<code>@pos</code>TAN-class-2.rngDefinition 1The 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 Definition 2The 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 Used by: ~tok-selector-attributes-one, ~tok-selector-attributes-manySequences may not include values less than 1.Sequences may not include values greater than the maximum allowed.Ranges in sequences must go from a lesser value to a greater.Every token must be locatable in every cited ref in every source.<code>@pos</code><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> Taken from ar.cat.TAN-A.claims

<code>@priority</code>TAN-class-2.rngThe 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. TAN-core.rngThe 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<code>@priority</code> <head> ......... <version> ......... </version> <numerals priority="letters"/> <source> ......... </source> ......... </head> Taken from ring-o-roses.deu.1897-prev<code>@priority</code> <head> ......... <version> ......... </version> <numerals priority="letters"/> <source> ......... </source> ......... </head> Taken from ring-o-roses.deu.1897<code>@priority</code> <head> ......... <license licensor="park"> ......... </license> <numerals priority="letters"/> <token-definition src="fra" pattern="\S+"/> ......... </head> Taken from ar.cat.TAN-A<code>@priority</code> <head> ......... <license licensor="park" which="by 4.0"/> <numerals priority="letters"/> <source xml:id="conf"> ......... </source> ......... </head> Taken from patricius.confessio.TAN-A

<code>@ref</code>TAN-class-2.rngDefinition 1The 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 Definition 2The 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-renameEvery part of a @ref must correspond to a <div> in every source.If a reference to a work is not found in some sources for that work, a warning will be returned.In a @ref range the first reference should precede the second.Any range in either an @n or in a @ref in an adjustment action must be predictably calculated.In a <rename> the quantity of values in @ref and @new must be identical.<code>@ref</code><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> Taken from ar.cat.TAN-A.claims

<code>@ref-alias</code>TAN-class-1.rngThe 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-divEach value in @ref-alias must consist of as many @n values as the current div is deep in the body structure.<code>@ref-alias</code> <div n="43" type="letter"> <div n="3" type="section" ref-alias="59 3">Ἦν ὅτε οὐκ ἦν κακία καὶ ἔσται ὅτε οὐκ ἔσται· οὐκ ἦν δὲ ὅτε οὐκ ἦν ἀρετή, οὐδὲ ἔσται ὅτε οὐκ ἔσται· ἀνεξάλειπτα γὰρ τὰ σπέρματα τῆς ἀρετῆς. Πείθει δέ με καὶ οὗτος παρ' ὀλίγον καὶ οὐ τελείως ἐν παντὶ κακῷ γεγονὼς καὶ ὁ πλούσιος ἐν τῷ ᾅδῃ διὰ κακίαν κρινόμενος καὶ οἰκτείρων τοὺς ἀδελφούς. Τὸ δὲ ἐλεεῖν σπέρμα τυγχάνει τὸ κάλλιστον τῆς ἀρετῆς.</div> </div> Taken from cpg2437.43.grc.1987.gehin

<code>@relationship</code>TAN-core.rngThe attribute relationship names via idrefs one or more <relationship>s Takes IDrefs to vocabulary items <relationship>Used by: ~link-element-see-alsoEvery idref in an attribute must point to a vocabulary item (by @xml:id or name) that is of the appropriate corresponding element.All idrefs in an attribute must be unique.Multiple idrefs in a single attribute should not point to the same entity.<code>@relationship</code> <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> Taken from ar.cat.eng.1926.edghill.ref-logical<code>@relationship</code> <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> Taken from ar.cat.lat.1961.minio-paluello.ref-scriptum

<code>@replacement</code>TAN-class-1.rngThe attribute replacement contains a string used to replace any occurrence of @pattern Used by: ~element-replace<code>@replacement</code> <adjustments> ......... <normalization> ......... </normalization> <replace pattern="--" replacement="—" flags="i"/> </adjustments> Taken from gomme.1989.ring-o-roses

<code>@reuse-type</code>TAN-A-tok.rngThe attribute reuse-type points via idrefs to one or more reuse-types. Multiple values are combinatory.This attribute is weakly inheritable. See Takes IDrefs to vocabulary items <reuse-type>Used by: ~body-attributes-non-core, ~element-alignEvery idref in an attribute must point to a vocabulary item (by @xml:id or name) that is of the appropriate corresponding element.All idrefs in an attribute must be unique.Multiple idrefs in a single attribute should not point to the same entity.<code>@reuse-type</code><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> Taken from ringoroses.01+02.token.1<code>@reuse-type</code><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> Taken from ringoroses.01+03.token.1<code>@reuse-type</code><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> Taken from ringoroses.01+03.token.2

<code>@rgx</code>TAN-class-2.rngThe 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 Used by: ~element-tok-abstract, ~tok-selector-attributes-one, ~tok-selector-attributes-manyAttributes that take regular expressions must use escape sequences recognized by XML schema or TAN escape extensions (\u{}). See http://www.w3.org/TR/xmlschema-2/#regexsEvery token must be locatable in every cited ref in every source.<code>@rgx</code> <align> <tok src="eng" ref="4" val="all"/> <tok src="ger" ref="4" rgx="alle"/> </align> Taken from ringoroses.01+03.token.2

<code>@roles</code>TAN-core.rngThe attribute roles refers via idrefs one or more <role>s Takes IDrefs to vocabulary items <role>Used by: ~element-respEvery idref in an attribute must point to a vocabulary item (by @xml:id or name) that is of the appropriate corresponding element.All idrefs in an attribute must be unique.Multiple idrefs in a single attribute should not point to the same entity.<code>@roles</code><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> Taken from ar.cat.eng.1926.edghill.ref-logical<code>@roles</code> <head> ......... <file-resp who="kalvesmaki"/> <resp roles="editor" who="kalvesmaki"/> <resp who="xslt1" roles="stylesheet1"/> ......... </head> Taken from ar.cat.eng.1926.edghill.ref-scriptum

<code>@root</code>catalog.tan.rng Used by: <doc>@root should match the target's root element name

<code>@scriptum</code>TAN-A.rngThe 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. TAN-class-1.rngThe 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<code>@scriptum</code> <head> ......... <work> ......... </work> <reference-system type="material" wf-ready="true" scriptum="bekker"/> <source> ......... </source> ......... </head> Taken from ar.cat.grc.1949.minio-paluello.ref-scriptum

<code>@shallow</code>TAN-class-2.rngThe attribute shallow indicates whether skipping should be done shallowly (default) or deeply Used by: ~adj-element-skip<code>@shallow</code> <adjustments src="fra"> <skip div-type="summ" shallow="false"/> <equate n="ti title"/> ......... </adjustments> Taken from ar.cat.TAN-A

<code>@src</code>TAN-class-2.rngDefinition 1The attribute src refers via idref to only one <source>Definition 2The 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-optEvery idref in an attribute must point to a vocabulary item (by @xml:id or name) that is of the appropriate corresponding element.All idrefs in an attribute must be unique.Multiple idrefs in a single attribute should not point to the same entity.Every part of a @ref must correspond to a <div> in every source.<code>@src</code><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> Taken from ar.cat.TAN-A.claims

<code>@stable</code>catalog.tan.rng Used by: <collection><code>@stable</code><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> Taken from catalog.tan<code>@stable</code><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> Taken from catalog.tan<code>@stable</code><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> Taken from catalog.tan<code>@stable</code><collection stable="true"> <doc href="bitext-relations.TAN-voc.xml"/> <doc href="catalog.tan.xml"/> <doc href="div-types.TAN-voc.xml"/> ......... </collection> Taken from collection

<code>@status</code>TAN-core.rngThe 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<code>@status</code> <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> Taken from patricius.confessio.2003.eng<code>@status</code> <teiHeader> <fileDesc> ......... </fileDesc> <revisionDesc status="draft"> <change when-iso="2015-05-14T16:30:25.958-04:00" status="draft"/> </revisionDesc> </teiHeader> Taken from ring-o-roses.eng.1951<code>@status</code> <constraints> <subject status="required" item-type="person work version scriptum"/> <at-ref status="required"/> ......... </constraints> Taken from ar.cat.TAN-A.claims

<code>@subject</code>TAN-A.rngThe 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, ~subjectEvery idref in an attribute must point to a vocabulary item (by @xml:id or name) that is of the appropriate corresponding element.All idrefs in an attribute must be unique.Multiple idrefs in a single attribute should not point to the same entity.<code>@subject</code><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> Taken from ar.cat.TAN-A.claims

<code>@TAN-version</code>TAN-core.rngThe attribute TAN-version specifies a version of TAN. Used by: ~TAN-rootTAN files using a version other than the current version will be marked with a warning.The @TAN-version for inclusions and vocabularies should match the current version.<code>@TAN-version</code><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> Taken from ar.cat.eng.1926.edghill.ref-logical<code>@TAN-version</code><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> Taken from ar.cat.eng.1926.edghill.ref-scriptum<code>@TAN-version</code><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> Taken from ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949<code>@TAN-version</code><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> Taken from ar.cat.fra.1844.saint-hilaire.ref-logical

<code>@to</code>TAN-core.rngThe attribute to specifies the end of a period of time. Used by: <period>Future dates are not permitted.@from must predate @to<code>@to</code> <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> Taken from ar.cat.TAN-A.claims

<code>@tok-matches</code>TAN-mor.rngThe 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<code>@tok-matches</code><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> Taken from eng.kalvesmaki.com,2014.2

<code>@tok-pop</code>TAN-A-lm.rngThe 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 Used by: ~element-ana<code>@tok-pop</code> <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> Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-A-lm-sample

<code>@type</code>TAN-class-1.rngThe 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 TAN-core.rngThe 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-coreEvery idref in an attribute must point to a vocabulary item (by @xml:id or name) that is of the appropriate corresponding element.All idrefs in an attribute must be unique.Multiple idrefs in a single attribute should not point to the same entity.<code>@type</code> <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> Taken from ar.cat.eng.1926.edghill.ref-logical

<code>@units</code>TAN-A.rngThe 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-referenceEvery idref in an attribute must point to a vocabulary item (by @xml:id or name) that is of the appropriate corresponding element.All idrefs in an attribute must be unique.Multiple idrefs in a single attribute should not point to the same entity.Claims involving verbs whose constrained content requires specification of units must use <object> or <subject> with @units..<object> or <subject> with @units may be used only with verbs with constrained content.<code>@units</code> <claim subject="n" verb="has_length"> <object units="folio">160</object> </claim> Taken from ar.cat.TAN-A.claims

<code>@val</code>TAN-class-2.rngThe attribute val contains a string that points to a word token by its value. Matches are case-, space-, and accent-sensitive.For more see Used by: ~element-tok-abstract, ~tok-selector-attributes-one, ~tok-selector-attributes-manyEvery token must be locatable in every cited ref in every source.<code>@val</code> <reassign> <passage ref="5 4 7 2"> <from-tok val=":" pos="1"/> <through-tok val=":" pos="1"/> </passage> ......... </reassign> Taken from ar.cat.TAN-A<code>@val</code> <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> Taken from grc-tan-a-lm-%CE%B1

<code>@verb</code>TAN-A.rngThe 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-claimEvery idref in an attribute must point to a vocabulary item (by @xml:id or name) that is of the appropriate corresponding element.All idrefs in an attribute must be unique.Multiple idrefs in a single attribute should not point to the same entity.Every <claim> must have or inherit at least one verb.Every <claim> must respect constraints defined by the verb.No <claim> with a verb that disallows an element may have another verb that requires that same element.<code>@verb</code><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> Taken from ar.cat.TAN-A.claims

<code>@wf-ready</code>TAN-class-1.rngThe 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<code>@wf-ready</code> <head> ......... <license licensor="kalvesmaki"> ......... </license> <reference-system type="logical" wf-ready="true"/> <work> ......... </work> ......... </head> Taken from ar.cat.fra.1844.saint-hilaire.ref-logical<code>@wf-ready</code> <head> ......... <work> ......... </work> <reference-system type="logical" wf-ready="true"/> <source> ......... </source> ......... </head> Taken from ar.cat.grc.1949.minio-paluello.ref-logical<code>@wf-ready</code> <head> ......... <work> ......... </work> <reference-system type="material" wf-ready="true" scriptum="bekker"/> <source> ......... </source> ......... </head> Taken from ar.cat.grc.1949.minio-paluello.ref-scriptum<code>@wf-ready</code> <head> ......... <work> ......... </work> <reference-system type="material" wf-ready="true"/> <source> ......... </source> ......... </head> Taken from ar.cat.lat.1961.minio-paluello.ref-scriptum

<code>@when</code>TAN-core.rngThe attribute when indicates a date or date and timeThis attribute is weakly inheritable. See Used by: ~element-change, ~element-commentFuture dates are not permitted.<code>@when</code><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> Taken from ar.cat.eng.1926.edghill.ref-logical

<code>@where</code>TAN-A.rngThe 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-claimEvery idref in an attribute must point to a vocabulary item (by @xml:id or name) that is of the appropriate corresponding element.All idrefs in an attribute must be unique.Multiple idrefs in a single attribute should not point to the same entity.<code>@where</code> <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> Taken from ar.cat.TAN-A.claims

<code>@which</code>TAN-core.rngThe 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-contentAn element's @which must have a value that corresponds to a <name>, either in a standard TAN vocabulary or an associated TAN-voc file, that is marked as applying to that element.A @which in a <vocabulary> may point only to items in the standard TAN file vocabularies.TAN-voc.xml<code>@which</code><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> Taken from ar.cat.eng.1926.edghill.ref-logical<code>@which</code> <adjustments> <normalization which="no hyphens"/> </adjustments> Taken from ar.cat.eng.1926.edghill.ref-scriptum

<code>@who</code>TAN-core.rngThe 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-respEvery idref in an attribute must point to a vocabulary item (by @xml:id or name) that is of the appropriate corresponding element.All idrefs in an attribute must be unique.Multiple idrefs in a single attribute should not point to the same entity.<code>@who</code><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> Taken from ar.cat.eng.1926.edghill.ref-logical

<code>@work</code>TAN-A.rngThe 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-referenceEvery idref in an attribute must point to a vocabulary item (by @xml:id or name) that is of the appropriate corresponding element.All idrefs in an attribute must be unique.Multiple idrefs in a single attribute should not point to the same entity.If a reference to a work is not found in some sources for that work, a warning will be returned.<code>@work</code> <claim verb="refers-to"> <subject src="grc" ref="1 b 25"/> <object work="grc" ref="1 a 16"/> </claim> Taken from ar.cat.TAN-A.claims<code>@work</code><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> Taken from ringoroses.div.1

<code>@xml:id</code>TAN-core.rngThe 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@xml:id values may not be repeated in the same document.An @xml:id on a vocabulary item need not duplicate a <name> (except in a TAN-mor file).<code>@xml:id</code> <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> Taken from ar.cat.eng.1926.edghill.ref-logical

<code>@xml:lang</code>TAN-core.rngThe 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 .Examples: 'eng' (English), 'grc' (classical Greek), 'lat' (Latin) Used by: ~nontextual-reference, ~body-attributes-non-core, ~element-div, ~metadata-human-readable-attributes<code>@xml:lang</code><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> Taken from ar.cat.eng.1926.edghill.ref-logical

TAN elements

<code><adjustments></code>TAN-core.rngThe element adjustments declares alterations. In a class-1 file, it specifies alterations that have been made to the underlying source. In a class-2 file, it specifies alterations that should be made to the class-1 source(s) before processing any claims in the <body>.The sequence of consecutive adjustments matters, in that their contents will be processed first by priority (<skip>, <rename>, <equate>, <reassign>), then in document order. The instructions in one <adjustment> may render null an instruction in a lower-priority, or subsequent adjustment action. Used by: ~adjustment-listAny range in either an @n or in a @ref in an adjustment action must be predictably calculated.No adjustment action should result in the mixing of leaf <div>s and non-leaf <div>s.<code><adjustments></code> <head> ......... <redivision> ......... </redivision> <adjustments> <normalization which="no hyphens"/> </adjustments> <vocabulary-key> ......... </vocabulary-key> ......... </head> Taken from ar.cat.eng.1926.edghill.ref-logical<code><adjustments></code> <head> ......... <model> ......... </model> <adjustments> <normalization which="no hyphens"/> </adjustments> <vocabulary-key> ......... </vocabulary-key> ......... </head> Taken from ar.cat.eng.1926.edghill.ref-scriptum<code><adjustments></code> <head> ......... <model> ......... </model> <adjustments> <normalization which="no hyphens"/> </adjustments> <vocabulary-key> ......... </vocabulary-key> ......... </head> Taken from ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949<code><adjustments></code> <head> ......... <redivision> ......... </redivision> <adjustments> <normalization which="no hyphens"/> <normalization which="no ligatures"/> </adjustments> <vocabulary-key> ......... </vocabulary-key> ......... </head> Taken from ar.cat.fra.1844.saint-hilaire.ref-logical

<code><algorithm></code>TAN-core.rngThe element algorithm contains an IRI + name pattern identifying an algorithm.The term "algorithm" covers any set of computational instructions. It does not include the hardware used to run the algorithm, nor does it identify any algorithms used to run an algorithm. For example, an algorithm might identify one or more XSLT stylesheets, but it does not identify the engine (e.g., Saxon), catalyzing software (e.g., oXygen), or operating system (e.g., Windows) used to run the algorithm. Used by: ~voc-element-agentAn element that has a <location> and is key for validation should have at least one document available.Every TAN file referred to by way of an element containing <location> should have an @id that matches the <IRI> of the parent of the <location>No element may point to a TAN file that has an identical @id value; the only exception is <predecessor> and <successor>.If a target file has children items in the <to-do>the corresponding comments will be returned as warnings.If a target file has a <successor> a warning will be returned, noting the update.If a target file points only to non-local locations and no internet is available, the following message will be returned. No internet available.If an element not essential to validation has no <location> that points to a document a warning should be returned.<code><algorithm></code> <head> ......... <vocabulary-key> <algorithm xml:id="xslt2"> <IRI>tag:textalign.net,2015:stylesheet:convert-tan2018-to-tan2020</IRI> <name>Stylesheet to create a TAN file.</name> <location href="../applications/convert/convert%20TAN%202018%20to%20TAN%202020.xsl" accessed-when="2018-08-04T23:55:36.096-04:00"/> </algorithm> <div-type xml:id="ch"> ......... </div-type> ......... <person xml:id="kalvesmaki"> ......... </person> <algorithm xml:id="xslt1"> <IRI>tag:textalign.net,2015:stylesheet:convert-tan2017-to-tan2018</IRI> <name>Stylesheet to populate a TAN-A file from collections.</name> <location href="../applications/convert/convert%20TAN%202017%20to%20TAN%202018.xsl" accessed-when="2018-08-05"/> </algorithm> <role xml:id="editor"> ......... </role> ......... </vocabulary-key> ......... </head> Taken from ar.cat.eng.1926.edghill.ref-logical<code><algorithm></code> <vocabulary-key> ......... <person xml:id="kalvesmaki"> ......... </person> <algorithm xml:id="xslt1"> <IRI>tag:textalign.net,2015:stylesheet:convert-tan2017-to-tan2018</IRI> <name>Stylesheet to populate a TAN-A file from collections.</name> <location href="../applications/convert/convert%20TAN%202017%20to%20TAN%202018.xsl" accessed-when="2018-08-02"/> </algorithm> <role xml:id="editor"> ......... </role> ......... </vocabulary-key> Taken from ar.cat.eng.1926.edghill.ref-scriptum<code><algorithm></code> <vocabulary-key> <algorithm xml:id="xslt2"> <IRI>tag:textalign.net,2015:stylesheet:convert-tan2018-to-tan2020</IRI> <name>Stylesheet to create a TAN file.</name> <location href="../applications/convert/convert%20TAN%202018%20to%20TAN%202020.xsl" accessed-when="2018-08-05T00:03:20.142-04:00"/> </algorithm> <div-type xml:id="ch"> ......... </div-type> ......... </vocabulary-key> Taken from ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949

<code><alias></code>TAN-core.rngThe element alias assigns a single id (@xml:id or @id) to multiple idrefs. An <alias> effectively groups multiple vocabulary items together. @xml:id and @id are equivalent alternatives. The latter supports characters disallowed by the former (e.g., colons). This feature is useful for creating groups of persons, works, scripta, etc., and referring to them. It is inspired by the model of the critical edition, where multiple manuscripts, each of which have their own identifier, can be assigned a family that has its own special siglum. Because ids and idrefs are encapsulated within a single file, and because <alias> serves exclusively idrefs, this element may neither include nor be included.The sequence of consecutive <alias>es is immaterial. Used by: ~voc-key-core<alias> references must not be circular.Every value in @idrefs must correspond to an @id or @xml:id in the file.<code><alias></code> <vocabulary-key> ......... <div-type xml:id="v" which="verse (scripture)"/> <alias xml:id="test" idrefs="ch v"/> </vocabulary-key> Taken from matt.eng.kjv.1760<code><alias></code> <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> Taken from ar.cat.TAN-A.claims

<code><align></code>TAN-A-tok.rngThe element align declares one or more groups of word-tokens that should be aligned with each other. <align> specifies that all the tokens invoked for one source collectively align with the tokens in the other. No special meaning is attached to sequences of <tok>s that do not follow the source order.The sequence of consecutive <align>s is immaterial. Used by: ~body-item<code><align></code><TAN-A-tok TAN-version="2021" id="tag:parkj@textalign.net,2015:TAN-A-tok,ring01+ring02"> ......... <body bitext-relation="B-descends-from-A" reuse-type="adaptation"> <align> <tok src="ring1881" ref="1" pos="1"/> <tok src="ring1987" ref="1" pos="1"/> </align> <align> <tok src="ring1881" ref="1" pos="2"/> <tok src="ring1987" ref="1" pos="2"/> </align> <align> <tok src="ring1881" ref="1" pos="3"/> <tok src="ring1987" ref="1" pos="3"/> </align> <align> <tok src="ring1881" ref="1" pos="4"/> <tok src="ring1987" ref="1" pos="4"/> </align> <align> ......... </align> ......... </body> </TAN-A-tok> Taken from ringoroses.01+02.token.1

<code><ana></code>TAN-A-lm.rngThe element ana contains a one or more assertions about the lexical or morphological properties of one or more tokens.Claims within an <ana> are distributive. That is, every combination of <l> and <m> within an <lm> is claimed to be true for every <tok>.The sequence of consecutive <ana>s is immaterial. Used by: ~body-item<code><ana></code><TAN-A-lm TAN-version="2021" id="tag:kalvesmaki.com,2014:tan-t:ar.cat.grc.1949.minio-paluello:semantic-refs:TAN-A-lm:2016-04-05T07:07:40.033-04:00"> ......... <body lexicon="LSJ Lampe new" morphology="Perseus" claimant="xslt2"> <ana tok-pop="2"> <tok ref="11 2 1 1" pos="1"/> <lm> ......... </lm> </ana> <ana> <tok ref="10 6 3 2" pos="4"/> <tok ref="10 6 3 3" pos="15"/> <tok ref="10 6 4 2" pos="37"/> ......... </ana> <ana> <tok ref="8 3 5 4" pos="6"/> <tok ref="8 3 7 3" pos="7"/> <lm> ......... </lm> </ana> <ana> <tok ref="7 1 2 1" pos="12"/> <tok ref="7 3 1 3" pos="22"/> <tok ref="7 3 1 3" pos="24"/> ......... </ana> <ana> ......... </ana> ......... </body> </TAN-A-lm> Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-A-lm-sample

<code><annotation></code>TAN-class-1.rngThe element annotation identifies a class-2 file that is an annotation on (and therefore a dependent of) the current file.The sequence of consecutive <annotation>s is immaterial. Used by: ~networked-files-non-core<annotation> must point to class 2 TAN filesAn element that has a <location> and is key for validation should have at least one document available.Every TAN file referred to by way of an element containing <location> should have an @id that matches the <IRI> of the parent of the <location>No element may point to a TAN file that has an identical @id value; the only exception is <predecessor> and <successor>.If a target file has children items in the <to-do>the corresponding comments will be returned as warnings.If a target file has a <successor> a warning will be returned, noting the update.If a target file points only to non-local locations and no internet is available, the following message will be returned. No internet available.If a linking element points to a file that must be resolved, that file must be a TAN file.<code><annotation></code> <head> ......... <redivision> ......... </redivision> <annotation> <IRI>tag:parkj@textalign.net,2015:ar.cat.tan-a:claims</IRI> <name>Comments and claims on Aristotle's Categories</name> <location accessed-when="2021-04-29T11:29:58.992-04:00" href="TAN-A/ar.cat.TAN-A.claims.xml"/> </annotation> <adjustments> ......... </adjustments> ......... </head> Taken from ar.cat.grc.1949.minio-paluello.ref-scriptum

<code><assert></code>TAN-mor.rngThe element assert names a pattern that, if found to be false in any <m> in a dependent TAN-A-lm file, will return the enclosed message upon validation of the dependent file, along with an error or warning. Modeled on Schematron <report>.The sequence of consecutive <assert>s is immaterial. Used by: ~element-rule<code><assert></code><TAN-mor TAN-version="2021" id="tag:kalvesmaki.com,2014:tan-r-mor:eng:penn"> ......... <body> <rule m-matches=".+"> <assert m-has-how-many-codes="1">Features may not be combined.</assert> </rule> <rule> <where m-has-codes="$"/> <assert tok-matches="$">Only $ may be tagged as a dollar sign.</assert> </rule> ......... </body> </TAN-mor> Taken from eng.kalvesmaki.com,2014.2<code><assert></code> <rule m-matches="^. i"> <assert m-matches="^[dp]">An interrogative must be either a determiner (d) or a pronoun (p).</assert> </rule> Taken from grc.perseus.tan-mor

<code><at-ref></code>TAN-A.rngThe element at-ref restricts a claim to a particular abstract textual reference. <at-ref> was designed primarily to serve claims related to apparatus critici. In traditional critical editions, the main text has an apparatus at the bottom of the page, indicating variations in the manuscript, e.g., "A om." or "A: γάρ". These terse statements are shorthand for: "Manuscript A omits the passage at line X word Y" and "Manuscript A reads γάρ in place of the passage at line X word Y." In those statements, the siglum A refers to the subject, and the reading (or lack thereof) is the object. The qualifier "at line X word Y" is the phrase that corresponds to <at-ref>. It functions much like <where>, but the geography is textual rather than spatial. <at-ref> is special, and must be explicitly allowed or required by each <verb> or @verb's IRI + name pattern plus constraints. <at-ref> contains a textual reference, and will look similar to <subject> or <object> built as a texutal reference. The sequence of consecutive <at-ref>s is immaterial. TAN-core.rngThe element at-ref specifies whether a verb uses <at-ref> (default: disallowed). Used by: ~element-claim, ~constraints-on-verb<code><at-ref></code><TAN-A TAN-version="2021" id="tag:parkj@textalign.net,2015:ar.cat.tan-a:claims"> <head> ......... <vocabulary-key> ......... <verb xml:id="om"> ......... <constraints> <subject status="required" item-type="person work version scriptum"/> <at-ref status="required"/> <object status="disallowed"/> </constraints> </verb> ......... </vocabulary-key> ......... </head> <body claimant="park" claim-period="per2010s"> ......... <claim subject="andronicus boethus" adverb="perhaps" verb="om" xml:id="cl1a2a" claim-when="2017-03-10" claimant="park"> <at-ref src="grc" ref="1 a 2"> <tok pos="3-4"/> </at-ref> </claim> ......... <claim subject="B" verb="reads"> <at-ref src="grc" ref="1 a 5"> <tok pos="1-2"/> </at-ref> <object>τις ἀποδιδῷ</object> </claim> <claim subject="Λ" adverb="perhaps" verb="reads"> <at-ref src="grc" ref="1 a 5"> <tok pos="1-2"/> </at-ref> <object>τις ἀποδιδῷ</object> </claim> ......... </body> </TAN-A> Taken from ar.cat.TAN-A.claims

<code><bitext-relation></code>TAN-A-tok.rngThe element bitext-relation identifies how the text of one text-bearing object relates to that of another by specifying a relationship, e.g., B is a direct copy of A; B and A descend from a commont parent, etc. See for theoretical background.In most cases, there will be need for only one of these elements as a vocabulary item. But multiple values may be helpful for cases where a bitext has a complex history, for example, a textual object that was created over time, and in different phases.This element should not be used to describe any activities (e.g., translation, copying), reserved for <reuse-type>. For examples see Used by: ~voc-element-non-class-2<code><bitext-relation></code> <vocabulary-key> <algorithm xml:id="xslt2"> ......... </algorithm> <bitext-relation xml:id="B-descends-from-A"> <IRI>tag:textalign.net,2015:bitext-relation:a/x+/b</IRI> <name>B descends directly from A, unknown number of intermediaries</name> <desc>The 1987 versions is hypothesized to descend somehow from the 1881 version, mainly for the sake of illustration.</desc> </bitext-relation> <reuse-type xml:id="adaptation"> ......... </reuse-type> ......... </vocabulary-key> Taken from ringoroses.01+02.token.1<code><bitext-relation></code> <vocabulary-key> <algorithm xml:id="xslt2"> ......... </algorithm> <bitext-relation xml:id="unclear"> <IRI>tag:kalvesmaki@gmail.com,2014:bitext-relation:unclear</IRI> <name>The German and English versions bear some relationship, but what exactly is unclear.</name> </bitext-relation> <reuse-type xml:id="correlationGeneral"> ......... </reuse-type> ......... </vocabulary-key> Taken from ringoroses.01+03.token.1<code><bitext-relation></code> <vocabulary-key> <algorithm xml:id="xslt2"> ......... </algorithm> <bitext-relation xml:id="unclear"> <IRI>tag:kalvesmaki@gmail.com,2014:bitext-relation:unclear</IRI> <name>The German and English versions bear some relationship, but what exactly is unclear.</name> </bitext-relation> <reuse-type xml:id="correlationGeneral"> ......... </reuse-type> ......... </vocabulary-key> Taken from ringoroses.01+03.token.2

<code><body></code>TAN-core.rngThe element body contains the data of a TAN file. Used by: ~TAN-root<code><body></code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2021"> <head> ......... </head> <body xml:lang="eng"> <div type="ch" n="1"> ......... </div> <div type="ch" n="2"> ......... </div> <div type="ch" n="3"> ......... </div> ......... </body> </TAN-T> Taken from ar.cat.eng.1926.edghill.ref-logical<code><body></code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:model-object-refs" TAN-version="2021"> <head> ......... </head> <body xml:lang="eng"> <div type="p" n="1"> ......... </div> <div type="p" n="2"> ......... </div> <div type="p" n="3"> ......... </div> ......... </body> </TAN-T> Taken from ar.cat.eng.1926.edghill.ref-scriptum<code><body></code><TAN-T TAN-version="2021" id="tag:kalvesmaki.com,2014:tan-t:ar.cat.fra.1844.saint-hilaire:semantic-refs-realigned"> <head> ......... </head> <body xml:lang="fra"> <div n="ti_1" type="ti"> ......... </div> <div n="1" type="ch"> ......... </div> <div n="2" type="ch"> ......... </div> ......... </body> </TAN-T> Taken from ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949<code><body></code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.fra.1844.saint-hilaire:semantic-refs" TAN-version="2021"> <head> ......... </head> <body xml:lang="fra"> <div type="ti" n="ti">CATÉGORIES</div> <div type="sec" n="1"> ......... </div> <div type="sec" n="2"> ......... </div> ......... </body> </TAN-T> Taken from ar.cat.fra.1844.saint-hilaire.ref-logical

<code><category></code>TAN-mor.rngThe element category groups a set of features that share a common grammatical trait such as gender, number, etc. The order of consecutive <category>s is important, dictating the sequence in which codes should appear in the values of <m> in a dependent TAN-A-lm file. Used by: ~features-categorized<code><category></code><TAN-mor TAN-version="2021" id="tag:kalvesmaki.com,2014:tan-r-mor:grc:perseus"> ......... <body> ......... <rule m-matches="^. v"> ......... </rule> <category feature="morphosyntactic_category"> <code feature="adjective"> ......... </code> <code feature="conjunction"> ......... </code> <code feature="adverb"> ......... </code> ......... </category> <category feature="secondary_morphosyntactic_category"> <code feature="article"> ......... </code> <code feature="adjectival_adverb"> ......... </code> <code feature="pronoun_reciprocal"> ......... </code> ......... </category> <category feature="feature_person"> <code feature="first"> ......... </code> <code feature="second"> ......... </code> <code feature="third"> ......... </code> </category> <category feature="feature_number"> <code feature="dual"> ......... </code> <code feature="plural"> ......... </code> <code feature="singular"> ......... </code> </category> <category feature="feature_tense"> ......... </category> ......... </body> </TAN-mor> Taken from grc.perseus.tan-mor

<code><change></code>TAN-core.rngThe element change declares a change made to the current file. Must credit/blame someone, specified by @who, and indicate when the change was made, specified by @when..Collectively, <change> elements are called the changelog, the revision history of the document. The editor has discretion as to how long or detailed a <change> should be, or how many should be retained in a changelog. Ideally, <change>s documenting every published version should be retained.<change> elements may appear in any order, but it is good practice to put the most recent at the top. <code><change></code><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> Taken from ar.cat.eng.1926.edghill.ref-logical

<code><checksum></code>TAN-core.rngThe element checksum specifies some checksum value of a digital file. This element contains other elements that define the type and value of the checksum. Must begin with an IRI + name pattern that identifies the type of checksum being used (e.g., SHA-1).This element allows other users to check to see if copies of a file are identical. No checksums will be generated, checked, or validated by TAN schemas. Used by: ~entity-digital-core-content<code><checksum></code> <source> ......... <name>The Saint Patrick's Confessio Hypertext Stack Project edition</name> <checksum> <IRI>http://dbpedia.org/resource/Sha-1</IRI> <name>SHA-1</name> <value>91D95564ABDF2B2C1B9EEF016CBA51E8179646CC</value> </checksum> <location href="http://www.confessio.ie/sites/confessio.ie/files/downloads/confessio_english.xml" accessed-when="2015-01-25"/> </source> Taken from patricius.confessio.2003.eng

<code><claim></code>TAN-A.rngThe element claim makes one or more claims (assertions). Used by: ~body-content-non-class-2, ~complex-objectClaims involving verbs whose constrained content requires specification of units must use <object> or <subject> with @units..<object> or <subject> with @units may be used only with verbs with constrained content.A claim with a verb that has content constraints must not allow other verbs.Every <claim> must have or inherit at least one verb.Every <claim> must respect constraints defined by the verb.No <claim> with a verb that disallows an element may have another verb that requires that same element.<code><claim></code><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> Taken from ar.cat.TAN-A.claims

<code><code></code>TAN-mor.rngThe element code attaches a grammatical feature to a code, and makes it available to a TAN-A-lm file. Because vocabulary item for a grammatical feature is language-agnostic, and because a TAN-mor code is language-specific, guidance to the editor of a TAN-A-lm file may be important. Ihildren <desc>s can be used to provide examples or other guidance. Used by: ~element-category, ~features-uncategorizedCodes for features must be case-indifferently unique.<code><code></code><TAN-mor TAN-version="2021" id="tag:kalvesmaki.com,2014:tan-r-mor:eng:penn"> ......... <body> ......... <rule m-has-codes="'' . ; :"> ......... </rule> <code feature="closing_quotation_mark"> <desc>Examples: ' ''</desc> <val>''</val> </code> <code feature="dash"> <desc>Example: --</desc> <val>--</val> </code> <code feature="dollar"> <desc>Examples: Examples: $ -$ --$ A$ C$ HK$ M$ NZ$ S$ U.S.$ US$</desc> <val>$</val> </code> <code feature="opening_parenthetical_punctuation"> <desc>Examples: ( [ {</desc> <val>[</val> </code> <code feature="closing_parenthetical_punctuation"> ......... </code> ......... </body> </TAN-mor> Taken from eng.kalvesmaki.com,2014.2

<code><collection></code>catalog.tan.rng

<code><comment></code>TAN-core.rngThe element comment discusses issues relevant to nearby data. Must credit someone, specified by @who, and indicate when the comment was made, specified by @when.. Used by: ~element-ana, ~element-lm, ~element-align, ~element-category, ~element-item, ~element-replace, ~element-adjustments, ~element-group, ~element-head, ~element-license, ~element-to-do, ~element-vocabulary-key, ~link-element-inclusion, ~link-element-see-also, ~body-content-core, ~constraints-on-verb, ~entity-digital-nontan-id, ~entity-digital-nontan-no-id, ~entity-digital-tan-id, ~entity-digital-tan-no-id, ~entity-nondigital-constrained, ~entity-nondigital-id, ~entity-nondigital-no-id<code><comment></code> <redivision> ......... <location href="ar.cat.eng.1926.edghill.ref-logical.xml" accessed-when="2016-07-07T16:36:28.867-04:00"/> <comment who="kalvesmaki" when="2021-02-12">A scan is available here: https://ia600908.us.archive.org/33/items/worksofaristotle01arisuoft/worksofaristotle01arisuoft.pdf</comment> </redivision> Taken from ar.cat.eng.1926.edghill.ref-scriptum<code><comment></code> <to-do> <comment when="2020-04-25" who="kalvesmaki">Text needs to be proofread</comment> </to-do> Taken from ar.cat.lat.1961.minio-paluello.ref-scriptum<code><comment></code><TEI TAN-version="2021" id="tag:parkj@textalign.net,2015:gomme.1898.ring-o-roses"> ......... <head> ......... <source> ......... <name>The traditional games of England, Scotland, and Ireland : with tunes, singing-rhymes, and methods of playing according to the variants extant and recorded in different parts of the Kingdom</name> <comment when="2015-03-10" who="park">This work is to be found at vol. 2, pp. 108-111.</comment> </source> ......... <to-do> <comment when="2018-08-09-04:00" who="park">Finish file.</comment> </to-do> </head> ......... </TEI> Taken from gomme.1989.ring-o-roses

<code><companion-version></code>TAN-core.rngThe element companion-version identifies a file closely associated with the current one.In a class 1 file, <companion-version> points to another class 1 file that has a different version of the same work found in the same scriptum.In class 2 and class 3 files, <companion-version> points to a file of the same type, but the nature of the relationship between the two files is not stipulated. It can be used to point to a continuation of a dataset, or to competing one.The sequence of consecutive <companion-version>s is immaterial. Used by: ~networked-files-core<successor> and <companion-version> must point to TAN files of the same type.Class 1 files must share the same source as any redivision or companion version.Class 1 files must share the same work as any model, redivision, or companion version.<code><companion-version></code> <head> ......... <source xml:id="eng"> ......... </source> <companion-version> <IRI>tag:parkj@textalign.net,2015:ar.cat.tan-a:claims</IRI> <name>Comments and claims on Aristotle's Categories</name> <location accessed-when="2021-04-29T11:41:57.716-04:00" href="ar.cat.TAN-A.claims.xml"/> </companion-version> <adjustments src="fra"> ......... </adjustments> ......... </head> Taken from ar.cat.TAN-A

<code><constraints></code>TAN-core.rngThe element constraints specifies the expectations for a given verb. Any verb without constraints is presumed to be transitive, requiring a subject and an object, allowing adverbs, but disallowing opt-in elements, e.g., <in-lang>. Used by: ~entity-nondigital-with-constraints-content<code><constraints></code> <head> ......... <vocabulary-key> ......... <verb xml:id="om"> ......... <desc>This verb is similar to the standard TAN verb "lacks", but expands the definition to persons.</desc> <constraints> <subject status="required" item-type="person work version scriptum"/> <at-ref status="required"/> <object status="disallowed"/> </constraints> </verb> <verb xml:id="attests"> ......... <desc>This verb is similar to the standard TAN verb "matches", but expands the definition to persons.</desc> <constraints> <subject status="required" item-type="person work version scriptum"/> <object status="required" item-type="ref"/> </constraints> </verb> <verb xml:id="has-length"> ......... <desc>This verb is used to describe the how many pages or folios a scriptum is.</desc> <constraints> <subject status="required" item-type="scriptum"/> <object status="required" content-datatype="integer" content-lexical-constraint="\d+"/> </constraints> </verb> ......... </vocabulary-key> ......... </head> Taken from ar.cat.TAN-A.claims<code><constraints></code> <item> ......... <name>wrote</name> <constraints> <subject status="required" item-type="person"/> <object status="required" item-type="work version"/> </constraints> </item> Taken from verbs.TAN-voc

<code><desc></code>TAN-core.rngThe element desc provides a human-readable description of a concept, person, or thing referred to by the parent element (or the current document, if the parent element is <head>). <desc> is, in effect, a <comment> about that concept, person, or thing. Used by: ~element-code, ~metadata-human-readableAll text must be normalized (Unicode NFC).<code><desc></code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2021"> <head> ......... <license licensor="kalvesmaki"> ......... <name>Creative Commons Attribution 4.0 International License</name> <desc>Exclusive of rights held and licenses offered by rightsholders of the source or sources listed below, this data file, insofar as it constitutes an independent work, is licensed under a Creative Commons Attribution 4.0 International License.</desc> </license> ......... <vocabulary-key> ......... <div-type xml:id="ic"> ......... <name>independent clause</name> <desc>used to identify two or more sentence parts that have a subject and predicate and function as a sentence.</desc> </div-type> ......... </vocabulary-key> ......... </head> ......... </TAN-T> Taken from ar.cat.eng.1926.edghill.ref-logical<code><desc></code> <license licensor="kalvesmaki"> ......... <name>Creative Commons Attribution 4.0 International License</name> <desc>Exclusive of rights held and licenses offered by rightsholders of the source or sources listed below, this data file, insofar as it constitutes an independent work, is licensed under a Creative Commons Attribution 4.0 International License.</desc> </license> Taken from ar.cat.eng.1926.edghill.ref-scriptum<code><desc></code> <license licensor="kalvesmaki"> ......... <name>Creative Commons Attribution 4.0 International License</name> <desc>Exclusive of rights held and licenses offered by rightsholders of the source or sources listed below, this data file, insofar as it constitutes an independent work, is licensed under a Creative Commons Attribution 4.0 International License.</desc> </license> Taken from ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949

<code><div></code>TAN-A.rngThe element div restricts a claim to a particular passage in a subject or object. In this context <div> is especially useful for clarifying which part of a scriptum is meant, e.g., page ranges.Unlike class-1 <div>s, this one takes no text and no inclusions.The sequence of consecutive <div>s in a <subject> or <object> is important. A <div> specifies not only which parts of an <object> or <subject> are relevant, but the sequence of those parts. TAN-T.rngThe element div marks a textual unit. Contains other <div>s or text, but not both (i.e., no mixed content).TAN's <div> differs from the TEI's, in that the latter is intended for the first level or levels of subdivision in the front, body, or back of a text, but not for paragraphs or anonymous blocks. The TAN <div> better resembles HTML's, and can be applied to any kind of textual division, even a single character. Used by: ~element-div, ~scriptum-filter, ~body-itemAll text must be normalized (Unicode NFC).Most div references are unique.An @n taking digit values should not begin with 0.Every leaf div must have at least some non-space text.No text may begin with a modifying character.No text may have a spacing character followed by a modifying character.No text may have Unicode characters that are disallowed, e.g., U+A0, NO BREAK SPACE.No reference may point to a mixture of leaf and non-leaf <div>s.An @n's value should not appear in the text.A <div>'s reference (self and ancestor @ns, concatenated) should not appear in the text.Each value in @ref-alias must consist of as many @n values as the current div is deep in the body structure.<code><div></code> <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> Taken from ar.cat.eng.1926.edghill.ref-logical

<code><div-type></code>TAN-core.rngThe element div-type declares a type of textual division (e.g., title, paragraph, stanza). For more information, see and for standard TAN values. Used by: ~voc-element-tan-a, ~voc-element-class-1<code><div-type></code> <head> ......... <vocabulary-key> <algorithm xml:id="xslt2"> ......... </algorithm> <div-type xml:id="ch"> <IRI>http://dbpedia.org/resource/Chapter_(books)</IRI> <name>chapter</name> </div-type> <div-type xml:id="par"> <IRI>http://dbpedia.org/resource/Paragraph</IRI> <name xml:lang="eng">paragraph</name> </div-type> <div-type xml:id="s"> <IRI>http://dbpedia.org/resource/Sentence_(linguistics)</IRI> <name>sentence</name> </div-type> <div-type xml:id="ic"> <IRI>https://en.wikipedia.org/wiki/Independent_clause</IRI> <name>independent clause</name> <desc>used to identify two or more sentence parts that have a subject and predicate and function as a sentence.</desc> </div-type> <div-type xml:id="pt" which="part"/> ......... </vocabulary-key> ......... </head> Taken from ar.cat.eng.1926.edghill.ref-logical

<code><doc></code>catalog.tan.rng Used by: <collection>

<code><equate></code>TAN-class-2.rngThe element equate declares an ad hoc equivalence in @n values. It behaves like <alias> but has scope only over a particular source. For example, <equate n="pr pref preface introduction"/> specifies that sources with <div> @n values of either "pr", "pref", "preface", or "introduction" should be treated as equivalent. Hence, in the <body> any @ref="pr" will also match a <div n="introduction"/>This element does not imply that the @n values are the same. It merely states that, for the purposes of this class-2 file, they should be treated as equivalent.Only the first <equate> applying to a <div> in a given source will be applied. Used by: ~adjust-class-2Only the first of multiple adjustment actions will be applied. Action priority: skip, ref-based rename, then for every @n n-based rename, equate.In adjustment actions involving @n, at least one value should be found in each source.The values of @n in <equate> should not have duplicates.At least one @n value in an equate should be found in every source.<code><equate></code> <adjustments src="fra"> <skip div-type="summ" shallow="false"/> <equate n="ti title"/> <reassign> ......... </reassign> </adjustments> Taken from ar.cat.TAN-A

<code><feature></code>TAN-mor.rngThe element feature names, through its IRI + name pattern, a grammatical feature or concept (e.g., plural, subjunctive, 1st person) that is part of a language. In the context of <category> a @code is always included. The first <feature> of a <category>, however, never has a @code, because it describes the grammatical class of the <category>.The sequence of consecutive <feature>s is immaterial.See for a list of standard features. Used by: ~voc-element-non-class-3<code><feature></code> <head> ......... <vocabulary-key ed-when="2015-03-03" ed-who="kalvesmaki"> ......... <algorithm xml:id="xslt1"> ......... </algorithm> <feature xml:id="cl-quo"> <IRI>tag:textalign.net,2015:morphology:option:quotation-mark-closing</IRI> <name>closing quotation mark</name> <desc>Examples: ' ''</desc> </feature> <feature xml:id="dash"> <IRI>http://dbpedia.org/resource/Dash</IRI> <name>dash</name> <desc>Examples: --</desc> </feature> <feature xml:id="x24"> <IRI>http://dbpedia.org/resource/Dollar_sign</IRI> <name>dollar</name> <desc>Examples: $ -$ --$ A$ C$ HK$ M$ NZ$ S$ U.S.$ US$</desc> </feature> <feature xml:id="x2E"> <IRI>tag:textalign.net,2015:morphology:option:punctuation:sentence-closer</IRI> <name>sentence closer</name> <desc>Examples: ; . ! ?</desc> </feature> <feature xml:id="x3A"> ......... </feature> ......... </vocabulary-key> ......... </head> Taken from eng.kalvesmaki.com,2014.2

<code><file-resp></code>TAN-core.rngThe element file-resp specifies the persons, organizations, or algorithms that are primarily responsible for the file. Any unattributed claims or assertions made in the file will be credited to/blamed upon these agents. At least one of these agents must be given an IRI in the namespace of the file @id.. Used by: ~resp-list<code><file-resp></code> <head> ......... <vocabulary-key> ......... </vocabulary-key> <file-resp who="kalvesmaki"/> <resp who="xslt2" roles="stylesheet1"/> ......... </head> Taken from ar.cat.eng.1926.edghill.ref-logical<code><file-resp></code> <head> ......... <vocabulary-key> ......... </vocabulary-key> <file-resp who="kalvesmaki"/> <resp roles="editor" who="kalvesmaki"/> ......... </head> Taken from ar.cat.eng.1926.edghill.ref-scriptum<code><file-resp></code> <head> ......... <vocabulary-key> ......... </vocabulary-key> <file-resp who="kalvesmaki"/> <resp who="xslt2" roles="stylesheet1"/> ......... </head> Taken from ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949<code><file-resp></code> <head> ......... <vocabulary-key> ......... </vocabulary-key> <file-resp who="kalvesmaki"/> <resp who="xslt2" roles="stylesheet1"/> ......... </head> Taken from ar.cat.fra.1844.saint-hilaire.ref-logical

<code><for-lang></code>TAN-core.rngThe element for-lang specifies a language that is being discussed. This element does not identify the language of the text enclosed by the parent element (one must use @xml:lang for that purpose).Values should adhere to BCP (Best Common Practices) 47, http://www.rfc-editor.org/rfc/bcp/bcp47.txt. For more details see .Examples: 'eng' (English), 'grc' (classical Greek), 'lat' (Latin). For more see The sequence of consecutive <for-lang>s is immaterial. Used by: ~decl-non-class-2, ~decl-non-class-3<code><for-lang></code> <head> ......... <license which="Attribution-ShareAlike 3.0 Unported" licensor="perseus"/> <for-lang>grc</for-lang> <tok-is>ἆ</tok-is> ......... </head> Taken from grc-tan-a-lm-%CE%B1<code><for-lang></code> <head> ......... <license which="Attribution-ShareAlike 3.0 Unported" licensor="perseus"/> <for-lang>grc</for-lang> <tok-starts-with>αʹ</tok-starts-with> ......... </head> Taken from grc-tan-a-lm-%CE%B1%CA%B9<code><for-lang></code> <head> ......... <license licensor="kalvesmaki"> ......... </license> <for-lang>eng</for-lang> <source> ......... </source> ......... </head> Taken from eng.kalvesmaki.com,2014.2<code><for-lang></code> <head> ......... <license licensor="kalvesmaki"> ......... </license> <for-lang>grc</for-lang> <source> ......... </source> ......... </head> Taken from grc.perseus.tan-mor

<code><from-tok></code>TAN-class-2.rngDefinition 1The element from-tok points to a single token that is the start of a range of tokens to be selected from a source, but without @ref..Definition 2The element from-tok points to a single token that is the start of a range of tokens to be selected from a source, in the context of @ref.. Used by: ~text-passage-selector-no-ref, ~text-passage-selector-with-refEvery token must be locatable in every cited ref in every source.In a <reassign>, the token referred to at <from-tok> must precede the one referred to by <through-tok>.<code><from-tok></code> <passage ref="5 4 7 2"> <from-tok val=":" pos="1"/> <through-tok val=":" pos="1"/> </passage> Taken from ar.cat.TAN-A<code><from-tok></code> <subject src="eng-uk"> <tok ref="2" pos="2-3" chars="3-4"/> <from-tok ref="1" pos="3"/> <through-tok ref="2" pos="1"/> </subject> Taken from ringoroses.div.1

<code><group></code>TAN-class-2.rngThe element group groups token references that should be treated as referring to but a single token. TAN-core.rngThe element group collects items that share a common property, defined by the <group-type> to which it refers. Used by: ~element-ana, ~element-align, ~body-group@affects-element may take names only of those TAN elements that accept @which@affects-element may take the value "vocabulary" only in official TAN-voc files.<code><group></code> <ana> <group> <tok ref="1" pos="1 - last-1"/> </group> <lm> ......... </lm> </ana> Taken from ring-o-roses.eng.1881.lm<code><group></code><TAN-voc TAN-version="2021" id="tag:parkj@textalign.net,2015:TAN-key:ar.cat"> ......... <body affects-element="work"> ......... <item> ......... </item> <group> <item> ......... </item> <item> ......... </item> </group> <group> <item> ......... </item> <item> ......... </item> </group> <group> <item> ......... </item> <item> ......... </item> </group> <group> ......... </group> ......... </body> </TAN-voc> Taken from ar.cat.TAN-voc

<code><group-type></code>TAN-core.rngThe element group-type names types of <group>s. See for standard TAN values. Used by: ~voc-element-class-2, ~voc-element-class-3<code><group-type></code> <vocabulary-key> ......... <morphology xml:id="Perseus"> ......... </morphology> <group-type xml:id="status" which="status"/> <person include="rel"/> ......... </vocabulary-key> Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-A-lm-sample<code><group-type></code> <head> ......... <vocabulary-key> <group-type xml:id="inline-start" which="no new line start"/> <group-type xml:id="inline-end" which="no new line end"/> <group-type xml:id="line-start" which="new line start"/> <group-type xml:id="line-end" which="new line end"/> ......... </vocabulary-key> ......... </head> Taken from div-types.TAN-voc

<code><head></code>TAN-core.rngThe element head contains the metadata (data about the data in the <body>)For more see Used by: ~TAN-root<code><head></code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2021"> <head> <name>Categories, Aristotle, English translation by E. M. Edghill</name> <master-location href="https://raw.githubusercontent.com/textalign/TAN-2021/master/examples/ar.cat.eng.1926.edghill.ref-logical.xml"/> <license licensor="kalvesmaki"> ......... </license> ......... </head> <body xml:lang="eng"> ......... </body> </TAN-T> Taken from ar.cat.eng.1926.edghill.ref-logical<code><head></code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:model-object-refs" TAN-version="2021"> <head> <name>Categories, Aristotle, English translation by E. M. Edghill</name> <master-location href="https://raw.githubusercontent.com/textalign/TAN-2021/master/examples/ar.cat.eng.1926.edghill.ref-scriptum.xml"/> <license licensor="kalvesmaki"> ......... </license> ......... </head> <body xml:lang="eng"> ......... </body> </TAN-T> Taken from ar.cat.eng.1926.edghill.ref-scriptum<code><head></code><TAN-T TAN-version="2021" id="tag:kalvesmaki.com,2014:tan-t:ar.cat.fra.1844.saint-hilaire:semantic-refs-realigned"> <head> <name>Realignment of Categories, Aristotle, French translation by J. Barthélemy Saint-Hilaire</name> <master-location href="https://raw.githubusercontent.com/textalign/TAN-2021/master/examples/ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949.xml"/> <license licensor="kalvesmaki"> ......... </license> ......... </head> <body xml:lang="fra"> ......... </body> </TAN-T> Taken from ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949<code><head></code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.fra.1844.saint-hilaire:semantic-refs" TAN-version="2021"> <head> <name>Categories, Aristotle, French translation by J. Barthélemy Saint-Hilaire</name> <master-location href="https://raw.githubusercontent.com/textalign/TAN-2021/master/examples/ar.cat.fra.1844.saint-hilaire.ref-logical-after.xml"/> <license licensor="kalvesmaki"> ......... </license> ......... </head> <body xml:lang="fra"> ......... </body> </TAN-T> Taken from ar.cat.fra.1844.saint-hilaire.ref-logical

<code><in-lang></code>TAN-A.rngThe element in-lang restricts a claim to a particular language; used with only certain verbs, e.g., "translates".Multiple values of <in-lang> are interpreted to mean "and", resulting in distribution of the claim. By default, <in-lang> is disallowed. A verb's constrained IRI + name pattern must explicitly require or allow it. TAN-core.rngThe element in-lang specifies whether a verb uses <in-lang> (default: disallowed). Used by: ~element-claim, ~in-lang, ~constraints-on-verb<code><in-lang></code> <constraints> ......... <object status="required" item-type="ref scriptum work version source"/> <in-lang status="allowed"/> </constraints> Taken from verbs.TAN-voc

<code><inclusion></code>TAN-core.rngThe element inclusion specifies a TAN file that is available for inclusion. An inclusion occurs whenever an element X points to this inclusion by means of @include.. TAN-compliant validators and processors will find every element X that is found in the included file (checked recursively, against any inclusions of X adopted by the inclusion) and insert them at that place in the dependent document.Only select elements will be included, not the entire inclusion file. Exactly which elements are included is dictated by @include placed in select empty elements.The presence of an <inclusion> does not require its use, although it may add time to the validation process. The sequence of consecutive <inclusion>s is immaterial.For more, see Used by: ~element-ana, ~element-align, ~element-claim, ~element-category, ~element-code, ~element-rule, ~element-div, ~element-item, ~element-replace, ~adj-element-equate, ~adj-element-reassign, ~adj-element-rename, ~adj-element-skip, ~element-group-for-tok, ~element-adjustments, ~element-file-resp, ~element-group, ~element-license, ~element-resp, ~element-to-do, ~element-token-definition, ~link-element-see-also, ~voc-element-period, ~entity-digital-nontan-id, ~entity-digital-nontan-no-id, ~entity-digital-tan-id, ~entity-digital-tan-no-id, ~entity-nondigital-constrained, ~entity-nondigital-id, ~entity-nondigital-no-id, ~networked-files-coreAn inclusion must point to a TAN fileFor any element with @include, at least one element of the same name must be found in target inclusion document.Inclusions are integral parts of any TAN file. Access to at least one copy is absolutely mandatory.Inclusions/vocabularies may not be invoked circularly.The vocabulary of a file may not include it.The @TAN-version for inclusions and vocabularies should match the current version.An element that has a <location> and is key for validation should have at least one document available.Every TAN file referred to by way of an element containing <location> should have an @id that matches the <IRI> of the parent of the <location>No element may point to a TAN file that has an identical @id value; the only exception is <predecessor> and <successor>.If a target file has children items in the <to-do>the corresponding comments will be returned as warnings.If a target file has a <successor> a warning will be returned, noting the update.If a target file points only to non-local locations and no internet is available, the following message will be returned. No internet available.If a linking element points to a file that must be resolved, that file must be a TAN file.If @accessed-when predates one or more dates in a target file, a warning will be returned.<code><inclusion></code> <head> ......... <work which="matthew"/> <inclusion xml:id="serm-mount"> <IRI>tag:parkj@textalign.net,2015:bible:matthew:sermon-on-the-mount</IRI> <name>Sermon on the Mount, King James Version of the Bible, 1760 edition</name> <location accessed-when="2019-10-09T02:09:11.163-04:00" href="sermon-on-the-mount.eng.kjv.1760.xml"/> </inclusion> <vocabulary which="bible eng" accessed-when="2019-10-08"/> ......... </head> Taken from matt.eng.kjv.1760<code><inclusion></code> <head> ......... <source which="kjv 1760"/> <inclusion xml:id="lords-prayer"> <IRI>tag:parkj@textalign.net,2015:bible:matthew:lords-prayer</IRI> <name>Matthew's version of the Lord's Prayer, King James Version of the Bible, 1760 edition</name> <location accessed-when="2019-10-09T02:32:50.973-04:00" href="lords-prayer.eng.kjv.1760.xml"/> </inclusion> <vocabulary-key> ......... </vocabulary-key> ......... </head> Taken from sermon-on-the-mount.eng.kjv.1760<code><inclusion></code> <head> ......... <token-definition pattern="[\w‍]+"/> <inclusion xml:id="rel"> <IRI>tag:kalvesmaki.com,2014:tan-t:ar.cat.grc.1949.minio-paluello:object-refs</IRI> <name>Categories, Aristotle, Greek text by Minio-Paluello</name> <location href="../ar.cat.grc.1949.minio-paluello.ref-scriptum.xml" accessed-when="2016-09-28T08:50:23.457-04:00"/> </inclusion> <source> ......... </source> ......... </head> Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-A-lm-sample

<code><IRI></code>TAN-core.rngThe element IRI contains an International Resource Identifier that names the concept, person, or thing referred to by the parent element. Any kind of IRIs are allowed: URLs, tag URNs, UUIDs, etc. For names of well-known resources, an HTTP URL identifier might be preferred, to facilitate linked data. If an entity/resource lacks a suitable URL-type name, you may use or coin any other valid IRI, such as a UUID, a tag URN, or an OID. Some concepts may be difficult to find IRIs for.Sibling <IRI>s are to be treated as names for the same thing, not as names of different things. Loosely, sibling <IRI>s can be thought of as synonymous, but technically the are only poecilonymic. In the terms of Web Ontology Language (http://www.w3.org/TR/owl-ref/), sibling <IRI>s cannot be assumed to share the relationship owl:sameAs, because they will draw from independent vocabularies that may identify similar concepts differently. An element given multiple <IRI>s refers to one or more items within the intersection, not the union, of the target concepts. Nevertheless, most interpretations of TAN files will draw inferences based upon the union. That is, if item A is assigned IRI X, item B IRIs X and Y, and item C IRI Y, it is likely that users of the data will infer identity between items A and C. The sequence of consecutive <IRI>s is immaterial.The element is named IRI instead of URI to encourage internationalization, and the use of alphabets other than Latin. An <IRI> from the standard TAN vocabulary may be overridden locally.For more see . Used by: ~entity-digital-core-content, ~entity-nondigital-content, ~entity-nondigital-with-constraints-contentAn IRI may appear no more than once in a TAN document.An IRI that names a TAN file must match that file's @id exactly.Any IRI beginning urn: must continue with a name that is part of the official IANA Registry of URN Namespaces. See RFC 2414, https://tools.ietf.org/html/rfc8141, and https://www.iana.org/assignments/urn-namespaces/urn-namespaces.xhtmlNo file may import vocabularies with items that have duplicate IRIs.All text must be normalized (Unicode NFC).Every item in a reserved TAN-voc must have at least one IRI with a tag URN in the TAN namespace<code><IRI></code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2021"> <head> ......... <license licensor="kalvesmaki"> <IRI>http://creativecommons.org/licenses/by/4.0/deed.en_US</IRI> <name>Creative Commons Attribution 4.0 International License</name> ......... </license> <work> <IRI>http://dbpedia.org/resource/Categories_(Aristotle)</IRI> <name>Aristotle, Categories</name> </work> <source> <IRI>http://id.lib.harvard.edu/aleph/007901738/catalog</IRI> <name>Aristotle: Categoriae & De interpretatione by E.M. Edghill. Analytica priora / by A.J. Jenkinson. Analytica posteriora / by G.R.G. Mure. Oxford : Clarendon Press, 1926. </name> </source> <model> <IRI>tag:kalvesmaki.com,2014:tan-t:ar.cat.grc.1949.minio-paluello:semantic-refs</IRI> <name>Categories, Aristotle, Greek text by Minio-Paluello</name> ......... </model> ......... </head> ......... </TAN-T> Taken from ar.cat.eng.1926.edghill.ref-logical

<code><item></code>TAN-voc.rngThe element item provides a container for IRI, names, and descriptions of something. The item is assumed to be a type (or types) of thing indicated by the values of the closest @affects-attribute or @affects-element..An <item> does not describe verbs, which have special constraints. Use <verb> instead. Used by: ~body-itemNames must be unique for vocabulary items assigned to a given element name.@affects-element may take names only of those TAN elements that accept @which@affects-element may take the value "vocabulary" only in official TAN-voc files.Every item in a reserved TAN-voc must have at least one IRI with a tag URN in the TAN namespace<code><item></code><TAN-voc TAN-version="2021" id="tag:parkj@textalign.net,2015:TAN-key:ar.cat"> ......... <body affects-element="work"> <item> <IRI>http://dbpedia.org/resource/Categories_(Aristotle)</IRI> <name xml:lang="fra">Aristote, Catégories</name> <name xml:lang="eng">Aristotle, Categories</name> </item> <item> <IRI>tag:parkj@textalign.net,2015:work:porphyry:on-aristotles-categories</IRI> <name xml:lang="lat">Commentarium graecum Porphyrii</name> <name xml:lang="eng">Porphyry's commentary on Aristotle's Categories</name> </item> <item> <IRI>tag:parkj@textalign.net,2015:work:dexippus:on-aristotles-categories</IRI> <name xml:lang="lat">Commentarium graecum Dexippi</name> <name xml:lang="eng">Dexippus's commentary on Aristotle's Categories</name> </item> <group> <item> <IRI>tag:parkj@textalign.net,2015:work:ammonius:on-aristotles-categories:lemmata</IRI> <name xml:lang="lat">Lemmata de commentario graeco Ammonii</name> <name xml:lang="eng">Lemmata from Ammonius's commentary on Aristotle's Categories</name> </item> <item> ......... </item> </group> ......... </body> </TAN-voc> Taken from ar.cat.TAN-voc

<code><l></code>TAN-A-lm.rngThe element l names a lexeme, by pointing to the main word entry in the lexicon identified by the element's inherited value(s) of @lexicon.. This element should not be used to point to roots, only to lexical headwords. In many languages, especially those that are lightly inflected, the lexeme will be identical to the word token itself. If <l> is omitted, the calculated value of <tok> is to be inferred as its value.The sequence of consecutive <l>s is immaterial. Used by: ~element-lm<code><l></code><TAN-A-lm TAN-version="2021" id="tag:kalvesmaki.com,2014:tan-t:ar.cat.grc.1949.minio-paluello:semantic-refs:TAN-A-lm:2016-04-05T07:07:40.033-04:00"> ......... <body lexicon="LSJ Lampe new" morphology="Perseus" claimant="xslt2"> <ana tok-pop="2"> ......... <lm> <l>Δῆλος</l> <m>n e - s - - - f a -</m> </lm> </ana> <ana> ......... <lm> <l>Σωκράτης</l> <m>n e - s - - - m g -</m> </lm> </ana> <ana> ......... <lm> <l>αἰσχύνω</l> <m>v - - - a n p - - -</m> </lm> </ana> <ana> ......... <lm> <l>αἴσθησις</l> <m>n - - s - - - f n -</m> </lm> </ana> <ana> ......... <lm> <l>αἴσθησις</l> <m>n - - s - - - f g -</m> </lm> </ana> ......... </body> </TAN-A-lm> Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-A-lm-sample

<code><lexicon></code>TAN-A-lm.rngThe element lexicon names a lexicographical authority. Used by: ~voc-element-non-class-2<code><lexicon></code> <head> ......... <vocabulary-key> <algorithm xml:id="xslt2"> ......... </algorithm> <lexicon xml:id="LSJ"> <IRI>http://lccn.loc.gov/95032369</IRI> <name xml:lang="eng">Liddell-Scott-Jones, 9th ed. plus rev. supplement</name> </lexicon> <lexicon xml:id="Lampe"> <IRI>http://lccn.loc.gov/77372171</IRI> <name xml:lang="eng">G.H.W. Lampe, A Patristic Greek Lexicon, Oxford 1961.</name> </lexicon> <lexicon xml:id="new"> <IRI>urn:uuid:d6558d00-8f68-11e3-950a-425861b86ab6</IRI> <name xml:lang="eng">Lexicon generated from words in this document not to be found in any other lexicon.</name> </lexicon> <morphology xml:id="Perseus"> ......... </morphology> ......... </vocabulary-key> ......... </head> Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-A-lm-sample<code><lexicon></code> <vocabulary-key> ......... <algorithm xml:id="xslt1"> ......... </algorithm> <lexicon xml:id="LSJ"> <IRI>http://lccn.loc.gov/95032369</IRI> <name>Liddell-Scott-Jones 9+</name> <name xml:lang="eng">Liddell-Scott-Jones, 9th ed. plus rev. supplement</name> </lexicon> <morphology xml:id="perseus-dik"> ......... </morphology> ......... </vocabulary-key> Taken from grc-tan-a-lm-%CE%B1

<code><license></code>TAN-core.rngThe element license states the license under which the data is distributed and the rights associated with it, exclusive of any rights attached to the source.Diligently check to ensure that the license you have claimed respects the rights of your sources' rightsholders. It is recommended that you license your data under a license that is similar to or more liberal than the one under which your sources have been released.For more discussion, see and for a list of standard TAN vocabulary, Used by: ~declaration-core<code><license></code> <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> Taken from ar.cat.eng.1926.edghill.ref-logical<code><license></code> <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> Taken from ar.cat.eng.1926.edghill.ref-scriptum<code><license></code> <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> Taken from ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949<code><license></code> <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> Taken from ar.cat.fra.1844.saint-hilaire.ref-logical

<code><lm></code>TAN-A-lm.rngThe element lm groups lexical or morphological data.Components within <lm> combine with each other and with all sibling <tok>s. That is, every <l> is asserted against every <m> within an <lm> is asserted of every <tok>.The sequence of consecutive <lm>s is immaterial. Used by: ~element-ana<code><lm></code><TAN-A-lm TAN-version="2021" id="tag:kalvesmaki.com,2014:tan-t:ar.cat.grc.1949.minio-paluello:semantic-refs:TAN-A-lm:2016-04-05T07:07:40.033-04:00"> ......... <body lexicon="LSJ Lampe new" morphology="Perseus" claimant="xslt2"> <ana tok-pop="2"> <tok ref="11 2 1 1" pos="1"/> <lm> <l>Δῆλος</l> <m>n e - s - - - f a -</m> </lm> </ana> <ana> ......... <tok ref="10 6 4 2" pos="37"/> <lm> <l>Σωκράτης</l> <m>n e - s - - - m g -</m> </lm> </ana> <ana> ......... <tok ref="8 3 7 3" pos="7"/> <lm> <l>αἰσχύνω</l> <m>v - - - a n p - - -</m> </lm> </ana> <ana> ......... <tok ref="7 4 9 2" pos="4"/> <lm> <l>αἴσθησις</l> <m>n - - s - - - f n -</m> </lm> </ana> ......... </body> </TAN-A-lm> Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-A-lm-sample

<code><location></code>TAN-core.rngThe element location declares where an electronic file was found and when. The URL may be absolute or relative to the current document. The sequence of consecutive <location>s is important. During TAN validation, the first <location> with an available document will be used, and the following sibling <location>s will be ignored. Used by: ~entity-digital-core-content@href must have <location> or <master-location> as a parent; any other parent will trigger a quick fix to populate the element with the IRI + name pattern of the target file.If an @href points to a local file that is not available, a warning will be returned. @href points to file that is either (1) not available or (2) not valid XMLIf an @href points to a file that is not local, and no internet is available, a warning will be returned. No internet access.If the internet is available, and an @href points to a non-local file that is not available, a warning will be returned. @href points to non-local file that is either (1) not available, (2) not valid XML, or (3) at a server not trusted by the validation engine.The only @href in a TAN document that may point to another document with the same document id is that of <master-location> or <see-also>No @href should point to the URI of the document itself.An @href that points to a local drive should have "file:/" prepended.An element that has a <location> and is key for validation should have at least one document available.Every TAN file referred to by way of an element containing <location> should have an @id that matches the <IRI> of the parent of the <location>No element may point to a TAN file that has an identical @id value; the only exception is <predecessor> and <successor>.If a target file has children items in the <to-do>the corresponding comments will be returned as warnings.If a target file has a <successor> a warning will be returned, noting the update.If a target file points only to non-local locations and no internet is available, the following message will be returned. No internet available.If a linking element points to a file that must be resolved, that file must be a TAN file.If an element not essential to validation has no <location> that points to a document a warning should be returned.If @accessed-when predates one or more dates in a target file, a warning will be returned.<code><location></code><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> Taken from ar.cat.eng.1926.edghill.ref-logical

<code><m></code>TAN-A-lm.rngThe element m carries a morphological code that conforms to the rules or patterns defined in the TAN-mor file upon which the data depends.Codes are space-delimited. If a value of <m> violates the rules established by the dependency TAN-mor file, an error will be generated. For more about how codes are built, and how they function, see .The sequence of consecutive <m>s is immaterial. Used by: ~element-lmWhen using a category-based morphology, the number of feature codes in an <m> may not exceed the number of categories.Every feature code in an <m> must be found in the target morphology file.Every condition of a relevant dependency morphology <assert> (<report>) must be true (false) otherwise an error will be returned.

<code><master-location></code>TAN-core.rngThe element master-location points to a location where a master copy of the file is to be found. Use of this element entails a commitment to updating the TAN file in that location.The URL may be absolute or relative to the current document. <master-location> does not disallow the file from being kept, published, or distributed elsewhere. It merely indicates where an authoritative version of the file is to be found. Used by: ~entity-digital-tan-self-contentAny TAN file without a to-do list will be treated as being no longer in progress and should have at least one master-location.@href must have <location> or <master-location> as a parent; any other parent will trigger a quick fix to populate the element with the IRI + name pattern of the target file.If an @href points to a local file that is not available, a warning will be returned. @href points to file that is either (1) not available or (2) not valid XMLIf an @href points to a file that is not local, and no internet is available, a warning will be returned. No internet access.If the internet is available, and an @href points to a non-local file that is not available, a warning will be returned. @href points to non-local file that is either (1) not available, (2) not valid XML, or (3) at a server not trusted by the validation engine.The only @href in a TAN document that may point to another document with the same document id is that of <master-location> or <see-also>No @href should point to the URI of the document itself.An @href that points to a local drive should have "file:/" prepended.No <master-location> may have an @href that points to a compressed archive.Files should match the version kept at <master-location>.<code><master-location></code> <head> <name>Categories, Aristotle, English translation by E. M. Edghill</name> <master-location href="https://raw.githubusercontent.com/textalign/TAN-2021/master/examples/ar.cat.eng.1926.edghill.ref-logical.xml"/> <license licensor="kalvesmaki"> ......... </license> ......... </head> Taken from ar.cat.eng.1926.edghill.ref-logical<code><master-location></code> <head> <name>Categories, Aristotle, English translation by E. M. Edghill</name> <master-location href="https://raw.githubusercontent.com/textalign/TAN-2021/master/examples/ar.cat.eng.1926.edghill.ref-scriptum.xml"/> <license licensor="kalvesmaki"> ......... </license> ......... </head> Taken from ar.cat.eng.1926.edghill.ref-scriptum<code><master-location></code> <head> <name>Realignment of Categories, Aristotle, French translation by J. Barthélemy Saint-Hilaire</name> <master-location href="https://raw.githubusercontent.com/textalign/TAN-2021/master/examples/ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949.xml"/> <license licensor="kalvesmaki"> ......... </license> ......... </head> Taken from ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949<code><master-location></code> <head> <name>Categories, Aristotle, French translation by J. Barthélemy Saint-Hilaire</name> <master-location href="https://raw.githubusercontent.com/textalign/TAN-2021/master/examples/ar.cat.fra.1844.saint-hilaire.ref-logical-after.xml"/> <license licensor="kalvesmaki"> ......... </license> ......... </head> Taken from ar.cat.fra.1844.saint-hilaire.ref-logical

<code><modal></code>TAN-A.rngThe element modal contains an IRI + name pattern identifying a modal or adverb that qualifies the verb of an assertion.See for standard TAN vocabulary. Used by: ~voc-element-tan-a<code><modal></code> <vocabulary-key> ......... <unit xml:id="folio"> ......... </unit> <modal which="possibly" xml:id="perhaps"/> <person xml:id="park"> ......... </person> ......... </vocabulary-key> Taken from ar.cat.TAN-A.claims

<code><model></code>TAN-class-1.rngThe element model identifies a class-1 file has been used as a model for how the current file has been segmented and labeled.A file need not follow its model exactly. Upon verbose validation, differences between the file and its model will be reported only as warnings. Used by: ~networked-files-non-core<model> and <redivision> must point to class 1 TAN filesAn element that has a <location> and is key for validation should have at least one document available.Every TAN file referred to by way of an element containing <location> should have an @id that matches the <IRI> of the parent of the <location>No element may point to a TAN file that has an identical @id value; the only exception is <predecessor> and <successor>.If a target file has children items in the <to-do>the corresponding comments will be returned as warnings.If a target file has a <successor> a warning will be returned, noting the update.If a target file points only to non-local locations and no internet is available, the following message will be returned. No internet available.If a linking element points to a file that must be resolved, that file must be a TAN file.If a class 1 file diverges from the structure of its model a warning will be generated specifying where differences exist.A class 1 file with a <model> should not declare a <reference-system>, which is inherited from the model.Class 1 files must share the same work as any model, redivision, or companion version.<code><model></code> <head> ......... <source> ......... </source> <model> <IRI>tag:kalvesmaki.com,2014:tan-t:ar.cat.grc.1949.minio-paluello:semantic-refs</IRI> <name>Categories, Aristotle, Greek text by Minio-Paluello</name> <location href="ar.cat.grc.1949.minio-paluello.ref-logical.xml" accessed-when="2016-02-10T14:08:52.058-05:00"/> </model> <see-also relationship="alt"> ......... </see-also> ......... </head> Taken from ar.cat.eng.1926.edghill.ref-logical<code><model></code> <head> ......... <redivision> ......... </redivision> <model> <IRI>tag:kalvesmaki.com,2014:tan-t:ar.cat.grc.1949.minio-paluello:object-refs</IRI> <name>Categories, Aristotle, Greek text by Minio-Paluello</name> <location href="ar.cat.grc.1949.minio-paluello.ref-scriptum.xml" accessed-when="2016-07-07T16:36:28.867-04:00"/> </model> <adjustments> ......... </adjustments> ......... </head> Taken from ar.cat.eng.1926.edghill.ref-scriptum<code><model></code> <head> ......... <redivision> ......... </redivision> <model> <IRI>tag:kalvesmaki.com,2014:tan-t:ar.cat.grc.1949.minio-paluello:semantic-refs</IRI> <name>Categories, Aristotle, Greek text by Minio-Paluello</name> <location href="ar.cat.grc.1949.minio-paluello.ref-logical.xml" accessed-when="2016-07-14T11:38:29.251-04:00"/> </model> <adjustments> ......... </adjustments> ......... </head> Taken from ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949<code><model></code> <head> ......... <vocabulary> ......... </vocabulary> <model> <IRI>tag:parkj@textalign.net,2015:ring04</IRI> <name>TAN transcription of 1790 version of Ring around the Rosie reported by Newell in 1883</name> <location accessed-when="2021-04-27-04:00" href="ring-o-roses.eng.1951.xml"/> </model> <adjustments> ......... </adjustments> ......... </head> Taken from ring-o-roses.eng.1987

<code><morphology></code>TAN-A-lm.rngThe element morphology identifies a dependency <TAN-mor> file that defines the parts of speech for a language, the codes for those parts, and the rules for combining them Used by: ~voc-element-non-class-2<morphology> must point to TAN-mor files.<code><morphology></code> <vocabulary-key> ......... <lexicon xml:id="new"> ......... </lexicon> <morphology xml:id="Perseus"> <IRI>tag:kalvesmaki.com,2014:tan-r-mor:grc:perseus</IRI> <name xml:lang="eng">Perseus Greek morphology</name> <location href="../../../library-lm/grc/grc.perseus.tan-mor.xml" accessed-when="2021-01-11"/> </morphology> <group-type xml:id="status" which="status"/> ......... </vocabulary-key> Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-A-lm-sample<code><morphology></code> <vocabulary-key> ......... <lexicon xml:id="LSJ"> ......... </lexicon> <morphology xml:id="perseus-dik"> <IRI>tag:kalvesmaki.com,2014:tan-r-mor:grc:perseus</IRI> <name xml:lang="eng">Perseus Greek morphology</name> <location accessed-when="2020-03-05" href="../TAN-mor/grc.perseus.tan-mor.xml"/> </morphology> <organization xml:id="perseus"> ......... </organization> ......... </vocabulary-key> Taken from grc-tan-a-lm-%CE%B1<code><morphology></code> <vocabulary-key> ......... <lexicon xml:id="LSJ"> ......... </lexicon> <morphology xml:id="perseus-dik"> <IRI>tag:kalvesmaki.com,2014:tan-r-mor:grc:perseus</IRI> <name xml:lang="eng">Perseus Greek morphology</name> <location accessed-when="2020-03-05" href="../TAN-mor/grc.perseus.tan-mor.xml"/> </morphology> <organization xml:id="perseus"> ......... </organization> ......... </vocabulary-key> Taken from grc-tan-a-lm-%CE%B1%CA%B9<code><morphology></code> <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> Taken from ring-o-roses.eng.1881.lm

<code><n-alias></code>TAN-class-1.rngThe element n-alias specifies whether aliases for n should be applied selectively. For files that use <vocabulary> with @which, for extra @n vocabulary, this element improves the efficiency of validation. Used by: ~decl-class-1<code><n-alias></code> <head> ......... <reference-system type="logical" wf-ready="true"/> <n-alias div-type="book"/> <work which="matthew"/> ......... </head> Taken from matt.eng.kjv.1760

<code><name></code>TAN-core.rngThe element name provides a human-readable name of a concept, person, or thing referred to by the parent element (or the current document, if the parent element is <head>).A name must be unique within a file for a given class of items. That is, if "page" is the name of a div type, there must be no other div type vocabulary item with that name, but "page" could still be used as the <name> of a verb or person. The sequence of consecutive <name>s is immaterial. Some applications may adopt the first <name> as the primary one. Used by: ~metadata-human-readableAll text must be normalized (Unicode NFC).Names must be unique for vocabulary items assigned to a given element name.Names may not duplicate names reserved by standard TAN vocabulary for the affected element.Names may not be duplicates of, case-variants of, or hyphen variants of other names for the same element.Each <name> in standard TAN vocabulary must already be normalized.<code><name></code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2021"> <head> <name>Categories, Aristotle, English translation by E. M. Edghill</name> <master-location href="https://raw.githubusercontent.com/textalign/TAN-2021/master/examples/ar.cat.eng.1926.edghill.ref-logical.xml"/> <license licensor="kalvesmaki"> <IRI>http://creativecommons.org/licenses/by/4.0/deed.en_US</IRI> <name>Creative Commons Attribution 4.0 International License</name> <desc>Exclusive of rights held and licenses offered by rightsholders of the source or sources listed below, this data file, insofar as it constitutes an independent work, is licensed under a Creative Commons Attribution 4.0 International License.</desc> </license> <work> <IRI>http://dbpedia.org/resource/Categories_(Aristotle)</IRI> <name>Aristotle, Categories</name> </work> <source> <IRI>http://id.lib.harvard.edu/aleph/007901738/catalog</IRI> <name>Aristotle: Categoriae & De interpretatione by E.M. Edghill. Analytica priora / by A.J. Jenkinson. Analytica posteriora / by G.R.G. Mure. Oxford : Clarendon Press, 1926. </name> </source> ......... <redivision> <IRI>tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:model-object-refs</IRI> <name>Categories, Aristotle, English translation by E. M. Edghill</name> <location href="ar.cat.eng.1926.edghill.ref-scriptum.xml" accessed-when="2016-06-22T08:13:35.791-04:00"/> </redivision> ......... </head> ......... </TAN-T> Taken from ar.cat.eng.1926.edghill.ref-logical

<code><normalization></code>TAN-class-1.rngThe element normalization specifies an alteration that has been made to a source file to bring the transcription into conformity with standards or common expectations. This element is used typically for minor corrections, e.g., suppression of discretionary hyphenation. You should declare every normalizing change you have made to the source.<normalization> is especially helpful in reference to nondigital sources, but it may be made also for digital sources, to declare global changes that would be cumbersome, difficult, or impossible to describe via regular expressions in <replace>. The sequence of consecutive <normalization> is immaterial.See for standard TAN vocabulary for normalizations. For general discussion see Used by: ~adjust-non-core<code><normalization></code> <adjustments> <normalization which="no hyphens"/> </adjustments> Taken from ar.cat.eng.1926.edghill.ref-logical<code><normalization></code> <adjustments> <normalization which="no hyphens"/> </adjustments> Taken from ar.cat.eng.1926.edghill.ref-scriptum<code><normalization></code> <adjustments> <normalization which="no hyphens"/> </adjustments> Taken from ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949<code><normalization></code> <adjustments> <normalization which="no hyphens"/> <normalization which="no ligatures"/> </adjustments> Taken from ar.cat.fra.1844.saint-hilaire.ref-logical

<code><numerals></code>TAN-core.rngThe element numerals specifies how nonarabic numerals should be interpreted, as letter numerals or as Roman numerals.If <numerals> is not present, any ambiguous numerical values are assumed to be Roman. Used by: ~declaration-core<code><numerals></code> <head> ......... <version> ......... </version> <numerals priority="letters"/> <source> ......... </source> ......... </head> Taken from ring-o-roses.deu.1897-prev<code><numerals></code> <head> ......... <version> ......... </version> <numerals priority="letters"/> <source> ......... </source> ......... </head> Taken from ring-o-roses.deu.1897<code><numerals></code> <head> ......... <license licensor="park"> ......... </license> <numerals priority="letters"/> <token-definition src="fra" pattern="\S+"/> ......... </head> Taken from ar.cat.TAN-A<code><numerals></code> <head> ......... <license licensor="park" which="by 4.0"/> <numerals priority="letters"/> <source xml:id="conf"> ......... </source> ......... </head> Taken from patricius.confessio.TAN-A

<code><object></code>TAN-A.rngThe element object points to text references that act as the object of the claim.Unlike @object, which points to any entity via idrefs, <subject> is intended exclusively to point to data content or a textual subject.Each textual <object> is interpreted as a single entity, with all textual references encoded by the element treated as a single, grouped passage. The sequence of its contents is therefore significant. TAN-core.rngThe element object specifies expectations on a verb's use of object. By default, an object is required. Used by: ~element-claim, ~complex-object, ~constraints-on-verbClaims involving verbs whose constrained content requires specification of units must use <object> or <subject> with @units..<object> or <subject> with @units may be used only with verbs with constrained content.<subject>s' and <object>s' content must be castable to any datatype constraints defined by the verb.<subject>s' and <object>s' content must match any lexical constraints defined by the verb.<code><object></code><TAN-A TAN-version="2021" id="tag:parkj@textalign.net,2015:ar.cat.tan-a:claims"> <head> ......... <vocabulary-key> ......... <verb xml:id="om"> ......... <constraints> ......... <at-ref status="required"/> <object status="disallowed"/> </constraints> </verb> <verb xml:id="attests"> ......... <constraints> <subject status="required" item-type="person work version scriptum"/> <object status="required" item-type="ref"/> </constraints> </verb> <verb xml:id="has-length"> ......... <constraints> <subject status="required" item-type="scriptum"/> <object status="required" content-datatype="integer" content-lexical-constraint="\d+"/> </constraints> </verb> ......... </vocabulary-key> ......... </head> <body claimant="park" claim-period="per2010s"> ......... <claim subject="comm-omnes" verb="attests" period="late_antiquity"> <object src="grc" ref="1 a 2"> <tok pos="3-4"/> </object> </claim> <claim subject="comm-omnes" verb="attests" xml:id="cl1a2b"> <object src="grc" ref="1 a 2"> <tok pos="3-4"/> </object> </claim> ......... </body> </TAN-A> Taken from ar.cat.TAN-A.claims

<code><organization></code>TAN-core.rngThe element organization contains an IRI + name pattern identifying an organization: a group of persons, whether formally incorporated or not.This term is taken in its loosest sense. "Organization" and "person" are treated as mutually exclusive and exhaustive categories of all human beings, real or fictive. Therefore a tribe or clan, which ordinarily might dislike being thought of as an organization, are nevertheless so classified here. Used by: ~voc-element-agent<code><organization></code> <vocabulary-key> ......... <morphology xml:id="perseus-dik"> ......... </morphology> <organization xml:id="perseus"> <IRI>http://dbpedia.org/resource/Perseus_Project</IRI> <name>Perseus Project</name> </organization> <person xml:id="dik"> ......... </person> ......... </vocabulary-key> Taken from grc-tan-a-lm-%CE%B1<code><organization></code> <vocabulary-key> ......... <morphology xml:id="perseus-dik"> ......... </morphology> <organization xml:id="perseus"> <IRI>http://dbpedia.org/resource/Perseus_Project</IRI> <name>Perseus Project</name> </organization> <person xml:id="dik"> ......... </person> ......... </vocabulary-key> Taken from grc-tan-a-lm-%CE%B1%CA%B9<code><organization></code> <vocabulary-key> <person which="Jenny Park" xml:id="park"/> <organization xml:id="pt" which="Project_team_for_TAN_examples"/> </vocabulary-key> Taken from park-projects.TAN-voc

<code><passage></code>TAN-class-2.rngThe element passage specifies a textual passage within a single <div> that should be reassigned to another <div>. Used by: ~adj-element-reassign<code><passage></code> <reassign> <passage ref="5 4 7 2"> <from-tok val=":" pos="1"/> <through-tok val=":" pos="1"/> </passage> <to ref="5 4 7 1"/> </reassign> Taken from ar.cat.TAN-A

<code><period></code>TAN-core.rngDefinition 1The element period as a constraint specifies expectations on a verb's use of period. By default, a period is optional.Definition 2The element period identifies or defines a period of time, either through specific dates or dateTimes, or to a vocabulary item that names a more generic period of time. Used by: ~constraints-on-verb, ~voc-key-core<code><period></code> <head> ......... <vocabulary-key> ......... <role xml:id="creator"> ......... </role> <period xml:id="per2010s" from="2010-01-01" to="2019-12-31"/> <period xml:id="late-antiquity"> <IRI>tag:parkj@textalign.net,2015:period:late-antiquity</IRI> <name>late antiquity</name> <desc>Roughly starting in the second to fourth century and finishing from the sixth to ninth, depending upon the context. Late antiquity tends to be later than you think.</desc> </period> <place xml:id="pavia"> ......... </place> </vocabulary-key> ......... </head> Taken from ar.cat.TAN-A.claims

<code><person></code>TAN-core.rngThe element person contains an IRI + name pattern identifying an individual human being. Used by: ~voc-element-agent<code><person></code> <vocabulary-key> ......... <div-type xml:id="pt" which="part"/> <person xml:id="kalvesmaki"> <IRI>http://viaf.org/viaf/299582703</IRI> <IRI>tag:kalvesmaki.com,2014:self</IRI> <name xml:lang="eng">Joel Kalvesmaki</name> </person> <algorithm xml:id="xslt1"> ......... </algorithm> ......... </vocabulary-key> Taken from ar.cat.eng.1926.edghill.ref-logical<code><person></code> <vocabulary-key> ......... <div-type xml:id="l"> ......... </div-type> <person xml:id="kalvesmaki"> <IRI>http://viaf.org/viaf/299582703</IRI> <IRI>tag:kalvesmaki.com,2014:self</IRI> <name xml:lang="eng">Joel Kalvesmaki</name> </person> <algorithm xml:id="xslt1"> ......... </algorithm> ......... </vocabulary-key> Taken from ar.cat.eng.1926.edghill.ref-scriptum<code><person></code> <vocabulary-key> ......... <div-type xml:id="pt" which="part"/> <person xml:id="kalvesmaki"> <IRI>http://viaf.org/viaf/299582703</IRI> <IRI>tag:kalvesmaki.com,2014:self</IRI> <name xml:lang="eng">Joel Kalvesmaki</name> </person> <role xml:id="editor"> ......... </role> ......... </vocabulary-key> Taken from ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949<code><person></code> <vocabulary-key> ......... <div-type xml:id="pt" which="part"/> <person xml:id="kalvesmaki"> <IRI>http://viaf.org/viaf/299582703</IRI> <IRI>tag:kalvesmaki.com,2014:self</IRI> <name xml:lang="eng">Joel Kalvesmaki</name> </person> <role xml:id="editor"> ......... </role> ......... </vocabulary-key> Taken from ar.cat.fra.1844.saint-hilaire.ref-logical

<code><place></code>TAN-A.rngThe element place contains an IRI + name pattern identifying a spatial location, usually somewhere on earth TAN-core.rngThe element place specifies expectations on a verb's use of place. By default, an place is optional. Used by: ~voc-element-tan-a, ~constraints-on-verb<code><place></code> <vocabulary-key> ......... <period xml:id="late-antiquity"> ......... </period> <place xml:id="pavia"> <IRI>http://dbpedia.org/resource/Pavia</IRI> <name>Pavia</name> </place> </vocabulary-key> Taken from ar.cat.TAN-A.claims

<code><predecessor></code>TAN-core.rngThe element predecessor identifies a file that the current file succeeds. Predecessors may or may not have the same @id value.The sequence of consecutive <predecessor>s is immaterial. Used by: ~networked-files-coreAn element that has a <location> and is key for validation should have at least one document available.Every TAN file referred to by way of an element containing <location> should have an @id that matches the <IRI> of the parent of the <location>No element may point to a TAN file that has an identical @id value; the only exception is <predecessor> and <successor>.If a target file has children items in the <to-do>the corresponding comments will be returned as warnings.If a target file has a <successor> a warning will be returned, noting the update.If a target file points only to non-local locations and no internet is available, the following message will be returned. No internet available.If a linking element points to a file that must be resolved, that file must be a TAN file.If an element not essential to validation has no <location> that points to a document a warning should be returned.<code><predecessor></code> <head> ......... <source> ......... </source> <predecessor> <IRI>tag:hans@beispiel.com,2014:ringel</IRI> <name>TAN Transkription, Ringelreihen mit Riederfallen</name> <location accessed-when="2021-04-29T11:46:36.281-04:00" href="ring-o-roses.deu.1897-prev.xml"/> </predecessor> <adjustments> ......... </adjustments> ......... </head> Taken from ring-o-roses.deu.1897

<code><reassign></code>TAN-class-2.rngThe element reassign identifies words and phrases that should be moved from one <div> to another in a given source.Only the first <reassign> applying to a <div> in a given source will be applied. Used by: ~adjust-class-2Any range in either an @n or in a @ref in an adjustment action must be predictably calculated.No token may be adjusted by more than one <reassign>.A <reassign> may be applied only to leaf <div>s.No adjustment action should result in the mixing of leaf <div>s and non-leaf <div>s.In a <reassign>, the token referred to at <from-tok> must precede the one referred to by <through-tok>.<code><reassign></code> <adjustments src="fra"> ......... <equate n="ti title"/> <reassign> <passage ref="5 4 7 2"> ......... </passage> <to ref="5 4 7 1"/> </reassign> </adjustments> Taken from ar.cat.TAN-A

<code><redivision></code>TAN-class-1.rngThe element redivision identifies a class-1 file that has the same work, scriptum, and version, but is segmented according to a different reference system.The normalized transcriptions of redivided texts must be identical.The sequence of consecutive <redivision>s is immaterial. Used by: ~networked-files-non-core<model> and <redivision> must point to class 1 TAN filesAn element that has a <location> and is key for validation should have at least one document available.Every TAN file referred to by way of an element containing <location> should have an @id that matches the <IRI> of the parent of the <location>No element may point to a TAN file that has an identical @id value; the only exception is <predecessor> and <successor>.If a target file has children items in the <to-do>the corresponding comments will be returned as warnings.If a target file has a <successor> a warning will be returned, noting the update.If a target file points only to non-local locations and no internet is available, the following message will be returned. No internet available.If a linking element points to a file that must be resolved, that file must be a TAN file.Class 1 files must share the same source as any redivision or companion version.Class 1 files must share the same work-version, if supplied, as any redivision.Class 1 files must have identical transcriptions, after TAN normalization, as any redivision.Class 1 files must share the same work as any model, redivision, or companion version.<code><redivision></code> <head> ......... <see-also relationship="alt"> ......... </see-also> <redivision> <IRI>tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:model-object-refs</IRI> <name>Categories, Aristotle, English translation by E. M. Edghill</name> <location href="ar.cat.eng.1926.edghill.ref-scriptum.xml" accessed-when="2016-06-22T08:13:35.791-04:00"/> </redivision> <adjustments> ......... </adjustments> ......... </head> Taken from ar.cat.eng.1926.edghill.ref-logical<code><redivision></code> <head> ......... <source> ......... </source> <redivision> <IRI>tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs</IRI> <name>Categories, Aristotle, English translation by E. M. Edghill</name> <location href="ar.cat.eng.1926.edghill.ref-logical.xml" accessed-when="2016-07-07T16:36:28.867-04:00"/> ......... </redivision> <model> ......... </model> ......... </head> Taken from ar.cat.eng.1926.edghill.ref-scriptum<code><redivision></code> <head> ......... <source> ......... </source> <redivision> <IRI>tag:kalvesmaki.com,2014:tan-t:ar.cat.fra.1844.saint-hilaire:semantic-refs</IRI> <name>Categories, Aristotle, French translation by J. Barthélemy Saint-Hilaire</name> <location href="ar.cat.fra.1844.saint-hilaire.ref-logical.xml" accessed-when="2016-07-14T11:38:29.251-04:00"/> </redivision> <model> ......... </model> ......... </head> Taken from ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949<code><redivision></code> <head> ......... <source> ......... </source> <redivision> <IRI>tag:kalvesmaki.com,2014:tan-t:ar.cat.fra.1844.saint-hilaire:semantic-refs-realigned</IRI> <name>Realignment of Categories, Aristotle, French translation by J. Barthélemy Saint-Hilaire</name> <location href="ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949.xml" accessed-when="2016-07-13T15:08:34.397-04:00"/> </redivision> <adjustments> ......... </adjustments> ......... </head> Taken from ar.cat.fra.1844.saint-hilaire.ref-logical

<code><reference-system></code>TAN-class-1.rngThe element reference-system specifies the type of reference system and its basis. The attributes of this element specify the type of reference system (material or logical); point to one or more reference scripta that form the basis of the reference system, and stipulate whether the scripta use that reference system as their key material or logical reference system. In the absence of this element or any individual attribute, the following values are presumed: The default reference type, material (i.e., scriptum-based: pages, columns, lines) or logical (based on conceptual divisions), is determined by the types of text units in the topmost tier of <div>s. The default reference scriptum is <source>. The reference system is assumed not to be the primary one.For a class 1 file to be a candidate for Literature Fragid URIs, whether as a target or as a source of creating LF URIs, the reference system must be the key reference system of its type in the reference scriptum. Used by: ~decl-class-1A class 1 file with a <model> should not declare a <reference-system>, which is inherited from the model.<code><reference-system></code> <head> ......... <license licensor="kalvesmaki"> ......... </license> <reference-system type="logical" wf-ready="true"/> <work> ......... </work> ......... </head> Taken from ar.cat.fra.1844.saint-hilaire.ref-logical<code><reference-system></code> <head> ......... <work> ......... </work> <reference-system type="logical" wf-ready="true"/> <source> ......... </source> ......... </head> Taken from ar.cat.grc.1949.minio-paluello.ref-logical<code><reference-system></code> <head> ......... <work> ......... </work> <reference-system type="material" wf-ready="true" scriptum="bekker"/> <source> ......... </source> ......... </head> Taken from ar.cat.grc.1949.minio-paluello.ref-scriptum<code><reference-system></code> <head> ......... <work> ......... </work> <reference-system type="material" wf-ready="true"/> <source> ......... </source> ......... </head> Taken from ar.cat.lat.1961.minio-paluello.ref-scriptum

<code><relationship></code>TAN-core.rngThe element relationship specifies a relationship that one document has to another. Used by: ~voc-key-core<code><relationship></code> <vocabulary-key> ......... <role xml:id="stylesheet1" which="stylesheet"/> <relationship xml:id="alt"> <IRI>tag:kalvesmaki.com,2014:relationship:diff-work-version</IRI> <name>different work version</name> </relationship> </vocabulary-key> Taken from ar.cat.eng.1926.edghill.ref-logical<code><relationship></code> <vocabulary-key> ......... <role xml:id="stylesheet1" which="stylesheet"/> <relationship xml:id="alt"> <IRI>tag:kalvesmaki.com,2014:relationship:diff-work-version</IRI> <name>different work version</name> </relationship> <scriptum xml:id="bekker"> ......... </scriptum> </vocabulary-key> Taken from ar.cat.lat.1961.minio-paluello.ref-scriptum

<code><rename></code>TAN-class-2.rngThe element rename provisionally reassigns values of @n's in class 1 sources, or their calculated ref value, to another value.A <rename> may be applied on the basis of either @n or @ref, but a ref-based <rename> always supersedes an n-based rename. Only the first matching <rename> will be applied to a given <div> in a source.A ref-based rename eliminates any alternative values of @n, inherited or native. That is, if a <div> has @n="prol pref" and the rename has @ref="prol" and @new="prologue" then the alternative value "pref" will be ignored.Renames override any equate actions. An exception is made when an n-based rename affects one value of @n but an equate affects another value. Ref-based renames always override any equate action.If a <div> is renamed such that it needs to be moved elsewhere in the hierarchy, and it matches the reference of another <div>, the text from the renamed <div> will be added to the end of the target <div>. Used by: ~adjust-class-2Any range in either an @n or in a @ref in an adjustment action must be predictably calculated.Only the first of multiple adjustment actions will be applied. Action priority: skip, ref-based rename, then for every @n n-based rename, equate.In adjustment actions involving @n, at least one value should be found in each source.@by may be applied only to those @n and @ref values that are calculable as integers.In a <rename> the quantity of values in @ref and @new must be identical.@new may not take the same value as what it replaces.No adjustment action should result in the mixing of leaf <div>s and non-leaf <div>s.<code><rename></code> <adjustments src="ger"> <skip div-type="Gedicht"/> <rename n="e" by="-1"/> </adjustments> Taken from ringoroses.div.1<code><rename></code> <adjustments src="ger"> <skip div-type="Gedicht"/> <rename ref="1 e" new="4"/> </adjustments> Taken from ringoroses.01+03.token.2

<code><replace></code>TAN-class-1.rngThe element replace contains the equivalent of the XPath replace() function plus parameters, indicating a replacement operation that should be, or has been, applied to a digital file.Multiple <replace>s will be assumed to have been implemented in the given order.The conventions of this element and its children parallel the XPath function replace(). See http://www.w3.org/TR/xpath-functions-30/#func-replaceThe sequence of consecutive <replace>s is important, reflecting the order in which replacements occured. Results may differ depending upon the order of replace operations. Used by: ~adjust-repl<code><replace></code> <adjustments> ......... <normalization> ......... </normalization> <replace pattern="--" replacement="—" flags="i"/> </adjustments> Taken from gomme.1989.ring-o-roses

<code><report></code>TAN-mor.rngThe element report names a pattern that, if found to be true in any <m> in a dependent TAN-A-lm file, will return the enclosed message upon validation of the dependent file, along with an error or warning. Modeled on Schematron <report>.The sequence of consecutive <report>s is immaterial. Used by: ~element-rule<code><report></code> <rule m-has-codes="'' . ; :"> <report tok-matches="\w">Nothing marked as punctuation should have word characters.</report> </rule> Taken from eng.kalvesmaki.com,2014.2<code><report></code> <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> Taken from grc.perseus.tan-mor

<code><resp></code>TAN-core.rngThe element resp specifies a role held by one or more persons, organizations, or algorithms, perhaps during a specified time period.The sequence of consecutive <resp>s is immaterial. Used by: ~resp-list<code><resp></code><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> Taken from ar.cat.eng.1926.edghill.ref-logical<code><resp></code> <head> ......... <file-resp who="kalvesmaki"/> <resp roles="editor" who="kalvesmaki"/> <resp who="xslt1" roles="stylesheet1"/> ......... </head> Taken from ar.cat.eng.1926.edghill.ref-scriptum

<code><reuse-type></code>TAN-A-tok.rngThe element reuse-type identifies a category of text reuse (e.g., translation, mistranslation, paraphrase, ridicule). See for theoretical background.For standard TAN vocabulary items see Used by: ~voc-element-non-class-2<code><reuse-type></code> <vocabulary-key> ......... <bitext-relation xml:id="B-descends-from-A"> ......... </bitext-relation> <reuse-type xml:id="adaptation"> <IRI>tag:textalign.net,2015:reuse-type:adaptation:general</IRI> <name>general adaptation</name> </reuse-type> <person xml:id="park"> ......... </person> ......... </vocabulary-key> Taken from ringoroses.01+02.token.1<code><reuse-type></code> <vocabulary-key> ......... <bitext-relation xml:id="unclear"> ......... </bitext-relation> <reuse-type xml:id="correlationGeneral"> <IRI>tag:kalvesmaki@gmail.com,2014:reuse-type:correlation-general</IRI> <name>Texts are generally correlated, but without specifying the relation</name> </reuse-type> <comment when="2016-02-22-05:00" who="park">The following is equivalent to @which = 'letters'</comment> ......... </vocabulary-key> Taken from ringoroses.01+03.token.1<code><reuse-type></code> <vocabulary-key> ......... <bitext-relation xml:id="unclear"> ......... </bitext-relation> <reuse-type xml:id="correlationGeneral"> <IRI>tag:kalvesmaki@gmail.com,2014:reuse-type:correlation-general</IRI> <name>Texts are generally correlated, but without specifying the relation</name> </reuse-type> <person xml:id="park"> ......... </person> ......... </vocabulary-key> Taken from ringoroses.01+03.token.2

<code><role></code>TAN-core.rngThe element role specifies a role (responsibility, task, or activity) that one or more <agent>s had in creating or editing the data.A role may be any activity, e.g., editor, funder, supervisor, data-processor, peer reviewer, patron, identified through the enclosed IRI + name pattern.See for standard TAN vocabulary. Used by: ~voc-key-core<code><role></code> <head> ......... <vocabulary-key> ......... <algorithm xml:id="xslt1"> ......... </algorithm> <role xml:id="editor"> <IRI>http://schema.org/editor</IRI> <name xml:lang="eng">Editor</name> </role> <role xml:id="stylesheet1" which="stylesheet"/> <relationship xml:id="alt"> ......... </relationship> </vocabulary-key> ......... </head> Taken from ar.cat.eng.1926.edghill.ref-logical<code><role></code> <head> ......... <vocabulary-key> ......... <algorithm xml:id="xslt1"> ......... </algorithm> <role xml:id="editor"> <IRI>http://schema.org/editor</IRI> <name xml:lang="eng">Editor</name> </role> <role xml:id="stylesheet1" which="stylesheet"/> <scriptum xml:id="bekker"> ......... </scriptum> </vocabulary-key> ......... </head> Taken from ar.cat.eng.1926.edghill.ref-scriptum

<code><rule></code>TAN-mor.rngThe element rule encloses asserts and reports that should be evaluated provided that the conditions specified in the attributes (or children <where> attributes) are true.The sequence of consecutive <rule>s is immaterial. Used by: ~TAN-mor-body<code><rule></code><TAN-mor TAN-version="2021" id="tag:kalvesmaki.com,2014:tan-r-mor:eng:penn"> ......... <body> <rule m-matches=".+"> <assert m-has-how-many-codes="1">Features may not be combined.</assert> </rule> <rule> <where m-has-codes="$"/> <assert tok-matches="$">Only $ may be tagged as a dollar sign.</assert> </rule> <rule m-has-codes="'' . ; :"> <report tok-matches="\w">Nothing marked as punctuation should have word characters.</report> </rule> <code feature="closing_quotation_mark"> ......... </code> ......... </body> </TAN-mor> Taken from eng.kalvesmaki.com,2014.2<code><rule></code> <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> Taken from grc.perseus.tan-mor

<code><scriptum></code>TAN-core.rngThe element scriptum contains an IRI + name pattern identifying a text-bearing object. Used by: ~voc-element-tan-a, ~voc-element-class-1<code><scriptum></code> <vocabulary-key> ......... <role xml:id="stylesheet1" which="stylesheet"/> <scriptum xml:id="bekker"> <IRI>http://id.lib.harvard.edu/alma/990017941240203941/catalog</IRI> <IRI>http://www.worldcat.org/oclc/490107033</IRI> <name>Bekker</name> ......... </scriptum> </vocabulary-key> Taken from ar.cat.eng.1926.edghill.ref-scriptum<code><scriptum></code> <vocabulary-key> ......... <role xml:id="stylesheet1" which="stylesheet"/> <scriptum xml:id="bekker"> <IRI>http://id.lib.harvard.edu/alma/990017941240203941/catalog</IRI> <IRI>http://www.worldcat.org/oclc/490107033</IRI> <name>Bekker</name> ......... </scriptum> </vocabulary-key> Taken from ar.cat.grc.1949.minio-paluello.ref-logical<code><scriptum></code> <vocabulary-key> ......... <role xml:id="stylesheet1" which="stylesheet"/> <scriptum xml:id="bekker"> <IRI>http://id.lib.harvard.edu/alma/990017941240203941/catalog</IRI> <IRI>http://www.worldcat.org/oclc/490107033</IRI> <name>Bekker</name> ......... </scriptum> </vocabulary-key> Taken from ar.cat.grc.1949.minio-paluello.ref-scriptum<code><scriptum></code> <vocabulary-key> ......... <relationship xml:id="alt"> ......... </relationship> <scriptum xml:id="bekker"> <IRI>http://id.lib.harvard.edu/alma/990017941240203941/catalog</IRI> <IRI>http://www.worldcat.org/oclc/490107033</IRI> <name>Bekker</name> ......... </scriptum> </vocabulary-key> Taken from ar.cat.lat.1961.minio-paluello.ref-scriptum

<code><see-also></code>TAN-core.rngThe element see-also identifies a file that is related to the current one.The sequence of consecutive <see-also>s is immaterial. Used by: ~networked-files-coreAn element that has a <location> and is key for validation should have at least one document available.Every TAN file referred to by way of an element containing <location> should have an @id that matches the <IRI> of the parent of the <location>No element may point to a TAN file that has an identical @id value; the only exception is <predecessor> and <successor>.If a target file has children items in the <to-do>the corresponding comments will be returned as warnings.If a target file has a <successor> a warning will be returned, noting the update.If a target file points only to non-local locations and no internet is available, the following message will be returned. No internet available.If an element not essential to validation has no <location> that points to a document a warning should be returned.If @accessed-when predates one or more dates in a target file, a warning will be returned.<code><see-also></code> <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> Taken from ar.cat.eng.1926.edghill.ref-logical<code><see-also></code> <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> Taken from ar.cat.lat.1961.minio-paluello.ref-scriptum

<code><skip></code>TAN-class-2.rngThe element skip marks parts of a source that have been ignored or should be skipped, either shallowly (default) or deeply.Note, the shallow skip of a <div> may result in the creation of empty <div>s, which will be ignored during validation.This element is useful for ignoring extraneous divs, e.g., where a source has introduced divs that do not exist in other versions of the same work. For example, a transcription may group the topmost divisions of a text into parts, or may adopt superfluous divisions (e.g., introducing a <div> for chapter in the New Testament book Philemon, which does not have more than one chapter, and can be identified purely by verse). Only the first <skip> applying to a <div> in a given source will be applied. Used by: ~adjust-class-2Any range in either an @n or in a @ref in an adjustment action must be predictably calculated.Only the first of multiple adjustment actions will be applied. Action priority: skip, ref-based rename, then for every @n n-based rename, equate.In adjustment actions involving @n, at least one value should be found in each source.Every div type reference must be valid in every source<code><skip></code> <adjustments src="fra"> <skip div-type="summ" shallow="false"/> <equate n="ti title"/> ......... </adjustments> Taken from ar.cat.TAN-A<code><skip></code> <adjustments src="ger"> <skip div-type="Gedicht"/> <rename n="e" by="-1"/> </adjustments> Taken from ringoroses.div.1<code><skip></code> <adjustments src="ger"> <skip div-type="Gedicht"/> </adjustments> Taken from ringoroses.01+03.token.1<code><skip></code> <adjustments src="ger"> <skip div-type="Gedicht"/> <rename ref="1 e" new="4"/> </adjustments> Taken from ringoroses.01+03.token.2

<code><source></code>TAN-core.rngThe element source identifies the source upon which the data in the <body> of the current file depends.TAN-T and TAN-A-lm allow only one <source>. TAN-A-tok allows exactly two. All other TAN formats require one or more. The sequence of consecutive <source>s is immaterial, but it does dictate the order in which sources are validated and processed. Used by: ~source-listAn element that has a <location> and is key for validation should have at least one document available.Every TAN file referred to by way of an element containing <location> should have an @id that matches the <IRI> of the parent of the <location>No element may point to a TAN file that has an identical @id value; the only exception is <predecessor> and <successor>.If a target file has children items in the <to-do>the corresponding comments will be returned as warnings.If a target file has a <successor> a warning will be returned, noting the update.If a target file points only to non-local locations and no internet is available, the following message will be returned. No internet available.If a linking element points to a file that must be resolved, that file must be a TAN file.If @accessed-when predates one or more dates in a target file, a warning will be returned.A class 1 <source> may not point to a TAN file.Sources are integral parts of a class 2 TAN file. Access to at least one non-faulty copy is absolutely mandatory.<code><source></code> <head> ......... <work> ......... </work> <source> <IRI>http://id.lib.harvard.edu/aleph/007901738/catalog</IRI> <name>Aristotle: Categoriae & De interpretatione by E.M. Edghill. Analytica priora / by A.J. Jenkinson. Analytica posteriora / by G.R.G. Mure. Oxford : Clarendon Press, 1926. </name> </source> <model> ......... </model> ......... </head> Taken from ar.cat.eng.1926.edghill.ref-logical<code><source></code> <head> ......... <work> ......... </work> <source> <IRI>http://id.lib.harvard.edu/aleph/007901738/catalog</IRI> <name>Aristotle: Categoriae & De interpretatione by E.M. Edghill. Analytica priora / by A.J. Jenkinson. Analytica posteriora / by G.R.G. Mure. Oxford : Clarendon Press, 1926. </name> </source> <redivision> ......... </redivision> ......... </head> Taken from ar.cat.eng.1926.edghill.ref-scriptum<code><source></code> <head> ......... <work> ......... </work> <source> <IRI>http://id.lib.harvard.edu/aleph/002773288/catalog</IRI> <name>Logique d'Aristote: Traduite en français pour la première fois et accompagnée de notes perpétuelles par J. Barthélemy Saint-Hilaire. Paris : Ladrange, 1839-1844. </name> </source> <redivision> ......... </redivision> ......... </head> Taken from ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949<code><source></code> <head> ......... <work> ......... </work> <source> <IRI>http://id.lib.harvard.edu/aleph/002773288/catalog</IRI> <name>Logique d'Aristote: Traduite en français pour la première fois et accompagnée de notes perpétuelles par J. Barthélemy Saint-Hilaire. Paris : Ladrange, 1839-1844. </name> </source> <redivision> ......... </redivision> ......... </head> Taken from ar.cat.fra.1844.saint-hilaire.ref-logical

<code><subject></code>TAN-A.rngThe element subject points to text references that act as the subject of the claim.Unlike @subject, which points to any entity via idrefs, <subject> is intended exclusively to point to data content or a textual subject.Each textual <subject> is interpreted as a single entity, with all textual references encoded by the element treated as a single, grouped passage. The sequence of its contents is therefore significant. TAN-core.rngThe element subject specifies expectations on a verb's use of subject. By default, a subject is required. Used by: ~element-claim, ~subject, ~constraints-on-verbClaims involving verbs whose constrained content requires specification of units must use <object> or <subject> with @units..<object> or <subject> with @units may be used only with verbs with constrained content.<subject>s' and <object>s' content must be castable to any datatype constraints defined by the verb.<subject>s' and <object>s' content must match any lexical constraints defined by the verb.<code><subject></code><TAN-A TAN-version="2021" id="tag:parkj@textalign.net,2015:ar.cat.tan-a:claims"> <head> ......... <vocabulary-key> ......... <verb xml:id="om"> ......... <constraints> <subject status="required" item-type="person work version scriptum"/> <at-ref status="required"/> ......... </constraints> </verb> <verb xml:id="attests"> ......... <constraints> <subject status="required" item-type="person work version scriptum"/> <object status="required" item-type="ref"/> </constraints> </verb> <verb xml:id="has-length"> ......... <constraints> <subject status="required" item-type="scriptum"/> <object status="required" content-datatype="integer" content-lexical-constraint="\d+"/> </constraints> </verb> ......... </vocabulary-key> ......... </head> <body claimant="park" claim-period="per2010s"> ......... <claim verb="refers-to"> <subject src="grc" ref="1 b 25"/> <object work="grc" ref="1 a 16"/> </claim> ......... </body> </TAN-A> Taken from ar.cat.TAN-A.claims

<code><successor></code>TAN-core.rngThe element successor identifies a file that succeeds the current file. Successors may or may not have the same document @id value.The sequence of consecutive <successor>s is immaterial. Used by: ~networked-files-core<successor> and <companion-version> must point to TAN files of the same type.An element that has a <location> and is key for validation should have at least one document available.Every TAN file referred to by way of an element containing <location> should have an @id that matches the <IRI> of the parent of the <location>No element may point to a TAN file that has an identical @id value; the only exception is <predecessor> and <successor>.If a target file has children items in the <to-do>the corresponding comments will be returned as warnings.If a target file has a <successor> a warning will be returned, noting the update.If a target file points only to non-local locations and no internet is available, the following message will be returned. No internet available.If a linking element points to a file that must be resolved, that file must be a TAN file.<code><successor></code> <head> ......... <source> ......... </source> <successor> <IRI>tag:hans@beispiel.com,2014:ringel</IRI> <name>TAN Transkription, Ringelreihen mit Riederfallen</name> <location accessed-when="2021-04-29T11:46:04.656-04:00" href="ring-o-roses.deu.1897.xml"/> </successor> <adjustments> ......... </adjustments> ......... </head> Taken from ring-o-roses.deu.1897-prev

<code><tail></code>TAN-core.rngThe element tail permits any arbitrary content. This element is suitable as a placeholder for temporary data, especially to improve the efficiency of applications. Used by: ~TAN-root<code><tail></code><TAN-T TAN-version="2021" id="tag:hans@beispiel.com,2014:ringel"> ......... <body xml:lang="deu"> ......... </body> <tail> </tail> </TAN-T> Taken from ring-o-roses.deu.1897-prev

<code><TAN-A></code>TAN-A.rngThe element TAN-A specifies that the file is a general TAN alignment file. Root element. Users should be warned about versions of TAN that are under development. This version of TAN is under development, and is subject to change. Participants in developing the TAN schemas, functions, and guidelines are welcome. See http://textalign.net for details.Users should be warned about TAN files whose last change was made by an algorithm.<code><TAN-A></code><TAN-A TAN-version="2021" id="tag:parkj@textalign.net,2015:ar.cat.tan-a:claims"> <head> ......... </head> <body claimant="park" claim-period="per2010s"> ......... </body> </TAN-A> Taken from ar.cat.TAN-A.claims<code><TAN-A></code><TAN-A TAN-version="2021" id="tag:parkj@textalign.net,2015:ar.cat.tan-a"> <head> ......... </head> <body claimant="park"> ......... </body> </TAN-A> Taken from ar.cat.TAN-A<code><TAN-A></code><TAN-A TAN-version="2021" id="tag:parkj@textalign.net,2015:patricius.confessio.tan-a"> <head> ......... </head> <body claimant="park"> ......... </body> </TAN-A> Taken from patricius.confessio.TAN-A<code><TAN-A></code><TAN-A TAN-version="2021" id="tag:parkj@textalign.net,2015:ring01-TAN-A-ring02"> <head> ......... </head> <body claimant="park"> ......... </body> </TAN-A> Taken from ringoroses.div.1

<code><TAN-A-lm></code>TAN-A-lm.rngThe element TAN-A-lm specifies that the file is a TAN file containing lexico-morphology data about a class-1 source or a language in general. Root element. Users should be warned about versions of TAN that are under development. This version of TAN is under development, and is subject to change. Participants in developing the TAN schemas, functions, and guidelines are welcome. See http://textalign.net for details.Users should be warned about TAN files whose last change was made by an algorithm.<code><TAN-A-lm></code><TAN-A-lm TAN-version="2021" id="tag:kalvesmaki.com,2014:tan-t:ar.cat.grc.1949.minio-paluello:semantic-refs:TAN-A-lm:2016-04-05T07:07:40.033-04:00"> <head> ......... </head> <body lexicon="LSJ Lampe new" morphology="Perseus" claimant="xslt2"> ......... </body> </TAN-A-lm> Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-A-lm-sample<code><TAN-A-lm></code><TAN-A-lm TAN-version="2021" id="tag:kalvesmaki.com,2015:tan-a-lm:grc:perseusα"> <head> ......... </head> <body lexicon="LSJ" morphology="perseus-dik" claimant="xslt2"> ......... </body> </TAN-A-lm> Taken from grc-tan-a-lm-%CE%B1<code><TAN-A-lm></code><TAN-A-lm TAN-version="2021" id="tag:kalvesmaki.com,2015:tan-a-lm:grc:perseusαʹ"> <head> ......... </head> <body lexicon="LSJ" morphology="perseus-dik" claimant="xslt2"> ......... </body> </TAN-A-lm> Taken from grc-tan-a-lm-%CE%B1%CA%B9<code><TAN-A-lm></code><TAN-A-lm TAN-version="2021" id="tag:parkj@textalign.net,2015:ring01-lm"> <head> ......... </head> <body lexicon="english" morphology="penn" claimant="xslt2"> ......... </body> </TAN-A-lm> Taken from ring-o-roses.eng.1881.lm

<code><TAN-A-tok></code>TAN-A-tok.rngThe element TAN-A-tok specifies that the file is contains token-to-token alignments between two sources. Root element. Users should be warned about versions of TAN that are under development. This version of TAN is under development, and is subject to change. Participants in developing the TAN schemas, functions, and guidelines are welcome. See http://textalign.net for details.Users should be warned about TAN files whose last change was made by an algorithm.<code><TAN-A-tok></code><TAN-A-tok TAN-version="2021" id="tag:parkj@textalign.net,2015:TAN-A-tok,ring01+ring02"> <head> ......... </head> <body bitext-relation="B-descends-from-A" reuse-type="adaptation"> ......... </body> </TAN-A-tok> Taken from ringoroses.01+02.token.1<code><TAN-A-tok></code><TAN-A-tok TAN-version="2021" id="tag:parkj@textalign.net,2015:TAN-A-tok,ring01+ring03"> <head> ......... </head> <body reuse-type="correlationGeneral" bitext-relation="unclear" claimant="xslt2"> ......... </body> </TAN-A-tok> Taken from ringoroses.01+03.token.1<code><TAN-A-tok></code><TAN-A-tok TAN-version="2021" id="tag:parkj@textalign.net,2015:TAN-A-tok,ring01+ring03:alt"> <head> ......... </head> <body reuse-type="correlationGeneral" bitext-relation="unclear" claimant="xslt2"> ......... </body> </TAN-A-tok> Taken from ringoroses.01+03.token.2

<code><TAN-mor></code>TAN-mor.rngThe element TAN-mor specifies that the TAN file contains codes and rules for the parts of speech for a language, the codes for those parts, and the rules for combining them. Root element. Users should be warned about versions of TAN that are under development. This version of TAN is under development, and is subject to change. Participants in developing the TAN schemas, functions, and guidelines are welcome. See http://textalign.net for details.Users should be warned about TAN files whose last change was made by an algorithm.<code><TAN-mor></code><TAN-mor TAN-version="2021" id="tag:kalvesmaki.com,2014:tan-r-mor:eng:penn"> <head> ......... </head> <body> ......... </body> </TAN-mor> Taken from eng.kalvesmaki.com,2014.2<code><TAN-mor></code><TAN-mor TAN-version="2021" id="tag:kalvesmaki.com,2014:tan-r-mor:grc:perseus"> <head> ......... </head> <body> ......... </body> </TAN-mor> Taken from grc.perseus.tan-mor

<code><TAN-T></code>TAN-T.rngThe element TAN-T specifies that the TAN file contains a transcription. Root element. TAN-core.rng Users should be warned about versions of TAN that are under development. This version of TAN is under development, and is subject to change. Participants in developing the TAN schemas, functions, and guidelines are welcome. See http://textalign.net for details.Users should be warned about TAN files whose last change was made by an algorithm.<code><TAN-T></code><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> Taken from ar.cat.eng.1926.edghill.ref-logical<code><TAN-T></code><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> Taken from ar.cat.eng.1926.edghill.ref-scriptum<code><TAN-T></code><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> Taken from ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949<code><TAN-T></code><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> Taken from ar.cat.fra.1844.saint-hilaire.ref-logical

<code><TAN-voc></code>TAN-voc.rngThe element TAN-voc specifies a TAN file that contains vocabulary items. Root element. Users should be warned about versions of TAN that are under development. This version of TAN is under development, and is subject to change. Participants in developing the TAN schemas, functions, and guidelines are welcome. See http://textalign.net for details.Users should be warned about TAN files whose last change was made by an algorithm.The vocabulary of a file may not include it.<code><TAN-voc></code><TAN-voc TAN-version="2021" id="tag:parkj@textalign.net,2015:TAN-key:ar.cat"> <head> ......... </head> <body affects-element="work"> ......... </body> </TAN-voc> Taken from ar.cat.TAN-voc<code><TAN-voc></code><TAN-voc TAN-version="2021" id="tag:parkj@textalign.net,2015:TAN-voc:standard"> <head> ......... </head> <body> ......... </body> </TAN-voc> Taken from park-projects.TAN-voc<code><TAN-voc></code><TAN-voc TAN-version="2021" id="tag:textalign.net,2015:tan-voc:bitext-relation"> <head> ......... </head> <body affects-element="bitext-relation"> ......... </body> </TAN-voc> Taken from bitext-relations.TAN-voc<code><TAN-voc></code><TAN-voc TAN-version="2021" id="tag:textalign.net,2015:tan-voc:div-types"> <head> ......... </head> <body affects-element="div-type"> ......... </body> </TAN-voc> Taken from div-types.TAN-voc

<code><through-tok></code>TAN-class-2.rngDefinition 1The element through-tok points to a single token that is the end of a range of tokens to be selected from a source, but without @ref..Definition 2The element through-tok points to a single token in a single reference that is the end of a range of tokens to be selected from a source, in the context of @ref.. Used by: ~text-passage-selector-no-ref, ~text-passage-selector-with-refEvery token must be locatable in every cited ref in every source.In a <reassign>, the token referred to at <from-tok> must precede the one referred to by <through-tok>.<code><through-tok></code> <passage ref="5 4 7 2"> <from-tok val=":" pos="1"/> <through-tok val=":" pos="1"/> </passage> Taken from ar.cat.TAN-A<code><through-tok></code> <subject src="eng-uk"> ......... <from-tok ref="1" pos="3"/> <through-tok ref="2" pos="1"/> </subject> Taken from ringoroses.div.1

<code><to></code>TAN-class-2.rngThe element to indicates a ref to which the preceding <tok>s should be moved. Used by: ~adj-element-reassignNo adjustment action should result in the mixing of leaf <div>s and non-leaf <div>s.<code><to></code> <reassign> <passage ref="5 4 7 2"> ......... </passage> <to ref="5 4 7 1"/> </reassign> Taken from ar.cat.TAN-A

<code><to-do></code>TAN-core.rngThe element to-do lists tasks that remain to be done (via <comment> children). Lack of content in <to-do> suggests that the file is no longer considered a work in progress, but it does not guarantee that the file will not be changed in the future.An empty <to-do> implies stability, so requires a file to have a <master-location>. Used by: ~element-headAny TAN file without a to-do list will be treated as being no longer in progress and should have at least one master-location.<code><to-do></code> <head> ......... <change who="xslt2" when="2018-08-04T23:55:36.096-04:00">Converted from 2018 to 2019 schemas.</change> <to-do/> </head> Taken from ar.cat.eng.1926.edghill.ref-logical<code><to-do></code> <head> ......... <change when="2018-07-30-04:00" who="kalvesmaki">updated to 2019 schemas</change> <to-do/> </head> Taken from ar.cat.eng.1926.edghill.ref-scriptum<code><to-do></code> <head> ......... <change who="xslt2" when="2018-08-05T00:03:20.142-04:00">Converted from 2018 to 2019 schemas.</change> <to-do/> </head> Taken from ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949<code><to-do></code> <head> ......... <change who="xslt2" when="2018-08-05T00:05:17.879-04:00">Converted from 2018 to 2019 schemas.</change> <to-do/> </head> Taken from ar.cat.fra.1844.saint-hilaire.ref-logical

<code><tok></code>TAN-A-lm.rngThe element tok points to a token in the abstract, no matter where it is found, either in the source (if there is one) or the language (if there is no source).The sequence of consecutive <tok>s is immaterial, except in the context of <group>. TAN-A.rngDefinition 1The element tok points to one or more tokens in the context source or reference. Definition 2The element tok points to one or more tokens in the context source. TAN-class-2.rngThe element tok identifies one or more tokens (words or word fragments). Used by class-2 files to make claims about specific words. In TAN-A and TAN-A-tok files, <tok> does not necessarily carry linguistic connotations; in TAN-A-lm, it normally does.Most <tok>s are restricted to a single token, or a portion of a single token, perhaps filtered by the value of @chars.. But they can refer to multiple tokens through multiple values of @src, @ref, and @pos, to save space and perhaps enhance legibility. For example, <tok src="a b" ref="1.1 - 1.3" pos="1-4"> would point to 24 tokens (assuming that the two sources each have at least four tokens in the three references 1.1, 1.2, and 1.3).If you wish to treat multiple word fragments as a single token, use <group>.The sequence of consecutive <tok>s is immaterial in the context of TAN-A-lm, and TAN-A-tok, except in the context of <group>, where the sequence dictates how the new token is to be constructed. The sequence of consecutive <tok>s is important in the context of TAN-A, where the sequence specifies the order in which word tokens should be supplied in the context of the <claim>. Used by: ~default-tok-element, ~single-div-partial-textual-reference, ~multi-div-partial-textual-referenceEvery token must be locatable in every cited ref in every source.Every character must be locatable in every token in every ref in every source.<code><tok></code><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> Taken from ar.cat.TAN-A.claims

<code><tok-is></code>TAN-A-lm.rngThe element tok-is specifies an exact value of @val of <tok>s in the file. Collectively, every <tok> should point to at least one <tok-is>.This element is an optional way to improve the efficiency of validation and applications. The sequence of consecutive <tok-is>s is immaterial. Used by: ~decl-non-class-2<code><tok-is></code><TAN-A-lm TAN-version="2021" id="tag:kalvesmaki.com,2015:tan-a-lm:grc:perseusα"> <head> ......... <for-lang>grc</for-lang> <tok-is>ἆ</tok-is> <tok-is>ἁ</tok-is> <tok-is>ἅ</tok-is> <tok-is>ἃ</tok-is> <tok-is>ᾇ</tok-is> ......... </head> ......... </TAN-A-lm> Taken from grc-tan-a-lm-%CE%B1

<code><tok-starts-with></code>TAN-A-lm.rngThe element tok-starts-with specifies one opening string that characterizes the @val of <tok>s in the file.This element is an optional way to improve the efficiency of validation and applications.The sequence of consecutive <tok-is>s is immaterial. Used by: ~decl-non-class-2<code><tok-starts-with></code><TAN-A-lm TAN-version="2021" id="tag:kalvesmaki.com,2015:tan-a-lm:grc:perseusαʹ"> <head> ......... <for-lang>grc</for-lang> <tok-starts-with>αʹ</tok-starts-with> <tok-starts-with>Αʹ</tok-starts-with> <vocabulary-key> ......... </vocabulary-key> ......... </head> ......... </TAN-A-lm> Taken from grc-tan-a-lm-%CE%B1%CA%B9

<code><token-definition></code>TAN-core.rngThe element token-definition defines a word token via a regular expression. The pattern in this element is used to split a string into tokens and non-tokens. The attributes of this element mirror the parameters for the function xsl:analyze-string (see https://www.w3.org/TR/xslt-30/#element-analyze-string).For more see and for standard TAN vocabulary items see Used by: ~decl-class-1, ~decl-class-2, ~entity-tok-defNo source may be given more than one token definition.<code><token-definition></code> <head> ......... <license licensor="park"> ......... </license> <token-definition src="*" which="letters only"/> <vocabulary> ......... </vocabulary> ......... </head> Taken from ar.cat.TAN-A.claims<code><token-definition></code> <head> ......... <numerals priority="letters"/> <token-definition src="fra" pattern="\S+"/> <source xml:id="grc"> ......... </source> ......... </head> Taken from ar.cat.TAN-A<code><token-definition></code> <head> ......... <license which="by_4.0" licensor="park"/> <token-definition src="eng-us" pattern="[-\w]+"/> <source xml:id="eng-uk"> ......... </source> ......... </head> Taken from ringoroses.div.1<code><token-definition></code> <head> ......... <license licensor="kalvesmaki"> ......... </license> <token-definition pattern="[\w‍]+"/> <inclusion xml:id="rel"> ......... </inclusion> ......... </head> Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-A-lm-sample

<code><topic></code>TAN-A.rngThe element topic contains an IRI + name pattern identifying a topic. Used by: ~voc-element-tan-a<code><topic></code> <vocabulary-key> ......... <verb which="is about" xml:id="concerns"/> <topic xml:id="predication"> <IRI>tag:parkj@textalign.net,2015:topic:predication</IRI> <name>predication</name> <desc>The act of asserting something about a grammatical subject.</desc> </topic> </vocabulary-key> Taken from ar.cat.TAN-A

<code><unit></code>TAN-A.rngThe element unit contains an IRI + name pattern identifying a unit type (e.g., millimeters, seconds, Euros), to be used in conjunction with <object> to specify what quantities measure. Used by: ~voc-element-tan-a<code><unit></code> <vocabulary-key> ......... <verb xml:id="has-length"> ......... </verb> <unit xml:id="folio"> <IRI>http://dbpedia.org/resource/Folio</IRI> <name>folio</name> </unit> <modal which="possibly" xml:id="perhaps"/> ......... </vocabulary-key> Taken from ar.cat.TAN-A.claims

<code><val></code>TAN-mor.rngThe element val contains the expected value for a morphological code Used by: ~element-code<code><val></code><TAN-mor TAN-version="2021" id="tag:kalvesmaki.com,2014:tan-r-mor:eng:penn"> ......... <body> ......... <code feature="closing_quotation_mark"> <desc>Examples: ' ''</desc> <val>''</val> </code> <code feature="dash"> <desc>Example: --</desc> <val>--</val> </code> <code feature="dollar"> <desc>Examples: Examples: $ -$ --$ A$ C$ HK$ M$ NZ$ S$ U.S.$ US$</desc> <val>$</val> </code> <code feature="opening_parenthetical_punctuation"> <desc>Examples: ( [ {</desc> <val>[</val> </code> ......... </body> </TAN-mor> Taken from eng.kalvesmaki.com,2014.2

<code><value></code>TAN-core.rngThe element value states the value of a <checksum> Used by: <checksum><code><value></code> <checksum> ......... <name>SHA-1</name> <value>91D95564ABDF2B2C1B9EEF016CBA51E8179646CC</value> </checksum> Taken from patricius.confessio.2003.eng

<code><verb></code>TAN-core.rngThe element verb contains an IRI + name pattern identifying a property, relationship, action, or something else that is used to say something about something. The preferred term "verb" is equivalent to RDF "predicate." The latter term is avoided, since in regular usage "predicate" signifies both a verb and all the words it governs.See for standard TAN vocabulary items. Used by: ~voc-element-tan-a, ~body-itemClaims involving verbs whose constrained content requires specification of units must use <object> or <subject> with @units..<object> or <subject> with @units may be used only with verbs with constrained content.A claim with a verb that has content constraints must not allow other verbs.<code><verb></code> <head> ......... <vocabulary-key> ......... <alias xml:id="comm-omnes" idrefs="π δ α.d φ.d ο.d η.d σ.d"/> <verb which="refers or alludes to" xml:id="refers-to"/> <verb xml:id="om"> <IRI>tag:parkj@textalign.net,2015:verb:omits</IRI> <name>omits</name> <name>omits text</name> ......... </verb> <verb xml:id="attests"> <IRI>tag:parkj@textalign.net,2015:verb:attests-to</IRI> <name>attests</name> <name>attests to</name> ......... </verb> <verb xml:id="has-length"> <IRI>tag:parkj@textalign.net,2015:verb:scriptum-has-length</IRI> <name>has length</name> <desc>This verb is used to describe the how many pages or folios a scriptum is.</desc> ......... </verb> <unit xml:id="folio"> ......... </unit> ......... </vocabulary-key> ......... </head> Taken from ar.cat.TAN-A.claims

<code><version></code>TAN-A.rngThe element version identifies the version of a work. Applicable to sources that contain multiple versions, e.g., original text and facing translations. Like <work>, <version> points to a conceptual entity, not a physical one.Very few work-versions have their own URNs. It is advisable to assign a tag URN or a UUID. If you have used an IRI for <work> that you are entitled to modify, you may wish to add a suffix that will name the version. If you need to specify exactly where on a text-bearing object a version appears, <desc> or <comment> should be used.For background, see TAN-class-1.rngThe element version identifies the version of a work. Applicable to sources that contain multiple versions, e.g., original text and facing translations. Like <work>, <version> points to a conceptual entity, not a physical one.In the context of a class 1 file, the entity identified by <version> is assumed to be a version of the entity defined in <work>. Very few work-versions have their own URN names. It is advisable to assign a tag URN or a UUID. If you have used an IRI for <work> that you are entitled to modify, you may wish to add a suffix that will name the version. If you need to specify exactly where on a text-bearing object a version appears, <desc> or <comment> should be used.For more, see Used by: ~voc-element-tan-a, ~decl-class-1<code><version></code> <head> ......... <work> ......... </work> <version> <IRI>tag:parkj@textalign.net,2015:version:matthews-version-of-the-lords-prayer</IRI> <name>Matthew's version of the Lord's Prayer</name> </version> <vocabulary> ......... </vocabulary> ......... </head> Taken from lords-prayer.eng.kjv.1760<code><version></code> <head> ......... <work> ......... </work> <version> <IRI>urn:uuid:31648039-3dbb-49b9-b66e-9bd2cd11630e</IRI> <name>zweite Version</name> </version> <numerals priority="letters"/> ......... </head> Taken from ring-o-roses.deu.1897-prev<code><version></code> <head> ......... <work> ......... </work> <version> <IRI>urn:uuid:31648039-3dbb-49b9-b66e-9bd2cd11630e</IRI> <name>zweite Version</name> </version> <numerals priority="letters"/> ......... </head> Taken from ring-o-roses.deu.1897<code><version></code> <head> ......... <work> ......... </work> <version> <IRI>tag:parkj@textalign.net,2015:work:ring:version:newell-reported</IRI> <name>Ring around the Rosie, second version</name> <name>Ring around the Rosie, version reported by Newell</name> </version> <source> ......... </source> ......... </head> Taken from ring-o-roses.eng.1951

<code><vocabulary></code>TAN-core.rngThe element vocabulary specifies a TAN-voc file that supplies vocabulary items for the host file. For more discussion, see The sequence of consecutive <vocabulary>s is immaterial. Used by: ~networked-files-core, ~vocabulary-listNo file may import vocabularies with items that have duplicate IRIs.<vocabulary> must point to TAN-voc files.Inclusions/vocabularies may not be invoked circularly.The vocabulary of a file may not include it.The @TAN-version for inclusions and vocabularies should match the current version.An element that has a <location> and is key for validation should have at least one document available.Every TAN file referred to by way of an element containing <location> should have an @id that matches the <IRI> of the parent of the <location>No element may point to a TAN file that has an identical @id value; the only exception is <predecessor> and <successor>.If a target file has children items in the <to-do>the corresponding comments will be returned as warnings.If a target file has a <successor> a warning will be returned, noting the update.If a target file points only to non-local locations and no internet is available, the following message will be returned. No internet available.If a linking element points to a file that must be resolved, that file must be a TAN file.If @accessed-when predates one or more dates in a target file, a warning will be returned.An element's @which must have a value that corresponds to a <name>, either in a standard TAN vocabulary or an associated TAN-voc file, that is marked as applying to that element.A @which in a <vocabulary> may point only to items in the standard TAN file vocabularies.TAN-voc.xmlVocabularies are integral parts of a document. Access to at least one version is absolutely mandatory.<code><vocabulary></code> <head> ......... <version> ......... </version> <vocabulary> <IRI>tag:parkj@textalign.net,2015:TAN-voc:standard</IRI> <name>Keywords for TAN files edited by Jenny Park</name> <location href="TAN-voc/park-projects.TAN-voc.xml" accessed-when="2019-10-08"/> </vocabulary> <source which="kjv 1760"/> ......... </head> Taken from lords-prayer.eng.kjv.1760<code><vocabulary></code><TAN-T TAN-version="2021" id="tag:parkj@textalign.net,2015:bible:matthew"> <head> ......... <inclusion xml:id="serm-mount"> ......... </inclusion> <vocabulary which="bible eng" accessed-when="2019-10-08"/> <vocabulary> <IRI>tag:parkj@textalign.net,2015:TAN-voc:standard</IRI> <name>Keywords for TAN files edited by Jenny Park</name> <location href="TAN-voc/park-projects.TAN-voc.xml" accessed-when="2019-10-08"/> </vocabulary> <source which="kjv 1760"/> ......... </head> ......... </TAN-T> Taken from matt.eng.kjv.1760<code><vocabulary></code> <head> ......... <source> ......... </source> <vocabulary> <IRI>tag:parkj@textalign.net,2015:TAN-voc:standard</IRI> <name>Vocabulary for TAN files edited by Jenny Park</name> <location href="TAN-voc/park-projects.TAN-voc.xml" accessed-when="2020-01-10"/> </vocabulary> <model> ......... </model> ......... </head> Taken from ring-o-roses.eng.1987

<code><vocabulary-key></code>TAN-core.rngThe element vocabulary-key contains vocabulary items for the immediate file. Used by: ~vocabulary-list<code><vocabulary-key></code> <head> ......... <adjustments> ......... </adjustments> <vocabulary-key> <algorithm xml:id="xslt2"> ......... </algorithm> <div-type xml:id="ch"> ......... </div-type> <div-type xml:id="par"> ......... </div-type> ......... </vocabulary-key> <file-resp who="kalvesmaki"/> ......... </head> Taken from ar.cat.eng.1926.edghill.ref-logical<code><vocabulary-key></code> <head> ......... <adjustments> ......... </adjustments> <vocabulary-key> <div-type xml:id="p"> ......... </div-type> <div-type xml:id="c"> ......... </div-type> <div-type xml:id="l"> ......... </div-type> ......... </vocabulary-key> <file-resp who="kalvesmaki"/> ......... </head> Taken from ar.cat.eng.1926.edghill.ref-scriptum<code><vocabulary-key></code> <head> ......... <adjustments> ......... </adjustments> <vocabulary-key> <algorithm xml:id="xslt2"> ......... </algorithm> <div-type xml:id="ch"> ......... </div-type> <div-type xml:id="par"> ......... </div-type> ......... </vocabulary-key> <file-resp who="kalvesmaki"/> ......... </head> Taken from ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949<code><vocabulary-key></code> <head> ......... <adjustments> ......... </adjustments> <vocabulary-key> <algorithm xml:id="xslt2"> ......... </algorithm> <div-type xml:id="ch"> ......... </div-type> <div-type xml:id="par"> ......... </div-type> ......... </vocabulary-key> <file-resp who="kalvesmaki"/> ......... </head> Taken from ar.cat.fra.1844.saint-hilaire.ref-logical

<code><where></code>TAN-core.rngThe element where identifies a set of conditions that must be met for any actions to be performed or rules to be evaluated.For a <where> to be considered true, each attribute must evaluate as true for the target context. That is, multiple attributes are evaluated as intersection operators (and), not union (or).Sibling <where>s provide alternative conditions. If the first <where> evaluates as true, the condition is considered true. If it does not, then the process is applied again to the second <where>. The sequence of consecutive <where>s is immaterial, although they will be processed in document order. It is advisable to start with <where>s that are most likely to make a match. Used by: ~action-complex-condition<code><where></code> <rule> <where m-has-codes="$"/> <assert tok-matches="$">Only $ may be tagged as a dollar sign.</assert> </rule> Taken from eng.kalvesmaki.com,2014.2

<code><work></code>TAN-class-1.rngThe element work identifies a creative textual work, understood conceptually, not physically (e.g., Homer's Iliad, not a particular version or copy of it).The term "work" is only loosely defined in TAN. Any text that has enough unity to be referred to in ordinary conversation as a single entity may be identified as a work. A work may be composed of other works, be a part of other works, or even overlap with other works. E.g., the Lord's Prayer, the Gospel of Luke, the Tetravengelion, the New Testament, and the Bible are all valid works, despite the complex relationship between each of them.This element takes the IRI + name pattern. For more, see TAN-core.rngThe element work identifies a creative textual work, understood conceptually, not physically (e.g., Homer's Iliad, not a particular version or copy of it).The term "work" is only loosely defined in TAN. Any text that has enough unity to be referred to in ordinary conversation as a single entity may be identified as a work. A work may be composed of other works, be a part of other works, or even overlap with other works. E.g., Q, the Lord's Prayer, the Gospel of Luke, the Tetravengelion, the New Testament, and the Bible are all valid works, despite their complex interrelationships of nesting and spanning one another.This element takes the IRI + name pattern. For more, see Used by: ~voc-element-tan-a, ~decl-class-1, ~voc-element-class-1<code><work></code> <head> ......... <license licensor="kalvesmaki"> ......... </license> <work> <IRI>http://dbpedia.org/resource/Categories_(Aristotle)</IRI> <name>Aristotle, Categories</name> </work> <source> ......... </source> ......... </head> Taken from ar.cat.eng.1926.edghill.ref-logical<code><work></code> <head> ......... <license licensor="kalvesmaki"> ......... </license> <work> <IRI>http://dbpedia.org/resource/Categories_(Aristotle)</IRI> <name>Aristotle, Categories</name> </work> <source> ......... </source> ......... </head> Taken from ar.cat.eng.1926.edghill.ref-scriptum<code><work></code> <head> ......... <license licensor="kalvesmaki"> ......... </license> <work> <IRI>http://dbpedia.org/resource/Categories_(Aristotle)</IRI> <name>Aristotle, Categories</name> </work> <source> ......... </source> ......... </head> Taken from ar.cat.fra.1844.saint-hilaire.ref-logical-after-1949<code><work></code> <head> ......... <reference-system type="logical" wf-ready="true"/> <work> <IRI>http://dbpedia.org/resource/Categories_(Aristotle)</IRI> <name xml:lang="fra">Aristote, Catégories</name> <name xml:lang="eng">Aristotle, Categories</name> </work> <source> ......... </source> ......... </head> Taken from ar.cat.fra.1844.saint-hilaire.ref-logical

TAN patterns

<code>~action-complex-condition</code>TAN-core.rng Used by: ~action-condition

<code>~action-condition</code>TAN-A-lm.rng TAN-core.rng Used by: ~element-rule, ~adjust-condition

<code>~action-condition-attributes</code>TAN-mor.rng TAN-class-2.rng TAN-core.rng Used by: ~condition-pattern, ~element-where, ~action-simple-condition

<code>~action-simple-condition</code>TAN-core.rng Used by: ~action-condition

<code>~adj-element-equate</code>TAN-class-2.rng Used by: ~adjust-class-2

<code>~adj-element-reassign</code>TAN-class-2.rng Used by: ~adjust-class-2

<code>~adj-element-rename</code>TAN-class-2.rng Used by: ~adjust-class-2

<code>~adj-element-skip</code>TAN-class-2.rng Used by: ~adjust-class-2

<code>~adjust-class-2</code>TAN-class-2.rng Used by: ~adjust-non-core

<code>~adjust-class-3</code>TAN-class-3.rng Used by: ~adjust-non-core

<code>~adjust-condition</code>TAN-class-2.rng TAN-core.rng Used by: ~element-adjustments

<code>~adjust-core</code>TAN-core.rng Used by: ~element-adjustments

<code>~adjust-non-class-2</code>TAN-class-2.rng Used by: ~adjust-non-core

<code>~adjust-non-class-3</code>TAN-class-3.rng Used by: ~adjust-non-core

<code>~adjust-non-core</code>TAN-class-1.rng TAN-class-2.rng TAN-class-3.rng TAN-core.rng Used by: ~element-adjustments

<code>~adjust-repl</code>TAN-class-1.rng Used by: ~adjust-non-core

<code>~adjustment-list</code>TAN-core.rng Used by: ~element-head

<code>~any-attribute</code>catalog.tan.rng TAN-core.rng Used by: ~any-element

<code>~any-content</code>catalog.tan.rng TAN-core.rng Used by: <doc>, ~any-element, ~element-tail

<code>~any-element</code>catalog.tan.rng TAN-core.rng Used by: ~any-content

<code>~attr-accessed-when</code>TAN-core.rng Used by: ~element-location, ~entity-digital-core-content

<code>~attr-by</code>TAN-class-2.rng Used by: ~complex-rename

<code>~attr-cert</code>TAN-core.rng Used by: ~certainty-claim

<code>~attr-cert2</code>TAN-core.rng Used by: ~certainty-claim

<code>~attr-chars</code>TAN-class-2.rng Used by: ~element-tok-abstract, ~element-tok-for-claim-no-ref, ~element-tok-for-claim-with-ref, ~element-tok-standard

<code>~attr-claim-period</code>TAN-class-2.rng Used by: ~claimant-attributes

<code>~attr-claim-when</code>TAN-class-2.rng Used by: ~claimant-attributes

<code>~attr-content-datatype</code>TAN-core.rng Used by: ~constraint-content

<code>~attr-content-lexical-constraint</code>TAN-core.rng Used by: ~constraint-content

<code>~attr-def-ref</code>TAN-A-lm.rng Used by: ~element-l

<code>~attr-ed-when</code>TAN-core.rng Used by: ~ed-stamp

<code>~attr-flags-for-errors</code>TAN-core.rng Used by: ~condition-pattern, ~element-change

<code>~attr-flags-for-functions</code>TAN-core.rng Used by: ~element-replace, ~element-token-definition

<code>~attr-href</code>TAN-core.rng Used by: ~element-location, ~element-master-location, ~entity-digital-tan-other-content

<code>~attr-id-alias</code>TAN-core.rng Used by: ~voc-element-alias

<code>~attr-id-tan</code>TAN-core.rng Used by: ~TAN-root

<code>~attr-id-xml</code>TAN-core.rng 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

<code>~attr-in-lang</code>TAN-A.rng Used by: ~in-lang

<code>~attr-item-type</code>TAN-core.rng Used by: ~constraint-item-type

<code>~attr-lang-xml</code>TAN-core.rng Used by: ~nontextual-reference, ~body-attributes-non-core, ~element-div, ~metadata-human-readable-attributes

<code>~attr-n</code>TAN-core.rng Used by: ~element-div, ~adj-element-equate, ~adj-element-skip, ~simple-rename, ~complex-rename, ~group-attributes-core

<code>~attr-new-name</code>TAN-class-2.rng Used by: ~simple-rename, ~complex-rename

<code>~attr-new-ref</code>TAN-class-2.rng Used by: ~simple-rename

<code>~attr-pattern</code>TAN-core.rng Used by: ~element-replace, ~element-token-definition

<code>~attr-pos-many</code>TAN-class-2.rng Used by: ~tok-selector-attributes-many

<code>~attr-pos-one</code>TAN-class-2.rng Used by: ~tok-selector-attributes-one

<code>~attr-priority</code>TAN-class-2.rng Used by: ~adj-element-reassign, ~adj-element-rename

<code>~attr-ref-alias</code>TAN-class-1.rng Used by: ~element-div

<code>~attr-ref-many</code>TAN-class-2.rng Used by: ~element-tok-for-claim-with-ref, ~multi-source-whole-div-textual-reference, ~adj-element-skip, ~element-tok-standard, ~complex-rename

<code>~attr-ref-one</code>TAN-class-2.rng Used by: ~single-div-partial-textual-reference, ~element-from-tok-with-ref, ~element-passage, ~element-to, ~element-through-tok-with-ref, ~simple-rename

<code>~attr-replacement</code>TAN-class-1.rng Used by: ~element-replace

<code>~attr-rgx</code>TAN-class-2.rng Used by: ~element-tok-abstract, ~tok-selector-attributes-one, ~tok-selector-attributes-many

<code>~attr-scriptum</code>TAN-class-1.rng Used by: ~element-reference-system

<code>~attr-shallow</code>TAN-class-2.rng Used by: ~adj-element-skip

<code>~attr-status</code>TAN-core.rng Used by: ~element-at-ref-constraint, ~element-in-lang-constraint, ~element-object-constraint, ~element-period-constraint, ~element-place-constraint, ~element-subject-constraint

<code>~attr-TAN-ver</code>TAN-core.rng Used by: ~TAN-root

<code>~attr-tok-pop</code>TAN-A-lm.rng Used by: ~element-ana

<code>~attr-type-ref-system</code>TAN-class-1.rng Used by: ~element-reference-system

<code>~attr-val</code>TAN-class-2.rng Used by: ~element-tok-abstract, ~tok-selector-attributes-one, ~tok-selector-attributes-many

<code>~attr-wf-ready</code>TAN-class-1.rng Used by: ~element-reference-system

<code>~attr-when</code>TAN-core.rng Used by: ~element-change, ~element-comment

<code>~attribute-scope</code>TAN-voc.rng Used by: ~body-attributes-non-core, ~group-attributes-non-core, ~element-item

<code>~body-attributes-non-core</code>TAN-A-lm.rng TAN-A-tok.rng TAN-T.rng TAN-voc.rng TAN-core.rng Used by: ~element-body

<code>~body-content-class-1</code>TAN-class-1.rng Used by: ~body-content-non-core

<code>~body-content-class-2</code>TAN-class-2.rng Used by: ~body-content-non-core

<code>~body-content-class-3</code>TAN-class-3.rng Used by: ~body-content-non-core

<code>~body-content-core</code>TAN-core.rng Used by: ~element-body

<code>~body-content-non-class-1</code>TAN-T.rng TAN-class-1.rng Used by: ~body-content-non-core

<code>~body-content-non-class-2</code>TAN-A.rng TAN-class-2.rng Used by: ~body-content-non-core

<code>~body-content-non-class-3</code>TAN-mor.rng TAN-voc.rng TAN-class-3.rng Used by: ~body-content-non-core

<code>~body-content-non-core</code>TAN-class-1.rng TAN-class-2.rng TAN-class-3.rng TAN-core.rng Used by: ~element-body

<code>~body-group</code>TAN-class-1.rng TAN-core.rng Used by: ~body-content-non-class-3, ~body-content-non-class-2, ~element-group

<code>~body-item</code>TAN-A-lm.rng TAN-A-tok.rng TAN-T.rng TAN-voc.rng TAN-core.rng Used by: ~body-content-non-class-1, ~body-content-non-class-3, ~body-content-non-class-2, ~element-group

<code>~certainty-claim</code>TAN-core.rng Used by: ~element-claim, ~tok-cert-opt, ~certainty-stamp

<code>~certainty-stamp</code>TAN-core.rng Used by: ~element-ana, ~element-l, ~element-lm, ~element-m, ~element-tok-abstract, ~element-align

<code>~claimant-attributes</code>TAN-class-2.rng Used by: ~element-ana, ~element-claim, ~body-content-class-2

<code>~complex-object</code>TAN-A.rng Used by: ~object

<code>~complex-rename</code>TAN-class-2.rng Used by: ~adj-element-rename

<code>~cond-attr-m-has-codes</code>TAN-mor.rng Used by: ~action-condition-attributes

<code>~cond-attr-m-has-how-many-codes</code>TAN-mor.rng Used by: ~action-condition-attributes

<code>~cond-attr-m-matches</code>TAN-mor.rng Used by: ~action-condition-attributes

<code>~cond-attr-tok-matches</code>TAN-mor.rng Used by: ~action-condition-attributes

<code>~condition-pattern</code>TAN-mor.rng Used by: ~element-assert, ~element-report

<code>~constraint-content</code>TAN-core.rng Used by: ~element-object-constraint, ~element-subject-constraint

<code>~constraint-item-type</code>TAN-core.rng Used by: ~element-object-constraint, ~element-subject-constraint

<code>~constraints-on-verb</code>TAN-core.rng Used by: ~entity-nondigital-with-constraints-content

<code>~data-certainty</code>TAN-core.rng Used by: ~attr-cert, ~attr-cert2

<code>~data-div-item-ref</code>TAN-core.rngTAN-core: String for a @ref that specifies a single <div>. Used by: ~attr-new-ref, ~attr-ref-one

<code>~data-div-range-ref</code>TAN-core.rngTAN-core: String for a @ref that specifies a range of <div>s: one or more data-div-item-ref patterns separated by a hyphen or a comma. Used by: ~attr-ref-many

<code>~data-IRI</code>TAN-core.rngTAN-core: Any generic IRI identifier. Used by: ~element-IRI

<code>~data-picker-item</code>TAN-core.rngTAN-core: String that specifies a single item from a sequence: digits or "last(-digit)?" Similar to ~data-picker-sequence.. Used by: ~attr-pos-one

<code>~data-picker-sequence</code>TAN-core.rngTAN-core: String that specifies a range of items in a sequence: digits or "last(-digit)?" joined by hyphens (ranges) or commas. Similar to ~data-picker-item.. Used by: ~cond-attr-m-has-how-many-codes, ~attr-chars, ~attr-pos-many

<code>~data-tag-uri</code>TAN-core.rngTAN-core: Tag URN, mandatory pattern for the IRI name of every TAN file Used by: ~attr-id-tan

<code>~decl-class-1</code>TAN-class-1.rng Used by: ~declaration-non-core

<code>~decl-class-2</code>TAN-class-2.rng Used by: ~declaration-non-core

<code>~decl-class-3</code>TAN-class-3.rng Used by: ~declaration-non-core

<code>~decl-non-class-1</code>TAN-class-1.rng Used by: ~declaration-non-core

<code>~decl-non-class-2</code>TAN-A-lm.rng TAN-class-2.rng Used by: ~declaration-non-core

<code>~decl-non-class-3</code>TAN-mor.rng TAN-class-3.rng Used by: ~declaration-non-core

<code>~declaration-core</code>TAN-core.rng Used by: ~declaration-list

<code>~declaration-list</code>TAN-core.rng Used by: ~element-head

<code>~declaration-non-core</code>TAN-class-1.rng TAN-class-2.rng TAN-class-3.rng TAN-core.rng Used by: ~declaration-list

<code>~default-tok-element</code>TAN-A-lm.rng TAN-class-2.rng Used by: ~element-ana, ~element-align, ~element-group-for-tok

<code>~doc-attributes</code>catalog.tan.rng Used by: <doc>

<code>~ed-stamp</code>TAN-core.rngTAN-core: Editorial stamp: who created or edited the enclosed data and when. Used by: ~element-claim, ~element-at-ref, ~element-div, ~element-in-lang, ~element-object, ~element-subject, ~element-category, ~element-code, ~element-rule, ~element-item, ~element-replace, ~adj-element-equate, ~adj-element-reassign, ~adj-element-rename, ~adj-element-skip, ~element-group-for-tok, ~element-passage, ~element-tok-standard, ~element-adjustments, ~element-at-ref-constraint, ~element-body, ~element-change, ~element-file-resp, ~element-group, ~element-head, ~element-in-lang-constraint, ~element-IRI, ~element-license, ~element-location, ~element-master-location, ~element-object-constraint, ~element-period-constraint, ~element-place-constraint, ~element-resp, ~element-subject-constraint, ~element-to-do, ~element-token-definition, ~element-vocabulary-key, ~element-where, ~link-element-inclusion, ~link-element-see-also, ~voc-element-alias, ~voc-element-period, ~certainty-stamp, ~constraints-on-verb, ~entity-digital-nontan-id, ~entity-digital-nontan-no-id, ~entity-digital-tan-id, ~entity-digital-tan-no-id, ~entity-nondigital-constrained, ~entity-nondigital-id, ~entity-nondigital-no-id, ~metadata-human-readable-attributes, ~TAN-root

<code>~element-adjustments</code>TAN-core.rng Used by: ~adjustment-list

<code>~element-align</code>TAN-A-tok.rng Used by: ~body-item

<code>~element-ana</code>TAN-A-lm.rng Used by: ~body-item

<code>~element-assert</code>TAN-mor.rng Used by: ~element-rule

<code>~element-at-ref</code>TAN-A.rng Used by: ~element-claim

<code>~element-at-ref-constraint</code>TAN-core.rng Used by: ~constraints-on-verb

<code>~element-body</code>TAN-core.rng Used by: ~TAN-root

<code>~element-category</code>TAN-mor.rng Used by: ~features-categorized

<code>~element-change</code>TAN-core.rng Used by: ~element-head

<code>~element-checksum</code>TAN-core.rng Used by: ~entity-digital-core-content

<code>~element-claim</code>TAN-A.rng Used by: ~body-content-non-class-2, ~complex-object

<code>~element-code</code>TAN-mor.rng Used by: ~element-category, ~features-uncategorized

<code>~element-comment</code>TAN-core.rng Used by: ~element-ana, ~element-lm, ~element-align, ~element-category, ~element-item, ~element-replace, ~element-adjustments, ~element-group, ~element-head, ~element-license, ~element-to-do, ~element-vocabulary-key, ~link-element-inclusion, ~link-element-see-also, ~body-content-core, ~constraints-on-verb, ~entity-digital-nontan-id, ~entity-digital-nontan-no-id, ~entity-digital-tan-id, ~entity-digital-tan-no-id, ~entity-nondigital-constrained, ~entity-nondigital-id, ~entity-nondigital-no-id

<code>~element-desc</code>TAN-core.rng Used by: ~element-code, ~metadata-human-readable

<code>~element-div</code>TAN-A.rng TAN-T.rng Used by: ~element-div, ~scriptum-filter, ~body-item

<code>~element-file-resp</code>TAN-core.rng Used by: ~resp-list

<code>~element-for-lang</code>TAN-core.rng Used by: ~decl-non-class-2, ~decl-non-class-3

<code>~element-from-tok-no-ref</code>TAN-class-2.rng Used by: ~text-passage-selector-no-ref

<code>~element-from-tok-with-ref</code>TAN-class-2.rng Used by: ~text-passage-selector-with-ref

<code>~element-group</code>TAN-core.rng Used by: ~body-group

<code>~element-group-for-tok</code>TAN-class-2.rng Used by: ~element-ana, ~element-align

<code>~element-head</code>TAN-core.rng Used by: ~TAN-root

<code>~element-in-lang</code>TAN-A.rng Used by: ~in-lang

<code>~element-in-lang-constraint</code>TAN-core.rng Used by: ~constraints-on-verb

<code>~element-IRI</code>TAN-core.rng Used by: ~entity-digital-core-content, ~entity-nondigital-content, ~entity-nondigital-with-constraints-content

<code>~element-item</code>TAN-voc.rng Used by: ~body-item

<code>~element-l</code>TAN-A-lm.rng Used by: ~element-lm

<code>~element-license</code>TAN-core.rng Used by: ~declaration-core

<code>~element-lm</code>TAN-A-lm.rng Used by: ~element-ana

<code>~element-location</code>TAN-core.rng Used by: ~entity-digital-core-content

<code>~element-m</code>TAN-A-lm.rng Used by: ~element-lm

<code>~element-master-location</code>TAN-core.rng Used by: ~entity-digital-tan-self-content

<code>~element-n-alias</code>TAN-class-1.rng Used by: ~decl-class-1

<code>~element-name</code>TAN-core.rng Used by: ~metadata-human-readable

<code>~element-normalization</code>TAN-class-1.rng Used by: ~adjust-non-core

<code>~element-numerals</code>TAN-core.rng Used by: ~declaration-core

<code>~element-object</code>TAN-A.rng Used by: ~complex-object

<code>~element-object-constraint</code>TAN-core.rng Used by: ~constraints-on-verb

<code>~element-passage</code>TAN-class-2.rng Used by: ~adj-element-reassign

<code>~element-period-constraint</code>TAN-core.rng Used by: ~constraints-on-verb

<code>~element-place-constraint</code>TAN-core.rng Used by: ~constraints-on-verb

<code>~element-reference-system</code>TAN-class-1.rng Used by: ~decl-class-1

<code>~element-replace</code>TAN-class-1.rng Used by: ~adjust-repl

<code>~element-report</code>TAN-mor.rng Used by: ~element-rule

<code>~element-resp</code>TAN-core.rng Used by: ~resp-list

<code>~element-rule</code>TAN-mor.rng Used by: ~TAN-mor-body

<code>~element-scope</code>TAN-voc.rng Used by: ~body-attributes-non-core, ~group-attributes-non-core, ~element-item

<code>~element-subject</code>TAN-A.rng Used by: ~subject

<code>~element-subject-constraint</code>TAN-core.rng Used by: ~constraints-on-verb

<code>~element-tail</code>TAN-core.rng Used by: ~TAN-root

<code>~element-through-tok-no-ref</code>TAN-class-2.rng Used by: ~text-passage-selector-no-ref

<code>~element-through-tok-with-ref</code>TAN-class-2.rng Used by: ~text-passage-selector-with-ref

<code>~element-to</code>TAN-class-2.rng Used by: ~adj-element-reassign

<code>~element-to-do</code>TAN-core.rng Used by: ~element-head

<code>~element-tok-abstract</code>TAN-A-lm.rng Used by: ~default-tok-element

<code>~element-tok-for-claim-no-ref</code>TAN-A.rng Used by: ~single-div-partial-textual-reference

<code>~element-tok-for-claim-with-ref</code>TAN-A.rng Used by: ~multi-div-partial-textual-reference

<code>~element-tok-is</code>TAN-A-lm.rng Used by: ~decl-non-class-2

<code>~element-tok-standard</code>TAN-class-2.rng Used by: ~default-tok-element

<code>~element-tok-starts-with</code>TAN-A-lm.rng Used by: ~decl-non-class-2

<code>~element-token-definition</code>TAN-core.rng Used by: ~decl-class-1, ~decl-class-2, ~entity-tok-def

<code>~element-val</code>TAN-mor.rng Used by: ~element-code

<code>~element-version</code>TAN-class-1.rng Used by: ~decl-class-1

<code>~element-vocabulary-key</code>TAN-core.rng Used by: ~vocabulary-list

<code>~element-where</code>TAN-core.rng Used by: ~action-complex-condition

<code>~element-work</code>TAN-class-1.rng Used by: ~decl-class-1

<code>~entity-digital-core-content</code>TAN-core.rng Used by: ~link-element-see-also, ~entity-digital-nontan-id, ~entity-digital-nontan-no-id, ~entity-digital-tan-other-content

<code>~entity-digital-nontan-id</code>TAN-core.rng Used by: ~voc-element-alg

<code>~entity-digital-nontan-no-id</code>TAN-core.rng Used by: ~source-content

<code>~entity-digital-tan-id</code>TAN-core.rng Used by: ~voc-element-lexicon, ~voc-element-morphology, ~source-content

<code>~entity-digital-tan-no-id</code>TAN-core.rng Used by: ~link-element-annotation, ~link-element-model, ~link-element-redivision, ~source-content, ~link-element-companion-version, ~link-element-predecessor, ~link-element-successor, ~link-element-vocabulary

<code>~entity-digital-tan-other-content</code>TAN-core.rng Used by: ~element-item, ~link-element-inclusion, ~link-element-see-also, ~entity-digital-tan-id, ~entity-digital-tan-no-id

<code>~entity-digital-tan-self-content</code>TAN-core.rng Used by: ~element-head

<code>~entity-nondigital-constrained</code>TAN-core.rng Used by: ~voc-element-verb

<code>~entity-nondigital-content</code>TAN-core.rng Used by: ~element-item, ~element-checksum, ~element-license, ~entity-nondigital-id, ~entity-nondigital-no-id

<code>~entity-nondigital-id</code>TAN-core.rng Used by: ~voc-element-lexicon, ~voc-element-brel, ~voc-element-reus, ~voc-element-modal, ~voc-element-place, ~voc-element-topic, ~voc-element-unit, ~voc-element-vers, ~voc-element-feature, ~voc-element-div-type, ~voc-element-group-type, ~voc-element-org, ~voc-element-period, ~voc-element-person, ~voc-element-relationship, ~voc-element-role, ~voc-element-scri, ~voc-element-work

<code>~entity-nondigital-no-id</code>TAN-core.rng Used by: ~source-content, ~element-normalization, ~element-version, ~element-work

<code>~entity-nondigital-with-constraints-content</code>TAN-core.rng Used by: ~element-item, ~entity-nondigital-constrained

<code>~entity-tok-def</code>TAN-core.rng Used by: ~element-item

<code>~extra-verb-attrs</code>TAN-voc.rng TAN-core.rng Used by: ~voc-element-verb

<code>~features-categorized</code>TAN-mor.rng Used by: ~TAN-mor-body

<code>~features-uncategorized</code>TAN-mor.rng Used by: ~TAN-mor-body

<code>~group-attributes</code>TAN-core.rng Used by: ~element-group-for-tok, ~element-group

<code>~group-attributes-core</code>TAN-core.rng Used by: ~group-attributes

<code>~group-attributes-non-core</code>TAN-A-lm.rng TAN-voc.rng TAN-core.rng Used by: ~group-attributes

<code>~in-lang</code>TAN-A.rng Used by: ~element-claim

<code>~inclusion</code>TAN-core.rng Used by: ~element-ana, ~element-align, ~element-claim, ~element-category, ~element-code, ~element-rule, ~element-div, ~element-item, ~element-replace, ~adj-element-equate, ~adj-element-reassign, ~adj-element-rename, ~adj-element-skip, ~element-group-for-tok, ~element-adjustments, ~element-file-resp, ~element-group, ~element-license, ~element-resp, ~element-to-do, ~element-token-definition, ~link-element-see-also, ~voc-element-period, ~entity-digital-nontan-id, ~entity-digital-nontan-no-id, ~entity-digital-tan-id, ~entity-digital-tan-no-id, ~entity-nondigital-constrained, ~entity-nondigital-id, ~entity-nondigital-no-id

<code>~link-element-annotation</code>TAN-class-1.rng Used by: ~networked-files-non-core

<code>~link-element-companion-version</code>TAN-core.rng Used by: ~networked-files-core

<code>~link-element-inclusion</code>TAN-core.rng Used by: ~networked-files-core

<code>~link-element-model</code>TAN-class-1.rng Used by: ~networked-files-non-core

<code>~link-element-predecessor</code>TAN-core.rng Used by: ~networked-files-core

<code>~link-element-redivision</code>TAN-class-1.rng Used by: ~networked-files-non-core

<code>~link-element-see-also</code>TAN-core.rng Used by: ~networked-files-core

<code>~link-element-source</code>TAN-core.rng Used by: ~source-list

<code>~link-element-successor</code>TAN-core.rng Used by: ~networked-files-core

<code>~link-element-vocabulary</code>TAN-core.rng Used by: ~networked-files-core, ~vocabulary-list

<code>~metadata-human-readable</code>TAN-core.rng Used by: ~entity-digital-core-content, ~entity-digital-tan-self-content, ~entity-nondigital-content, ~entity-nondigital-with-constraints-content, ~entity-tok-def

<code>~metadata-human-readable-attributes</code>TAN-core.rng Used by: ~element-desc, ~element-name

<code>~multi-div-partial-textual-reference</code>TAN-A.rng Used by: ~single-source-partial-div-textual-reference

<code>~multi-source-whole-div-textual-reference</code>TAN-A.rng Used by: ~textual-reference

<code>~networked-files</code>TAN-core.rng Used by: ~element-head

<code>~networked-files-core</code>TAN-core.rng Used by: ~networked-files

<code>~networked-files-non-core</code>TAN-class-1.rng TAN-core.rng Used by: ~networked-files

<code>~nondoc-attributes</code>catalog.tan.rng Used by: <doc>

<code>~nontextual-reference</code>TAN-A.rng Used by: ~element-object, ~element-subject

<code>~object</code>TAN-A.rng Used by: ~element-claim

<code>~ptr-attr-bitext-relation</code>TAN-A-tok.rng Used by: ~body-attributes-non-core, ~element-align

<code>~ptr-attr-claimant</code>TAN-class-2.rng Used by: ~claimant-attributes

<code>~ptr-attr-div-type</code>TAN-core.rng Used by: ~element-n-alias, ~action-condition-attributes, ~adj-element-skip

<code>~ptr-attr-ed-who</code>TAN-core.rng Used by: ~ed-stamp

<code>~ptr-attr-feature</code>TAN-mor.rng Used by: ~element-category, ~element-code

<code>~ptr-attr-group</code>TAN-core.rng Used by: ~element-ana, ~element-align, ~extra-verb-attrs, ~element-item

<code>~ptr-attr-idrefs</code>TAN-core.rng Used by: ~voc-element-alias

<code>~ptr-attr-include</code>TAN-core.rng Used by: ~inclusion

<code>~ptr-attr-lexicon</code>TAN-A-lm.rng Used by: ~group-attributes-non-core, ~body-attributes-non-core, ~element-ana, ~element-l, ~element-lm

<code>~ptr-attr-licensor</code>TAN-core.rng Used by: ~element-license

<code>~ptr-attr-modal</code>TAN-A.rng Used by: ~element-claim

<code>~ptr-attr-morphology</code>TAN-A-lm.rng Used by: ~group-attributes-non-core, ~body-attributes-non-core, ~element-ana, ~element-lm, ~element-m

<code>~ptr-attr-object</code>TAN-A.rng Used by: ~body-content-non-class-2, ~object

<code>~ptr-attr-period</code>TAN-core.rng Used by: ~element-claim, ~element-resp

<code>~ptr-attr-place</code>TAN-A.rng Used by: ~element-claim

<code>~ptr-attr-relationship</code>TAN-core.rng Used by: ~link-element-see-also

<code>~ptr-attr-reuse-type</code>TAN-A-tok.rng Used by: ~body-attributes-non-core, ~element-align

<code>~ptr-attr-role</code>TAN-core.rng Used by: ~element-resp

<code>~ptr-attr-scriptum</code>TAN-A.rng Used by: ~scriptum-reference

<code>~ptr-attr-src-many</code>TAN-A-lm.rng TAN-class-2.rng Used by: ~multi-source-whole-div-textual-reference, ~token-definition-attributes, ~action-condition-attributes, ~tok-sources-ref-opt

<code>~ptr-attr-src-one</code>TAN-class-2.rng Used by: ~single-source-partial-div-textual-reference

<code>~ptr-attr-subject</code>TAN-A.rng Used by: ~body-content-non-class-2, ~subject

<code>~ptr-attr-type</code>TAN-core.rng Used by: ~element-div, ~group-attributes-core

<code>~ptr-attr-units</code>TAN-A.rng Used by: ~nontextual-reference

<code>~ptr-attr-verb</code>TAN-A.rng Used by: ~body-content-non-class-2, ~element-claim

<code>~ptr-attr-which</code>TAN-core.rng Used by: ~element-token-definition, ~entity-digital-core-content, ~entity-nondigital-content, ~entity-nondigital-with-constraints-content

<code>~ptr-attr-who</code>TAN-core.rng Used by: ~element-change, ~element-comment, ~element-file-resp, ~element-resp

<code>~ptr-attr-work</code>TAN-A.rng Used by: ~multi-source-whole-div-textual-reference, ~work-version-reference

<code>~resp-list</code>TAN-core.rng Used by: ~element-head

<code>~scriptum-filter</code>TAN-A.rng Used by: ~scriptum-reference

<code>~scriptum-reference</code>TAN-A.rng Used by: ~textual-reference

<code>~simple-rename</code>TAN-class-2.rng Used by: ~adj-element-rename

<code>~single-div-partial-textual-reference</code>TAN-A.rng Used by: ~single-source-partial-div-textual-reference

<code>~single-source-partial-div-textual-reference</code>TAN-A.rng Used by: ~textual-reference

<code>~source-content</code>TAN-A-lm.rng TAN-class-1.rng TAN-class-2.rng TAN-class-3.rng TAN-core.rng Used by: ~link-element-source

<code>~source-list</code>TAN-A-lm.rng TAN-A-tok.rng TAN-A.rng TAN-voc.rng TAN-class-3.rngTAN-class-3: Class 3 files allow zero or many sources TAN-core.rng Used by: ~networked-files-core

<code>~subject</code>TAN-A.rng Used by: ~element-claim

<code>~TAN-mor-body</code>TAN-mor.rng Used by: ~body-content-non-class-3

<code>~TAN-root</code>TAN-core.rng Used by: <TAN-A-lm>, <TAN-A-tok>, <TAN-A>, <TAN-mor>, <TAN-T>, <TAN-voc>

<code>~text-passage-selector-no-ref</code>TAN-class-2.rng Used by: ~single-div-partial-textual-reference, ~element-passage

<code>~text-passage-selector-with-ref</code>TAN-class-2.rng Used by: ~multi-div-partial-textual-reference

<code>~textual-reference</code>TAN-A.rng Used by: ~element-at-ref, ~element-object, ~element-subject

<code>~tok-cert-opt</code>TAN-A.rng TAN-class-2.rng Used by: ~element-tok-standard

<code>~tok-selector-attributes-many</code>TAN-class-2.rng Used by: ~element-tok-for-claim-no-ref, ~element-tok-for-claim-with-ref, ~element-tok-standard

<code>~tok-selector-attributes-one</code>TAN-class-2.rng Used by: ~element-from-tok-no-ref, ~element-from-tok-with-ref, ~element-through-tok-no-ref, ~element-through-tok-with-ref

<code>~tok-sources-ref-opt</code>TAN-A-lm.rng TAN-class-2.rng Used by: ~element-tok-standard

<code>~token-definition-attributes</code>TAN-A-lm.rng TAN-class-2.rng TAN-core.rng Used by: ~element-token-definition

<code>~voc-element-agent</code>TAN-core.rng Used by: ~voc-key-core

<code>~voc-element-alg</code>TAN-core.rng Used by: ~voc-element-agent

<code>~voc-element-alias</code>TAN-core.rng Used by: ~voc-key-core

<code>~voc-element-brel</code>TAN-A-tok.rng Used by: ~voc-element-non-class-2

<code>~voc-element-class-1</code>TAN-class-1.rng Used by: ~voc-key-non-core

<code>~voc-element-class-2</code>TAN-class-2.rng Used by: ~voc-key-non-core

<code>~voc-element-class-3</code>TAN-class-3.rng Used by: ~voc-key-non-core

<code>~voc-element-div-type</code>TAN-core.rng Used by: ~voc-element-tan-a, ~voc-element-class-1

<code>~voc-element-feature</code>TAN-mor.rng Used by: ~voc-element-non-class-3

<code>~voc-element-group-type</code>TAN-core.rng Used by: ~voc-element-class-2, ~voc-element-class-3

<code>~voc-element-lexicon</code>TAN-A-lm.rng Used by: ~voc-element-non-class-2

<code>~voc-element-modal</code>TAN-A.rng Used by: ~voc-element-tan-a

<code>~voc-element-morphology</code>TAN-A-lm.rng Used by: ~voc-element-non-class-2

<code>~voc-element-non-class-1</code>TAN-class-1.rng Used by: ~voc-key-non-core

<code>~voc-element-non-class-2</code>TAN-A-lm.rng TAN-A-tok.rng TAN-A.rng TAN-class-2.rng Used by: ~voc-key-non-core

<code>~voc-element-non-class-3</code>TAN-mor.rng TAN-class-3.rng Used by: ~voc-key-non-core

<code>~voc-element-org</code>TAN-core.rng Used by: ~voc-element-agent

<code>~voc-element-period</code>TAN-core.rng Used by: ~voc-key-core

<code>~voc-element-person</code>TAN-core.rng Used by: ~voc-element-agent

<code>~voc-element-place</code>TAN-A.rng Used by: ~voc-element-tan-a

<code>~voc-element-relationship</code>TAN-core.rng Used by: ~voc-key-core

<code>~voc-element-reus</code>TAN-A-tok.rng Used by: ~voc-element-non-class-2

<code>~voc-element-role</code>TAN-core.rng Used by: ~voc-key-core

<code>~voc-element-scri</code>TAN-core.rng Used by: ~voc-element-tan-a, ~voc-element-class-1

<code>~voc-element-tan-a</code>TAN-A.rng Used by: ~voc-element-non-class-2

<code>~voc-element-topic</code>TAN-A.rng Used by: ~voc-element-tan-a

<code>~voc-element-unit</code>TAN-A.rng Used by: ~voc-element-tan-a

<code>~voc-element-verb</code>TAN-core.rng Used by: ~voc-element-tan-a, ~body-item

<code>~voc-element-vers</code>TAN-A.rng Used by: ~voc-element-tan-a

<code>~voc-element-work</code>TAN-core.rng Used by: ~voc-element-tan-a, ~voc-element-class-1

<code>~voc-key-core</code>TAN-core.rng Used by: ~element-vocabulary-key

<code>~voc-key-non-core</code>TAN-class-1.rng TAN-class-2.rng TAN-class-3.rng TAN-core.rng Used by: ~element-vocabulary-key

<code>~vocabulary-list</code>TAN-core.rng Used by: ~element-head

<code>~work-version-reference</code>TAN-A.rng Used by: ~textual-reference