TAN patterns, elements, and attributes definedThe contents of this chapter have been generated automatically. Although much effort has
been spent to ensure accurate representation of the schemas and function library, you may
find errors or inconsistencies. In such cases, the functions and schemas (particularly the
RELAX-NG, compact syntax) are to be given priority.The 81 elements and 61 attributes defined in TAN, excluding TEI, are the following:TAN-core@affects-element<algorithm><alias><alter><ambiguous-letter-numerals-are-roman><body>@cert@cert2<change><checksum><comment><definitions><desc>@ed-when@ed-who@flags@flags<for-lang>@from@group<group><group-type><head>@help@href@id@id@idrefs@in-progress@include<inclusion><IRI><key><license>@licensor<licensor><location><master-location>@n<name><organization>@pattern@period<period><person>@relationship<relationship><resp><role>@roles<see-also><source><tail><TAN-T>@TAN-version@to<token-definition>@type<value><version>@when@when-accessed<where>@which@who<work>@xml:id@xml:langTAN-class-1<div-type><normalization><replace>@replacementTAN-T<div><TAN-T>TAN-class-2@by@chars<div-ref>@div-type<equate><from><group>@new@new@pos@pos<reassign>@ref@ref<rename>@shallow<skip>@src@src<to><to><tok><tok>@valTAN-A-div@adverb<claim>@claimant<locus><modal>@object<object>@object-datatype@object-lexical-constraint<place><scriptum>@subject<subject><TAN-A-div><topic><unit>@units<verb>@verb@where@workTAN-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>TAN-class-3TAN-key<item><TAN-key>TAN-mor<assert><category>@code<feature><feature>@m-has-features@m-has-how-many-features@m-matches<report><rule><TAN-mor>@tok-matchescatalog.tan<collection><doc>@href@id@root@stable<code>@adverb</code>The attribute adverb names a <modal> that qualifies the claim. Multiple values of @adverb are interpreted to mean "and" with intersection. No distribution takes place (e.g., adverb="x y" means "[subject] x & y [verby]...", not "[subject] x [verb]..." and "[subject] y [verb]...").Formal DefinitionDefined at:
TAN-A-div.rngUsed by: ~claim<code>@adverb</code><TAN-A-div TAN-version="2018" id="tag:parkj@textalign.net,2015:ar.cat.tan-a-div:claims">
.........
<body claimant="lmp">
.........
<claim subject="dexippus porphyry">
<claim subject="andronicus boethus" adverb="perhaps" verb="omits">
<object src="grc">
.........
</object>
</claim>
</claim>
.........
<claim subject="B" verb="replaces">
.........
</claim>
<claim subject="Λ" adverb="perhaps" verb="replaces">
<locus src="grc">
.........
</locus>
<object>τις ἀποδιδῷ</object>
</claim>
<claim subject="π α φ ο" verb="agrees">
.........
</claim>
.........
</body>
</TAN-A-div>
Taken from ar.cat.tan-a-div.claims<code>@affects-element</code>The attribute affects-element names one or more TAN elements that the keywords apply toFormal DefinitionDefined at:
TAN-core.rngUsed by: ~body-attributes-non-core, ~group-attributes, ~TAN-key-item@affects-element must include only names of TAN elements that accept @which<code>@affects-element</code><TAN-key TAN-version="2018" id="tag:parkj@textalign.net,2015:TAN-key:ar.cat">
<head>
.........
</head>
<body in-progress="true" affects-element="work">
<item>
.........
</item>
<item>
.........
</item>
<group>
.........
</group>
.........
</body>
</TAN-key>
Taken from ar.cat.TAN-key<code>@affects-element</code><TAN-key TAN-version="2018" id="tag:textalign.net,2015:tan-key:bitext-relation">
<head>
.........
</head>
<body in-progress="true" affects-element="bitext-relation">
<item>
.........
</item>
<item>
.........
</item>
<item>
.........
</item>
.........
</body>
</TAN-key>
Taken from bitext-relations.TAN-key<code>@affects-element</code><TAN-key TAN-version="2018" id="tag:textalign.net,2015:tan-key:div-types">
<head>
.........
</head>
<body in-progress="false" affects-element="div-type">
<item group="line-start line-end leading-start leading-end">
.........
</item>
<item>
.........
</item>
<item>
.........
</item>
.........
</body>
</TAN-key>
Taken from div-types.TAN-key<code>@affects-element</code><TAN-key TAN-version="2018" id="tag:textalign.net,2015:tan-key:features">
<head>
.........
</head>
<body in-progress="false" affects-element="feature">
<item>
.........
</item>
<item>
.........
</item>
<item>
.........
</item>
.........
</body>
</TAN-key>
Taken from features.TAN-key<code>@bitext-relation</code>The attribute bitext-relation points to one or more <bitext-relation>@xml:id values that qualify the type of relation that holds. Multiple values assume inclusive or (A or B or A and B)This attribute is inheritable. See Formal DefinitionDefined at:
TAN-A-tok.rngUsed by: ~body-attributes-non-core, ~alignment-attributes-non-class-2Every idref in an attribute must point to the @xml:id value of the appropriate corresponding element.All idrefs in an attribute must be unique.<code>@bitext-relation</code><TAN-A-tok TAN-version="2018" id="tag:parkj@textalign.net,2015:TAN-A-tok,ring01+ring02">
<head>
.........
</head>
<body bitext-relation="B-descends-from-A" reuse-type="adaptation" in-progress="false">
<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="2018" id="tag:parkj@textalign.net,2015:TAN-A-tok,ring01+ring03">
<head>
.........
</head>
<body reuse-type="correlationGeneral" bitext-relation="unclear">
<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="2018" id="tag:parkj@textalign.net,2015:TAN-A-tok,ring01+ring03:alt">
<head>
.........
</head>
<body reuse-type="correlationGeneral" bitext-relation="unclear">
<align>
.........
</align>
<align>
.........
</align>
<align>
.........
</align>
.........
</body>
</TAN-A-tok>
Taken from ringoroses.01+03.token.2<code>@by</code>The attribute by specifies an amount by which an series of @n values or the last component in a series of @ref values should be incremented or decremented.Formal Definitioninteger Defined at:
TAN-class-2.rngUsed by: ~complex-rename@by may be applied only to those @n and @ref values that are calculable as integers.<code>@by</code> <alter src="ger">
<skip div-type="Gedicht"/>
<rename n="v" by="-1"/>
</alter>
Taken from ringoroses.div.1<code>@cert</code>The attribute cert states how certain an agent is of the data governed by the parent element, expressed as a real number from 0 (no certainty) to 1 (completely 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 data:...."Values of @cert amplify. Any @cert will be multiplied against any other values of @cert in a given context. 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 combination of the two is 0.25. 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 actual certainty is 0.18.This attribute is inheritable. See Formal Definitiondouble (pattern 1|0|(0\.\d*[1-9]))Defined at:
TAN-core.rngUsed by: ~cert-claim<code>@cert</code> <body reuse-type="correlationGeneral" bitext-relation="unclear">
.........
<align>
<tok src="eng" ref="1" pos="5" cert="0.3"/>
<tok src="ger" ref="1" pos="3" cert="0.3"/>
</align>
</body>
Taken from ringoroses.01+03.token.1<code>@cert</code> <body reuse-type="correlationGeneral" bitext-relation="unclear">
.........
<align>
<tok src="eng" ref="1" pos="5" cert="0.3"/>
<tok src="ger" ref="1" pos="3" cert="0.3"/>
</align>
</body>
Taken from ringoroses.01+03.token.2<code>@cert2</code>The attribute cert2 provides a second measure of certainty. The value is taken along with @cert as the range in which an editors certainty resides. Formal Definitiondouble (pattern 1|0|(0\.\d*[1-9]))Defined at:
TAN-core.rngUsed by: ~cert-claim<code>@chars</code>The attribute chars list of one or more characters, specified through Arabic numerals, the keyword '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'Formal Definitionstring (pattern ((last|max|all|\*)|((last|max)-\d+)|(\d+))(\s*-\s*(((last|max))|((last|max)-\d+)|(\d+)))?(\s*[, ]\s*(((last|max))|((last|max)-\d+)|(\d+))(\s+-\s+(((last|max))|((last|max)-\d+)|(\d+)))?)*|.*\?\?\?.*)Defined at:
TAN-class-2.rngUsed by: ~tok-ref-itemSequences 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.Ranges consist of exactly two values separated by a hyphen.<code>@claimant</code>The attribute claimant points to an <agent> or <person> who makes a claim. @claimant within <body> indicates the default persons to be credited or blamed for an assertion.Claimants are not to be confused with the editor of a TAN file. If an editor X writes a TAN-c file that says that person Y makes such-and-such a claim, then the implication is that X claims that Y claims that.... 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...").If you wish to claim that claimant X claimed that claimant Y claimed that claimant Z...., only the original claimant is given to @claimant, and each of the other claimants are placed in a @subject in an embedded <claim> that serves as the object of the master <claim>. This attribute is inheritable. See Formal DefinitionDefined at:
TAN-A-div.rngUsed by: ~body-content-non-class-2, ~claim<code>@claimant</code><TAN-A-div TAN-version="2018" id="tag:parkj@textalign.net,2015:ar.cat.tan-a-div:claims">
<head>
.........
</head>
<body claimant="lmp">
<comment when="2017-03-10-05:00" who="park">The following 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. This interpretation
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="dexippus porphyry">
.........
</claim>
<claim subject="herminus comm-omnes" verb="agrees">
.........
</claim>
.........
</body>
</TAN-A-div>
Taken from ar.cat.tan-a-div.claims<code>@claimant</code><TAN-A-div TAN-version="2018" id="tag:parkj@textalign.net,2015:ar.cat.tan-a-div">
<head>
.........
</head>
<body claimant="park">
<claim verb="is-about" object="predication">
.........
</claim>
</body>
</TAN-A-div>
Taken from ar.cat.tan-a-div<code>@claimant</code><TAN-A-div TAN-version="2018" id="tag:parkj@textalign.net,2015:ring01-TAN-A-ring02">
<head>
.........
</head>
<body claimant="park"/>
</TAN-A-div>
Taken from ringoroses.div.1<code>@code</code>The attribute code contains a string that serves as an identifier for <feature>.Formal Definitionstring (pattern [^\-\+\s]|[^\+\s]+)Defined at:
TAN-mor.rngUsed by: ~feature-refId values for features must be case-indifferently unique within a given category.<code>@def-ref</code>The attribute def-ref identifies which definition is meant. This attribute is essential in cases where a lexicon has multiple entries for lexemes that are orthographically indistinguishable. Because there is no TAN format for lexicons, the value in this attribute will not be validated.Formal DefinitionDefined at:
TAN-A-lm.rngUsed by: <l><code>@div-type</code>The attribute div-type is used by class-2 files to point to one or more <div-type>s in class-1 files. Permits multiple values separated by spaces.Formal DefinitionDefined at:
TAN-class-2.rngUsed by: ~action-condition-attributes, ~alt-skipEvery div type reference must be valid in every source<code>@div-type</code> <alter src="fra">
<skip div-type="sec"/>
<rename ref="1 1-3" new="1 1 1-3"/>
.........
</alter>
Taken from ar.cat.tan-a-div<code>@div-type</code> <alter src="ger">
<skip div-type="Gedicht"/>
<rename n="v" by="-1"/>
</alter>
Taken from ringoroses.div.1<code>@div-type</code> <alter src="ger">
<skip div-type="Gedicht"/>
</alter>
Taken from ringoroses.01+03.token.1<code>@div-type</code> <alter src="ger">
<skip div-type="Gedicht"/>
<rename ref="5" new="4"/>
</alter>
Taken from ringoroses.01+03.token.2<code>@ed-when</code>The attribute ed-when marks the date or time when an element or its content was edited (added or modified)The value of must always conform to an ISO date or dateTime pattern. See .Along with @ed-who, this forms the Edit Stamp pattern. See This attribute is inheritable. See Formal Definition(
dateTime
date )Defined at:
TAN-core.rngUsed by: ~ed-stampDate attributes must be castable either as xs:dateTime or xs:dateFuture dates are not permitted.<code>@ed-when</code> <head>
.........
<see-also relationship="model">
.........
</see-also>
<definitions ed-who="park" ed-when="2015-10-31">
<work>
.........
</work>
<div-type xml:id="l">
.........
</div-type>
<person xml:id="park">
.........
</person>
.........
</definitions>
<alter>
.........
</alter>
.........
</head>
Taken from ring-o-roses.eng.1987<code>@ed-when</code> <definitions>
<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" when-accessed="2015-11-03-05:00"/>
</morphology>
<lexicon xml:id="english">
.........
</lexicon>
.........
</definitions>
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>
<definitions ed-when="2015-03-03" ed-who="kalvesmaki">
<person xml:id="kalvesmaki">
.........
</person>
<algorithm xml:id="xslt1">
.........
</algorithm>
<role xml:id="editor">
.........
</role>
.........
</definitions>
<resp roles="editor" who="kalvesmaki"/>
.........
</head>
Taken from eng.kalvesmaki.com,2014.2<code>@ed-who</code>The attribute ed-who refers to one or more <agent>s who have edited (added or modified) an element or its content.Along with @ed-when, this forms the Edit Stamp pattern. See This attribute is inheritable. See Formal DefinitionDefined at:
TAN-core.rngUsed by: ~ed-stampEvery idref in an attribute must point to the @xml:id value of the appropriate corresponding element.All idrefs in an attribute must be unique.<code>@ed-who</code> <head>
.........
<see-also relationship="model">
.........
</see-also>
<definitions ed-who="park" ed-when="2015-10-31">
<work>
.........
</work>
<div-type xml:id="l">
.........
</div-type>
<person xml:id="park">
.........
</person>
.........
</definitions>
<alter>
.........
</alter>
.........
</head>
Taken from ring-o-roses.eng.1987<code>@ed-who</code> <definitions>
<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" when-accessed="2015-11-03-05:00"/>
</morphology>
<lexicon xml:id="english">
.........
</lexicon>
.........
</definitions>
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>
<definitions ed-when="2015-03-03" ed-who="kalvesmaki">
<person xml:id="kalvesmaki">
.........
</person>
<algorithm xml:id="xslt1">
.........
</algorithm>
<role xml:id="editor">
.........
</role>
.........
</definitions>
<resp roles="editor" who="kalvesmaki"/>
.........
</head>
Taken from eng.kalvesmaki.com,2014.2<code>@flags</code>The attribute flags indicates the level of error that should be flagged to any algorithm that uses the parent element . Similar to Schematron's @role, but under a different name, to avoid confusion with TAN @roles.The attribute flags specifies flags to be applied in an XPath function that uses regular expressions.s = dot-all mode; m = multi-line mode; i = case-insensitive mode; x = remove whitespace characters from regular expression; q = no metacharacters For more see http://www.w3.org/TR/xpath-functions-30/#flagsFormal Definitionstring (pattern warning|error|info|fatal)string (pattern [smixq]+)Defined at:
TAN-core.rngUsed by: ~condition-pattern, ~func-replace, ~change-log, ~defn-tok-def<code>@flags</code> <head>
.........
<change when="2014-10-28" who="park">Created new TAN-TEI file.</change>
<change when="2017-10-21" who="park" flags="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.1957<code>@from</code>The attribute from specifies the beginning of a period of timeFormal Definition(
dateTime
date )Defined at:
TAN-core.rngUsed by: <period>Date attributes must be castable either as xs:dateTime or xs:dateFuture dates are not permitted.@from must predate @to<code>@group</code>The attribute group identifies one or more <group-type>s under which the parent element, and its children, should be grouped.Formal DefinitionDefined at:
TAN-core.rngUsed by: ~TAN-A-lm-item, ~non-class-2-opt, ~TAN-key-item<code>@group</code><TAN-key TAN-version="2018" id="tag:textalign.net,2015:tan-key:div-types">
.........
<body in-progress="false" affects-element="div-type">
<item group="line-start line-end leading-start leading-end">
<IRI>tag:textalign.net,2015:div-type:abstract</IRI>
<IRI>http://www.tei-c.org/ns/1.0/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/page/Afterword</IRI>
<name>afterword</name>
</item>
<item>
.........
</item>
.........
<item>
.........
</item>
<item group="line-start line-end leading-start leading-end">
<IRI>tag:textalign.net,2015:div-type:block_quote</IRI>
<IRI>http://www.w3.org/1999/xhtml/blockquote</IRI>
<IRI>http://dbpedia.org/resource/Block_quotation</IRI>
.........
</item>
<item group="page-start page-end">
<IRI>tag:textalign.net,2015:div-type:book</IRI>
<IRI>http://dbpedia.org/resource/Book</IRI>
<name>book</name>
.........
</item>
<item>
.........
</item>
.........
</body>
</TAN-key>
Taken from div-types.TAN-key<code>@help</code>The attribute help requests help on the context element. This attribute is equivalent to the help requested string, ???, but is useful in cases where the string cannot be placed (e.g., elements with no content or few attributes)Formal Definition{empty}Defined at:
TAN-core.rngUsed by: ~inclusion<code>@href</code>The attribute href points to the location of a file. In some contexts, this attribute is allowed only as a temporary measure, to invoke editing assistance by means of Schematron Quick Fixes.Formal DefinitionDefined at:
catalog.tan.rng, TAN-core.rngUsed by: <doc>, ~entity-digital-tan-other-ref, ~loc-self, ~loc-src@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 fn:doc-available() for an @href returns false, the following message will be returned. @href points to 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 the same document id is that of <master-location>No @href should point to the URI of the document itself.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:model-object-refs" TAN-version="2018">
<head>
.........
<see-also relationship="ade">
.........
<name>Categories, Aristotle, English translation by E. M. Edghill</name>
<location href="ar.cat.eng.1926.edghill.sem.xml" when-accessed="2016-07-07T16:36:28.867-04:00"/>
</see-also>
<see-also relationship="model">
.........
<name>Categories, Aristotle, Greek text by Minio-Paluello</name>
<location href="ar.cat.grc.1949.minio-paluello-obj.xml" when-accessed="2016-07-07T16:36:28.867-04:00"/>
</see-also>
.........
</head>
.........
</TAN-T>
Taken from ar.cat.eng.1926.edghill.obj<code>@href</code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2018">
<head>
.........
<see-also relationship="model">
.........
<name>Categories, Aristotle, Greek text by Minio-Paluello</name>
<location href="ar.cat.grc.1949.minio-paluello-sem.xml" when-accessed="2016-02-10T14:08:52.058-05:00"/>
</see-also>
<see-also relationship="alt">
.........
<name>Categories, Aristotle, Greek text by Minio-Paluello</name>
<location href="ar.cat.grc.1949.minio-paluello-obj.xml" when-accessed="2016-02-11T12:40:42.823-05:00"/>
</see-also>
.........
</head>
.........
</TAN-T>
Taken from ar.cat.eng.1926.edghill.sem<code>@id</code>The attribute id identifies an entity described within an element. Must be unique within a given file. Must consist only of non-spacing characters.The attribute id contains a tag URN that permanently and uniquely names the current file, the so-called IRI Name of the current file. See for discussion.For more on the syntax of tag URNs see Formal DefinitionanyURI string (pattern \S+)anyURI (pattern tag:([\-a-zA-Z0-9._%+]+@)?[\-a-zA-Z0-9.]+\.[A-Za-z]{2,4},\d{4}(-(0\d|1[0-2]))?(-([0-2]\d|3[01]))?:\S+)Defined at:
catalog.tan.rng, TAN-core.rngUsed by: <doc>, <TAN-A-div>, <TAN-A-lm>, <TAN-A-tok>, <TAN-key>, <TAN-mor>, <TAN-T>, ~defn-aliasEvery TAN file must have a primary agent, the organization or person that takes the greatest responsibility for the content of the TAN file. The primary agent is defined as the first <agent> 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.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:model-object-refs" TAN-version="2018">
<head>
.........
</head>
<body xml:lang="eng">
.........
</body>
</TAN-T>
Taken from ar.cat.eng.1926.edghill.obj<code>@id</code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2018">
<head>
.........
</head>
<body xml:lang="eng">
.........
</body>
</TAN-T>
Taken from ar.cat.eng.1926.edghill.sem<code>@id</code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.fra.1844.saint-hilaire:semantic-refs" TAN-version="2018">
<head>
.........
</head>
<body xml:lang="fra">
.........
</body>
</TAN-T>
Taken from ar.cat.fra.1844.saint-hilaire.sem-native<code>@id</code><TAN-T TAN-version="2018" 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.sem<code>@idrefs</code>The attribute idrefs contains references to one or more values of @xml:id or @id in the file Formal DefinitionDefined at:
TAN-core.rngUsed by: ~defn-aliasAn <alias> may not mix idrefs from different elements.<alias> references must not be circular.<code>@idrefs</code> <head>
.........
<definitions>
.........
<work xml:id="αc" which="Explanationes de commentario graeco Ammonii"/>
<alias xml:id="αd" idrefs="α αc"/>
<work xml:id="φ" which="Lemmata de commentario graeco Ioannis Philoponi"/>
<work xml:id="φc" which="Explanationes de commentario graeco Ioannis Philoponi"/>
<alias xml:id="φd" idrefs="φ φc"/>
<work xml:id="ο" which="Lemmata de commentario graeco Olympiodori"/>
<work xml:id="οc" which="Explanationes de commentario graeco Olympiodori"/>
<alias xml:id="οd" idrefs="ο οc"/>
<work xml:id="η" which="Lemmata de commentario graeco Eliae"/>
<work xml:id="ηc" which="Explanationes de commentario graeco Eliae"/>
<alias xml:id="ηd" idrefs="η ηc"/>
<work xml:id="σ" which="Lemmata de commentario graeco Simplicii"/>
.........
</definitions>
.........
</head>
Taken from ar.cat.tan-a-div.claims<code>@in-progress</code>The attribute in-progress specifies whether or not the editors of the current file have not yet finished supplying the data, intend to make important changes, or otherwise wish to reserve the right to make major changes. This attribute does not claim that the data is perfect or that it will not be changed. Rather, it signals to users, especially those who would use the file the object of a <source>, <see-also>, or <inclusion>, the possibility of major work that may render dependent data as wrong or invalid. Formal Definitionboolean Defined at:
TAN-core.rngUsed by: ~TAN-bodyAny TAN file marked as being no longer in progress should have at least one master-location.<code>@in-progress</code><TAN-T TAN-version="2018" id="tag:hans@beispiel.com,2014:ringel">
<head>
.........
</head>
<body xml:lang="deu" in-progress="false">
<div type="Gedicht" n="1">
.........
</div>
</body>
</TAN-T>
Taken from ring-o-roses.deu.1897<code>@in-progress</code><TAN-T TAN-version="2018" id="tag:parkj@textalign.net,2015:ring01">
<head>
.........
</head>
<body xml:lang="eng" in-progress="false">
<div type="line" n="1">Ring-a-ring-a-roses,</div>
<div type="line" n="2">A pocket full of posies;</div>
<div type="line" n="3">Hush! Hush! Hush! Hush!</div>
.........
</body>
</TAN-T>
Taken from ring-o-roses.eng.1881<code>@in-progress</code> <text>
<body xml:lang="eng" in-progress="false">
<div type="l" n="1" part="N" org="uniform" sample="complete">
.........
</div>
<div type="l" n="2" part="N" org="uniform" sample="complete">
.........
</div>
<div type="l" n="3" part="N" org="uniform" sample="complete">
.........
</div>
.........
</body>
</text>
Taken from ring-o-roses.eng.1957<code>@in-progress</code><TAN-T TAN-version="2018" id="tag:parkj@textalign.net,2015:ring02">
<head>
.........
</head>
<body xml:lang="eng" in-progress="false">
<div type="l" n="1">Ring-a-round the rosie,</div>
<div type="l" n="2">A pocket full of posies,</div>
<div type="l" n="3">Ashes! Ashes!</div>
.........
</body>
</TAN-T>
Taken from ring-o-roses.eng.1987<code>@include</code>The attribute include signals that the parent element is to be replaced by all elements of the same name found in the referred <inclusion>.Formal DefinitionDefined at:
TAN-core.rngUsed by: ~inclusionEvery idref in an attribute must point to the @xml:id value of the appropriate corresponding element.All idrefs in an attribute must be unique.For any element with @include, at least one element of the same name must be found in target inclusion document.Inclusions may not be circular.Inclusions are integral parts of any TAN file. Access to at least one copy is absolutely mandatory.A work element may invoke no more than one inclusion.<code>@include</code><TAN-A-lm TAN-version="2018" 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>
.........
<definitions>
.........
<group-type xml:id="status" which="status"/>
<person include="rel"/>
<person xml:id="stylesheet">
.........
</person>
.........
</definitions>
<alter>
</alter>
<resp include="rel"/>
<resp roles="editor" who="stylesheet"/>
.........
</head>
.........
</TAN-A-lm>
Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-LM-sample<code>@lexicon</code>The attribute lexicon points to one or more <lexicon> or <agent> IDsThis attribute is inheritable. See Formal DefinitionDefined at:
TAN-A-lm.rngUsed by: ~body-attributes-non-core, ~lexemeEvery idref in an attribute must point to the @xml:id value of the appropriate corresponding element.All idrefs in an attribute must be unique.<code>@lexicon</code><TAN-A-lm TAN-version="2018" 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">
<ana>
.........
</ana>
<ana>
.........
</ana>
<ana>
.........
</ana>
.........
</body>
</TAN-A-lm>
Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-LM-sample<code>@lexicon</code><TAN-A-lm TAN-version="2018" id="tag:parkj@textalign.net,2015:ring01-lm">
<head>
.........
</head>
<body lexicon="english" morphology="penn" in-progress="false">
<ana>
.........
</ana>
<ana>
.........
</ana>
<ana>
.........
</ana>
.........
</body>
</TAN-A-lm>
Taken from ring-o-roses.eng.1881.lm<code>@licensor</code>The attribute licensor specifies one or more <agent>s 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).Nothing should be inferred from a missing @licensor from <rights-source-only>. Its absence does not mean that the rightsholder is unknown or nonexistent. For more, see Formal DefinitionDefined at:
TAN-core.rng<code>@m-has-features</code>The attribute m-has-features specifies one or more features 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 test is one of four tests for determining the truth value that will trigger the message in a <report> or <assert>Formal Definitionstring (pattern [^\s\+]+(\s(\+\s)?[^\s\+]+)*)Defined at:
TAN-mor.rngUsed by: ~action-condition-attributes<code>@m-has-features</code><TAN-mor TAN-version="2018" id="tag:kalvesmaki.com,2014:tan-r-mor:eng:penn">
.........
<body>
.........
<rule m-matches=".+">
.........
</rule>
<rule m-has-features="$">
<assert tok-matches="$">Only $ may be tagged as a dollar sign.</assert>
</rule>
<rule m-has-features="'' . ; :">
<report tok-matches="\w">Nothing marked as punctuation should have word
characters.</report>
</rule>
</body>
</TAN-mor>
Taken from eng.kalvesmaki.com,2014.2<code>@m-has-how-many-features</code>The attribute m-has-how-many-features 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 number of features will be substituted. This test is useful for non-category based languages to put a limit on the number of features that can be declared in an <m>. It is one of four tests for determining the truth value that will determine whether a <report> or <assert> will be acted upon. Formal Definitionstring (pattern ((last|max|all|\*)|((last|max)-\d+)|(\d+))(\s*-\s*(((last|max))|((last|max)-\d+)|(\d+)))?(\s*[, ]\s*(((last|max))|((last|max)-\d+)|(\d+))(\s+-\s+(((last|max))|((last|max)-\d+)|(\d+)))?)*|.*\?\?\?.*)Defined at:
TAN-mor.rngUsed by: ~action-condition-attributes<code>@m-has-how-many-features</code> <rule m-matches=".+">
<assert m-has-how-many-features="1">Features may not be combined.</assert>
</rule>
Taken from eng.kalvesmaki.com,2014.2<code>@m-matches</code>The attribute m-matches takes a regular expression. If an <m> matches the pattern, then the condition will be true. One of four tests for determining the truth value that will trigger the message in a <report> or <assert>Formal DefinitionDefined at:
TAN-mor.rngUsed by: ~action-condition-attributes<code>@m-matches</code> <body>
<for-lang>eng</for-lang>
<rule m-matches=".+">
<assert m-has-how-many-features="1">Features may not be combined.</assert>
</rule>
<rule m-has-features="$">
.........
</rule>
.........
</body>
Taken from eng.kalvesmaki.com,2014.2<code>@morphology</code>The attribute morphology points to one or more <morphology> IDsThis attribute is inheritable. See Formal DefinitionDefined at:
TAN-A-lm.rngUsed by: ~body-attributes-non-core, ~morphEvery idref in an attribute must point to the @xml:id value of the appropriate corresponding element.All idrefs in an attribute must be unique.<code>@morphology</code><TAN-A-lm TAN-version="2018" 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">
<ana>
.........
</ana>
<ana>
.........
</ana>
<ana>
.........
</ana>
.........
</body>
</TAN-A-lm>
Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-LM-sample<code>@morphology</code><TAN-A-lm TAN-version="2018" id="tag:parkj@textalign.net,2015:ring01-lm">
<head>
.........
</head>
<body lexicon="english" morphology="penn" in-progress="false">
<ana>
.........
</ana>
<ana>
.........
</ana>
<ana>
.........
</ana>
.........
</body>
</TAN-A-lm>
Taken from ring-o-roses.eng.1881.lm<code>@n</code>The attribute n names a <div> or <group>. If @n is to be given more than one value, those items must be separated by a space, a comma, or some other non-word character except the hyphen. A hyphen may be used between numbers to specify a range. This feature is useful for cases where a <div> straddles reference markers (e.g., a translation of Aristotle that cannot be easily tied to Bekker numbers).Formal DefinitionDefined at:
TAN-core.rngUsed by: ~text-div, ~alt-skip, ~simple-rename, ~complex-rename, ~alt-equate, ~group-attributesLeaf div references must be unique.An @n taking digit values should not begin with 0.@n suffices for labeling text in a <div>; the @n's value should not appear in the text.concatenated @n's suffice for labeling text in a <div>; the <div>'s reference should not appear in the text.At least one instance of an @n value should be found in each source.<code>@n</code> <body xml:lang="eng">
<div type="p" n="1">
<div type="c" n="a">
<div type="l" n="1">Things are said to be named 'equivocally' when, though they have a common name, the definition corresponding</div>
<div type="l" n="2">with the name differs for each. Thus, a real man and a figure in a picture can both</div>
<div type="l" n="3">lay claim to the name 'animal'; yet these are equivocally so named, for, though they have</div>
.........
</div>
<div type="c" n="b">
.........
</div>
</div>
<div type="p" n="2">
.........
</div>
.........
</body>
Taken from ar.cat.eng.1926.edghill.obj<code>@new</code>The attribute new provides the new name for an @n or reference that is to be renamedThe attribute new provides the new ref for a <div> that is to be renamedFormal Definitionstring (pattern (\w+([^\w\-]\w+)*)|.*\?\?\?.*)Defined at:
TAN-class-2.rngUsed by: ~simple-rename, ~complex-renameIn a <rename>, the number of values in @ref and @new must be identical.@new may not take the same value as what it replaces.No alter action should result in the mixing of leaf <div>s and non-leaf <div>s.<code>@new</code> <head>
.........
<alter src="fra">
<skip div-type="sec"/>
<rename ref="1 1-3" new="1 1 1-3"/>
<rename ref="3 1-3" new="3 1 1-3"/>
<rename ref="4 1-3" new="4 1 1-3"/>
<rename ref="5 1-4" new="5 1 1-4"/>
<rename ref="5 7-9" new="5 2 3-5"/>
.........
</alter>
.........
</head>
Taken from ar.cat.tan-a-div<code>@object</code>The attribute object takes one or more ID refs of entities defined in <head> 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 the object would have the ID ref for work B. If you wish to make more complex assertions, use <object>. Multiple values of @object are interpreted to mean "and", resulting in distribution of the claim (e.g., object="x y" becomes "[subject] [verb] x" and "[subject] [verb] y...").In RDF, the concept of object (the third element of a triple) is required. In TAN-c, it is not required, since some <verb>s may be intransitive (e.g., "Charlie slept.").Formal DefinitionDefined at:
TAN-A-div.rngUsed by: ~body-content-non-class-2, ~claim, ~object<code>@object</code> <body claimant="park">
<claim verb="is-about" object="predication">
<subject work="grc" ref="1 1"/>
</claim>
</body>
Taken from ar.cat.tan-a-div<code>@object-datatype</code>The attribute object-datatype specifies the type of data that the object must take. This attribute is intended to specify that a particular verb governs raw units, not entities definable by the IRI + name pattern. Use this attribute if and only if the verb may not govern objects defined in <definitions>.Formal Definitionstring (pattern string|boolean|decimal|float|double|duration|dateTime|time|date|gYearMonth|gYear|gMonthDay|gDay|gMonth|hexBinary|base64Binary|anyURI|QName|normalizedString|token|language|NMTOKEN|NMTOKENS|Name|NCName|ID|IDREF|IDREFS|ENTITY|ENTITIES|integer|nonPositiveInteger|negativeInteger|long|int|short|byte|nonNegativeInteger|unsignedLong|unsignedInt|unsignedShort|unsignedByte|positiveInteger)Defined at:
TAN-A-div.rngUsed by: ~object-constraintClaims involving verbs whose object is constrained must use <object>, not @object.Verbs that have object constraints must not be combined with other verbs in @verb.<object>s taking strings must match the predefined @object-datatype for the verb.<code>@object-datatype</code> <definitions>
.........
<verb xml:id="agrees" which="agrees"/>
<verb xml:id="replaces" which="replaces" object-datatype="string"/>
<verb xml:id="quotes" which="quotes"/>
.........
</definitions>
Taken from ar.cat.tan-a-div.claims<code>@object-lexical-constraint</code>The attribute object-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". If you wish to constrain the entire value, be sure to use ^ and $, e.g., "^\d+$". Formal DefinitionDefined at:
TAN-A-div.rngUsed by: ~object-constraintClaims involving verbs whose object is constrained must use <object>, not @object.Verbs that have object constraints must not be combined with other verbs in @verb.<object>s taking strings for verbs that have lexical constraints must match those lexical constraints.<code>@pattern</code>The attribute pattern specifies a regular expression pattern to be searched for or matched. TAN regular expressions include an extended syntax, most noted by the special escape character \k{}. For more see and https://www.w3.org/TR/xpath-functions-30/#regex-syntaxFormal DefinitionDefined at:
TAN-core.rngUsed by: ~func-replace, ~defn-tok-def<code>@pattern</code> <definitions>
<comment when="2016-02-22-05:00" who="park">The following token definition treats the
following as words: sequences of letters, any individual character that is neither a
letter nor a space (i.e., punctuation).</comment>
<token-definition src="eng-us" pattern="[-\w]+"/>
<person xml:id="park">
.........
</person>
.........
</definitions>
Taken from ringoroses.div.1<code>@pattern</code> <definitions>
<token-definition pattern="[\w]+"/>
<lexicon xml:id="LSJ">
.........
</lexicon>
.........
</definitions>
Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-LM-sample<code>@pattern</code> <definitions>
.........
<comment when="2016-02-22-05:00" who="park">The following is equivalent to @which = 'letters'</comment>
<token-definition src="eng ger" pattern="\w+"/>
<person xml:id="park">
.........
</person>
.........
</definitions>
Taken from ringoroses.01+03.token.1<code>@pattern</code> <item>
<token-definition pattern="[\w]+"/>
<name>letters</name>
.........
</item>
Taken from token-definitions.TAN-key<code>@period</code>The attribute period names one or more <period>s.Formal DefinitionDefined at:
TAN-core.rngUsed by: ~claim, ~resp-item<code>@pos</code>The attribute pos lists one items, specified through Arabic numerals and the keyword 'last' or 'last-X' (where X is a valid number).Examples: '1', 'last', 'last-3 - last-1'For more see The attribute pos lists one or more items, specified through Arabic numerals and the keyword '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 Formal Definitionstring (pattern ((last|max)|((last|max)-\d+)|(\d+))|.*\?\?\?.*)string (pattern ((last|max|all|\*)|((last|max)-\d+)|(\d+))(\s*-\s*(((last|max))|((last|max)-\d+)|(\d+)))?(\s*[, ]\s*(((last|max))|((last|max)-\d+)|(\d+))(\s+-\s+(((last|max))|((last|max)-\d+)|(\d+)))?)*|.*\?\?\?.*)Defined at:
TAN-class-2.rngUsed by: ~tok-single-selector-attributes, ~tok-mult-selector-attributesSequences 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.<tok> must reference a leaf <div>.Ranges consist of exactly two values separated by a hyphen.<code>@pos</code><TAN-A-div TAN-version="2018" id="tag:parkj@textalign.net,2015:ar.cat.tan-a-div:claims">
.........
<body claimant="lmp">
.........
<claim subject="dexippus porphyry">
<claim subject="andronicus boethus" adverb="perhaps" verb="omits">
<object src="grc">
<tok ref="1 a 2" pos="3-4"/>
</object>
</claim>
</claim>
<claim subject="herminus comm-omnes" verb="agrees">
<locus src="grc">
<tok ref="1 a 2" pos="3-4"/>
</locus>
</claim>
.........
<claim subject="B" verb="replaces">
<locus src="grc">
<tok ref="1 a 5" pos="1-2"/>
</locus>
.........
</claim>
<claim subject="Λ" adverb="perhaps" verb="replaces">
<locus src="grc">
<tok ref="1 a 5" pos="1-2"/>
</locus>
.........
</claim>
<claim subject="π α φ ο" verb="agrees">
<locus src="grc">
<tok ref="1 a 5" pos="1-2"/>
</locus>
</claim>
.........
</body>
</TAN-A-div>
Taken from ar.cat.tan-a-div.claims<code>@ref</code>The attribute ref lists references to one or more <div>s. It consists of one or more simple references joined by commas or hyphens. A simple reference is a string value that points to a single <div>, 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. Other examples: '2.4 - 7, 9', 'iv 7 - 9'In a range with members of uneven depth, those <div>s that are closest to the shallowest member are retrieved. For example, 2 - 3 2 2 might fetch 2, 3 1, 3 2 1, 3 2 2 (and not 3 or 3 1 1).For more, see Formal Definitionstring (pattern (\w+([^\w\-]\w+)*)(((\s*-\s*)|(\s*,\s+))(\w+([^\w\-]\w+)*))*|.*\?\?\?.*)string (pattern (\w+([^\w\-]\w+)*)|.*\?\?\?.*)Defined at:
TAN-class-2.rngUsed by: ~simple-textual-reference, ~alt-skip, ~simple-rename, ~complex-rename, ~target-div-ref, ~div-ref-range, ~tok-ref-item, ~tok-ref-rangeEvery part of a @ref must correspond to a <div> in every source.If a reference to a work is not found in some sources, a warning will be returned.Ranges consist of exactly two values separated by a hyphen.When renaming references, ranges must be predictably calculated.In a <rename>, the number of values in @ref and @new must be identical.<code>@ref</code><TAN-A-div TAN-version="2018" id="tag:parkj@textalign.net,2015:ar.cat.tan-a-div:claims">
.........
<body claimant="lmp">
.........
<claim subject="dexippus porphyry">
<claim subject="andronicus boethus" adverb="perhaps" verb="omits">
<object src="grc">
<tok ref="1 a 2" pos="3-4"/>
</object>
</claim>
</claim>
<claim subject="herminus comm-omnes" verb="agrees">
<locus src="grc">
<tok ref="1 a 2" pos="3-4"/>
</locus>
</claim>
.........
<claim subject="B" verb="replaces">
<locus src="grc">
<tok ref="1 a 5" pos="1-2"/>
</locus>
.........
</claim>
<claim subject="Λ" adverb="perhaps" verb="replaces">
<locus src="grc">
<tok ref="1 a 5" pos="1-2"/>
</locus>
.........
</claim>
<claim subject="π α φ ο" verb="agrees">
<locus src="grc">
<tok ref="1 a 5" pos="1-2"/>
</locus>
</claim>
.........
</body>
</TAN-A-div>
Taken from ar.cat.tan-a-div.claims<code>@relationship</code>The attribute relationship names one or more <relationship>sFormal DefinitionDefined at:
TAN-core.rngUsed by: ~see-also-item<code>@relationship</code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:model-object-refs" TAN-version="2018">
<head>
.........
<source>
.........
</source>
<see-also relationship="ade">
<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.sem.xml" when-accessed="2016-07-07T16:36:28.867-04:00"/>
</see-also>
<see-also relationship="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-obj.xml" when-accessed="2016-07-07T16:36:28.867-04:00"/>
</see-also>
<definitions>
.........
</definitions>
.........
</head>
.........
</TAN-T>
Taken from ar.cat.eng.1926.edghill.obj<code>@relationship</code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2018">
<head>
.........
<source>
.........
</source>
<see-also relationship="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-sem.xml" when-accessed="2016-02-10T14:08:52.058-05:00"/>
</see-also>
<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-obj.xml" when-accessed="2016-02-11T12:40:42.823-05:00"/>
</see-also>
<see-also relationship="ade">
.........
</see-also>
.........
</head>
.........
</TAN-T>
Taken from ar.cat.eng.1926.edghill.sem<code>@replacement</code>The attribute replacement contains a string used to replace any occurrence of <pattern>Formal DefinitionDefined at:
TAN-class-1.rngUsed by: <replace><code>@reuse-type</code>The attribute reuse-type points to one or more <reuse-type>@xml:id values that qualify the type of textual reuse that holds. Multiple values assume inclusive or (A or B or A and B)This attribute is inheritable. See Formal DefinitionDefined at:
TAN-A-tok.rngUsed by: ~body-attributes-non-core, ~alignment-attributes-non-class-2Every idref in an attribute must point to the @xml:id value of the appropriate corresponding element.All idrefs in an attribute must be unique.<code>@reuse-type</code><TAN-A-tok TAN-version="2018" id="tag:parkj@textalign.net,2015:TAN-A-tok,ring01+ring02">
<head>
.........
</head>
<body bitext-relation="B-descends-from-A" reuse-type="adaptation" in-progress="false">
<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="2018" id="tag:parkj@textalign.net,2015:TAN-A-tok,ring01+ring03">
<head>
.........
</head>
<body reuse-type="correlationGeneral" bitext-relation="unclear">
<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="2018" id="tag:parkj@textalign.net,2015:TAN-A-tok,ring01+ring03:alt">
<head>
.........
</head>
<body reuse-type="correlationGeneral" bitext-relation="unclear">
<align>
.........
</align>
<align>
.........
</align>
<align>
.........
</align>
.........
</body>
</TAN-A-tok>
Taken from ringoroses.01+03.token.2<code>@roles</code>The attribute roles refers to the ID of one or more <role>sFormal DefinitionDefined at:
TAN-core.rngUsed by: ~resp-itemEvery idref in an attribute must point to the @xml:id value of the appropriate corresponding element.All idrefs in an attribute must be unique.<code>@roles</code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:model-object-refs" TAN-version="2018">
<head>
.........
<alter>
.........
</alter>
<resp roles="editor" who="kalvesmaki"/>
<resp who="xslt1" roles="stylesheet1"/>
<change when="2016-07-07T16:36:28.867-04:00" who="kalvesmaki">Reformatted file at
ar.cat.eng.1926.edghill.sem.xml to the structure of the copy of the model.</change>
.........
</head>
.........
</TAN-T>
Taken from ar.cat.eng.1926.edghill.obj<code>@roles</code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2018">
<head>
.........
<alter>
.........
</alter>
<resp roles="editor" who="kalvesmaki"/>
<resp who="xslt1" roles="stylesheet1"/>
<change when="2016-06-22T08:04:25.003-04:00" who="kalvesmaki">Reformatted according to first
model found. Backup made at
file:/C:/Users/jdkalv/Dropbox/TAN/library/TAN-2018/examples/ar.cat.eng.1926.edghill.sem-201606220804250030400.xml.</change>
.........
</head>
.........
</TAN-T>
Taken from ar.cat.eng.1926.edghill.sem<code>@root</code>Formal DefinitionNCName Defined at:
catalog.tan.rngUsed by: <doc>@root should match the target's root element name<code>@root</code><collection stable="true">
<doc href="ar.cat.eng.1926.edghill.obj.xml" id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:model-object-refs" root="TAN-T"/>
<doc href="ar.cat.eng.1926.edghill.sem.xml" id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" root="TAN-T"/>
<doc href="ar.cat.fra.1844.saint-hilaire.sem-native.xml" id="tag:kalvesmaki.com,2014:tan-t:ar.cat.fra.1844.saint-hilaire:semantic-refs" root="TAN-T"/>
<doc href="ar.cat.fra.1844.saint-hilaire.sem.xml" id="tag:kalvesmaki.com,2014:tan-t:ar.cat.fra.1844.saint-hilaire:semantic-refs-realigned" root="TAN-T"/>
<doc href="ar.cat.grc.1949.minio-paluello-obj.xml" id="tag:kalvesmaki.com,2014:tan-t:ar.cat.grc.1949.minio-paluello:object-refs" root="TAN-T"/>
.........
</collection>
Taken from catalog.tan<code>@shallow</code>The attribute shallow indicates whether skipping should be done shallowly (default) or deeplyFormal Definitionboolean Defined at:
TAN-class-2.rngUsed by: ~alt-skip<code>@src</code>The attribute src refers to the ID of one or more <source>s The attribute src refers to the ID of only one <source>Formal DefinitionNCName Defined at:
TAN-class-2.rngUsed by: ~simple-textual-reference, ~complex-textual-reference-set, ~action-condition-attributes, ~tok-sources-ref-opt, ~defn-tok-defEvery idref in an attribute must point to the @xml:id value of the appropriate corresponding element.All idrefs in an attribute must be unique.Every part of a @ref must correspond to a <div> in every source.<code>@src</code><TAN-A-div TAN-version="2018" id="tag:parkj@textalign.net,2015:ar.cat.tan-a-div:claims">
.........
<body claimant="lmp">
.........
<claim subject="dexippus porphyry">
<claim subject="andronicus boethus" adverb="perhaps" verb="omits">
<object src="grc">
<tok ref="1 a 2" pos="3-4"/>
</object>
</claim>
</claim>
<claim subject="herminus comm-omnes" verb="agrees">
<locus src="grc">
<tok ref="1 a 2" pos="3-4"/>
</locus>
</claim>
.........
<claim subject="B" verb="replaces">
<locus src="grc">
<tok ref="1 a 5" pos="1-2"/>
</locus>
<object>τις ἀποδιδῷ</object>
</claim>
<claim subject="Λ" adverb="perhaps" verb="replaces">
<locus src="grc">
<tok ref="1 a 5" pos="1-2"/>
</locus>
<object>τις ἀποδιδῷ</object>
</claim>
<claim subject="π α φ ο" verb="agrees">
<locus src="grc">
<tok ref="1 a 5" pos="1-2"/>
</locus>
</claim>
.........
</body>
</TAN-A-div>
Taken from ar.cat.tan-a-div.claims<code>@stable</code>Formal Definitionboolean Defined at:
catalog.tan.rngUsed by: <collection><code>@stable</code><collection stable="true">
<doc href="ar.cat.eng.1926.edghill.obj.xml" id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:model-object-refs" root="TAN-T"/>
<doc href="ar.cat.eng.1926.edghill.sem.xml" id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" root="TAN-T"/>
<doc href="ar.cat.fra.1844.saint-hilaire.sem-native.xml" id="tag:kalvesmaki.com,2014:tan-t:ar.cat.fra.1844.saint-hilaire:semantic-refs" root="TAN-T"/>
.........
</collection>
Taken from catalog.tan<code>@stable</code><collection stable="true">
<doc href="bitext-relations.TAN-key.xml"/>
<doc href="collection.xml"/>
<doc href="div-types.TAN-key.xml"/>
.........
</collection>
Taken from collection<code>@subject</code>The attribute subject points to one or more ID refs of entities defined in <head> that serve as the grammatical subject of a claim. @subject within <body> indicates the default subject(s) for <claim>s. Multiple values of @subject are interpreted to mean "and", resulting in distribution of the claim (e.g., subject="x y" becomes "x [verby]..." and "y [verb]...").Formal DefinitionDefined at:
TAN-A-div.rngUsed by: ~body-content-non-class-2, ~claim, ~subjectEvery <claim> must have at least one subject, either @subject (self or ancestral <body>) or a child <subject><code>@TAN-version</code>The attribute TAN-version specifies the version of TAN schemas used. Formal Definitionstring Defined at:
TAN-core.rngUsed by: ~TAN-rootFiles that point to older versions of TAN rules will be pointed to conversion stylesheets.<code>@TAN-version</code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:model-object-refs" TAN-version="2018">
<head>
.........
</head>
<body xml:lang="eng">
.........
</body>
</TAN-T>
Taken from ar.cat.eng.1926.edghill.obj<code>@TAN-version</code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2018">
<head>
.........
</head>
<body xml:lang="eng">
.........
</body>
</TAN-T>
Taken from ar.cat.eng.1926.edghill.sem<code>@TAN-version</code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.fra.1844.saint-hilaire:semantic-refs" TAN-version="2018">
<head>
.........
</head>
<body xml:lang="fra">
.........
</body>
</TAN-T>
Taken from ar.cat.fra.1844.saint-hilaire.sem-native<code>@TAN-version</code><TAN-T TAN-version="2018" 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.sem<code>@to</code>The attribute to specifies the end of a period of timeFormal Definition(
dateTime
date )Defined at:
TAN-core.rngUsed by: <period>Date attributes must be castable either as xs:dateTime or xs:dateFuture dates are not permitted.@from must predate @to<code>@tok-matches</code>The attribute tok-matches takes a regular expression. When validating a given <m>, a test will be made against each companion <tok> (i.e., those <tok>s that have the same ancestral <ana>). The condition will be treated as true only if there is a match with the resolved value of every such <tok>, and false if there is any nonmatch. One of four tests for determining the truth value that will trigger the message in a <report> or <assert>Formal DefinitionDefined at:
TAN-mor.rngUsed by: ~action-condition-attributes<code>@tok-matches</code><TAN-mor TAN-version="2018" id="tag:kalvesmaki.com,2014:tan-r-mor:eng:penn">
.........
<body>
.........
<rule m-has-features="$">
<assert tok-matches="$">Only $ may be tagged as a dollar sign.</assert>
</rule>
<rule m-has-features="'' . ; :">
<report tok-matches="\w">Nothing marked as punctuation should have word
characters.</report>
</rule>
</body>
</TAN-mor>
Taken from eng.kalvesmaki.com,2014.2<code>@type</code>The attribute type indicates what type of its parent element. In the context of <div> it specifies a type of textual unit, defined by a <div-type>. In the context of <group> it specifies a kind of group defined by a <group-type>.Formal DefinitionDefined at:
TAN-core.rngUsed by: ~group-attributes, ~category, ~feature-ref, ~text-div<code>@type</code> <body xml:lang="eng">
<div type="p" n="1">
<div type="c" n="a">
<div type="l" n="1">Things are said to be named 'equivocally' when, though they have a common name, the definition corresponding</div>
<div type="l" n="2">with the name differs for each. Thus, a real man and a figure in a picture can both</div>
<div type="l" n="3">lay claim to the name 'animal'; yet these are equivocally so named, for, though they have</div>
.........
</div>
<div type="c" n="b">
.........
</div>
</div>
<div type="p" n="2">
.........
</div>
.........
</body>
Taken from ar.cat.eng.1926.edghill.obj<code>@units</code>The attribute units points to the ID ref of a <unit>, defining the type of units.Formal DefinitionDefined at:
TAN-A-div.rngUsed by: ~nontextual-reference<code>@val</code>The attribute val specifies a particular word token by means of its string value. Treated as a constrained regular expression (the expression must match the entire token).For more see Formal Definitionstring (pattern .+)Defined at:
TAN-class-2.rngUsed by: ~abstract-tok-ref, ~tok-single-selector-attributes, ~tok-mult-selector-attributesAttributes that take a regular expression 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.<tok> must reference a leaf <div>.<code>@val</code> <head>
.........
<alter src="fra">
.........
<reassign>
<tok ref="5 5">
<from val="Ceci"/>
<to pos="4" val="corps"/>
</tok>
.........
</reassign>
<reassign>
<tok ref="5 5">
<from val="Il"/>
<to val="exister"/>
</tok>
.........
</reassign>
.........
<reassign>
<tok ref="6 23">
<from val="Il"/>
<to val="même" pos="last-1"/>
</tok>
.........
</reassign>
.........
<reassign>
<tok ref="7 17">
<from val="Il"/>
<to pos="last"/>
</tok>
.........
</reassign>
.........
<reassign>
<tok ref="7 26">
<from val="Ceci"/>
<to pos="last"/>
</tok>
.........
</reassign>
.........
<reassign>
<tok ref="8 11">
<from val="Il"/>
<to pos="last"/>
</tok>
.........
</reassign>
.........
<reassign>
<tok ref="11 2">
<from val="Ceci"/>
<to pos="last"/>
</tok>
.........
</reassign>
.........
<reassign>
<tok ref="14 4">
<from val="Il"/>
<to val="autres" pos="2"/>
</tok>
.........
</reassign>
.........
</alter>
.........
</head>
Taken from ar.cat.tan-a-div<code>@verb</code>The attribute verb points to one or more <verb>s that serve to assert something of the @subject.The preferred term "verb" is equivalent to RDF "predicate." The latter term is avoided as being misleading -- most who use TAN will understand "predicate," grammatically speaking, to refer to everything in a sentence that is not the subject. Multiple values of @verb are interpreted to mean "and", resulting in distribution of the claim (e.g., verb="x y" becomes "[subject] x ..." and "[subject] y...").Formal DefinitionDefined at:
TAN-A-div.rngUsed by: ~body-content-non-class-2, ~claimAny predefined strictures on verbs must be respected.Every <claim> must have at least one verb, either @verb (self or ancestral <body>)<code>@verb</code><TAN-A-div TAN-version="2018" id="tag:parkj@textalign.net,2015:ar.cat.tan-a-div:claims">
.........
<body claimant="lmp">
.........
<claim subject="dexippus porphyry">
<claim subject="andronicus boethus" adverb="perhaps" verb="omits">
<object src="grc">
.........
</object>
</claim>
</claim>
<claim subject="herminus comm-omnes" verb="agrees">
<locus src="grc">
.........
</locus>
</claim>
<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 subject="B" verb="replaces">
<locus src="grc">
.........
</locus>
<object>τις ἀποδιδῷ</object>
</claim>
<claim subject="Λ" adverb="perhaps" verb="replaces">
<locus src="grc">
.........
</locus>
<object>τις ἀποδιδῷ</object>
</claim>
<claim subject="π α φ ο" verb="agrees">
.........
</claim>
.........
</body>
</TAN-A-div>
Taken from ar.cat.tan-a-div.claims<code>@when</code>The attribute when indicates a date or date and timeFormal Definition(
dateTime
date )Defined at:
TAN-core.rngUsed by: ~comment, ~change-logDate attributes must be castable either as xs:dateTime or xs:dateFuture dates are not permitted.<code>@when</code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:model-object-refs" TAN-version="2018">
<head>
.........
<resp who="xslt1" roles="stylesheet1"/>
<change when="2016-07-07T16:36:28.867-04:00" who="kalvesmaki">Reformatted file at
ar.cat.eng.1926.edghill.sem.xml to the structure of the copy of the model.</change>
<change who="xslt1" when="2017-11-02T22:27:59.302-04:00">TAN file updated to 2018 schemas.</change>
</head>
.........
</TAN-T>
Taken from ar.cat.eng.1926.edghill.obj<code>@when</code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2018">
<head>
.........
<resp who="xslt1" roles="stylesheet1"/>
<change when="2016-06-22T08:04:25.003-04:00" who="kalvesmaki">Reformatted according to first
model found. Backup made at
file:/C:/Users/jdkalv/Dropbox/TAN/library/TAN-2018/examples/ar.cat.eng.1926.edghill.sem-201606220804250030400.xml.</change>
<change when="2016-01-26-04:00" who="kalvesmaki">Started new file.</change>
<change who="xslt1" when="2017-11-02T22:29:17.742-04:00">TAN file updated to 2018 schemas.</change>
</head>
.........
</TAN-T>
Taken from ar.cat.eng.1926.edghill.sem<code>@when-accessed</code>The attribute when-accessed specifies when an electronic file was last examinedFormal Definition(
date
dateTime )Defined at:
TAN-core.rngUsed by: <location>If @when-accessed predates one or more dates in a target file, a warning will be returned.Date attributes must be castable either as xs:dateTime or xs:dateFuture dates are not permitted.<code>@when-accessed</code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:model-object-refs" TAN-version="2018">
<head>
.........
<see-also relationship="ade">
.........
<name>Categories, Aristotle, English translation by E. M. Edghill</name>
<location href="ar.cat.eng.1926.edghill.sem.xml" when-accessed="2016-07-07T16:36:28.867-04:00"/>
</see-also>
<see-also relationship="model">
.........
<name>Categories, Aristotle, Greek text by Minio-Paluello</name>
<location href="ar.cat.grc.1949.minio-paluello-obj.xml" when-accessed="2016-07-07T16:36:28.867-04:00"/>
</see-also>
.........
</head>
.........
</TAN-T>
Taken from ar.cat.eng.1926.edghill.obj<code>@when-accessed</code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2018">
<head>
.........
<see-also relationship="model">
.........
<name>Categories, Aristotle, Greek text by Minio-Paluello</name>
<location href="ar.cat.grc.1949.minio-paluello-sem.xml" when-accessed="2016-02-10T14:08:52.058-05:00"/>
</see-also>
<see-also relationship="alt">
.........
<name>Categories, Aristotle, Greek text by Minio-Paluello</name>
<location href="ar.cat.grc.1949.minio-paluello-obj.xml" when-accessed="2016-02-11T12:40:42.823-05:00"/>
</see-also>
.........
</head>
.........
</TAN-T>
Taken from ar.cat.eng.1926.edghill.sem<code>@where</code>The attribute where restricts the <claim> to a specific <place>.
Multiple values of @where are interpreted to mean "or" with union. No distribution takes place (e.g., where="x y" means "[subject] x or y [verby]...", not "[subject] x [verb]..." and "[subject] y [verb]...").Formal DefinitionDefined at:
TAN-A-div.rngUsed by: ~claim<code>@which</code>The attribute which used to point to a reserved keyword, either a reserved tokenization pattern or a relationship.Formal DefinitionDefined at:
TAN-core.rngUsed by: ~defn-morph, ~entity-digital-generic-ref, ~entity-nondigital-ref, ~metadata-human, ~defn-tok-defAn element's @which must have a value that corresponds to a <name>, either in the core TAN keyword or an associated TAN-key file, that is marked as applying to that element.Keywords (values of @which) must be unique for a given element name.Any element that takes @which must have keywords defined for that element.Keys are integral parts of a document. Access to at least one version is absolutely mandatory.<code>@which</code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:model-object-refs" TAN-version="2018">
<head>
.........
<definitions>
.........
<role xml:id="editor">
.........
</role>
<role xml:id="stylesheet1" which="stylesheet"/>
<relationship xml:id="model" which="model"/>
<relationship xml:id="ade" which="alternatively divided edition"/>
</definitions>
<alter>
<normalization which="no hyphens"/>
</alter>
.........
</head>
.........
</TAN-T>
Taken from ar.cat.eng.1926.edghill.obj<code>@who</code>The attribute who names an <agent>Formal DefinitionDefined at:
TAN-core.rngUsed by: ~comment, ~nonsource-license, ~resp-item, ~change-logEvery idref in an attribute must point to the @xml:id value of the appropriate corresponding element.All idrefs in an attribute must be unique.<code>@who</code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:model-object-refs" TAN-version="2018">
<head>
.........
<license>
.........
</license>
<licensor who="kalvesmaki"/>
<source>
.........
</source>
.........
<alter>
.........
</alter>
<resp roles="editor" who="kalvesmaki"/>
<resp who="xslt1" roles="stylesheet1"/>
<change when="2016-07-07T16:36:28.867-04:00" who="kalvesmaki">Reformatted file at
ar.cat.eng.1926.edghill.sem.xml to the structure of the copy of the model.</change>
<change who="xslt1" when="2017-11-02T22:27:59.302-04:00">TAN file updated to 2018 schemas.</change>
</head>
.........
</TAN-T>
Taken from ar.cat.eng.1926.edghill.obj<code>@work</code>The attribute work refers to a work by means of a source ID as a proxy. The attribute will be treated as indicating all sources that share the same work as the one mentioned.If you wish to avoid making a claim applying to all other versions of a work, use @src instead.Formal DefinitionDefined at:
TAN-A-div.rngUsed by: ~simple-textual-reference, ~complex-textual-reference-setIf a reference to a work is not found in some sources, 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-div.claims<code>@work</code> <claim verb="is-about" object="predication">
<subject work="grc" ref="1 1"/>
</claim>
Taken from ar.cat.tan-a-div<code>@xml:id</code>The attribute xml:id identifies an entity described within an element. Must be unique within a given file. Must consist only of word characters.Formal DefinitionDefined at:
TAN-core.rngUsed by: ~defn-id-ref-opt, ~source-id-opt, ~defn-morph, ~defn-lexi, ~alignment-attributes-non-class-2, ~id-option, ~inclusion-item, ~defn-pattern-id, ~defn-alias, ~defn-period, ~defn-relationship@xml:id values may not be repeated in the same document.Id values for features must be case-indifferently unique within a given category.<code>@xml:id</code> <head>
.........
<definitions>
<work>
.........
</work>
<div-type xml:id="p">
<IRI>http://dbpedia.org/resource/Page_(paper)</IRI>
<name>page</name>
</div-type>
<div-type xml:id="c">
<IRI>http://dbpedia.org/resource/Column_(typography)</IRI>
<name>column</name>
</div-type>
<div-type xml:id="l">
<IRI>tag:textalign.net,2015:div-type:line:physical</IRI>
<name>physical line</name>
</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>
.........
</definitions>
.........
</head>
Taken from ar.cat.eng.1926.edghill.obj<code>@xml:lang</code>The attribute xml:lang specifies a language code that names the language of the text enclosed by the parent element. Values are inherited by all descendants except for those that have an @xml:lang and their descendants. Values should adhere to BCP (Best Common Practices) 47, http://www.rfc-editor.org/rfc/bcp/bcp47.txt. For more details see .Examples: 'eng' (English), 'grc' (classical Greek), 'lat' (Latin) Formal Definitionlanguage Defined at:
TAN-core.rngUsed by: ~nontextual-reference, ~body-attributes-non-core, ~text-div, ~metadata-desc<code>@xml:lang</code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:model-object-refs" TAN-version="2018">
<head>
.........
<definitions>
.........
<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>
.........
</definitions>
.........
</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.obj<code>@xml:lang</code> <div-type xml:id="par">
<IRI>http://dbpedia.org/resource/Paragraph</IRI>
<name xml:lang="eng">paragraph</name>
</div-type>
Taken from ar.cat.eng.1926.edghill.sem<code><algorithm></code>The element algorithm contains an IRI + name pattern identifying an algorithm.Algorithm covers any set of computational instructions. It does not include the hardware or software used to run the algorithm. For example, a set of XSLT styleshteets is an algorithm, but the engine (e.g., Saxon) or software (e.g., oXygen) is not. Formal Definition~defn-pattern-idDefined at:
TAN-core.rngUsed by: ~defn-agent<code><algorithm></code> <definitions>
.........
<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-div file from collections.</name>
<desc>Stylesheet at: ../do%20things/convert/convert%20TAN%202017%20to%20TAN%202018.xsl</desc>
</algorithm>
<role xml:id="editor">
.........
</role>
.........
</definitions>
Taken from ar.cat.eng.1926.edghill.obj<code><algorithm></code> <definitions>
.........
<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-div file from collections.</name>
<desc>Stylesheet at: ../do%20things/convert/convert%20TAN%202017%20to%20TAN%202018.xsl</desc>
</algorithm>
<role xml:id="editor">
.........
</role>
.........
</definitions>
Taken from ar.cat.eng.1926.edghill.sem<code><algorithm></code> <definitions>
.........
<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-div file from collections.</name>
<desc>Stylesheet at: ../do%20things/convert/convert%20TAN%202017%20to%20TAN%202018.xsl</desc>
</algorithm>
<role xml:id="editor">
.........
</role>
.........
</definitions>
Taken from ar.cat.fra.1844.saint-hilaire.sem-native<code><algorithm></code> <definitions>
.........
<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-div file from collections.</name>
<desc>Stylesheet at: ../do%20things/convert/convert%20TAN%202017%20to%20TAN%202018.xsl</desc>
</algorithm>
<role xml:id="editor">
.........
</role>
.........
</definitions>
Taken from ar.cat.fra.1844.saint-hilaire.sem<code><alias></code>The element alias assigns a group of xml:id values to a single xml:id.This feature is useful for referring repeatedly to a group of agents, works, scripta, etc. Formal Definition~ed-stamp?,
(~inclusion |
((@xml:id | @id), @idrefs))Defined at:
TAN-core.rngUsed by: ~definition-coreAn <alias> may not mix idrefs from different elements.<alias> references must not be circular.<code><alias></code> <head>
.........
<definitions>
.........
<work xml:id="αc" which="Explanationes de commentario graeco Ammonii"/>
<alias xml:id="αd" idrefs="α αc"/>
<work xml:id="φ" which="Lemmata de commentario graeco Ioannis Philoponi"/>
<work xml:id="φc" which="Explanationes de commentario graeco Ioannis Philoponi"/>
<alias xml:id="φd" idrefs="φ φc"/>
<work xml:id="ο" which="Lemmata de commentario graeco Olympiodori"/>
<work xml:id="οc" which="Explanationes de commentario graeco Olympiodori"/>
<alias xml:id="οd" idrefs="ο οc"/>
<work xml:id="η" which="Lemmata de commentario graeco Eliae"/>
<work xml:id="ηc" which="Explanationes de commentario graeco Eliae"/>
<alias xml:id="ηd" idrefs="η ηc"/>
<work xml:id="σ" which="Lemmata de commentario graeco Simplicii"/>
.........
</definitions>
.........
</head>
Taken from ar.cat.tan-a-div.claims<code><align></code>The element align declares one or more groups of words 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. Formal Definition
(~inclusion |
(~alignment-attributes-non-class-2, ~certainty-stamp, @group?, (<comment>* &
(<tok> | <group> | <tok>)+)))Defined at:
TAN-A-tok.rngUsed by: ~body-itemNo <tok> should duplicate any sibling <tok>.<code><align></code><TAN-A-tok TAN-version="2018" id="tag:parkj@textalign.net,2015:TAN-A-tok,ring01+ring02">
.........
<body bitext-relation="B-descends-from-A" reuse-type="adaptation" in-progress="false">
<align>
<tok src="ring1881" ref="1" val="\u{.latin}"/>
<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><alter></code>The element alter declares alterations that have been made, or should be made, to the source(s).Formal Definition~ed-stamp?,
(~inclusion |
(
{[TAN-class-2 (~alter-condition):]
(
{{{{[TAN-mor (~action-condition-attributes):] ~action-condition-attributes}}}} OR
{{{{[TAN-class-2 (~action-condition-attributes):] ~action-condition-attributes}}}} OR
{{{{[TAN-core (~action-condition-attributes):] {empty}}}}} | <where>+)} OR
{[TAN-core (~alter-condition):] {empty}},
(<comment>* & ({empty},
{[TAN-class-1 (~alter-non-core):]
(<normalization>* & <replace>*)} OR
{[TAN-class-2 (~alter-non-core):] ~alter-non-core} OR
{[TAN-class-3 (~alter-non-core):]
({empty} & {empty})} OR
{[TAN-core (~alter-non-core):] {empty}}))))Defined at:
TAN-core.rngUsed by: ~alter-statementNo alter action should result in the mixing of leaf <div>s and non-leaf <div>s.<code><alter></code> <head>
.........
<definitions>
.........
</definitions>
<alter>
<normalization which="no hyphens"/>
</alter>
<resp roles="editor" who="kalvesmaki"/>
.........
</head>
Taken from ar.cat.eng.1926.edghill.obj<code><alter></code> <head>
.........
<definitions>
.........
</definitions>
<alter>
<normalization which="no hyphens"/>
</alter>
<resp roles="editor" who="kalvesmaki"/>
.........
</head>
Taken from ar.cat.eng.1926.edghill.sem<code><alter></code> <head>
.........
<definitions>
.........
</definitions>
<alter>
<normalization which="no hyphens"/>
</alter>
<resp roles="editor" who="kalvesmaki"/>
.........
</head>
Taken from ar.cat.fra.1844.saint-hilaire.sem-native<code><alter></code> <head>
.........
<definitions>
.........
</definitions>
<alter>
<normalization which="no hyphens"/>
</alter>
<resp roles="editor" who="kalvesmaki"/>
.........
</head>
Taken from ar.cat.fra.1844.saint-hilaire.sem<code><ambiguous-letter-numerals-are-roman></code>The element ambiguous-letter-numerals-are-roman specifies whether letters that can be interpreted both as letter numerals and as roman numerals should be interpreted as the latter.E.g., 'c' would be interpreted as 3 if false and 100 if true.If element is not present, the value is assumed to be true.Formal Definitionboolean Defined at:
TAN-core.rngUsed by: ~definition-core<code><ambiguous-letter-numerals-are-roman></code> <definitions>
.........
<role xml:id="Produzent">
.........
</role>
<ambiguous-letter-numerals-are-roman>false</ambiguous-letter-numerals-are-roman>
</definitions>
Taken from ring-o-roses.deu.1897<code><ambiguous-letter-numerals-are-roman></code> <definitions>
<ambiguous-letter-numerals-are-roman>false</ambiguous-letter-numerals-are-roman>
<person xml:id="park">
.........
</person>
.........
</definitions>
Taken from ar.cat.tan-a-div<code><ana></code>The element ana contains a one or more assertions about the lexical or morphological properties of one or more tokens.Claims within an <ana> are distributive. That is, every combination of <l> and <m> within an <lm> is asserted of every <tok>.Formal Definition
((~ed-stamp?, ~inclusion) |
(~certainty-stamp?, @group?,
(<comment>* & (
(
(<tok> | <group> | <tok>) | <tok>)+, <lm>+))))Defined at:
TAN-A-lm.rngUsed by: ~body-itemNo <tok> should duplicate any sibling <tok>.<code><ana></code><TAN-A-lm TAN-version="2018" 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">
<ana>
<tok ref="11 2 1 1" pos="1"/>
<lm>
.........
</lm>
</ana><ana>
<tok ref="10 6 3 2" pos="4"/>
<tok ref="10 6 3 3" pos="15"/>
<tok ref="10 6 4 2" pos="37"/>
.........
</ana><ana>
<tok ref="8 3 5 4" pos="6"/>
<tok ref="8 3 7 3" pos="7"/>
<lm>
.........
</lm>
</ana><ana>
<tok ref="7 1 2 1" pos="12"/>
<tok ref="7 3 1 3" pos="22"/>
<tok ref="7 3 1 3" pos="24"/>
.........
</ana><ana>
.........
</ana>
.........
</body>
</TAN-A-lm>
Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-LM-sample<code><assert></code>The element assert names a pattern that, if found to be false in any <m> in a dependent TAN-A-lm file, will return the enclosed message upon validation of the dependent file, along with an error or warning. Modeled on Schematron <report>.Formal Definition~condition-patternDefined at:
TAN-mor.rngUsed by: ~morphology-rule<code><assert></code><TAN-mor TAN-version="2018" id="tag:kalvesmaki.com,2014:tan-r-mor:eng:penn">
.........
<body>
.........
<rule m-matches=".+">
<assert m-has-how-many-features="1">Features may not be combined.</assert>
</rule>
<rule m-has-features="$">
<assert tok-matches="$">Only $ may be tagged as a dollar sign.</assert>
</rule>
.........
</body>
</TAN-mor>
Taken from eng.kalvesmaki.com,2014.2<code><bitext-relation></code>The element bitext-relation identifies how the text on one text-bearing object relates to that on another by specifying a relationship, e.g., B is a direct copy of A, B and A descent from a commont parent, etc. See for theoretical background.In most cases, there will be need for only one of these elements. 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 main.xml# keywords-bitext-relationFormal Definition~defn-pattern-defaultDefined at:
TAN-A-tok.rngUsed by: ~definition-non-class-2<code><bitext-relation></code> <definitions>
<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>
.........
</definitions>
Taken from ringoroses.01+02.token.1<code><bitext-relation></code> <definitions>
<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>
.........
</definitions>
Taken from ringoroses.01+03.token.1<code><bitext-relation></code> <definitions>
<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>
.........
</definitions>
Taken from ringoroses.01+03.token.2<code><body></code>The element body contains the dataFormal Definition@in-progress?, ~ed-stamp?,
{[TAN-A-lm (~body-attributes-non-core):] ~body-attributes-non-core} OR
{[TAN-A-tok (~body-attributes-non-core):] ~body-attributes-non-core} OR
{[TAN-key (~body-attributes-non-core):] @affects-element?} OR
{[TAN-T (~body-attributes-non-core):] @xml:lang} OR
{[TAN-core (~body-attributes-non-core):] {empty}}, (<comment>* &
{[TAN-class-1 (~body-content-non-core):]
({empty} &
{{[TAN-T (~body-content-non-class-1):]
{{{[TAN-T (~body-item):] <div>}}} OR
{{{[TAN-core (~body-item):] {empty}}}}+}} OR
{{[TAN-class-1 (~body-content-non-class-1):] {empty}}})} OR
{[TAN-class-2 (~body-content-non-core):]
({empty} &
{{[TAN-A-div (~body-content-non-class-2):] ~body-content-non-class-2}} OR
{{[TAN-A-lm (~body-content-non-class-2):] ~body-content-non-class-2}} OR
{{[TAN-A-tok (~body-content-non-class-2):]
(<group>* &
{{{[TAN-A-tok (~body-item):] <align>}}} OR
{{{[TAN-core (~body-item):] {empty}}}}*)}} OR
{{[TAN-class-2 (~body-content-non-class-2):] {empty}}})} OR
{[TAN-class-3 (~body-content-non-core):]
({empty} &
{{[TAN-key (~body-content-non-class-3):]
(<group>* &
{{{[TAN-key (~body-item):] <item>}}} OR
{{{[TAN-core (~body-item):] {empty}}}}*)}} OR
{{[TAN-mor (~body-content-non-class-3):] ~TAN-R-mor-body}} OR
{{[TAN-class-3 (~body-content-non-class-3):] {empty}}})} OR
{[TAN-core (~body-content-non-core):] {empty}})Defined at:
TAN-core.rngUsed by: ~TAN-root<code><body></code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:model-object-refs" TAN-version="2018">
<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.obj<code><body></code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2018">
<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.sem<code><body></code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.fra.1844.saint-hilaire:semantic-refs" TAN-version="2018">
<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.sem-native<code><body></code><TAN-T TAN-version="2018" 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.sem<code><category></code>The element category groups a set of features that share a common grammatical trait such as gender, number, etc.Formal Definition~ed-stamp?,
(~inclusion |
(@type, (<comment>* & <feature>+)))Defined at:
TAN-mor.rngUsed by: ~category-list<code><change></code>The element change declares a change made to the current file. Must credit an <agent>, specified by @who, and a time the change was made, specified by @when.Collectively, <change> elements are called the changelog, the revision history of the document. The editor has discretion as to how long or detailed a <change> should be, or how many should be retained in a changelog. Ideally, <change>s documenting every published version should be retained.<change> elements may appear in any order, but it is good practice to put the most recent at the top.Formal Definition~ed-stamp?, @when, @flags?, @who, textDefined at:
TAN-core.rng<code><change></code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:model-object-refs" TAN-version="2018">
<head>
.........
<resp who="xslt1" roles="stylesheet1"/>
<change when="2016-07-07T16:36:28.867-04:00" who="kalvesmaki">Reformatted file at
ar.cat.eng.1926.edghill.sem.xml to the structure of the copy of the model.</change><change who="xslt1" when="2017-11-02T22:27:59.302-04:00">TAN file updated to 2018 schemas.</change>
</head>
.........
</TAN-T>
Taken from ar.cat.eng.1926.edghill.obj<code><change></code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2018">
<head>
.........
<resp who="xslt1" roles="stylesheet1"/>
<change when="2016-06-22T08:04:25.003-04:00" who="kalvesmaki">Reformatted according to first
model found. Backup made at
file:/C:/Users/jdkalv/Dropbox/TAN/library/TAN-2018/examples/ar.cat.eng.1926.edghill.sem-201606220804250030400.xml.</change><change when="2016-01-26-04:00" who="kalvesmaki">Started new file.</change><change who="xslt1" when="2017-11-02T22:29:17.742-04:00">TAN file updated to 2018 schemas.</change>
</head>
.........
</TAN-T>
Taken from ar.cat.eng.1926.edghill.sem<code><checksum></code>The element checksum specifies some checksum that can be used to confirm the identity of a digital file being referred to. This element contains other elements that define the type and value of the checksum. Must begin with an IRI + name pattern that defines the type of checksum being used (e.g., SHA-1).This element allows later users ensure that a copies of a file are identical. The checksum will not be generated, checked, or validated by TAN schemas. Checksum validation must be provided by other means.Formal Definition
((<IRI>+, ~metadata-human) | @which), <value>Defined at:
TAN-core.rngUsed by: ~entity-digital-tan-other-ref, ~entity-digital-generic-ref<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="confessio_english_temp.xml" when-accessed="2016-09-09"/>
</source>
Taken from patricius.confessio.2003.eng<code><claim></code>The element claim makes one or more claims.Formal Definition
(~inclusion |
(~ed-stamp?,
(@cert | (@cert, @cert2))?, @claimant?, @period?, @adverb?, @verb?, @where?, (
(@subject | <subject>+)? &
(@object |
(<object> | <claim>+)+)? & <locus>+?)))Defined at:
TAN-A-div.rngUsed by: ~body-content-non-class-2, ~complex-objectClaims involving verbs whose object is constrained must use <object>, not @object.Verbs that have object constraints must not be combined with other verbs in @verb.Every <claim> must have at least one subject, either @subject (self or ancestral <body>) or a child <subject>Any predefined strictures on verbs must be respected.Every <claim> must have at least one verb, either @verb (self or ancestral <body>)<code><collection></code>Formal Definition@stable, <doc>+Defined at:
catalog.tan.rng<code><comment></code>The element comment discusses issues relevant to nearby data. Must credit an <agent>, specified by @who, and a time the comment was made, specified by @when.Formal Definition@when, @who, textDefined at:
TAN-core.rngUsed by: ~TAN-A-lm-item, ~alignment, ~category, ~alt-norm, ~func-replace, ~TAN-head, ~nonsource-license, ~inclusion-item, ~key-item, ~source-item, ~see-also-item, ~definition-list, ~alter-element, ~body-content-core, ~defn-pattern-default, ~defn-pattern-id, ~defn-pattern-no-id, ~defn-pattern-language<code><comment></code> <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>
Taken from gomme.1989.ring-o-roses<code><comment></code> <definitions>
.........
<div-type xml:id="para" which="paragraph"/>
<comment when="2016-01-25-05:00" who="park">The following agents and roles apply only to the
preparation of the TAN file, not the original TEI file that serves as the source. See the
teiHeader for details on responsibility.</comment>
<person xml:id="park">
.........
</person>
.........
</definitions>
Taken from patricius.confessio.2003.eng<code><comment></code> <head>
.........
<change when="2014-08-13" who="schmidt">Anfang</change>
<comment when="2014-08-13" who="schmidt">unten auf der Z. 438, recht</comment>
</head>
Taken from ring-o-roses.deu.1897<code><comment></code> <head>
.........
<change when="2014-10-24" who="park">Started file</change>
<comment when="2014-10-24" who="park">See p. 39 of source.</comment>
</head>
Taken from ring-o-roses.eng.1987<code><definitions></code>The element definitions lists terminology and definitions assumed in encoding the data.Formal Definition~ed-stamp?, (<comment>* &
(
(<person> | <organization> | <algorithm>)+ & <role>+ & <period>* & <alias>* & <relationship>* & <ambiguous-letter-numerals-are-roman>?) &
{[TAN-class-1 (~definition-non-core):]
(
(<work> & <version>? & <div-type>+ & <token-definition>*) & {empty})} OR
{[TAN-class-2 (~definition-non-core):]
(
(<token-definition>* & <group-type>*) &
{{[TAN-A-div (~definition-non-class-2):]
(<work>* & <place>* & <unit>* & <modal>* & <version>* & <scriptum>* & <topic>* & <verb>*)}} OR
{{[TAN-A-lm (~definition-non-class-2):]
(<lexicon>+ & <morphology>+)}} OR
{{[TAN-A-tok (~definition-non-class-2):]
(<bitext-relation>+ & <reuse-type>++)}} OR
{{[TAN-class-2 (~definition-non-class-2):] {empty}}})} OR
{[TAN-class-3 (~definition-non-core):]
(<group-type>* &
{{[TAN-key (~definition-non-class-3):] {empty}}} OR
{{[TAN-mor (~definition-non-class-3):] <feature>*}} OR
{{[TAN-class-3 (~definition-non-class-3):] {empty}}})} OR
{[TAN-core (~definition-non-core):] {empty}})Defined at:
TAN-core.rngUsed by: ~TAN-head<code><definitions></code> <head>
.........
<see-also relationship="model">
.........
</see-also>
<definitions>
<work>
.........
</work>
<div-type xml:id="p">
.........
</div-type>
<div-type xml:id="c">
.........
</div-type>
.........
</definitions>
<alter>
.........
</alter>
.........
</head>
Taken from ar.cat.eng.1926.edghill.obj<code><definitions></code> <head>
.........
<see-also relationship="ade">
.........
</see-also>
<definitions>
<work>
.........
</work>
<div-type xml:id="ch">
.........
</div-type>
<div-type xml:id="par">
.........
</div-type>
.........
</definitions>
<alter>
.........
</alter>
.........
</head>
Taken from ar.cat.eng.1926.edghill.sem<code><definitions></code> <head>
.........
<see-also relationship="ade">
.........
</see-also>
<definitions>
<work>
.........
</work>
<div-type xml:id="ch">
.........
</div-type>
<div-type xml:id="par">
.........
</div-type>
.........
</definitions>
<alter>
.........
</alter>
.........
</head>
Taken from ar.cat.fra.1844.saint-hilaire.sem-native<code><definitions></code> <head>
.........
<see-also relationship="model">
.........
</see-also>
<definitions>
<work>
.........
</work>
<div-type xml:id="ch">
.........
</div-type>
<div-type xml:id="par">
.........
</div-type>
.........
</definitions>
<alter>
.........
</alter>
.........
</head>
Taken from ar.cat.fra.1844.saint-hilaire.sem<code><desc></code>The element desc provides a 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. It has two possible structures, one human-readable and the other computer-readable.Under the first, human-readable approach, <desc> takes merely a descriptive text about the entity, optionally with @xml:lang. If you provide descriptions in other languages, it best to make sure that each version says roughly the same thing.Under the second, computer-readable approach, <desc> takes an IRI + name pattern plus <location> and @href pointing to a <TAN-c> file, which provides contextual information about the concept, person, or thing. Formal Definition
(~metadata-desc | (@which |
(@href | (<IRI>, ~metadata-human, <checksum>*, <location>+))))Defined at:
TAN-core.rngAll text must be normalized (Unicode NFC).<code><desc></code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:model-object-refs" TAN-version="2018">
<head>
.........
<license>
.........
<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>
.........
<definitions>
.........
<algorithm xml:id="xslt1">
.........
<name>Stylesheet to populate a TAN-A-div file from collections.</name>
<desc>Stylesheet at: ../do%20things/convert/convert%20TAN%202017%20to%20TAN%202018.xsl</desc>
</algorithm>
.........
</definitions>
.........
</head>
.........
</TAN-T>
Taken from ar.cat.eng.1926.edghill.obj<code><desc></code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2018">
<head>
.........
<license>
.........
<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>
.........
<definitions>
.........
<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>
.........
</definitions>
.........
</head>
.........
</TAN-T>
Taken from ar.cat.eng.1926.edghill.sem<code><div></code>The element div marks a textual unit. Contains other <div>s or text, but not both (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 the one defined by HTML, and can be applied to any kind of division whatsoever., even down to the letter or character level.Formal Definition~ed-stamp?,
(~inclusion |
(@type, @n, @xml:lang?, (<div>+ | text)))Defined at:
TAN-T.rngUsed by: ~body-item, ~text-divAll text must be normalized (Unicode NFC).Leaf div references must be 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.<div>s may not be mixed with other elements: a <div> must parent either only <div>s or none at all, and may have as siblings only other <div>s.A <div> must not mix @include with any other attributes.A <div> must have either @type + @n or @include but not both.@n suffices for labeling text in a <div>; the @n's value should not appear in the text.concatenated @n's suffice for labeling text in a <div>; the <div>'s reference should not appear in the text.<code><div></code> <body xml:lang="eng">
<div type="p" n="1"><div type="c" n="a"><div type="l" n="1">Things are said to be named 'equivocally' when, though they have a common name, the definition corresponding</div><div type="l" n="2">with the name differs for each. Thus, a real man and a figure in a picture can both</div><div type="l" n="3">lay claim to the name 'animal'; yet these are equivocally so named, for, though they have</div>
.........
</div><div type="c" n="b">
.........
</div></div><div type="p" n="2">
.........
</div>
.........
</body>
Taken from ar.cat.eng.1926.edghill.obj<code><div-ref></code>The element div-ref refers to one or more <div>s.<div-ref>s are expanded against @src/@work and @ref. That is, a <div-ref> points to every div of every source cited.Formal Definition~ed-stamp?, @refDefined at:
TAN-class-2.rngUsed by: ~complex-text-ref<code><div-type></code>The element div-type declares a type of textual division (e.g., title, paragraph, stanza). You may have as many <div-types> as you wish, and they need not all be used.For more information, see This element takes a reserved keyword or IRI + name pattern. See for suggested values. Formal Definition~defn-pattern-idDefined at:
TAN-class-1.rngUsed by: ~defn-class-1<code><div-type></code> <head>
.........
<definitions>
<work>
.........
</work>
<div-type xml:id="p">
<IRI>http://dbpedia.org/resource/Page_(paper)</IRI>
<name>page</name>
</div-type><div-type xml:id="c">
<IRI>http://dbpedia.org/resource/Column_(typography)</IRI>
<name>column</name>
</div-type><div-type xml:id="l">
<IRI>tag:textalign.net,2015:div-type:line:physical</IRI>
<name>physical line</name>
</div-type>
<person xml:id="kalvesmaki">
.........
</person>
.........
</definitions>
.........
</head>
Taken from ar.cat.eng.1926.edghill.obj<code><div-type></code> <definitions>
<work>
.........
</work>
<div-type xml:id="ch">
<IRI>http://dbpedia.org/resource/Chapter_(books)</IRI>
<name>chapter</name>
</div-type><div-type xml:id="par">
.........
</div-type>
.........
</definitions>
Taken from ar.cat.eng.1926.edghill.sem<code><doc></code>Formal Definition@href, @id, @rootDefined at:
catalog.tan.rngUsed by: <collection><code><equate></code>The element equate declares an ad hoc equivalence between works or @n values.This is useful for handling sources that have not used the the same <IRI>s in defining works that you believe to be equivalent, or for associating values of @n that should be treated as synonymous.Equating is transitive and greedy. If work A is defined with <IRI> X, work B with <IRI>s X and Y, and work C with only <IRI> Y, then works A and C will be automatically equated.This element does not imply that the works are necessarily one and the same, or than the @n values are the same. It merely states that, for the purposes of this alignment, they should be treated as equivalent.Formal Definition~ed-stamp?, (~inclusion | @n)Defined at:
TAN-class-2.rngUsed by: ~alter-class-2<code><equate></code> <head>
.........
<alter src="*">
<equate n="ti title"/><equate n="pr praef pref preface"/>
</alter>
.........
</head>
Taken from ar.cat.tan-a-div<code><feature></code>The element feature names, through its IRI + name pattern, a grammatical feature or concept (e.g., plural, subjunctive, 1st person) that is part of a language. In the context of <feature> a @code is always included. The first <feature> of a <category> never has @code, and refers to the grammatical feature that characterizes the category.See main.xml# keywords-feature for a list of standard features, derived from OLiA.Formal Definition~defn-pattern-id@type, @codeDefined at:
TAN-mor.rngUsed by: ~defn-features, ~category<code><feature></code> <head>
.........
<definitions ed-when="2015-03-03" ed-who="kalvesmaki">
.........
<alias id="''" idrefs="cl-quo"/>
<feature xml:id="cl-quo">
<IRI>tag:textalign.net,2015:morphology:option:quotation-mark-closing</IRI>
<name>closing quotation mark</name>
<desc>Examples: ' ''</desc>
</feature>
<alias id="--" idrefs="dash"/>
<feature xml:id="dash">
<IRI>http://dbpedia.org/resource/Dash</IRI>
<name>dash</name>
<desc>Examples: --</desc>
</feature>
<alias id="$" idrefs="x24"/>
<feature xml:id="x24">
<IRI>http://dbpedia.org/resource/Dollar_sign</IRI>
<name>dollar</name>
<desc>Examples: $ -$ --$ A$ C$ HK$ M$ NZ$ S$ U.S.$ US$</desc>
</feature>
<alias id="[" idrefs="x5B"/>
<feature xml:id="x5B">
<IRI>tag:textalign.net,2015:morphology:option:bracket-opening</IRI>
<name>opening bracket</name>
<desc>Examples: ( [ {</desc>
</feature>
<alias id="]" idrefs="x5D"/>
.........
</definitions>
.........
</head>
Taken from eng.kalvesmaki.com,2014.2<code><for-lang></code>The element for-lang specifies a language that is being discussed. This element does NOT name the language of the text enclosed by the parent element, which is the province of @xml:lang.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 Formal Definitionlanguage Defined at:
TAN-core.rngUsed by: ~defn-morph, ~lang-preface, ~TAN-R-mor-body, ~defn-pattern-language<for-lang> and <source> are mutually exclusive in a TAN-A-lm file.<code><for-lang></code> <morphology xml:id="Perseus">
<for-lang>grc</for-lang>
<IRI>tag:kalvesmaki.com,2014:tan-r-mor:grc:perseus</IRI>
.........
</morphology>
Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-LM-sample<code><for-lang></code> <body>
<for-lang>eng</for-lang>
<rule m-matches=".+">
.........
</rule>
.........
</body>
Taken from eng.kalvesmaki.com,2014.2<code><from></code>The element from points to a single token that is the start of a range of tokens to be selectedFormal Definition
(@val | @pos | (@val, @pos))Defined at:
TAN-class-2.rngUsed by: ~tok-ref-rangeIn a ranged <tok> in a <reassign>, the token referred to by <from> must precede the one referred to by <to>.<code><group></code>The element group groups references that should be treated as a single passage.The element group collects items that share a common property, defined by the <group-type> to which it refers.Formal Definition~ed-stamp?,
(~inclusion | (~group-attributes, <tok>+))~ed-stamp?,
(~inclusion | (
{[TAN-key (~group-attributes):] ~group-attributes} OR
{[TAN-core (~group-attributes):] ~group-attributes}, (
{[TAN-class-1 (~body-group):] {empty}} OR
{[TAN-core (~body-group):] <group>} |
{[TAN-A-lm (~body-item):] <ana>} OR
{[TAN-A-tok (~body-item):] <align>} OR
{[TAN-key (~body-item):] <item>} OR
{[TAN-T (~body-item):] <div>} OR
{[TAN-core (~body-item):] {empty}})+))Defined at:
TAN-class-2.rng, TAN-core.rngUsed by: ~body-content-non-class-2, ~body-content-non-class-3, ~tok-ref, ~body-group@affects-element must include only names of TAN elements that accept @which<code><group></code><TAN-key TAN-version="2018" id="tag:parkj@textalign.net,2015:TAN-key:ar.cat">
.........
<body in-progress="true" affects-element="work">
.........
<item>
.........
</item>
<group>
<item>
.........
</item>
<item>
.........
</item>
</group><group>
<item>
.........
</item>
<item>
.........
</item>
</group><group>
<item>
.........
</item>
<item>
.........
</item>
</group><group>
<item>
.........
</item>
<item>
.........
</item>
</group><group>
.........
</group>
.........
</body>
</TAN-key>
Taken from ar.cat.TAN-key<code><group-type></code>The element group-type defines types of <group>s. See main.xml# keywords-group-typeFormal Definition~defn-pattern-idDefined at:
TAN-core.rngUsed by: ~definition-class-2, ~definition-class-3<code><group-type></code> <definitions>
.........
<morphology xml:id="Perseus">
.........
</morphology>
<group-type xml:id="status" which="status"/>
<person include="rel"/>
.........
</definitions>
Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-LM-sample<code><group-type></code> <head>
.........
<definitions>
<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"/>
.........
</definitions>
.........
</head>
Taken from div-types.TAN-key<code><head></code>The element head contains the metadata (data about the data contained by <body>)This element indicates at a bare minimum the name of the file, the sources, the most significant parts of the editorial history; the linguistic or scholarly conventions that have been adopted in creating the data; the license, i.e., who holds what rights to the data, and what kind of reuse is allowed; the persons, organizations, or entities that helped create the data, and the roles played by each.The structure of <head> is shared across TAN files, with differences between them isolated to the child <definitions>.Formal Definition~ed-stamp?,
(<comment>* &
(~head-prelude, (<inclusion>* & <key>* &
{[TAN-A-div (~source-list):] <source>+} OR
{[TAN-A-lm (~source-list):] <source>?} OR
{[TAN-A-tok (~source-list):] ~source-list} OR
{[TAN-key (~source-list):] {empty}} OR
{[TAN-class-3 (~source-list):] <source>*} OR
{[TAN-core (~source-list):] <source>} & <see-also>*), <definitions>,
{[TAN-class-2 (~alter-statement):] <alter>*} OR
{[TAN-core (~alter-statement):] <alter>?}, <resp>+, <change>+))Defined at:
TAN-core.rngUsed by: ~TAN-root<code><head></code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:model-object-refs" TAN-version="2018">
<head>
<name>Categories, Aristotle, English translation by E. M. Edghill</name>
<license>
.........
</license>
<licensor who="kalvesmaki"/>
.........
</head>
<body xml:lang="eng">
.........
</body>
</TAN-T>
Taken from ar.cat.eng.1926.edghill.obj<code><head></code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2018">
<head>
<name>Categories, Aristotle, English translation by E. M. Edghill</name>
<license>
.........
</license>
<licensor who="kalvesmaki"/>
.........
</head>
<body xml:lang="eng">
.........
</body>
</TAN-T>
Taken from ar.cat.eng.1926.edghill.sem<code><head></code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.fra.1844.saint-hilaire:semantic-refs" TAN-version="2018">
<head>
<name>Categories, Aristotle, French translation by J. Barthélemy Saint-Hilaire</name>
<license>
.........
</license>
<licensor who="kalvesmaki"/>
.........
</head>
<body xml:lang="fra">
.........
</body>
</TAN-T>
Taken from ar.cat.fra.1844.saint-hilaire.sem-native<code><head></code><TAN-T TAN-version="2018" 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>
<license>
.........
</license>
<licensor who="kalvesmaki"/>
.........
</head>
<body xml:lang="fra">
.........
</body>
</TAN-T>
Taken from ar.cat.fra.1844.saint-hilaire.sem<code><inclusion></code>The element inclusion specifies a TAN file that is available for inclusion. An inclusion occurs whenever an element X points to this inclusion by means of @include. TAN-compliant validators and processors will find every 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 main document.Only select elements will be included, not the entire inclusion file. Exactly which elements are included is dictated by @include.Invoking an <inclusion> does not require its use. For more on this, see Formal Definition~ed-stamp?, @xml:id, (<comment>* &
(@href | (<IRI>, ~metadata-human, <checksum>*, <location>+)))Defined at:
TAN-core.rngUsed by: ~claim, ~defn-morph, ~defn-lexi, ~TAN-A-lm-item, ~alignment-inclusion-opt, ~TAN-key-item, ~category, ~morphology-rule, ~text-div, ~alt-norm, ~func-replace, ~alt-skip, ~alt-rename, ~alt-equate, ~alt-reassign, ~tok-ref-group, ~nonsource-license, ~inclusion-list, ~key-item, ~source-item, ~see-also-item, ~alter-element, ~resp-item, ~body-group, ~defn-pattern-default, ~defn-pattern-id, ~defn-pattern-no-id, ~defn-pattern-language, ~defn-alias, ~defn-period, ~defn-relationship, ~defn-tok-defFor any element with @include, at least one element of the same name must be found in target inclusion document.Inclusions may not be circular.Inclusions are integral parts of any TAN file. Access to at least one copy is absolutely mandatory.Every element with a <location> 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 a <see-also> pointing to an older or new version.If a target file does not explicitly give the <body>'s @in-progress the value of true() a warning will be returned. Target file is marked as being in progress.If a target file has a <see-also> marked as a new version (update) a warning will be returned.If @when-accessed predates one or more dates in a target file, a warning will be returned.<code><inclusion></code> <head>
.........
<licensor who="kalvesmaki"/>
<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-obj.xml" when-accessed="2016-09-28T08:50:23.457-04:00"/>
</inclusion>
<source>
.........
</source>
.........
</head>
Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-LM-sample<code><IRI></code>The element IRI contains an International Resource Identifier that serves as a name for the a concept, person, or thing referred to by the parent element. IRIs are explained at .Any kind of IRIs are allowed: URLs, tag URNs, UUIDs, etc. For names of well-known resources, a URL identifier might be preferred (http://...), 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. Nevertheless, they are not synonymous, 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 define similar concepts differently. An element defined with multiple <IRI>s is technically within the intersection, not the union, of those definitions. Nevertheless, most interpretations of TAN files will draw inferences based upon the union. That is, if item A is defined by IRI X, item B by IRIs X and Y, and item C with IRI Y, it is likely that users of the data will infer identity between items A and C. It is advisable to be cautious is assigning multiple IRIs to entities.The element is named IRI instead of URI to encourage internationalization. Alphabets other than the Latin are welcome. Formal Definition~ed-stamp?, anyURI (pattern [a-zA-Z][\-.+a-zA-Z0-9]+:\S+)Defined at:
TAN-core.rngUsed by: ~entity-digital-tan-other-ref, ~entity-digital-generic-ref, ~entity-nondigital-refAn 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 keys that have duplicate IRIs.All text must be normalized (Unicode NFC).Every item in a reserved TAN-key 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:model-object-refs" TAN-version="2018">
<head>
.........
<license>
<IRI>http://creativecommons.org/licenses/by/4.0/deed.en_US</IRI>
<name>Creative Commons Attribution 4.0 International License</name>
.........
</license>
.........
<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>
<see-also relationship="ade">
<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>
.........
</see-also>
<see-also relationship="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>
.........
</see-also>
.........
</head>
.........
</TAN-T>
Taken from ar.cat.eng.1926.edghill.obj<code><item></code>The element item names an item that is being described. The item is assumed to be a species of the type of thing discussed by the TAN element that is affected.Formal Definition~ed-stamp?,
(~inclusion |
(@affects-element?, @group?, (
(@href | (<IRI>, ~metadata-human, <checksum>*, <location>+)) |
((<IRI>+, ~metadata-human, <checksum>*, <location>+) | @which) |
((<IRI>+, ~metadata-human) | @which) | ~entity-tok-def)))Defined at:
TAN-key.rngUsed by: ~body-item@affects-element must include only names of TAN elements that accept @whichEvery item in a reserved TAN-key must have at least one IRI with a tag URN in the TAN namespace<code><item></code><TAN-key TAN-version="2018" id="tag:parkj@textalign.net,2015:TAN-key:ar.cat">
.........
<body in-progress="true" affects-element="work">
<item>
<IRI>tag:parkj@textalign.net,2015:work:porphyry:on-aristotles-categories</IRI>
<name xml:lang="lat">Commentarium graecum Porphyrii</name>
<name xml:lang="eng">Porphyry's commentary on Aristotle's Categories</name>
</item><item>
<IRI>tag:parkj@textalign.net,2015:work:dexippus:on-aristotles-categories</IRI>
<name xml:lang="lat">Commentarium graecum Dexippi</name>
<name xml:lang="eng">Dexippus's commentary on Aristotle's Categories</name>
</item>
<group>
<item>
<IRI>tag:parkj@textalign.net,2015:work:ammonius:on-aristotles-categories:lemmata</IRI>
<name xml:lang="lat">Lemmata de commentario graeco Ammonii</name>
<name xml:lang="eng">Lemmata from Ammonius's commentary on Aristotle's
Categories</name>
</item><item>
<IRI>tag:parkj@textalign.net,2015:work:ammonius:on-aristotles-categories:discussions</IRI>
<name xml:lang="lat">Explanationes de commentario graeco Ammonii</name>
<name xml:lang="eng">Discussions in Ammonius's commentary on Aristotle's
Categories</name>
</item>
</group>
.........
</body>
</TAN-key>
Taken from ar.cat.TAN-key<code><key></code>The element key specifies a TAN-key file that defines concepts that may be invoked by @which.For more discussion, see Formal Definition~ed-stamp?,
(~inclusion | (<comment>* &
(@href | (<IRI>, ~metadata-human, <checksum>*, <location>+))))Defined at:
TAN-core.rngUsed by: ~key-listNo file may import keys that have duplicate IRIs.Every element with a <location> 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 a <see-also> pointing to an older or new version.If a target file does not explicitly give the <body>'s @in-progress the value of true() a warning will be returned. Target file is marked as being in progress.If a target file has a <see-also> marked as a new version (update) a warning will be returned.If @when-accessed 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 the core TAN keyword or an associated TAN-key file, that is marked as applying to that element.Keywords (values of @which) must be unique for a given element name.Any element that takes @which must have keywords defined for that element.Keys are integral parts of a document. Access to at least one version is absolutely mandatory.<code><key></code> <head>
.........
<licensor who="park"/>
<key>
<IRI>tag:parkj@textalign.net,2015:TAN-key:ar.cat</IRI>
<name>Keywords for Aristotle's Categories</name>
<location href="../TAN-key/ar.cat.TAN-key.xml" when-accessed="2017-03-10T11:50:15.499-05:00"/>
</key>
<source xml:id="grc">
.........
</source>
.........
</head>
Taken from ar.cat.tan-a-div.claims<code><l></code>The element l names a lexeme, by points to the main word entry in the lexicon defined by the element's inherited value 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, this word will be identical to the word token itself. In those cases, <l> may be left empty, indicating that the value of <tok> is to be supplied.Because there is no TAN format for lexicons, values in this element will not be validated.Formal Definition@lexicon?, @def-ref?, ~certainty-stamp?, textDefined at:
TAN-A-lm.rngUsed by: ~TAN-A-lm-item<code><l></code><TAN-A-lm TAN-version="2018" 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">
<ana>
.........
<lm>
<l>Δῆλος</l>
<m>n e - s - - - f a -</m>
</lm>
</ana>
<ana>
.........
<lm>
<l>Σωκράτης</l>
<m>n e - s - - - m g -</m>
</lm>
</ana>
<ana>
.........
<lm>
<l>αἰσχύνω</l>
<m>v - - - a n p - - -</m>
</lm>
</ana>
<ana>
.........
<lm>
<l>αἴσθησις</l>
<m>n - - s - - - f n -</m>
</lm>
</ana>
<ana>
.........
<lm>
<l>αἴσθησις</l>
<m>n - - s - - - f g -</m>
</lm>
</ana>
.........
</body>
</TAN-A-lm>
Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-LM-sample<code><lexicon></code>The element lexicon names a lexicographical authority. This element is optional, because the lexical informat could be based upon the knowledge of the <agent>s who wrote the data.Formal Definition~ed-stamp?,
(~inclusion |
(@xml:id, (
((<IRI>+, ~metadata-human, <checksum>*, <location>+) | @which) |
((<IRI>+, ~metadata-human) | @which))))Defined at:
TAN-A-lm.rngUsed by: ~definition-non-class-2<code><lexicon></code> <head>
.........
<definitions>
<token-definition pattern="[\w]+"/>
<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>
.........
</definitions>
.........
</head>
Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-LM-sample<code><lexicon></code> <definitions>
<morphology xml:id="penn" ed-when="2015-08-20-04:00" ed-who="park">
.........
</morphology>
<lexicon xml:id="english">
<IRI>tag:parkj@textalign.net,2015:lexicon:eng:test</IRI>
<name>An English dictionary</name>
</lexicon>
<token-definition which="letters and punctuation"/>
.........
</definitions>
Taken from ring-o-roses.eng.1881.lm<code><license></code>The element license states the license under which the data is distributed and the rights associated with it, EXCLUSIVE of any rights attached to the source.Diligently check to ensure that the license you have claimed respects the rights of your sources' rightsholders. It is recommended that you license your data under a license that is similar to or more liberal than the one under which your sources have been released.For more discussion, see and for a list of standard vocabulary, main.xml# keywords-rights-excluding-sourcesFormal Definition~ed-stamp?,
(~inclusion | (<comment>* &
((<IRI>+, ~metadata-human) | @which)))Defined at:
TAN-core.rngUsed by: ~head-prelude-core<code><license></code> <head>
<name>Categories, Aristotle, English translation by E. M. Edghill</name>
<license>
<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>
<licensor who="kalvesmaki"/>
.........
</head>
Taken from ar.cat.eng.1926.edghill.obj<code><license></code> <head>
<name>Categories, Aristotle, English translation by E. M. Edghill</name>
<license>
<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>
<licensor who="kalvesmaki"/>
.........
</head>
Taken from ar.cat.eng.1926.edghill.sem<code><license></code> <head>
<name>Categories, Aristotle, French translation by J. Barthélemy Saint-Hilaire</name>
<license>
<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>
<licensor who="kalvesmaki"/>
.........
</head>
Taken from ar.cat.fra.1844.saint-hilaire.sem-native<code><license></code> <head>
<name>Realignment of Categories, Aristotle, French translation by J. Barthélemy
Saint-Hilaire</name>
<license>
<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>
<licensor who="kalvesmaki"/>
.........
</head>
Taken from ar.cat.fra.1844.saint-hilaire.sem<code><licensor></code>Formal Definition~ed-stamp?, (~inclusion | @who)Defined at:
TAN-core.rngUsed by: ~head-prelude-core<code><licensor></code> <head>
.........
<license>
.........
</license>
<licensor who="kalvesmaki"/>
<source>
.........
</source>
.........
</head>
Taken from ar.cat.eng.1926.edghill.obj<code><licensor></code> <head>
.........
<license>
.........
</license>
<licensor who="kalvesmaki"/>
<source>
.........
</source>
.........
</head>
Taken from ar.cat.eng.1926.edghill.sem<code><licensor></code> <head>
.........
<license>
.........
</license>
<licensor who="kalvesmaki"/>
<source>
.........
</source>
.........
</head>
Taken from ar.cat.fra.1844.saint-hilaire.sem-native<code><licensor></code> <head>
.........
<license>
.........
</license>
<licensor who="kalvesmaki"/>
<source>
.........
</source>
.........
</head>
Taken from ar.cat.fra.1844.saint-hilaire.sem<code><lm></code>The element lm contains lexical or morphological data.Claims within an <lm> are distributive. That is, every <l> is asserted against every <m> within an <lm> is asserted of every <tok>.Formal Definition~certainty-stamp?,
(<comment>* &
((<l>+, <m>*) | (<l>*, <m>+)))Defined at:
TAN-A-lm.rngUsed by: <ana><code><lm></code><TAN-A-lm TAN-version="2018" 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">
<ana>
<tok ref="11 2 1 1" pos="1"/>
<lm>
<l>Δῆλος</l>
<m>n e - s - - - f a -</m>
</lm>
</ana>
<ana>
.........
<tok ref="10 6 4 2" pos="37"/>
<lm>
<l>Σωκράτης</l>
<m>n e - s - - - m g -</m>
</lm>
</ana>
<ana>
.........
<tok ref="8 3 7 3" pos="7"/>
<lm>
<l>αἰσχύνω</l>
<m>v - - - a n p - - -</m>
</lm>
</ana>
<ana>
.........
<tok ref="7 4 9 2" pos="4"/>
<lm>
<l>αἴσθησις</l>
<m>n - - s - - - f n -</m>
</lm>
</ana>
.........
</body>
</TAN-A-lm>
Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-LM-sample<code><location></code>The element location declares where an electronic file was found and when. The URL may be absolute or relative to the current document. Formal Definition~ed-stamp?, @when-accessed, @hrefDefined at:
TAN-core.rngUsed by: ~entity-digital-tan-other-ref, ~entity-digital-generic-refEvery element with a <location> 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 a <see-also> pointing to an older or new version.If a target file does not explicitly give the <body>'s @in-progress the value of true() a warning will be returned. Target file is marked as being in progress.If a target file has a <see-also> marked as a new version (update) a warning will be returned.If @when-accessed 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:model-object-refs" TAN-version="2018">
<head>
.........
<see-also relationship="ade">
.........
<name>Categories, Aristotle, English translation by E. M. Edghill</name>
<location href="ar.cat.eng.1926.edghill.sem.xml" when-accessed="2016-07-07T16:36:28.867-04:00"/>
</see-also>
<see-also relationship="model">
.........
<name>Categories, Aristotle, Greek text by Minio-Paluello</name>
<location href="ar.cat.grc.1949.minio-paluello-obj.xml" when-accessed="2016-07-07T16:36:28.867-04:00"/>
</see-also>
.........
</head>
.........
</TAN-T>
Taken from ar.cat.eng.1926.edghill.obj<code><location></code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2018">
<head>
.........
<see-also relationship="model">
.........
<name>Categories, Aristotle, Greek text by Minio-Paluello</name>
<location href="ar.cat.grc.1949.minio-paluello-sem.xml" when-accessed="2016-02-10T14:08:52.058-05:00"/>
</see-also>
<see-also relationship="alt">
.........
<name>Categories, Aristotle, Greek text by Minio-Paluello</name>
<location href="ar.cat.grc.1949.minio-paluello-obj.xml" when-accessed="2016-02-11T12:40:42.823-05:00"/>
</see-also>
.........
</head>
.........
</TAN-T>
Taken from ar.cat.eng.1926.edghill.sem<code><locus></code>The element locus restricts a claim to a particular location within a scriptum or work.This element functions much like <place>, but the geography is textual rather than spatial.Formal Definition~ed-stamp?,
(~simple-textual-reference | ~complex-textual-reference-set)Defined at:
TAN-A-div.rngUsed by: ~claimNo <tok> should duplicate any sibling <tok>.<code><locus></code><TAN-A-div TAN-version="2018" id="tag:parkj@textalign.net,2015:ar.cat.tan-a-div:claims">
.........
<body claimant="lmp">
.........
<claim subject="herminus comm-omnes" verb="agrees">
<locus src="grc">
<tok ref="1 a 2" pos="3-4"/>
</locus>
</claim>
.........
<claim subject="B" verb="replaces">
<locus src="grc">
<tok ref="1 a 5" pos="1-2"/>
</locus>
<object>τις ἀποδιδῷ</object>
</claim>
<claim subject="Λ" adverb="perhaps" verb="replaces">
<locus src="grc">
<tok ref="1 a 5" pos="1-2"/>
</locus>
<object>τις ἀποδιδῷ</object>
</claim>
<claim subject="π α φ ο" verb="agrees">
<locus src="grc">
<tok ref="1 a 5" pos="1-2"/>
</locus>
</claim>
.........
</body>
</TAN-A-div>
Taken from ar.cat.tan-a-div.claims<code><m></code>The element m carries a morphological code that conforms to the rules or patterns defined in the TAN-mor file upon which the data depends.Codes are space-delimited. If a value of <m> violates the rules established by the TAN-mor file, an error will be generated. For more about how codes are built, and how they function, see .Formal Definition~certainty-stamp?, @morphology?, string (pattern [^\+\s]+(\s+[^\+\s]+)*)Defined at:
TAN-A-lm.rngUsed by: ~TAN-A-lm-itemWhen 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>The element master-location points to a location where a master copy of the file is to be found. Use of this element entails a commitment to updating the TAN file in those locations. Also, if @in-progress is false, a <master-location> must be provided.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 points to the main locations where an authoritative version of the file is to be found. Formal Definition~ed-stamp?, @hrefDefined at:
TAN-core.rngUsed by: ~entity-digital-tan-self-refAny TAN file marked as being no longer in progress should have at least one master-location.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>Dictionary entry by Alice Bertha Gomme on Ring a Ring o' Roses</name>
<master-location href="http://textalign.net/release/TAN-2018/examples/gomme.1989.ring-o-roses.xml"/>
<license>
.........
</license>
.........
</head>
Taken from gomme.1989.ring-o-roses<code><master-location></code> <head>
<name>TAN Transkription, Ringelreihen mit Riederfallen</name>
<master-location href="http://beispiel.com/TAN-T/ringel.xml"/>
<license>
.........
</license>
.........
</head>
Taken from ring-o-roses.deu.1897<code><master-location></code> <head>
<name>TAN transcription of Ring a Ring o' Roses</name>
<master-location href="http://textalign.net/release/TAN-2018/examples/ring-o-roses.eng.1881.xml"/>
<license which="by_4.0"/>
.........
</head>
Taken from ring-o-roses.eng.1881<code><master-location></code> <head>
<name>TAN transcription of 1790 version of Ring around the Rosie reported by Newell in
1883</name>
<master-location href="http://textalign.net/release/TAN-2018/examples/ring-o-roses.eng.1957.xml"/>
<license>
.........
</license>
.........
</head>
Taken from ring-o-roses.eng.1957<code><modal></code>The element modal contains an IRI + name pattern identifying a modal or adverb that qualifies the verb of an assertion.See main.xml# keywords-modal for standard vocabulary.Formal Definition~defn-pattern-defaultDefined at:
TAN-A-div.rngUsed by: ~defn-claims<code><modal></code> <definitions>
.........
<verb which="refers or alludes to" xml:id="refers-to"/>
<modal which="possibly" xml:id="perhaps"/>
<person xml:id="park">
.........
</person>
.........
</definitions>
Taken from ar.cat.tan-a-div.claims<code><morphology></code>The element morphology identifies a <TAN-mor> file that defines the parts of speech for a language, the codes for those parts, and the rules for combining themFormal Definition~ed-stamp?,
(~inclusion |
(@xml:id, <for-lang>*, (@which |
(@href | (<IRI>, ~metadata-human, <checksum>*, <location>+)))))Defined at:
TAN-A-lm.rngUsed by: ~definition-non-class-2<code><morphology></code> <definitions>
.........
<lexicon xml:id="new">
.........
</lexicon>
<morphology xml:id="Perseus">
<for-lang>grc</for-lang>
<IRI>tag:kalvesmaki.com,2014:tan-r-mor:grc:perseus</IRI>
<name xml:lang="eng">Perseus Greek morphology</name>
.........
</morphology>
<group-type xml:id="status" which="status"/>
.........
</definitions>
Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-LM-sample<code><morphology></code> <definitions>
<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" when-accessed="2015-11-03-05:00"/>
</morphology>
<lexicon xml:id="english">
.........
</lexicon>
.........
</definitions>
Taken from ring-o-roses.eng.1881.lm<code><name></code>The element name provides a human-readable name of a concept, person, or thing referred to by the parent element (or the current document, if the parent element is <head>)Formal Definition~metadata-descDefined at:
TAN-core.rngAll text must be normalized (Unicode NFC).Names may not duplicate reserved TAN keyword names for the affected element.Names may not be duplicates of, case-variants of, or hyphen variants of other names for the same element.<code><name></code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:model-object-refs" TAN-version="2018">
<head>
<name>Categories, Aristotle, English translation by E. M. Edghill</name>
<license>
<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>
.........
<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>
<see-also relationship="ade">
<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.sem.xml" when-accessed="2016-07-07T16:36:28.867-04:00"/>
</see-also>
.........
</head>
.........
</TAN-T>
Taken from ar.cat.eng.1926.edghill.obj<code><normalization></code>The element normalization specifies an alteration 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 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 in <replace>. See for suggested IRI + name values for normalizations. For general discussion see Formal Definition~ed-stamp?,
(~inclusion |
({empty}, (<comment>* &
((<IRI>+, ~metadata-human) | @which))))Defined at:
TAN-class-1.rngUsed by: ~alter-non-core<code><normalization></code> <alter>
<normalization which="no hyphens"/>
</alter>
Taken from ar.cat.eng.1926.edghill.obj<code><normalization></code> <alter>
<normalization which="no hyphens"/>
</alter>
Taken from ar.cat.eng.1926.edghill.sem<code><normalization></code> <alter>
<normalization which="no hyphens"/>
</alter>
Taken from ar.cat.fra.1844.saint-hilaire.sem-native<code><normalization></code> <alter>
<normalization which="no hyphens"/>
</alter>
Taken from ar.cat.fra.1844.saint-hilaire.sem<code><object></code>The element object is similar to @object, but for complex content, mainly concepts that do not lend themselves to the IRI + name pattern, particularly languages and units or passages of text.Formal Definition~ed-stamp?, (~nontextual-reference |
(~simple-textual-reference | ~complex-textual-reference-set))Defined at:
TAN-A-div.rngUsed by: ~claim, ~complex-objectNo <tok> should duplicate any sibling <tok>.<object>s taking strings must match the predefined @object-datatype for the verb.<object>s taking strings for verbs that have lexical constraints must match those lexical constraints.<code><object></code><TAN-A-div TAN-version="2018" id="tag:parkj@textalign.net,2015:ar.cat.tan-a-div:claims">
.........
<body claimant="lmp">
.........
<claim subject="dexippus porphyry">
<claim subject="andronicus boethus" adverb="perhaps" verb="omits">
<object src="grc">
<tok ref="1 a 2" pos="3-4"/>
</object>
</claim>
</claim>
.........
<claim subject="B" verb="replaces">
<locus src="grc">
.........
</locus>
<object>τις ἀποδιδῷ</object>
</claim>
<claim subject="Λ" adverb="perhaps" verb="replaces">
<locus src="grc">
.........
</locus>
<object>τις ἀποδιδῷ</object>
</claim>
.........
<claim verb="refers-to">
<subject src="grc" ref="1 b 25"/>
<object work="grc" ref="1 a 16"/>
</claim>
</body>
</TAN-A-div>
Taken from ar.cat.tan-a-div.claims<code><organization></code>The element organization contains an IRI + name pattern identifying an organization, a group of persons, whether formally incorporated or not.Formal Definition~defn-pattern-idDefined at:
TAN-core.rngUsed by: ~defn-agent<code><period></code>The element period defines a period of time.Formal Definition~ed-stamp?,
(~inclusion | (@xml:id, @from, @to))Defined at:
TAN-core.rngUsed by: ~definition-core<code><person></code>The element person contains an IRI + name pattern identifying an individual human being.Formal Definition~defn-pattern-idDefined at:
TAN-core.rngUsed by: ~defn-agent<code><person></code> <definitions>
.........
<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>
.........
</definitions>
Taken from ar.cat.eng.1926.edghill.obj<code><person></code> <definitions>
.........
<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>
.........
</definitions>
Taken from ar.cat.eng.1926.edghill.sem<code><person></code> <definitions>
.........
<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>
.........
</definitions>
Taken from ar.cat.fra.1844.saint-hilaire.sem-native<code><person></code> <definitions>
.........
<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>
.........
</definitions>
Taken from ar.cat.fra.1844.saint-hilaire.sem<code><place></code>The element place contains an IRI + name pattern identifying a spatial location, usually somewhere on earthFormal Definition~defn-pattern-defaultDefined at:
TAN-A-div.rngUsed by: ~defn-claims<code><reassign></code>The element reassign identifies word fragments that should be moved from one ref to anotherFormal Definition~ed-stamp?,
(~inclusion | (<tok>+, <to>))Defined at:
TAN-class-2.rngUsed by: ~alter-class-2Only the first of multiple <reassign>s that apply to a particular token will be applied.If a <div> is renamed, and the target reference is subject to <reassign> instructions, the following message will appear. <reassign> targets a reference that has been altered by <rename>. Any reassignments will treat the newly created <div>, not the original.No alter action should result in the mixing of leaf <div>s and non-leaf <div>s.No <tok> should duplicate any sibling <tok>.In a ranged <tok> in a <reassign>, the token referred to by <from> must precede the one referred to by <to>.<code><reassign></code> <head>
.........
<alter src="fra">
.........
<rename ref="15 10" new="15 1 3"/>
<reassign>
<tok ref="5 5" pos="1-27"/>
<to ref="5 1 5"/>
</reassign><reassign>
<tok ref="5 5">
.........
</tok>
<to ref="5 1 6"/>
</reassign><reassign>
<tok ref="5 5">
.........
</tok>
<to ref="5 1 7"/>
</reassign><reassign>
<tok ref="5 6">
.........
</tok>
<to ref="5 2 1"/>
</reassign><reassign>
.........
</reassign>
.........
</alter>
.........
</head>
Taken from ar.cat.tan-a-div<code><relationship></code>The element relationship specifies a relationship that one document has to another.See for standardized vocabulary.Formal Definition~ed-stamp?,
(~inclusion | (@xml:id,
((<IRI>+, ~metadata-human) | @which)))Defined at:
TAN-core.rngUsed by: ~see-also-item, ~definition-coreAny <see-also> whose <relationship> is defined as requiring a target TAN file must point to a file whose root element is a TAN file.Any <see-also> whose <relationship> is defined as requiring a target copy must point to a TAN file whose root element is identical.<see-also> may have the <relationship> of a different work version only if both are class 1 files and both share the same work.Class 1 files must share the same source as any alternatively divided edition.Class 1 files must share the same work as any model or alternatively divided edition.Class 1 files must share the same work-version, if supplied, as any alternatively divided edition.Class 1 files must have identical transcriptions, after TAN normalization, as any alternatively divided edition.A class 1 file may have no more than one model.If a class 1 file diverges from the structure of its model a warning will be generated specifying where differences exist.<code><relationship></code> <head>
.........
<definitions>
.........
<role xml:id="stylesheet1" which="stylesheet"/>
<relationship xml:id="model" which="model"/><relationship xml:id="ade" which="alternatively divided edition"/>
</definitions>
.........
</head>
Taken from ar.cat.eng.1926.edghill.obj<code><relationship></code> <head>
.........
<definitions>
.........
<role xml:id="stylesheet1" which="stylesheet"/>
<relationship which="model" xml:id="model"/><relationship which="alternatively divided edition" xml:id="ade"/><relationship which="different work version" xml:id="alt"/>
</definitions>
.........
</head>
Taken from ar.cat.eng.1926.edghill.sem<code><rename></code>The element rename provisionally reassigns values of @n's in class 1 sources, or their calculated ref value, to another value.Values of @n will be renamed before attempting to rename references. Only the first renaming match will be applied.Formal Definition~ed-stamp?,
(~inclusion | (
((@n, @new) | (@ref, @new)) | ~complex-rename))Defined at:
TAN-class-2.rngUsed by: ~alter-class-2When renaming references, ranges must be predictably calculated.At least one instance of an @n 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 number of values in @ref and @new must be identical.Every div type reference must be valid in every source@new may not take the same value as what it replaces.Only the first of multiple <rename>s that apply to a particular <div> will be applied.If a <div> is renamed, and the target reference is subject to <reassign> instructions, the following message will appear. <reassign> targets a reference that has been altered by <rename>. Any reassignments will treat the newly created <div>, not the original.No alter action should result in the mixing of leaf <div>s and non-leaf <div>s.<code><rename></code> <head>
.........
<alter src="fra">
<skip div-type="sec"/>
<rename ref="1 1-3" new="1 1 1-3"/><rename ref="3 1-3" new="3 1 1-3"/><rename ref="4 1-3" new="4 1 1-3"/><rename ref="5 1-4" new="5 1 1-4"/><rename ref="5 7-9" new="5 2 3-5"/>
.........
</alter>
.........
</head>
Taken from ar.cat.tan-a-div<code><replace></code>The element replace contains the equivalent of the XPath replace() function plus parameters, indicating a replacement operation that should be, or has been, applied to a digital file.Multiple <replace>s will be assumed to have been implemented in document order.The conventions of this element and its children accord with the definition of the function and its parameters provided at http://www.w3.org/TR/xpath-functions-30/#func-replaceFormal Definition~ed-stamp?,
(~inclusion |
(<comment>* & (@pattern, @replacement, @flags?)))Defined at:
TAN-class-1.rngUsed by: ~alt-repl<code><report></code>The element report names a pattern that, if found to be true in any <m> in a dependent TAN-A-lm file, will return the enclosed message upon validation of the dependent file, along with an error or warning. Modeled on Schematron <report>.Formal Definition~condition-patternDefined at:
TAN-mor.rngUsed by: ~morphology-rule<code><report></code> <rule m-has-features="'' . ; :">
<report tok-matches="\w">Nothing marked as punctuation should have word
characters.</report>
</rule>
Taken from eng.kalvesmaki.com,2014.2<code><resp></code>The element resp specifies a role held by one or more persons, organizations, or algorithms, perhaps during a specified time period.Formal Definition~ed-stamp?,
(~inclusion | (@who, @roles, @period?))Defined at:
TAN-core.rngUsed by: ~resp-list<code><resp></code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:model-object-refs" TAN-version="2018">
<head>
.........
<alter>
.........
</alter>
<resp roles="editor" who="kalvesmaki"/><resp who="xslt1" roles="stylesheet1"/>
<change when="2016-07-07T16:36:28.867-04:00" who="kalvesmaki">Reformatted file at
ar.cat.eng.1926.edghill.sem.xml to the structure of the copy of the model.</change>
.........
</head>
.........
</TAN-T>
Taken from ar.cat.eng.1926.edghill.obj<code><resp></code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2018">
<head>
.........
<alter>
.........
</alter>
<resp roles="editor" who="kalvesmaki"/><resp who="xslt1" roles="stylesheet1"/>
<change when="2016-06-22T08:04:25.003-04:00" who="kalvesmaki">Reformatted according to first
model found. Backup made at
file:/C:/Users/jdkalv/Dropbox/TAN/library/TAN-2018/examples/ar.cat.eng.1926.edghill.sem-201606220804250030400.xml.</change>
.........
</head>
.........
</TAN-T>
Taken from ar.cat.eng.1926.edghill.sem<code><reuse-type></code>The element reuse-type identifies a category of text reuse (e.g., translation, mistranslation, paraphrase, ridicule). See for theoretical background.For examples see main.xml# keywords-reuse-typeFormal Definition~defn-pattern-defaultDefined at:
TAN-A-tok.rng<code><reuse-type></code> <definitions>
<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>
<token-definition src="ring1881 ring1987" which="letters"/>
.........
</definitions>
Taken from ringoroses.01+02.token.1<code><reuse-type></code> <definitions>
<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>
.........
</definitions>
Taken from ringoroses.01+03.token.1<code><reuse-type></code> <definitions>
<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>
<token-definition src="eng ger" which="letters and punctuation"/>
.........
</definitions>
Taken from ringoroses.01+03.token.2<code><role></code>The element role specifies a role (responsibility, task, or activity) that one or more <agent>s did in creating or editing the data.A role may be any activity, e.g., editor, funder, supervisor, data-processor, peer reviewer, patron, defined through the enclosed IRI + name pattern.Formal Definition~defn-pattern-idDefined at:
TAN-core.rngUsed by: ~definition-core<code><role></code> <head>
.........
<definitions>
.........
<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="model" which="model"/>
.........
</definitions>
.........
</head>
Taken from ar.cat.eng.1926.edghill.obj<code><role></code> <head>
.........
<definitions>
.........
<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 which="model" xml:id="model"/>
.........
</definitions>
.........
</head>
Taken from ar.cat.eng.1926.edghill.sem<code><rule></code>The element rule encloses asserts and reports that should be evaluated provided that the conditions specified in the attributes (or children <where> attributes) are true.Formal Definition~ed-stamp?,
(~inclusion | (
(
{{{[TAN-mor (~action-condition-attributes):] ~action-condition-attributes}}} OR
{{{[TAN-class-2 (~action-condition-attributes):] ~action-condition-attributes}}} OR
{{{[TAN-core (~action-condition-attributes):] {empty}}}} | <where>+), (<assert> | <report>)+))Defined at:
TAN-mor.rngUsed by: ~TAN-R-mor-body<code><rule></code><TAN-mor TAN-version="2018" id="tag:kalvesmaki.com,2014:tan-r-mor:eng:penn">
.........
<body>
<for-lang>eng</for-lang>
<rule m-matches=".+">
<assert m-has-how-many-features="1">Features may not be combined.</assert>
</rule><rule m-has-features="$">
<assert tok-matches="$">Only $ may be tagged as a dollar sign.</assert>
</rule><rule m-has-features="'' . ; :">
<report tok-matches="\w">Nothing marked as punctuation should have word
characters.</report>
</rule>
</body>
</TAN-mor>
Taken from eng.kalvesmaki.com,2014.2<code><scriptum></code>The element scriptum contains an IRI + name pattern identifying a text-bearing object.Formal Definition~defn-pattern-defaultDefined at:
TAN-A-div.rngUsed by: ~defn-claims<code><scriptum></code> <head>
.........
<definitions>
.........
<work xml:id="Γ">
.........
</work>
<scriptum xml:id="n">
<IRI>tag:parkj@textalign.net,2015:scriptum:ita:milan:ambrosianus:L-93</IRI>
<name>Ambrosianus L 93</name>
<desc>saec. ix</desc>
</scriptum><scriptum xml:id="B">
<IRI>tag:parkj@textalign.net,2015:scriptum:ita:venezia:marcianus:201</IRI>
<name>Marcianus 201</name>
<desc>saec. x</desc>
</scriptum>
<work xml:id="π" which="Commentarium graecum Porphyrii"/>
.........
</definitions>
.........
</head>
Taken from ar.cat.tan-a-div.claims<code><see-also></code>The element see-also identifies other documents that are related to the current file.Formal Definition~ed-stamp?,
(~inclusion |
(@relationship,
(<comment>* & (
((<IRI>+, ~metadata-human, <checksum>*, <location>+) | @which) |
(@href | (<IRI>, ~metadata-human, <checksum>*, <location>+))))))Defined at:
TAN-core.rngUsed by: ~see-also-listAny <see-also> whose <relationship> is defined as requiring a target TAN file must point to a file whose root element is a TAN file.Any <see-also> whose <relationship> is defined as requiring a target copy must point to a TAN file whose root element is identical.<see-also> may have the <relationship> of a different work version only if both are class 1 files and both share the same work.Every element with a <location> 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 a <see-also> pointing to an older or new version.If a target file does not explicitly give the <body>'s @in-progress the value of true() a warning will be returned. Target file is marked as being in progress.If a target file has a <see-also> marked as a new version (update) a warning will be returned.If @when-accessed predates one or more dates in a target file, a warning will be returned.Class 1 files must share the same source as any alternatively divided edition.Class 1 files must share the same work as any model or alternatively divided edition.Class 1 files must share the same work-version, if supplied, as any alternatively divided edition.Class 1 files must have identical transcriptions, after TAN normalization, as any alternatively divided edition.A class 1 file may have no more than one model.If a class 1 file diverges from the structure of its model a warning will be generated specifying where differences exist.<code><see-also></code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:model-object-refs" TAN-version="2018">
<head>
.........
<source>
.........
</source>
<see-also relationship="ade">
<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.sem.xml" when-accessed="2016-07-07T16:36:28.867-04:00"/>
</see-also><see-also relationship="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-obj.xml" when-accessed="2016-07-07T16:36:28.867-04:00"/>
</see-also>
<definitions>
.........
</definitions>
.........
</head>
.........
</TAN-T>
Taken from ar.cat.eng.1926.edghill.obj<code><see-also></code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2018">
<head>
.........
<source>
.........
</source>
<see-also relationship="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-sem.xml" when-accessed="2016-02-10T14:08:52.058-05:00"/>
</see-also><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-obj.xml" when-accessed="2016-02-11T12:40:42.823-05:00"/>
</see-also><see-also relationship="ade">
.........
</see-also>
.........
</head>
.........
</TAN-T>
Taken from ar.cat.eng.1926.edghill.sem<code><skip></code>The element skip marks parts of a source that have been ignored or should be skipped, either shallowly (default) or deeply.Note, the shallow skip of a <div> may result in the source with leaf divs that have the same reference, breaking the Leaf Div Uniqueness Rule (LDUR). See 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). Formal Definition~ed-stamp?,
(~inclusion | (@shallow?, (@n | @ref | @div-type)?))Defined at:
TAN-class-2.rngUsed by: ~alter-class-2If more than one <skip> applies to a <div> only the first will be applied.Every div type reference must be valid in every source<code><skip></code> <alter src="fra">
<skip div-type="sec"/>
<rename ref="1 1-3" new="1 1 1-3"/>
.........
</alter>
Taken from ar.cat.tan-a-div<code><skip></code> <alter src="ger">
<skip div-type="Gedicht"/>
<rename n="v" by="-1"/>
</alter>
Taken from ringoroses.div.1<code><skip></code> <alter src="ger">
<skip div-type="Gedicht"/>
</alter>
Taken from ringoroses.01+03.token.1<code><skip></code> <alter src="ger">
<skip div-type="Gedicht"/>
<rename ref="5" new="4"/>
</alter>
Taken from ringoroses.01+03.token.2<code><source></code>The element source identifies the source upon which the data in the <body> of the current file depends.TAN-T and TAN-A-lm allow only one <source>. TAN-A-tok allows exactly two. All other TAN formats require one or more. Formal Definition~ed-stamp?,
(~inclusion |
(
{[TAN-A-div (~source-id-opt):] @xml:id} OR
{[TAN-A-tok (~source-id-opt):] @xml:id} OR
{[TAN-class-3 (~source-id-opt):] @xml:id?} OR
{[TAN-core (~source-id-opt):] {empty}},
(<comment>* & (
((<IRI>+, ~metadata-human) | @which) |
((<IRI>+, ~metadata-human, <checksum>*, <location>+) | @which) |
(@href | (<IRI>, ~metadata-human, <checksum>*, <location>+))))))Defined at:
TAN-core.rngUsed by: ~source-listEvery element with a <location> 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 a <see-also> pointing to an older or new version.If a target file does not explicitly give the <body>'s @in-progress the value of true() a warning will be returned. Target file is marked as being in progress.If a target file has a <see-also> marked as a new version (update) a warning will be returned.If @when-accessed predates one or more dates in a target file, a warning will be returned.Sources are integral parts of a class 2 TAN file. Access to at least one copy is absolutely mandatory.<for-lang> and <source> are mutually exclusive in a TAN-A-lm file.<code><source></code> <head>
.........
<licensor who="kalvesmaki"/>
<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>
<see-also relationship="ade">
.........
</see-also>
.........
</head>
Taken from ar.cat.eng.1926.edghill.obj<code><source></code> <head>
.........
<licensor who="kalvesmaki"/>
<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>
<see-also relationship="model">
.........
</see-also>
.........
</head>
Taken from ar.cat.eng.1926.edghill.sem<code><source></code> <head>
.........
<licensor who="kalvesmaki"/>
<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>
<see-also relationship="ade">
.........
</see-also>
.........
</head>
Taken from ar.cat.fra.1844.saint-hilaire.sem-native<code><source></code> <head>
.........
<licensor who="kalvesmaki"/>
<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>
<see-also relationship="ade">
.........
</see-also>
.........
</head>
Taken from ar.cat.fra.1844.saint-hilaire.sem<code><subject></code>The element subject points to text references that act as the subject of the claim. Multiple values of <subject> are interpreted to mean "and", resulting in distribution of the claim (e.g., subject="x y" becomes "x [verby]..." and "y [verb]...").Formal Definition~ed-stamp?,
(~simple-textual-reference | ~complex-textual-reference-set)Defined at:
TAN-A-div.rngUsed by: ~claim, ~subjectNo <tok> should duplicate any sibling <tok>.Every <claim> must have at least one subject, either @subject (self or ancestral <body>) or a child <subject><code><subject></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-div.claims<code><subject></code> <claim verb="is-about" object="predication">
<subject work="grc" ref="1 1"/>
</claim>
Taken from ar.cat.tan-a-div<code><tail></code>The element tail permits any arbitrary content. This element is suitable as a placeholder for temporary data, especially to facilitate time-consuming validation routines. Formal Definition
(<[ANY]>* & text)Defined at:
TAN-core.rngUsed by: ~TAN-root<code><TAN-A-div></code>The element TAN-A-div specifies that the file is a div-based TAN alignment file. Root element.Formal Definition~TAN-rootDefined at:
TAN-A-div.rngUsers 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 versions of TAN that are semi-stable. This version of TAN is semi-stable. RELAX-NG schemas will be changed only to correct egregious errors. Other files might be edited, but most efforts on improvement will be spent on future versions.<code><TAN-A-div></code><TAN-A-div TAN-version="2018" id="tag:parkj@textalign.net,2015:ar.cat.tan-a-div:claims">
<head>
.........
</head>
<body claimant="lmp">
.........
</body>
</TAN-A-div>Taken from ar.cat.tan-a-div.claims<code><TAN-A-div></code><TAN-A-div TAN-version="2018" id="tag:parkj@textalign.net,2015:ar.cat.tan-a-div">
<head>
.........
</head>
<body claimant="park">
.........
</body>
</TAN-A-div>Taken from ar.cat.tan-a-div<code><TAN-A-div></code><TAN-A-div TAN-version="2018" id="tag:parkj@textalign.net,2015:ring01-TAN-A-ring02">
<head>
.........
</head>
<body claimant="park"/>
</TAN-A-div>Taken from ringoroses.div.1<code><TAN-A-lm></code>The element TAN-A-lm specifies that the file is a TAN file containing lexico-morphology data about a text. Root element.Formal Definition~TAN-rootDefined at:
TAN-A-lm.rngUsers 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 versions of TAN that are semi-stable. This version of TAN is semi-stable. RELAX-NG schemas will be changed only to correct egregious errors. Other files might be edited, but most efforts on improvement will be spent on future versions.<code><TAN-A-lm></code><TAN-A-lm TAN-version="2018" 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">
.........
</body>
</TAN-A-lm>Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-LM-sample<code><TAN-A-lm></code><TAN-A-lm TAN-version="2018" id="tag:parkj@textalign.net,2015:ring01-lm">
<head>
.........
</head>
<body lexicon="english" morphology="penn" in-progress="false">
.........
</body>
</TAN-A-lm>Taken from ring-o-roses.eng.1881.lm<code><TAN-A-tok></code>The element TAN-A-tok specifies that the file is a token-based TAN alignment file. Root element.Formal Definition~TAN-rootDefined at:
TAN-A-tok.rngUsers 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 versions of TAN that are semi-stable. This version of TAN is semi-stable. RELAX-NG schemas will be changed only to correct egregious errors. Other files might be edited, but most efforts on improvement will be spent on future versions.<code><TAN-A-tok></code><TAN-A-tok TAN-version="2018" id="tag:parkj@textalign.net,2015:TAN-A-tok,ring01+ring02">
<head>
.........
</head>
<body bitext-relation="B-descends-from-A" reuse-type="adaptation" in-progress="false">
.........
</body>
</TAN-A-tok>Taken from ringoroses.01+02.token.1<code><TAN-A-tok></code><TAN-A-tok TAN-version="2018" id="tag:parkj@textalign.net,2015:TAN-A-tok,ring01+ring03">
<head>
.........
</head>
<body reuse-type="correlationGeneral" bitext-relation="unclear">
.........
</body>
</TAN-A-tok>Taken from ringoroses.01+03.token.1<code><TAN-A-tok></code><TAN-A-tok TAN-version="2018" id="tag:parkj@textalign.net,2015:TAN-A-tok,ring01+ring03:alt">
<head>
.........
</head>
<body reuse-type="correlationGeneral" bitext-relation="unclear">
.........
</body>
</TAN-A-tok>Taken from ringoroses.01+03.token.2<code><TAN-key></code>The element TAN-key specifies that the TAN file contains vocabulary suitable for inclusion in other TAN files. Root element.Formal Definition~TAN-rootDefined at:
TAN-key.rngUsers 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 versions of TAN that are semi-stable. This version of TAN is semi-stable. RELAX-NG schemas will be changed only to correct egregious errors. Other files might be edited, but most efforts on improvement will be spent on future versions.<code><TAN-key></code><TAN-key TAN-version="2018" id="tag:parkj@textalign.net,2015:TAN-key:ar.cat">
<head>
.........
</head>
<body in-progress="true" affects-element="work">
.........
</body>
</TAN-key>Taken from ar.cat.TAN-key<code><TAN-key></code><TAN-key TAN-version="2018" id="tag:textalign.net,2015:tan-key:bitext-relation">
<head>
.........
</head>
<body in-progress="true" affects-element="bitext-relation">
.........
</body>
</TAN-key>Taken from bitext-relations.TAN-key<code><TAN-key></code><TAN-key TAN-version="2018" id="tag:textalign.net,2015:tan-key:div-types">
<head>
.........
</head>
<body in-progress="false" affects-element="div-type">
.........
</body>
</TAN-key>Taken from div-types.TAN-key<code><TAN-key></code><TAN-key TAN-version="2018" id="tag:textalign.net,2015:tan-key:features">
<head>
.........
</head>
<body in-progress="false" affects-element="feature">
.........
</body>
</TAN-key>Taken from features.TAN-key<code><TAN-mor></code>The element TAN-mor specifies that the TAN file contains definitions for the parts of speech for a language, the codes for those parts, and the rules for combining them. Root element.Formal Definition~TAN-rootDefined at:
TAN-mor.rngUsers 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 versions of TAN that are semi-stable. This version of TAN is semi-stable. RELAX-NG schemas will be changed only to correct egregious errors. Other files might be edited, but most efforts on improvement will be spent on future versions.<code><TAN-mor></code><TAN-mor TAN-version="2018" 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-T></code>The element TAN-T specifies that the TAN file contains a transcription. Root element.Formal Definition~TAN-root{empty}Defined at:
TAN-T.rng, TAN-core.rngUsers 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 versions of TAN that are semi-stable. This version of TAN is semi-stable. RELAX-NG schemas will be changed only to correct egregious errors. Other files might be edited, but most efforts on improvement will be spent on future versions.<code><TAN-T></code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:model-object-refs" TAN-version="2018">
<head>
.........
</head>
<body xml:lang="eng">
.........
</body>
</TAN-T>Taken from ar.cat.eng.1926.edghill.obj<code><TAN-T></code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="2018">
<head>
.........
</head>
<body xml:lang="eng">
.........
</body>
</TAN-T>Taken from ar.cat.eng.1926.edghill.sem<code><TAN-T></code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.fra.1844.saint-hilaire:semantic-refs" TAN-version="2018">
<head>
.........
</head>
<body xml:lang="fra">
.........
</body>
</TAN-T>Taken from ar.cat.fra.1844.saint-hilaire.sem-native<code><TAN-T></code><TAN-T TAN-version="2018" 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.sem<code><to></code>The element to indicates a ref to which the preceding <tok>s should be moved.The element to points to a single token that is the end of a range of tokens to be selectedFormal Definition@ref
(@val | @pos | (@val, @pos))Defined at:
TAN-class-2.rngUsed by: ~alt-reassign, ~tok-ref-rangeNo alter action should result in the mixing of leaf <div>s and non-leaf <div>s.In a ranged <tok> in a <reassign>, the token referred to by <from> must precede the one referred to by <to>.<code><to></code> <head>
.........
<alter src="fra">
.........
<reassign>
<tok ref="5 5" pos="1-27"/>
<to ref="5 1 5"/>
</reassign>
<reassign>
<tok ref="5 5">
<from val="Ceci"/>
<to pos="4" val="corps"/>
</tok>
<to ref="5 1 6"/>
</reassign>
<reassign>
<tok ref="5 5">
<from val="Il"/>
<to val="exister"/>
</tok>
.........
</reassign>
.........
</alter>
.........
</head>
Taken from ar.cat.tan-a-div<code><tok></code>The element tok identifies one or more words or word fragments. Used by class 2 files to make assertions about specific words. In TAN-A-div and TAN-A-tok files, <tok> has no linguistic connotations; in TAN-A-lm, it normally does.<tok>s that are restricted to a single token, or a portion of a single token. This is the normal behavior of <tok>. Multiple values in @src, @ref, and @pos will result in expansion across all values. But multiple values of @chars are taken to refer to the constituent parts of a single <tok> and so no expansion occurs on @chars.This syntax allows multiple <tok>s to be collapsed into a single one, to save space and perhaps enhance legibility. For example, a <tok> with 2 values for @src, 3 for @ref, 4 for @pos, and 5 for @chars will result in a <tok> that points to 24 tokens, each of which is filtered to the same five characters (by position, not content). Put another way, <tok src="X" ref="a" pos="1"/> and <tok src="X" ref="a" pos="2"/> is always identical to <tok src="X" ref="a" pos="1-2"/>If you wish to treat multiple word fragments as a single token, use <group>.Formal Definition~certainty-stamp?, @val~ed-stamp?,
{[TAN-A-div (~tok-sources-ref-opt):] {empty}} OR
{[TAN-class-2 (~tok-sources-ref-opt):]
{{[TAN-A-lm (~sources-ref):] {empty}}} OR
{{[TAN-class-2 (~sources-ref):] @src}} OR
{{[TAN-core (~sources-ref):] {empty}}}}, @ref,
(@val | @pos | (@val, @pos)),
{[TAN-A-div (~tok-cert-opt):] {empty}} OR
{[TAN-class-2 (~tok-cert-opt):]
(@cert | (@cert, @cert2))?}, @chars?~ed-stamp?, @ref, (
(@val | @pos | (@val, @pos)) | ~tok-range-selector)Defined at:
TAN-A-lm.rng, TAN-class-2.rngUsed by: ~lm-tok-ref, ~alt-reassign, ~tok-ref, ~tok-ref-groupEvery token must be locatable in every cited ref in every source.<tok> must reference a leaf <div>.Every character must be locatable in every token in every ref in every source.No <tok> should duplicate any sibling <tok>.In a ranged <tok> in a <reassign>, the token referred to by <from> must precede the one referred to by <to>.<code><tok></code><TAN-A-div TAN-version="2018" id="tag:parkj@textalign.net,2015:ar.cat.tan-a-div:claims">
.........
<body claimant="lmp">
.........
<claim subject="dexippus porphyry">
<claim subject="andronicus boethus" adverb="perhaps" verb="omits">
<object src="grc">
<tok ref="1 a 2" pos="3-4"/>
</object>
</claim>
</claim>
<claim subject="herminus comm-omnes" verb="agrees">
<locus src="grc">
<tok ref="1 a 2" pos="3-4"/>
</locus>
</claim>
.........
<claim subject="B" verb="replaces">
<locus src="grc">
<tok ref="1 a 5" pos="1-2"/>
</locus>
.........
</claim>
<claim subject="Λ" adverb="perhaps" verb="replaces">
<locus src="grc">
<tok ref="1 a 5" pos="1-2"/>
</locus>
.........
</claim>
<claim subject="π α φ ο" verb="agrees">
<locus src="grc">
<tok ref="1 a 5" pos="1-2"/>
</locus>
</claim>
.........
</body>
</TAN-A-div>
Taken from ar.cat.tan-a-div.claims<code><token-definition></code>The element token-definition takes a regular expression to define a word token. This element will be used to segment a string into token and non-token components. This element takes attributes that function as the parameters for the function xsl:analyze-string (see https://www.w3.org/TR/xslt-30/#element-analyze-string).For more see Formal Definition~ed-stamp?,
(~inclusion |
(
{[TAN-A-lm (~sources-ref):] {empty}} OR
{[TAN-class-2 (~sources-ref):] @src} OR
{[TAN-core (~sources-ref):] {empty}},
(@which | (@pattern, @flags?))))Defined at:
TAN-core.rngUsed by: ~defn-class-1, ~definition-class-2, ~entity-tok-defNo source may be given more than one token definition.<code><token-definition></code> <definitions>
<comment when="2016-02-22-05:00" who="park">The following token definition treats the
following as words: sequences of letters, any individual character that is neither a
letter nor a space (i.e., punctuation).</comment>
<token-definition src="eng-us" pattern="[-\w]+"/>
<person xml:id="park">
.........
</person>
.........
</definitions>
Taken from ringoroses.div.1<code><token-definition></code> <definitions>
<token-definition pattern="[\w]+"/>
<lexicon xml:id="LSJ">
.........
</lexicon>
.........
</definitions>
Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-LM-sample<code><token-definition></code> <definitions>
.........
<lexicon xml:id="english">
.........
</lexicon>
<token-definition which="letters and punctuation"/>
<person xml:id="park">
.........
</person>
.........
</definitions>
Taken from ring-o-roses.eng.1881.lm<code><token-definition></code> <definitions>
.........
<reuse-type xml:id="adaptation">
.........
</reuse-type>
<token-definition src="ring1881 ring1987" which="letters"/>
<person xml:id="park">
.........
</person>
.........
</definitions>
Taken from ringoroses.01+02.token.1<code><topic></code>The element topic declares one or more topics, to be used in conjunction with @topic under <align> to associate alignments with specific topics instead of verbatim parallels. Formal Definition~defn-pattern-defaultDefined at:
TAN-A-div.rngUsed by: ~defn-claims<code><topic></code> <definitions>
.........
<verb which="is about" xml:id="is-about"/>
<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>
</definitions>
Taken from ar.cat.tan-a-div<code><unit></code>The element unit contains an IRI + name pattern identifying a unit type (e.g., millimeters, seconds, Euros), to be used in conjunction with <object> to specify the meaning of a valueFormal Definition~defn-pattern-defaultDefined at:
TAN-A-div.rngUsed by: ~defn-claims<code><value></code>The element value states the value of a <checksum>Formal Definitionstring Defined at:
TAN-core.rngUsed by: <checksum><code><value></code> <checksum>
.........
<name>SHA-1</name>
<value>91D95564ABDF2B2C1B9EEF016CBA51E8179646CC</value>
</checksum>
Taken from patricius.confessio.2003.eng<code><verb></code>The element verb contains an IRI + name pattern identifying a property, relationship, action, or something else that is used to say something about something. The preferred term "verb" is equivalent to RDF "predicate." The latter term is avoided as misleading, since in ordinary usage the term "predicate" implies everything in a sentence that is not the subject.Formal Definition~object-constraint?, ~defn-pattern-defaultDefined at:
TAN-A-div.rngUsed by: ~defn-claimsClaims involving verbs whose object is constrained must use <object>, not @object.Verbs that have object constraints must not be combined with other verbs in @verb.<code><verb></code> <head>
.........
<definitions>
.........
<alias xml:id="comm-omnes" idrefs="π δ αd φd οd ηd σd"/>
<verb xml:id="omits" which="omits"/><verb xml:id="agrees" which="agrees"/><verb xml:id="replaces" which="replaces" object-datatype="string"/><verb xml:id="quotes" which="quotes"/><verb which="refers or alludes to" xml:id="refers-to"/>
.........
</definitions>
.........
</head>
Taken from ar.cat.tan-a-div.claims<code><version></code>The element version identifies the version of a work. Applicable to sources that contain multiple versions, e.g., original text and facing translations. Like <work>, <version> points to a conceptual entity, not a physical one.In the context of a class 1 file, the entity identified by <version> is assumed to be a version of the entity defined in <work>. In TAN-c files, however, no relationship is assumed between <version> and any putative work, unless explicitly stated in that file. 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 Formal Definition~defn-pattern-defaultDefined at:
TAN-core.rngUsed by: ~defn-claims, ~defn-class-1<code><version></code> <definitions>
<work>
.........
</work>
<version>
<IRI>urn:uuid:31648039-3dbb-49b9-b66e-9bd2cd11630e</IRI>
<name>zweite Version</name>
</version>
<div-type xml:id="Zeile">
.........
</div-type>
.........
</definitions>
Taken from ring-o-roses.deu.1897<code><where></code>The element where identifies a condition that must be true for the following actions to be evaluated.The condition must be true for at least one value in every attribute.Formal Definition~ed-stamp?,
{[TAN-mor (~action-condition-attributes):] ~action-condition-attributes} OR
{[TAN-class-2 (~action-condition-attributes):] ~action-condition-attributes} OR
{[TAN-core (~action-condition-attributes):] {empty}}Defined at:
TAN-core.rng<code><work></code>The element work identifies a creative textual work, understood conceptually, not physically (e.g., Homer's Iliad, not a particular version or copy of it).The term "work" is only loosely defined in TAN. Any text that has enough unity to be referred to in ordinary conversation as a single entity may be identified as a work. A work may be composed of other works, be a part of other works, or even overlap with other works. E.g., the Lord's Prayer, the Gospel of Luke, the Tetravengelion, the New Testament, and the Bible are all valid works, despite the complex relationship between each of them.This element takes the IRI + name pattern. For more, see Formal Definition~defn-pattern-defaultDefined at:
TAN-core.rngUsed by: ~defn-claims, ~defn-class-1A work element may invoke no more than one inclusion.<code><work></code> <definitions>
<work>
<IRI>http://dbpedia.org/resource/Categories_(Aristotle)</IRI>
<name>Aristotle, Categories</name>
</work>
<div-type xml:id="p">
.........
</div-type>
.........
</definitions>
Taken from ar.cat.eng.1926.edghill.obj<code><work></code> <definitions>
<work>
<IRI>http://dbpedia.org/resource/Categories_(Aristotle)</IRI>
<name>Aristotle, Categories</name>
</work>
<div-type xml:id="ch">
.........
</div-type>
.........
</definitions>
Taken from ar.cat.eng.1926.edghill.sem<code><work></code> <definitions>
<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>
<div-type xml:id="ch">
.........
</div-type>
.........
</definitions>
Taken from ar.cat.fra.1844.saint-hilaire.sem-native<code><work></code> <definitions>
<work>
<IRI>http://dbpedia.org/resource/Categories_(Aristotle)</IRI>
<name>Aristotle, Categories</name>
</work>
<div-type xml:id="ch">
.........
</div-type>
.........
</definitions>
Taken from ar.cat.fra.1844.saint-hilaire.semTAN patterns<code>~abstract-tok-ref</code>Formal Definition<tok>Defined at:
TAN-A-lm.rngUsed by: ~lm-tok-ref<code>~action-complex-condition</code>Formal Definition<where>+Defined at:
TAN-core.rngUsed by: ~action-condition<code>~action-condition</code>Formal Definition(
{{[TAN-mor (~action-condition-attributes):] ~action-condition-attributes}} OR
{{[TAN-class-2 (~action-condition-attributes):] ~action-condition-attributes}} OR
{{[TAN-core (~action-condition-attributes):] {empty}}} | <where>+)Defined at:
TAN-core.rngUsed by: ~morphology-rule, ~alter-condition<code>~action-condition-attributes</code>Formal Definition@m-matches?, @tok-matches?, @m-has-features?, @m-has-how-many-features?
{[TAN-A-lm (~sources-ref):] {empty}} OR
{[TAN-class-2 (~sources-ref):] @src} OR
{[TAN-core (~sources-ref):] {empty}}, @div-type?{empty}Defined at:
TAN-mor.rng, TAN-class-2.rng, TAN-core.rngUsed by: ~condition-pattern, ~action-simple-condition, ~action-complex-condition<code>~action-simple-condition</code>Formal Definition
{[TAN-mor (~action-condition-attributes):] ~action-condition-attributes} OR
{[TAN-class-2 (~action-condition-attributes):] ~action-condition-attributes} OR
{[TAN-core (~action-condition-attributes):] {empty}}Defined at:
TAN-core.rngUsed by: ~action-condition<code>~agent-ref</code>Formal Definition@whoDefined at:
TAN-core.rngUsed by: ~comment, ~nonsource-license, ~resp-item, ~change-log<code>~alignment</code>Formal Definition<align>Defined at:
TAN-A-tok.rngUsed by: ~body-item<code>~alignment-attributes-non-class-2</code>TAN-A-tok: alignments may claim bitext relations and reuse typeFormal Definition@xml:id?, @bitext-relation?, @reuse-type?Defined at:
TAN-A-tok.rngUsed by: ~alignment<code>~alignment-content-non-class-2</code>TAN-A-tok: alignments must contain one or more toksFormal Definition
(<tok> | <group> | <tok>)+Defined at:
TAN-A-tok.rngUsed by: ~alignment<code>~alignment-inclusion-opt</code>Formal Definition~inclusionDefined at:
TAN-A-tok.rngUsed by: ~alignment<code>~alt-equate</code>Formal Definition<equate>Defined at:
TAN-class-2.rngUsed by: ~alter-class-2<code>~alt-norm</code>Formal Definition<normalization>Defined at:
TAN-class-1.rngUsed by: ~alter-non-core<code>~alt-reassign</code>Formal Definition<reassign>Defined at:
TAN-class-2.rngUsed by: ~alter-class-2<code>~alt-rename</code>Formal Definition<rename>Defined at:
TAN-class-2.rngUsed by: ~alter-class-2<code>~alt-repl</code>TAN-class-1: Replacements that have been made to an XML source file. Formal Definition<replace>Defined at:
TAN-class-1.rngUsed by: ~alter-non-core<code>~alt-skip</code>Formal Definition<skip>Defined at:
TAN-class-2.rngUsed by: ~alter-class-2<code>~alter-class-2</code>Formal Definition<skip>*, <rename>*, <equate>*, <reassign>*Defined at:
TAN-class-2.rngUsed by: ~alter-non-core<code>~alter-class-3</code>Formal Definition{empty}Defined at:
TAN-class-3.rngUsed by: ~alter-non-core<code>~alter-condition</code>Formal Definition
(
{{{[TAN-mor (~action-condition-attributes):] ~action-condition-attributes}}} OR
{{{[TAN-class-2 (~action-condition-attributes):] ~action-condition-attributes}}} OR
{{{[TAN-core (~action-condition-attributes):] {empty}}}} | <where>+){empty}Defined at:
TAN-class-2.rng, TAN-core.rngUsed by: ~alter-element<code>~alter-core</code>Formal Definition{empty}Defined at:
TAN-core.rngUsed by: ~alter-element<code>~alter-element</code>Formal Definition<alter>Defined at:
TAN-core.rngUsed by: ~alter-statement<code>~alter-non-class-2</code>Formal Definition{empty}{empty}{empty}{empty}Defined at:
TAN-A-div.rng, TAN-A-lm.rng, TAN-A-tok.rng, TAN-class-2.rngUsed by: ~alter-non-core<code>~alter-non-class-3</code>Formal Definition{empty}Defined at:
TAN-class-3.rngUsed by: ~alter-non-core<code>~alter-non-core</code>Formal Definition(<normalization>* & <replace>*)~alter-class-2,
{[TAN-A-div (~alter-non-class-2):] {empty}} OR
{[TAN-A-lm (~alter-non-class-2):] {empty}} OR
{[TAN-A-tok (~alter-non-class-2):] {empty}} OR
{[TAN-class-2 (~alter-non-class-2):] {empty}}({empty} & {empty}){empty}Defined at:
TAN-class-1.rng, TAN-class-2.rng, TAN-class-3.rng, TAN-core.rngUsed by: ~alter-element<code>~alter-statement</code>TAN-core: normalizations are defined at more specific levelsFormal Definition<alter>*<alter>?Defined at:
TAN-class-2.rng, TAN-core.rngUsed by: ~TAN-head<code>~any-attribute</code>Formal Definition@[ANY]Defined at:
TAN-core.rngUsed by: ~any-element<code>~any-content</code>Formal Definition(<[ANY]>* & text)Defined at:
TAN-core.rngUsed by: ~TAN-tail, ~any-element<code>~any-element</code>Formal Definition<[ANY]>Defined at:
TAN-core.rngUsed by: ~any-content<code>~assert</code>Formal Definition<assert>Defined at:
TAN-mor.rngUsed by: ~morphology-rule<code>~attr-cert</code>Formal Definition@certDefined at:
TAN-core.rngUsed by: ~cert-claim<code>~attr-cert2</code>Formal Definition@cert2Defined at:
TAN-core.rngUsed by: ~cert-claim<code>~bitext-relation-attr</code>Formal Definition@bitext-relationDefined at:
TAN-A-tok.rngUsed by: ~body-attributes-non-core, ~alignment-attributes-non-class-2<code>~body-attributes-non-core</code>Formal Definition@lexicon, @morphology@bitext-relation, @reuse-type@affects-element?@xml:lang{empty}Defined at:
TAN-A-lm.rng, TAN-A-tok.rng, TAN-key.rng, TAN-T.rng, TAN-core.rngUsed by: ~TAN-body<code>~body-content-class-1</code>Formal Definition{empty}Defined at:
TAN-class-1.rngUsed by: ~body-content-non-core<code>~body-content-class-2</code>Formal Definition{empty}Defined at:
TAN-class-2.rngUsed by: ~body-content-non-core<code>~body-content-class-3</code>Formal Definition{empty}Defined at:
TAN-class-3.rngUsed by: ~body-content-non-core<code>~body-content-core</code>Formal Definition<comment>*Defined at:
TAN-core.rngUsed by: ~TAN-body<code>~body-content-non-class-1</code>Formal Definition
{[TAN-T (~body-item):] <div>} OR
{[TAN-core (~body-item):] {empty}}+{empty}Defined at:
TAN-T.rng, TAN-class-1.rngUsed by: ~body-content-non-core<code>~body-content-non-class-2</code>TAN-A-div: Redefining TAN-body-core not only defines what is in the body of a TAN-A-div but also excludes groups from it.Formal Definition@claimant?, @subject?, @object?, @verb?, <claim>*<for-lang>*?, (
{[TAN-A-lm (~body-item):] <ana>} OR
{[TAN-core (~body-item):] {empty}}* & <group>*)(<group>* &
{[TAN-A-tok (~body-item):] <align>} OR
{[TAN-core (~body-item):] {empty}}*){empty}Defined at:
TAN-A-div.rng, TAN-A-lm.rng, TAN-A-tok.rng, TAN-class-2.rngUsed by: ~body-content-non-core<code>~body-content-non-class-3</code>Formal Definition(<group>* &
{[TAN-key (~body-item):] <item>} OR
{[TAN-core (~body-item):] {empty}}*)~TAN-R-mor-body{empty}Defined at:
TAN-key.rng, TAN-mor.rng, TAN-class-3.rngUsed by: ~body-content-non-core<code>~body-content-non-core</code>Formal Definition({empty} &
{[TAN-T (~body-content-non-class-1):]
{{[TAN-T (~body-item):] <div>}} OR
{{[TAN-core (~body-item):] {empty}}}+} OR
{[TAN-class-1 (~body-content-non-class-1):] {empty}})({empty} &
{[TAN-A-div (~body-content-non-class-2):] ~body-content-non-class-2} OR
{[TAN-A-lm (~body-content-non-class-2):] ~body-content-non-class-2} OR
{[TAN-A-tok (~body-content-non-class-2):]
(<group>* &
{{[TAN-A-tok (~body-item):] <align>}} OR
{{[TAN-core (~body-item):] {empty}}}*)} OR
{[TAN-class-2 (~body-content-non-class-2):] {empty}})({empty} &
{[TAN-key (~body-content-non-class-3):]
(<group>* &
{{[TAN-key (~body-item):] <item>}} OR
{{[TAN-core (~body-item):] {empty}}}*)} OR
{[TAN-mor (~body-content-non-class-3):] ~TAN-R-mor-body} OR
{[TAN-class-3 (~body-content-non-class-3):] {empty}}){empty}Defined at:
TAN-class-1.rng, TAN-class-2.rng, TAN-class-3.rng, TAN-core.rngUsed by: ~TAN-body<code>~body-group</code>Formal Definition{empty}<group>Defined at:
TAN-class-1.rng, TAN-core.rngUsed by: ~body-content-non-class-2, ~body-content-non-class-3, ~body-group<code>~body-item</code>Formal Definition<ana><align><item><div>{empty}Defined at:
TAN-A-lm.rng, TAN-A-tok.rng, TAN-key.rng, TAN-T.rng, TAN-core.rngUsed by: ~body-content-non-class-2, ~body-content-non-class-3, ~body-content-non-class-1, ~body-group<code>~category</code>Formal Definition<category>Defined at:
TAN-mor.rngUsed by: ~category-list<code>~category-list</code>Formal Definition<category>*Defined at:
TAN-mor.rngUsed by: ~TAN-R-mor-body<code>~cert-claim</code>Formal Definition
(@cert | (@cert, @cert2))Defined at:
TAN-core.rngUsed by: ~claim, ~tok-cert-opt, ~certainty-stamp<code>~cert-content</code>Formal Definitiondouble (pattern 1|0|(0\.\d*[1-9]))Defined at:
TAN-core.rngUsed by: ~attr-cert, ~attr-cert2<code>~certainty-stamp</code>Formal Definition
(@cert | (@cert, @cert2))?, ~ed-stamp?Defined at:
TAN-core.rngUsed by: ~TAN-A-lm-item, ~abstract-tok-ref, ~lexeme, ~morph, ~alignment<code>~change-log</code>Formal Definition<change>+Defined at:
TAN-core.rngUsed by: ~TAN-head<code>~char-ref</code>Formal Definition@charsDefined at:
TAN-class-2.rngUsed by: ~tok-ref-item<code>~checksum</code>Formal Definition<checksum>Defined at:
TAN-core.rngUsed by: ~entity-digital-tan-other-ref, ~entity-digital-generic-ref<code>~claim</code>Formal Definition<claim>Defined at:
TAN-A-div.rngUsed by: ~body-content-non-class-2, ~complex-object<code>~claimant-ref</code>Formal Definition@claimantDefined at:
TAN-A-div.rngUsed by: ~body-content-non-class-2, ~claim<code>~code</code>Formal Definition@codeDefined at:
TAN-mor.rngUsed by: ~feature-ref<code>~comment</code>Formal Definition<comment>Defined at:
TAN-core.rngUsed by: ~TAN-A-lm-item, ~alignment, ~category, ~alt-norm, ~func-replace, ~TAN-head, ~nonsource-license, ~inclusion-item, ~key-item, ~source-item, ~see-also-item, ~definition-list, ~alter-element, ~body-content-core, ~defn-pattern-default, ~defn-pattern-id, ~defn-pattern-no-id, ~defn-pattern-language<code>~complex-object</code>Formal Definition(<object> | <claim>+)Defined at:
TAN-A-div.rngUsed by: ~object<code>~complex-rename</code>Formal Definition(@n | @ref), (@by | @new)Defined at:
TAN-class-2.rngUsed by: ~alt-rename<code>~complex-subject</code>Formal Definition<subject>Defined at:
TAN-A-div.rngUsed by: ~subject<code>~complex-text-ref</code>Formal Definition(<div-ref> |
(<tok> | <group> | <tok>))Defined at:
TAN-A-div.rngUsed by: ~complex-textual-reference-set<code>~complex-textual-reference-set</code>Formal Definition(
{[TAN-class-2 (~sources-ref):] @src} OR
{[TAN-core (~sources-ref):] {empty}} | @work),
(<div-ref> |
(<tok> | <group> | <tok>))+Defined at:
TAN-A-div.rngUsed by: ~textual-reference<code>~condition-m-has-features</code>Formal Definition@m-has-featuresDefined at:
TAN-mor.rngUsed by: ~action-condition-attributes<code>~condition-m-has-how-many-features</code>Formal Definition@m-has-how-many-featuresDefined at:
TAN-mor.rngUsed by: ~action-condition-attributes<code>~condition-m-matches</code>Formal Definition@m-matchesDefined at:
TAN-mor.rngUsed by: ~action-condition-attributes<code>~condition-pattern</code>TAN-mor: Test pattern attributes for determining whether to return the message provided by text.Formal Definition@flags?,
{[TAN-mor (~action-condition-attributes):] ~action-condition-attributes} OR
{[TAN-core (~action-condition-attributes):] {empty}}, textDefined at:
TAN-mor.rngUsed by: ~assert, ~report<code>~condition-tok-matches</code>Formal Definition@tok-matchesDefined at:
TAN-mor.rngUsed by: ~action-condition-attributes<code>~definition-class-2</code>Formal Definition(<token-definition>* & <group-type>*)Defined at:
TAN-class-2.rngUsed by: ~definition-non-core<code>~definition-class-3</code>Formal Definition<group-type>*Defined at:
TAN-class-3.rngUsed by: ~definition-non-core<code>~definition-core</code>Formal Definition(
(<person> | <organization> | <algorithm>)+ & <role>+ & <period>* & <alias>* & <relationship>* & <ambiguous-letter-numerals-are-roman>?)Defined at:
TAN-core.rngUsed by: ~definition-list<code>~definition-list</code>Formal Definition<definitions>Defined at:
TAN-core.rngUsed by: ~TAN-head<code>~definition-non-class-2</code>Formal Definition
(<work>* & <place>* & <unit>* & <modal>* & <version>* & <scriptum>* & <topic>* & <verb>*)(<lexicon>+ & <morphology>+)(<bitext-relation>+ & <reuse-type>++){empty}Defined at:
TAN-A-div.rng, TAN-A-lm.rng, TAN-A-tok.rng, TAN-class-2.rngUsed by: ~definition-non-core<code>~definition-non-class-3</code>Formal Definition{empty}<feature>*{empty}Defined at:
TAN-key.rng, TAN-mor.rng, TAN-class-3.rngUsed by: ~definition-non-core<code>~definition-non-core</code>Formal Definition(
(<work> & <version>? & <div-type>+ & <token-definition>*) & {empty})(
(<token-definition>* & <group-type>*) &
{[TAN-A-div (~definition-non-class-2):]
(<work>* & <place>* & <unit>* & <modal>* & <version>* & <scriptum>* & <topic>* & <verb>*)} OR
{[TAN-A-lm (~definition-non-class-2):]
(<lexicon>+ & <morphology>+)} OR
{[TAN-A-tok (~definition-non-class-2):]
(<bitext-relation>+ & <reuse-type>++)} OR
{[TAN-class-2 (~definition-non-class-2):] {empty}})(<group-type>* &
{[TAN-key (~definition-non-class-3):] {empty}} OR
{[TAN-mor (~definition-non-class-3):] <feature>*} OR
{[TAN-class-3 (~definition-non-class-3):] {empty}}){empty}Defined at:
TAN-class-1.rng, TAN-class-2.rng, TAN-class-3.rng, TAN-core.rngUsed by: ~definition-list<code>~defn-agent</code>Formal Definition(<person> | <organization> | <algorithm>)Defined at:
TAN-core.rngUsed by: ~definition-core<code>~defn-alg</code>Formal Definition<algorithm>Defined at:
TAN-core.rngUsed by: ~defn-agent<code>~defn-alias</code>Formal Definition<alias>Defined at:
TAN-core.rngUsed by: ~definition-core<code>~defn-ambig-numerals</code>Formal Definition<ambiguous-letter-numerals-are-roman>Defined at:
TAN-core.rngUsed by: ~definition-core<code>~defn-brel</code>Formal Definition<bitext-relation>Defined at:
TAN-A-tok.rngUsed by: ~definition-non-class-2<code>~defn-claims</code>Formal Definition(<work>* & <place>* & <unit>* & <modal>* & <version>* & <scriptum>* & <topic>* & <verb>*)Defined at:
TAN-A-div.rngUsed by: ~definition-non-class-2<code>~defn-class-1</code>Formal Definition(<work> & <version>? & <div-type>+ & <token-definition>*)Defined at:
TAN-class-1.rngUsed by: ~definition-non-core<code>~defn-div-type</code>Formal Definition<div-type>Defined at:
TAN-class-1.rngUsed by: ~defn-class-1<code>~defn-features</code>Formal Definition<feature>*Defined at:
TAN-mor.rngUsed by: ~definition-non-class-3<code>~defn-group-type</code>Formal Definition<group-type>Defined at:
TAN-core.rngUsed by: ~definition-class-2, ~definition-class-3<code>~defn-id-ref-opt</code>TAN-A-div: definitions by default have idsTAN-A-tok: all definitions must have idsTAN-key: all definitions must have idsTAN-core: Option to allow an @xml:id in children of <definitions>Formal Definition@xml:id@xml:id@xml:id{empty}Defined at:
TAN-A-div.rng, TAN-A-tok.rng, TAN-key.rng, TAN-core.rngUsed by: ~alt-norm, ~defn-pattern-default, ~defn-pattern-language<code>~defn-lexi</code>Formal Definition<lexicon>Defined at:
TAN-A-lm.rngUsed by: ~definition-non-class-2<code>~defn-mode</code>Formal Definition<modal>Defined at:
TAN-A-div.rngUsed by: ~defn-claims<code>~defn-morph</code>Formal Definition<morphology>Defined at:
TAN-A-lm.rngUsed by: ~definition-non-class-2<code>~defn-non-class-1</code>TAN-class-1: Reserved for definitions specific to individual types of class 1 filesFormal Definition{empty}Defined at:
TAN-class-1.rngUsed by: ~definition-non-core<code>~defn-org</code>Formal Definition<organization>Defined at:
TAN-core.rngUsed by: ~defn-agent<code>~defn-pattern-default</code>Formal Definition~ed-stamp?,
(~inclusion |
(
{[TAN-A-div (~defn-id-ref-opt):] @xml:id} OR
{[TAN-A-tok (~defn-id-ref-opt):] @xml:id} OR
{[TAN-key (~defn-id-ref-opt):] @xml:id} OR
{[TAN-core (~defn-id-ref-opt):] {empty}}, (<comment>* &
((<IRI>+, ~metadata-human) | @which))))Defined at:
TAN-core.rngUsed by: ~defn-place, ~defn-scri, ~defn-topic, ~defn-verb, ~defn-unit, ~defn-mode, ~defn-brel, ~defn-reus, ~defn-work, ~defn-vers<code>~defn-pattern-id</code>Formal Definition~ed-stamp?,
(~inclusion |
(@xml:id, (<comment>* &
((<IRI>+, ~metadata-human) | @which))))Defined at:
TAN-core.rngUsed by: ~feature, ~defn-div-type, ~defn-alg, ~defn-group-type, ~defn-org, ~defn-pers, ~defn-role<code>~defn-pattern-language</code>Formal Definition~ed-stamp?,
(~inclusion |
(
{[TAN-A-div (~defn-id-ref-opt):] @xml:id} OR
{[TAN-A-tok (~defn-id-ref-opt):] @xml:id} OR
{[TAN-key (~defn-id-ref-opt):] @xml:id} OR
{[TAN-core (~defn-id-ref-opt):] {empty}},
(<comment>* & (<for-lang>*,
((<IRI>+, ~metadata-human) | @which)))))Defined at:
TAN-core.rng<code>~defn-pattern-no-id</code>Formal Definition~ed-stamp?,
(~inclusion | (<comment>* &
((<IRI>+, ~metadata-human) | @which)))Defined at:
TAN-core.rng<code>~defn-period</code>Formal Definition<period>Defined at:
TAN-core.rngUsed by: ~definition-core<code>~defn-pers</code>Formal Definition<person>Defined at:
TAN-core.rngUsed by: ~defn-agent<code>~defn-place</code>Formal Definition<place>Defined at:
TAN-A-div.rngUsed by: ~defn-claims<code>~defn-relationship</code>Formal Definition<relationship>Defined at:
TAN-core.rngUsed by: ~definition-core<code>~defn-reus</code>Formal Definition<reuse-type>+Defined at:
TAN-A-tok.rngUsed by: ~definition-non-class-2<code>~defn-role</code>Formal Definition<role>Defined at:
TAN-core.rngUsed by: ~definition-core<code>~defn-scri</code>Formal Definition<scriptum>Defined at:
TAN-A-div.rngUsed by: ~defn-claims<code>~defn-tok-def</code>Formal Definition<token-definition>Defined at:
TAN-core.rngUsed by: ~defn-class-1, ~definition-class-2, ~entity-tok-def<code>~defn-topic</code>Formal Definition<topic>Defined at:
TAN-A-div.rngUsed by: ~defn-claims<code>~defn-unit</code>Formal Definition<unit>Defined at:
TAN-A-div.rngUsed by: ~defn-claims<code>~defn-verb</code>Formal Definition<verb>Defined at:
TAN-A-div.rngUsed by: ~defn-claims<code>~defn-vers</code>Formal Definition<version>Defined at:
TAN-core.rngUsed by: ~defn-claims, ~defn-class-1<code>~defn-work</code>Formal Definition<work>Defined at:
TAN-core.rngUsed by: ~defn-claims, ~defn-class-1<code>~div-item-ref</code>TAN-core: String that specifies a range of divs using the div-ref pattern joined by a hyphen or a comma.TAN-core: String that specifies a single <div>Formal Definitionstring (pattern (\w+([^\w\-]\w+)*)|.*\?\?\?.*)Defined at:
TAN-core.rngUsed by: ~new-ref-name, ~pointer-to-div-item<code>~div-range-ref</code>Formal Definitionstring (pattern (\w+([^\w\-]\w+)*)(((\s*-\s*)|(\s*,\s+))(\w+([^\w\-]\w+)*))*|.*\?\?\?.*)Defined at:
TAN-core.rngUsed by: ~pointer-to-div-range<code>~div-ref-range</code>Formal Definition<div-ref>Defined at:
TAN-class-2.rngUsed by: ~complex-text-ref<code>~div-type-ref</code>Formal Definition@div-typeDefined at:
TAN-class-2.rngUsed by: ~action-condition-attributes, ~alt-skip<code>~ed-agent</code>Formal Definition@ed-whoDefined at:
TAN-core.rngUsed by: ~ed-stamp<code>~ed-stamp</code>TAN-core: Editorial stamp: who created or edited the enclosed data and when. Formal Definition@ed-who, @ed-whenDefined at:
TAN-core.rngUsed by: ~claim, ~complex-subject, ~object-element, ~locus, ~defn-morph, ~defn-lexi, ~TAN-A-lm-item, ~TAN-key-item, ~category, ~morphology-rule, ~text-div, ~alt-norm, ~func-replace, ~alt-skip, ~alt-rename, ~alt-equate, ~alt-reassign, ~div-ref-range, ~tok-ref-item, ~tok-ref-group, ~tok-ref-range, ~certainty-stamp, ~action-complex-condition, ~IRI-gen-ref, ~loc-self, ~loc-src, ~metadata-desc, ~TAN-root, ~TAN-head, ~nonsource-license, ~inclusion-item, ~key-item, ~source-item, ~see-also-item, ~definition-list, ~alter-element, ~resp-item, ~change-log, ~TAN-body, ~body-group, ~defn-pattern-default, ~defn-pattern-id, ~defn-pattern-no-id, ~defn-pattern-language, ~defn-alias, ~defn-period, ~defn-relationship, ~defn-tok-def<code>~ed-time</code>Formal Definition@ed-whenDefined at:
TAN-core.rngUsed by: ~ed-stamp<code>~element-scope</code>Formal Definition@affects-elementDefined at:
TAN-core.rngUsed by: ~body-attributes-non-core, ~group-attributes, ~TAN-key-item<code>~entity-digital-generic-ref</code>TAN-core: Reference to an external digital entity that is not a TAN fileFormal Definition
((<IRI>+, ~metadata-human, <checksum>*, <location>+) | @which)Defined at:
TAN-core.rngUsed by: ~defn-lexi, ~TAN-key-item, ~source-item, ~see-also-item<code>~entity-digital-tan-other-ref</code>TAN-core: Reference to an external digital entity that is a TAN file; unlike other types, the keyword-ref option much be turned on and off for specific elements (e.g., not advisable for <inclusion>)Formal Definition
(@href | (<IRI>, ~metadata-human, <checksum>*, <location>+))Defined at:
TAN-core.rngUsed by: ~defn-morph, ~TAN-key-item, ~metadata-human, ~inclusion-item, ~key-item, ~source-item, ~see-also-item<code>~entity-digital-tan-self-ref</code>TAN-core: Reference to self as digital entity (i.e., TAN file)Formal Definition~metadata-human, <master-location>*Defined at:
TAN-core.rngUsed by: ~head-prelude-core<code>~entity-nondigital-ref</code>TAN-core: Reference to an external non-digital entity (e.g., persons, roles, works, topics)Formal Definition
((<IRI>+, ~metadata-human) | @which)Defined at:
TAN-core.rngUsed by: ~defn-lexi, ~TAN-key-item, ~alt-norm, ~checksum, ~nonsource-license, ~source-item, ~defn-pattern-default, ~defn-pattern-id, ~defn-pattern-no-id, ~defn-pattern-language, ~defn-relationship<code>~entity-tok-def</code>Formal Definition<token-definition>, ~metadata-humanDefined at:
TAN-core.rngUsed by: ~TAN-key-item<code>~error-flag</code>Formal Definition@flagsDefined at:
TAN-core.rngUsed by: ~condition-pattern, ~change-log<code>~feature</code>TAN-mor: TAN-R-mor files declare the morphological features that are allowed for a given languageFormal Definition<feature>Defined at:
TAN-mor.rngUsed by: ~defn-features<code>~feature-ref</code>Formal Definition<feature>Defined at:
TAN-mor.rngUsed by: ~category<code>~func-param-flags</code>Formal Definition@flagsDefined at:
TAN-core.rngUsed by: ~func-replace, ~defn-tok-def<code>~func-param-pattern</code>Formal Definition@patternDefined at:
TAN-core.rngUsed by: ~func-replace, ~defn-tok-def<code>~func-replace</code>Formal Definition<replace>Defined at:
TAN-class-1.rngUsed by: ~alt-repl<code>~grammar-attr</code>Formal Definition@morphologyDefined at:
TAN-A-lm.rngUsed by: ~body-attributes-non-core, ~morph<code>~group-attributes</code>Formal Definition@type?, @affects-element?@type?, @n?Defined at:
TAN-key.rng, TAN-core.rngUsed by: ~tok-ref-group, ~body-group<code>~group-ref</code>Formal Definition@groupDefined at:
TAN-core.rngUsed by: ~TAN-A-lm-item, ~non-class-2-opt, ~TAN-key-item<code>~head-prelude</code>Formal Definition~head-prelude-core, {empty}Defined at:
TAN-core.rngUsed by: ~TAN-head<code>~head-prelude-core</code>Formal Definition~entity-digital-tan-self-ref, ~nonsource-licenseDefined at:
TAN-core.rngUsed by: ~head-prelude<code>~head-prelude-non-core</code>Formal Definition{empty}Defined at:
TAN-core.rngUsed by: ~head-prelude<code>~help-opt</code>Formal Definition@helpDefined at:
TAN-core.rngUsed by: ~inclusion<code>~href-opt</code>Formal Definition@hrefDefined at:
TAN-core.rngUsed by: ~entity-digital-tan-other-ref, ~loc-self, ~loc-src<code>~id-option</code>TAN-class-2: Option to include an internal id. Not needed in TAN-A-lm files.Formal Definition{empty}@xml:idDefined at:
TAN-A-lm.rng, TAN-class-2.rng<code>~inclusion</code>Formal Definition@include, @help?Defined at:
TAN-core.rngUsed by: ~claim, ~defn-morph, ~defn-lexi, ~TAN-A-lm-item, ~alignment-inclusion-opt, ~TAN-key-item, ~category, ~morphology-rule, ~text-div, ~alt-norm, ~func-replace, ~alt-skip, ~alt-rename, ~alt-equate, ~alt-reassign, ~tok-ref-group, ~nonsource-license, ~key-item, ~source-item, ~see-also-item, ~alter-element, ~resp-item, ~body-group, ~defn-pattern-default, ~defn-pattern-id, ~defn-pattern-no-id, ~defn-pattern-language, ~defn-alias, ~defn-period, ~defn-relationship, ~defn-tok-def<code>~inclusion-att</code>Formal Definition@includeDefined at:
TAN-core.rngUsed by: ~inclusion<code>~inclusion-item</code>Formal Definition<inclusion>Defined at:
TAN-core.rngUsed by: ~inclusion-list<code>~inclusion-list</code>Formal Definition<inclusion>*Defined at:
TAN-core.rngUsed by: ~TAN-head<code>~increment</code>Formal Definition@byDefined at:
TAN-class-2.rngUsed by: ~complex-rename<code>~internal-idrefs</code>Formal Definition@idrefsDefined at:
TAN-core.rngUsed by: ~defn-alias<code>~internal-non-xml-id</code>Formal Definition@idDefined at:
TAN-core.rngUsed by: ~defn-alias<code>~internal-xml-id</code>Formal Definition@xml:idDefined at:
TAN-core.rngUsed by: ~defn-id-ref-opt, ~source-id-opt, ~defn-morph, ~defn-lexi, ~alignment-attributes-non-class-2, ~id-option, ~inclusion-item, ~defn-pattern-id, ~defn-alias, ~defn-period, ~defn-relationship<code>~IRI-gen</code>TAN-core: Any generic IRI identifier.Formal DefinitionanyURI (pattern [a-zA-Z][\-.+a-zA-Z0-9]+:\S+)Defined at:
TAN-core.rngUsed by: ~IRI-gen-ref<code>~IRI-gen-ref</code>Formal Definition<IRI>Defined at:
TAN-core.rngUsed by: ~entity-digital-tan-other-ref, ~entity-digital-generic-ref, ~entity-nondigital-ref<code>~item-picker</code>TAN-core: String that specifies a single item from a sequence: digits or "last(-digit)?" Similar to seq-picker.Formal Definitionstring (pattern ((last|max)|((last|max)-\d+)|(\d+))|.*\?\?\?.*)Defined at:
TAN-core.rngUsed by: ~item-pos-ref<code>~item-pos-ref</code>Formal Definition@posDefined at:
TAN-class-2.rngUsed by: ~tok-single-selector-attributes<code>~key-item</code>Formal Definition<key>Defined at:
TAN-core.rngUsed by: ~key-list<code>~key-list</code>Formal Definition<key>*Defined at:
TAN-core.rngUsed by: ~TAN-head<code>~keyword-ref</code>Formal Definition@whichDefined at:
TAN-core.rngUsed by: ~defn-morph, ~entity-digital-generic-ref, ~entity-nondigital-ref, ~metadata-human, ~defn-tok-def<code>~lang-of-content</code>Formal Definition@xml:langDefined at:
TAN-core.rngUsed by: ~nontextual-reference, ~body-attributes-non-core, ~text-div, ~metadata-desc<code>~lang-outside</code>Formal Definition<for-lang>Defined at:
TAN-core.rngUsed by: ~defn-morph, ~lang-preface, ~TAN-R-mor-body, ~defn-pattern-language<code>~lang-preface</code>Formal Definition<for-lang>*Defined at:
TAN-A-lm.rngUsed by: ~body-content-non-class-2<code>~lexeme</code>Formal Definition<l>Defined at:
TAN-A-lm.rngUsed by: ~TAN-A-lm-item<code>~lexicon-attr</code>Formal Definition@lexiconDefined at:
TAN-A-lm.rngUsed by: ~body-attributes-non-core, ~lexeme<code>~licensor</code>Formal Definition@licensorDefined at:
TAN-core.rng<code>~lm-tok-ref</code>Formal Definition(
(<tok> | <group> | <tok>) | <tok>)Defined at:
TAN-A-lm.rngUsed by: ~TAN-A-lm-item<code>~loc-self</code>Formal Definition<master-location>Defined at:
TAN-core.rngUsed by: ~entity-digital-tan-self-ref<code>~loc-src</code>Formal Definition<location>Defined at:
TAN-core.rngUsed by: ~entity-digital-tan-other-ref, ~entity-digital-generic-ref<code>~locus</code>Formal Definition<locus>+Defined at:
TAN-A-div.rngUsed by: ~claim<code>~metadata-desc</code>Formal Definition~ed-stamp?, (@xml:lang?,
string (pattern (.|\n)+))Defined at:
TAN-core.rngUsed by: ~metadata-human<code>~metadata-human</code>Formal Definition<name>+, <desc>*Defined at:
TAN-core.rngUsed by: ~entity-digital-tan-other-ref, ~entity-digital-generic-ref, ~entity-digital-tan-self-ref, ~entity-nondigital-ref, ~entity-tok-def<code>~modal-ref</code>Formal Definition@adverbDefined at:
TAN-A-div.rngUsed by: ~claim<code>~morph</code>Formal Definition<m>Defined at:
TAN-A-lm.rngUsed by: ~TAN-A-lm-item<code>~morphology-rule</code>Formal Definition<rule>Defined at:
TAN-mor.rngUsed by: ~TAN-R-mor-body<code>~n</code>Formal Definition@nDefined at:
TAN-core.rngUsed by: ~text-div, ~alt-skip, ~simple-rename, ~complex-rename, ~alt-equate, ~group-attributes<code>~new-name</code>Formal Definition@newDefined at:
TAN-class-2.rngUsed by: ~simple-rename, ~complex-rename<code>~new-ref-name</code>Formal Definition@newDefined at:
TAN-class-2.rngUsed by: ~simple-rename<code>~non-class-2-opt</code>Formal Definition@group?Defined at:
TAN-A-tok.rngUsed by: ~alignment<code>~nonsource-license</code>Formal Definition<license>, <licensor>Defined at:
TAN-core.rngUsed by: ~head-prelude-core<code>~nontextual-reference</code>Formal Definition(@xml:lang | @units)?, textDefined at:
TAN-A-div.rngUsed by: ~object-element<code>~object</code>Formal Definition(@object |
(<object> | <claim>+)+)Defined at:
TAN-A-div.rngUsed by: ~claim<code>~object-constraint</code>Formal Definition@object-datatype, @object-lexical-constraint?Defined at:
TAN-A-div.rngUsed by: ~defn-verb<code>~object-datatype</code>Formal Definition@object-datatypeDefined at:
TAN-A-div.rngUsed by: ~object-constraint<code>~object-element</code>Formal Definition<object>Defined at:
TAN-A-div.rngUsed by: ~complex-object<code>~object-lexical-constraint</code>Formal Definition@object-lexical-constraintDefined at:
TAN-A-div.rngUsed by: ~object-constraint<code>~object-ref</code>Formal Definition@objectDefined at:
TAN-A-div.rngUsed by: ~body-content-non-class-2, ~object<code>~period-ref</code>TAN-core: specifies whether the creation and editing of the data is still in progress. Default value is true.Formal Definition@periodDefined at:
TAN-core.rngUsed by: ~claim, ~resp-item<code>~place-ref</code>Formal Definition@whereDefined at:
TAN-A-div.rngUsed by: ~claim<code>~pointer-to-div-item</code>Formal Definition@refDefined at:
TAN-class-2.rngUsed by: ~alt-skip, ~simple-rename, ~target-div-ref, ~tok-ref-range<code>~pointer-to-div-range</code>Formal Definition@refDefined at:
TAN-class-2.rngUsed by: ~simple-textual-reference, ~complex-rename, ~div-ref-range, ~tok-ref-item<code>~progress</code>Formal Definition@in-progressDefined at:
TAN-core.rngUsed by: ~TAN-body<code>~relationship</code>Formal Definition@relationshipDefined at:
TAN-core.rngUsed by: ~see-also-item<code>~report</code>Formal Definition<report>Defined at:
TAN-mor.rngUsed by: ~morphology-rule<code>~resp-item</code>Formal Definition<resp>Defined at:
TAN-core.rngUsed by: ~resp-list<code>~resp-list</code>Formal Definition<resp>+Defined at:
TAN-core.rngUsed by: ~TAN-head<code>~reuse-type-attr</code>Formal Definition@reuse-typeDefined at:
TAN-A-tok.rngUsed by: ~body-attributes-non-core, ~alignment-attributes-non-class-2<code>~role-ref</code>Formal Definition@rolesDefined at:
TAN-core.rngUsed by: ~resp-item<code>~see-also-item</code>Formal Definition<see-also>Defined at:
TAN-core.rngUsed by: ~see-also-list<code>~see-also-list</code>Formal Definition<see-also>*Defined at:
TAN-core.rngUsed by: ~TAN-head<code>~seq-picker</code>TAN-core: String that specifies a range of items in a sequence: digits or "last(-digit)?" joined by hyphens (ranges) or commas. Similar to item-picker.Formal Definitionstring (pattern ((last|max|all|\*)|((last|max)-\d+)|(\d+))(\s*-\s*(((last|max))|((last|max)-\d+)|(\d+)))?(\s*[, ]\s*(((last|max))|((last|max)-\d+)|(\d+))(\s+-\s+(((last|max))|((last|max)-\d+)|(\d+)))?)*|.*\?\?\?.*)Defined at:
TAN-core.rngUsed by: ~condition-m-has-how-many-features, ~seq-pos-ref, ~char-ref<code>~seq-pos-ref</code>Formal Definition@posDefined at:
TAN-class-2.rngUsed by: ~tok-mult-selector-attributes<code>~shallow-option</code>Formal Definition@shallowDefined at:
TAN-class-2.rngUsed by: ~alt-skip<code>~simple-rename</code>Formal Definition
((@n, @new) | (@ref, @new))Defined at:
TAN-class-2.rngUsed by: ~alt-rename<code>~simple-textual-reference</code>Formal Definition(
{[TAN-class-2 (~sources-ref):] @src} OR
{[TAN-core (~sources-ref):] {empty}} | @work), @refDefined at:
TAN-A-div.rngUsed by: ~textual-reference<code>~source-id-opt</code>TAN-A-div: TAN-A-div sources must be namedTAN-A-tok: TAN-A-tok sources must be namedTAN-core: Parameter to indicate whether <source> should be allowed to take xml:id (forbidden for TAN files with only one source; mandated otherwise)Formal Definition@xml:id@xml:id@xml:id?{empty}Defined at:
TAN-A-div.rng, TAN-A-tok.rng, TAN-class-3.rng, TAN-core.rngUsed by: ~source-item<code>~source-item</code>Formal Definition<source>Defined at:
TAN-core.rngUsed by: ~source-list<code>~source-list</code>TAN-A-div: TAN-A-div files must have one or more sourcesTAN-A-tok: TAN-A-tok files take exactly two sourcesTAN-class-3: Class 3 files allow zero or many sourcesFormal Definition<source>+<source>?<source>, <source>{empty}<source>*<source>Defined at:
TAN-A-div.rng, TAN-A-lm.rng, TAN-A-tok.rng, TAN-key.rng, TAN-class-3.rng, TAN-core.rngUsed by: ~TAN-head<code>~source-ref</code>Formal Definition@srcDefined at:
TAN-class-2.rng<code>~sources-ref</code>TAN-A-lm: Because TAN-A-lm files depend on only one source, no id references to sources are neededTAN-class-2: All sources are TAN files, so no source rights should be declared--they're already statedFormal Definition{empty}@src{empty}Defined at:
TAN-A-lm.rng, TAN-class-2.rng, TAN-core.rngUsed by: ~simple-textual-reference, ~complex-textual-reference-set, ~action-condition-attributes, ~tok-sources-ref-opt, ~defn-tok-def<code>~subject</code>Formal Definition(@subject | <subject>+)Defined at:
TAN-A-div.rngUsed by: ~claim<code>~subject-ref</code>Formal Definition@subjectDefined at:
TAN-A-div.rngUsed by: ~body-content-non-class-2, ~subject<code>~TAN-A-lm-item</code>Formal Definition<ana>Defined at:
TAN-A-lm.rngUsed by: ~body-item<code>~TAN-body</code>Formal Definition<body>Defined at:
TAN-core.rngUsed by: ~TAN-root<code>~TAN-head</code>Formal Definition<head>Defined at:
TAN-core.rngUsed by: ~TAN-root<code>~TAN-key-item</code>Formal Definition<item>Defined at:
TAN-key.rngUsed by: ~body-item<code>~TAN-R-mor-body</code>TAN-mor: TAN-R-mor body consists of zero or more assert, report, category, or optionsFormal Definition<for-lang>+, (<category>*? & <rule>*)Defined at:
TAN-mor.rngUsed by: ~body-content-non-class-3<code>~TAN-root</code>Formal Definition@id, @TAN-version, ~ed-stamp?, <head>, <body>, <tail>?Defined at:
TAN-core.rngUsed by: <TAN-A-div>, <TAN-A-lm>, <TAN-A-tok>, <TAN-key>, <TAN-mor>, <TAN-T><code>~TAN-tail</code>Formal Definition<tail>Defined at:
TAN-core.rngUsed by: ~TAN-root<code>~TAN-ver</code>Formal Definition@TAN-versionDefined at:
TAN-core.rngUsed by: ~TAN-root<code>~target-div-ref</code>Formal Definition<to>Defined at:
TAN-class-2.rngUsed by: ~alt-reassign<code>~text-div</code>Formal Definition<div>Defined at:
TAN-T.rngUsed by: ~body-item, ~text-div<code>~textual-reference</code>Formal Definition(~simple-textual-reference | ~complex-textual-reference-set)Defined at:
TAN-A-div.rngUsed by: ~complex-subject, ~object-element, ~locus<code>~tok-cert-opt</code>Formal Definition{empty}
(@cert | (@cert, @cert2))?Defined at:
TAN-A-div.rng, TAN-class-2.rngUsed by: ~tok-ref-item<code>~tok-mult-selector-attributes</code>Formal Definition
(@val | @pos | (@val, @pos))Defined at:
TAN-class-2.rngUsed by: ~tok-ref-item, ~tok-ref-range<code>~tok-range-selector</code>Formal Definition<from>, <to>Defined at:
TAN-class-2.rngUsed by: ~tok-ref-range<code>~tok-ref</code>Formal Definition(<tok> | <group> | <tok>)Defined at:
TAN-class-2.rngUsed by: ~complex-text-ref, ~lm-tok-ref, ~alignment-content-non-class-2<code>~tok-ref-group</code>Formal Definition<group>Defined at:
TAN-class-2.rngUsed by: ~tok-ref<code>~tok-ref-item</code>Formal Definition<tok>Defined at:
TAN-class-2.rngUsed by: ~tok-ref, ~tok-ref-group<code>~tok-ref-range</code>Formal Definition<tok>Defined at:
TAN-class-2.rngUsed by: ~alt-reassign, ~tok-ref<code>~tok-single-selector-attributes</code>Formal Definition
(@val | @pos | (@val, @pos))Defined at:
TAN-class-2.rngUsed by: ~tok-range-selector<code>~tok-sources-ref-opt</code>Formal Definition{empty}
{[TAN-A-lm (~sources-ref):] {empty}} OR
{[TAN-class-2 (~sources-ref):] @src} OR
{[TAN-core (~sources-ref):] {empty}}Defined at:
TAN-A-div.rng, TAN-class-2.rngUsed by: ~tok-ref-item<code>~token-value-ref</code>Formal Definition@valDefined at:
TAN-class-2.rngUsed by: ~abstract-tok-ref, ~tok-single-selector-attributes, ~tok-mult-selector-attributes<code>~type</code>Formal Definition@typeDefined at:
TAN-core.rngUsed by: ~group-attributes, ~category, ~feature-ref, ~text-div<code>~units</code>Formal Definition@unitsDefined at:
TAN-A-div.rngUsed by: ~nontextual-reference<code>~URI-tag</code>TAN-core: Tag URN, mandatory pattern for the IRI name of every TAN file Formal DefinitionanyURI (pattern tag:([\-a-zA-Z0-9._%+]+@)?[\-a-zA-Z0-9.]+\.[A-Za-z]{2,4},\d{4}(-(0\d|1[0-2]))?(-([0-2]\d|3[01]))?:\S+)Defined at:
TAN-core.rngUsed by: ~TAN-root<code>~verb-ref</code>Formal Definition@verbDefined at:
TAN-A-div.rngUsed by: ~body-content-non-class-2, ~claim<code>~when-claim</code>Formal Definition@whenDefined at:
TAN-core.rngUsed by: ~comment, ~change-log<code>~work-ref</code>Formal Definition@workDefined at:
TAN-A-div.rngUsed by: ~simple-textual-reference, ~complex-textual-reference-set