TAN patterns, elements, and attributes definedThe 81 elements and 60 attributes defined in TAN, excluding TEI, are the following::@adverb@affects-element<agent><agentrole><alias><align><ana><anchor-div-ref><assert>@bitext-relation<bitext-relation><body><category>@cert@cert2<change>@chars<checksum><claim>@claim-basis<claim-basis>@claimant@code<comment>@cont@context<declarations>@def-ref<desc><div><div-ref><div-type>@div-type-ref<div-type-ref>@ed-when@ed-who<equate-div-types><equate-works><feature>@feature-qty-test@feature-test<filter>@flags<for-lang>@from@group<group><group-type><head>@help@href@id@idrefs@in-progress@include<inclusion><IRI><item><key><l>@lexicon<lexicon><lm><location><locus><m><master-location>@matches-m@matches-tok<modal>@morphology<morphology>@n<name>@new<normalization>@object<object>@object-datatype@object-lexical-constraint@old<person><place>@pos<realign>@ref@regex<relationship><rename><rename-div-ns><replace>@replacement<report>@reuse-type<reuse-type><rights-excluding-sources>@rights-holder<rights-source-only><role>@roles<scriptum><see-also>@seg<source><split-leaf-div-at>@src@subject<subject><suppress-div-types><tail><TAN-A-div><TAN-A-tok><TAN-c><TAN-key><TAN-LM><TAN-mor><TAN-T>@TAN-version@to<tok><token-definition><topic><transliteration>@type<unit>@units@val<value>@verb<verb><version>@when<when>@when-accessed@where@which@who@work<work>@xml:id@xml:langThe 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.TAN-core elements and attributes summarized<code><agent></code>The element agent specifies a person or organization that played a direct or indirect role in preparing, creating, or editing the data.At least one <agent> must have an <IRI> that is a tag URN whose namespace matches that of the IRI name. By default, the first such <agent>, called the key agent, is taken to be the person or organization ultimately responsible for the assertions in the current file. See This element may also name a computer or algorithm that performed a task. This feature is useful for crediting software, e.g., an OCR program used to convert an image, or an algorithm that estimates word-to-word alignments.Formal Definition~ed-stamp?,
(~inclusion |
(@roles?, @xml:id, (<comment>* &
((<IRI>+, ~metadata-human) | @which))))Used by: ~TAN-headEvery 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.<code><agent></code> <head>
.........
<declarations>
.........
</declarations>
<agent roles="editor" xml:id="kalvesmaki">
<IRI>http://viaf.org/viaf/299582703</IRI>
<IRI>tag:kalvesmaki.com,2014:self</IRI>
<name xml:lang="eng">Joel Kalvesmaki</name>
</agent>
<role xml:id="editor">
.........
</role>
.........
</head>
Taken from ar.cat.eng.1926.edghill.obj<code><agent></code> <head>
.........
<declarations>
.........
</declarations>
<agent roles="editor" xml:id="kalvesmaki">
<IRI>http://viaf.org/viaf/299582703</IRI>
<IRI>tag:kalvesmaki.com,2014:self</IRI>
<name xml:lang="eng">Joel Kalvesmaki</name>
</agent>
<role xml:id="editor">
.........
</role>
.........
</head>
Taken from ar.cat.eng.1926.edghill.sem<code><agent></code> <head>
.........
<declarations>
.........
</declarations>
<agent roles="editor" xml:id="kalvesmaki">
<IRI>http://viaf.org/viaf/299582703</IRI>
<IRI>tag:kalvesmaki.com,2014:self</IRI>
<name xml:lang="eng">Joel Kalvesmaki</name>
</agent>
<role xml:id="editor">
.........
</role>
.........
</head>
Taken from ar.cat.fra.1844.saint-hilaire.sem-native<code><agent></code> <head>
.........
<declarations>
.........
</declarations>
<agent roles="editor" xml:id="kalvesmaki">
<IRI>http://viaf.org/viaf/299582703</IRI>
<IRI>tag:kalvesmaki.com,2014:self</IRI>
<name xml:lang="eng">Joel Kalvesmaki</name>
</agent>
<role xml:id="editor">
.........
</role>
.........
</head>
Taken from ar.cat.fra.1844.saint-hilaire.sem<code><agentrole></code>The element agentrole specifies a time period when one or more <agent>s held one or more <role>s.Formal Definition~ed-stamp?,
(~inclusion | (@who, @roles, <when>+))Used by: ~TAN-head<code><alias></code>The element alias assigns multiple values of xml:id to a single xml:id.Formal Definition~ed-stamp?,
(~inclusion | (@xml:id, @idrefs))Used by: ~declaration-coreA <alias> may not mix idrefs from different elements.<alias> references must not be circular.<code><alias></code> <head>
.........
<declarations>
.........
<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"/>
.........
</declarations>
.........
</head>
Taken from ar.cat.tan-a-div.claims<code><body></code>The element body contains the dataFormal Definition@in-progress?, ~ed-stamp?, (<comment>* &
{[TAN-A-div (~TAN-body-core):] ~TAN-body-core} OR
{[TAN-mor (~TAN-body-core):] ~TAN-R-mor-body} OR
{[TAN-core (~TAN-body-core):] ~TAN-body-core})Used 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="1 dev">
<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="1 dev">
<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="1 dev">
<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="1 dev" 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><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, text<code><change></code> <head>
.........
<role xml:id="editor">
.........
</role>
<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>
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="1 dev">
<head>
.........
<role xml:id="editor">
.........
</role>
<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-1-dev/examples/ar.cat.eng.1926.edghill.sem-201606220804250030400.xml.</change>
<change when="2016-01-26-04:00" who="kalvesmaki">Started new file.</change>
</head>
.........
</TAN-T>
Taken from ar.cat.eng.1926.edghill.sem<code><change></code> <head>
.........
<role xml:id="editor">
.........
</role>
<change when="2016-07-10" who="kalvesmaki">Began new file</change>
</head>
Taken from ar.cat.fra.1844.saint-hilaire.sem-native<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>Used 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><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, textUsed by: ~split, ~realignment, ~alignment, ~feature-pattern, ~feature-pattern-no-code, ~category, ~decl-div, ~decl-filt, ~decl-filt-norm, ~func-replace, ~decl-pattern-default, ~decl-pattern-no-id, ~decl-pattern-language, ~decl-group-type, ~TAN-head, ~TAN-body, ~nonsource-rights, ~inclusion-item, ~key-item, ~source-item, ~source-rights, ~see-also-item, ~decl-opt, ~agent-list, ~role-list, ~TAN-LM-item<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> <head>
.........
<declarations>
.........
</declarations>
<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>
<agent xml:id="park" roles="editor">
.........
</agent>
.........
</head>
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><declarations></code>The element declarations contains assumptions or decisions made that materially affect the interpretation of the data in <body>. Every TAN format's <declarations> is unique.Formal Definition~ed-stamp?, (<comment>* & <alias>* &
{[TAN-A-div (~declaration-items):]
(<token-definition>* & <suppress-div-types>* & <rename-div-ns>* & )} OR
{[TAN-A-tok (~declaration-items):]
(<token-definition>* & <suppress-div-types>* & <rename-div-ns>* & <bitext-relation>+ & <reuse-type>++ & <group-type>*)} OR
{[TAN-c (~declaration-items):] } OR
{[TAN-key (~declaration-items):] <group-type>*} OR
{[TAN-class-1 (~declaration-items):]
(
(<work> & <version>? & <div-type>+ & <token-definition>* & <filter>?) & {empty})} OR
{[TAN-core (~declaration-items):] {empty}} OR
{[TAN-LM-core (~declaration-items):]
(<token-definition>* & <suppress-div-types>* & <rename-div-ns>* & <lexicon>+ & <morphology>+ & <group-type>*)})Used by: ~TAN-head<code><declarations></code> <head>
.........
<see-also>
.........
</see-also>
<declarations>
<work>
.........
</work>
<div-type xml:id="p">
.........
</div-type>
<div-type xml:id="c">
.........
</div-type>
.........
</declarations>
<agent roles="editor" xml:id="kalvesmaki">
.........
</agent>
.........
</head>
Taken from ar.cat.eng.1926.edghill.obj<code><declarations></code> <head>
.........
<see-also>
.........
</see-also>
<declarations>
<work>
.........
</work>
<div-type xml:id="ch">
.........
</div-type>
<div-type xml:id="par">
.........
</div-type>
.........
</declarations>
<agent roles="editor" xml:id="kalvesmaki">
.........
</agent>
.........
</head>
Taken from ar.cat.eng.1926.edghill.sem<code><declarations></code> <head>
.........
<see-also>
.........
</see-also>
<declarations>
<work>
.........
</work>
<div-type xml:id="ch">
.........
</div-type>
<div-type xml:id="par">
.........
</div-type>
.........
</declarations>
<agent roles="editor" xml:id="kalvesmaki">
.........
</agent>
.........
</head>
Taken from ar.cat.fra.1844.saint-hilaire.sem-native<code><declarations></code> <head>
.........
<see-also>
.........
</see-also>
<declarations>
<work>
.........
</work>
<div-type xml:id="ch">
.........
</div-type>
<div-type xml:id="par">
.........
</div-type>
.........
</declarations>
<agent roles="editor" xml:id="kalvesmaki">
.........
</agent>
.........
</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>+))))All text must be normalized (Unicode NFC).<code><desc></code> <rights-excluding-sources rights-holder="kalvesmaki">
.........
<name>Creative Commons Attribution 4.0 International License</name>
<desc>Exclusive of rights held and licenses offered by rightsholders of the source or
sources listed below, this data file, insofar as it constitutes an independent work, is
licensed under a Creative Commons Attribution 4.0 International License.</desc>
</rights-excluding-sources>
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="1 dev">
<head>
.........
<rights-excluding-sources rights-holder="kalvesmaki">
.........
<name>Creative Commons Attribution 4.0 International License</name>
<desc>Exclusive of rights held and licenses offered by rightsholders of the source or
sources listed below, this data file, insofar as it constitutes an independent work, is
licensed under a Creative Commons Attribution 4.0 International License.</desc>
</rights-excluding-sources>
.........
<declarations>
.........
<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>
.........
</declarations>
.........
</head>
.........
</TAN-T>
Taken from ar.cat.eng.1926.edghill.sem<code><desc></code> <rights-excluding-sources rights-holder="kalvesmaki">
.........
<name>Creative Commons Attribution 4.0 International License</name>
<desc>Exclusive of rights held and licenses offered by rightsholders of the source or
sources listed below, this data file, insofar as it constitutes an independent work, is
licensed under a Creative Commons Attribution 4.0 International License.</desc>
</rights-excluding-sources>
Taken from ar.cat.fra.1844.saint-hilaire.sem-native<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 Used by: ~source-list, ~TAN-R-mor-body, ~decl-pattern-language, ~decl-morph, ~decl-lexi<code><for-lang></code> <head>
.........
<declarations>
.........
<lexicon xml:id="LSJ">
<for-lang>grc</for-lang>
<IRI>http://lccn.loc.gov/95032369</IRI>
.........
</lexicon>
<lexicon xml:id="Lampe">
<for-lang>grc</for-lang>
<IRI>http://lccn.loc.gov/77372171</IRI>
.........
</lexicon>
<lexicon xml:id="new">
<for-lang>grc</for-lang>
<IRI>urn:uuid:d6558d00-8f68-11e3-950a-425861b86ab6</IRI>
.........
</lexicon>
<morphology xml:id="Perseus">
<for-lang>grc</for-lang>
<IRI>tag:kalvesmaki.com,2014:tan-r-mor:grc:perseus</IRI>
.........
</morphology>
.........
</declarations>
.........
</head>
Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-LM-sample<code><group></code>The element group collects items that share a common property, defined by the <group-type> to which it refers.Formal Definition~ed-stamp?,
(~inclusion | (
{[TAN-key (~group-attributes):] ~group-attributes} OR
{[TAN-class-2 (~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-tok (~item):] <align>} OR
{[TAN-c (~item):] +} OR
{[TAN-key (~item):] <item>} OR
{[TAN-T (~item):] <div>} OR
{[TAN-core (~item):] {empty}} OR
{[TAN-LM-core (~item):] <ana>})*))Used by: ~body-group-opt, ~body-group@affects-element must include only names of TAN elements that accept @which<code><group></code><TAN-key TAN-version="1 dev" 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~ed-stamp?,
(~inclusion |
(@xml:id, (<comment>* &
((<IRI>+, ~metadata-human) | @which))))Used by: ~declaration-items, ~TAN-key-decl<code><group-type></code> <declarations>
.........
<morphology xml:id="Perseus">
.........
</morphology>
<group-type xml:id="status" which="status"/>
</declarations>
Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-LM-sample<code><group-type></code> <head>
.........
<declarations>
<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"/>
.........
</declarations>
.........
</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 <declarations>.Formal Definition~ed-stamp?,
(<comment>* &
(~entity-digital-tan-self-ref, <rights-excluding-sources>, (<inclusion>* & <key>* &
{[TAN-A-div (~source-list):] <source>+} OR
{[TAN-A-tok (~source-list):] ~source-list} OR
{[TAN-c (~source-list):] {empty}} OR
{[TAN-key (~source-list):] {empty}} OR
{[TAN-LM-lang (~source-list):] <for-lang>} OR
{[TAN-LM (~source-list):] <source>} OR
{[TAN-class-3 (~source-list):] <source>*} OR
{[TAN-core (~source-list):] <source>} & <see-also>*), <declarations>, <agent>+, <role>+, <agentrole>*, <change>+))Used 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="1 dev">
<head>
<name>Categories, Aristotle, English translation by E. M. Edghill</name>
<rights-excluding-sources rights-holder="kalvesmaki">
.........
</rights-excluding-sources>
<source>
.........
</source>
.........
</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="1 dev">
<head>
<name>Categories, Aristotle, English translation by E. M. Edghill</name>
<rights-excluding-sources rights-holder="kalvesmaki">
.........
</rights-excluding-sources>
<source>
.........
</source>
.........
</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="1 dev">
<head>
<name>Categories, Aristotle, French translation by J. Barthélemy Saint-Hilaire</name>
<rights-excluding-sources rights-holder="kalvesmaki">
.........
</rights-excluding-sources>
<source>
.........
</source>
.........
</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="1 dev" 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>
<rights-excluding-sources rights-holder="kalvesmaki">
.........
</rights-excluding-sources>
<source>
.........
</source>
.........
</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>+)))Used by: ~work-equiv, ~div-type-equiv, ~split, ~realignment, ~alignment-inclusion-opt, ~TAN-key-item, ~feature-pattern, ~feature-pattern-no-code, ~category, ~test-pattern, ~text-div, ~claim, ~decl-div, ~decl-filt-norm, ~func-replace, ~decl-supp-div-type, ~decl-rename-div-n, ~decl-pattern-default, ~decl-pattern-no-id, ~decl-pattern-language, ~decl-group-type, ~decl-tok-def, ~body-group, ~nonsource-rights, ~inclusion-list, ~key-item, ~source-item, ~source-rights, ~see-also-item, ~relationship, ~agent-list, ~role-list, ~agent-role-list, ~decl-alias, ~decl-morph, ~decl-lexi, ~TAN-LM-itemInclusions may not introduce duplicate values of @xml:id.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.Every inclusion should have at least one document available.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 @when-accessed predates one or more dates in a target file, a warning will be returned.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.<code><inclusion></code> <head>
.........
<rights-excluding-sources rights-holder="kalvesmaki">
.........
</rights-excluding-sources>
<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+)Used 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.No 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="1 dev">
<head>
.........
<rights-excluding-sources rights-holder="kalvesmaki">
<IRI>http://creativecommons.org/licenses/by/4.0/deed.en_US</IRI>
<name>Creative Commons Attribution 4.0 International License</name>
.........
</rights-excluding-sources>
<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 which="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>
<see-also>
<relationship which="alternatively divided edition"/>
<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>
.........
</head>
.........
</TAN-T>
Taken from ar.cat.eng.1926.edghill.obj<code><key></code>The element key specifies a tan:item from a TAN-key (predefined, or declared in a <key>) that defines the contents of an element that has @which.Any number of <key>s may be supplied, but all <item>s with unique names for the element indicated by @affects-elements.For more discussion, see Formal Definition~ed-stamp?,
(~inclusion | (<comment>* &
(@href | (<IRI>, ~metadata-human, <checksum>*, <location>+))))Used 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 @when-accessed predates one or more dates in a target file, a warning will be returned.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.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>
.........
<rights-excluding-sources rights-holder="park">
.........
</rights-excluding-sources>
<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><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, @hrefUsed 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 @when-accessed predates one or more dates in a target file, a warning will be returned.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.<code><location></code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:model-object-refs" TAN-version="1 dev">
<head>
.........
<see-also>
.........
<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>
<see-also>
.........
<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><location></code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="1 dev">
<head>
.........
<see-also>
.........
<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>
.........
<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><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?, @hrefUsed 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.<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-1-dev/examples/gomme.1989.ring-o-roses.xml"/>
<rights-excluding-sources rights-holder="park">
.........
</rights-excluding-sources>
.........
</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"/>
<rights-excluding-sources rights-holder="schmidt">
.........
</rights-excluding-sources>
.........
</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="ring-o-roses.eng.1881.xml"/>
<rights-excluding-sources which="by-nc-nd_2.0" rights-holder="park"/>
.........
</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="ring-o-roses.eng.1957.xml"/>
<rights-excluding-sources rights-holder="park">
.........
</rights-excluding-sources>
.........
</head>
Taken from ring-o-roses.eng.1957<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-descAll text must be normalized (Unicode NFC).Names may not duplicate reserved TAN keywords 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="1 dev">
<head>
<name>Categories, Aristotle, English translation by E. M. Edghill</name>
<rights-excluding-sources rights-holder="kalvesmaki">
<IRI>http://creativecommons.org/licenses/by/4.0/deed.en_US</IRI>
<name>Creative Commons Attribution 4.0 International License</name>
<desc>Exclusive of rights held and licenses offered by rightsholders of the source or
sources listed below, this data file, insofar as it constitutes an independent work, is
licensed under a Creative Commons Attribution 4.0 International License.</desc>
</rights-excluding-sources>
<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>
.........
<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>
<see-also>
.........
<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><relationship></code>The element relationship specifies the role that the item named by the parent <see-also> played. This may be either a reserved keyword or an IRI + name pattern that identifies a specific kind of relationship.See main.xml# keywords-relationship f or standardized vocabulary.Formal Definition~ed-stamp?, (~inclusion |
((<IRI>+, ~metadata-human) | @which))Used by: ~see-also-itemAny <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 TAN-c file must point to a TAN file whose root element is <TAN-c>.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.In class 1 files, alternative editions must share the same source.In class 1 files, alternative editions must share the same work.In class 1 files, alternative editions must share the same work-version, if supplied.In class 1 files, resegmented copies must have identical transcriptions, after TAN normalization.A class 1 file and its model must have the same work.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><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:model-object-refs" TAN-version="1 dev">
<head>
.........
<see-also>
<relationship which="model"/>
<IRI>tag:kalvesmaki.com,2014:tan-t:ar.cat.grc.1949.minio-paluello:object-refs</IRI>
.........
</see-also>
<see-also>
<relationship which="alternatively divided edition"/>
<IRI>tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs</IRI>
.........
</see-also>
.........
</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="1 dev">
<head>
.........
<see-also>
<relationship which="model"/>
<IRI>tag:kalvesmaki.com,2014:tan-t:ar.cat.grc.1949.minio-paluello:semantic-refs</IRI>
.........
</see-also>
<see-also>
<relationship which="different work version"/>
<IRI>tag:kalvesmaki.com,2014:tan-t:ar.cat.grc.1949.minio-paluello:object-refs</IRI>
.........
</see-also>
.........
</head>
.........
</TAN-T>
Taken from ar.cat.eng.1926.edghill.sem<code><rights-excluding-sources></code>The element rights-excluding-sources 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 |
(@rights-holder, (<comment>* &
((<IRI>+, ~metadata-human) | @which))))Used by: ~TAN-head<code><rights-excluding-sources></code> <head>
<name>Categories, Aristotle, English translation by E. M. Edghill</name>
<rights-excluding-sources rights-holder="kalvesmaki">
<IRI>http://creativecommons.org/licenses/by/4.0/deed.en_US</IRI>
<name>Creative Commons Attribution 4.0 International License</name>
<desc>Exclusive of rights held and licenses offered by rightsholders of the source or
sources listed below, this data file, insofar as it constitutes an independent work, is
licensed under a Creative Commons Attribution 4.0 International License.</desc>
</rights-excluding-sources>
<source>
.........
</source>
.........
</head>
Taken from ar.cat.eng.1926.edghill.obj<code><rights-excluding-sources></code> <head>
<name>Categories, Aristotle, English translation by E. M. Edghill</name>
<rights-excluding-sources rights-holder="kalvesmaki">
<IRI>http://creativecommons.org/licenses/by/4.0/deed.en_US</IRI>
<name>Creative Commons Attribution 4.0 International License</name>
<desc>Exclusive of rights held and licenses offered by rightsholders of the source or
sources listed below, this data file, insofar as it constitutes an independent work, is
licensed under a Creative Commons Attribution 4.0 International License.</desc>
</rights-excluding-sources>
<source>
.........
</source>
.........
</head>
Taken from ar.cat.eng.1926.edghill.sem<code><rights-excluding-sources></code> <head>
<name>Categories, Aristotle, French translation by J. Barthélemy Saint-Hilaire</name>
<rights-excluding-sources rights-holder="kalvesmaki">
<IRI>http://creativecommons.org/licenses/by/4.0/deed.en_US</IRI>
<name>Creative Commons Attribution 4.0 International License</name>
<desc>Exclusive of rights held and licenses offered by rightsholders of the source or
sources listed below, this data file, insofar as it constitutes an independent work, is
licensed under a Creative Commons Attribution 4.0 International License.</desc>
</rights-excluding-sources>
<source>
.........
</source>
.........
</head>
Taken from ar.cat.fra.1844.saint-hilaire.sem-native<code><rights-excluding-sources></code> <head>
<name>Realignment of Categories, Aristotle, French translation by J. Barthélemy
Saint-Hilaire</name>
<rights-excluding-sources rights-holder="kalvesmaki">
<IRI>http://creativecommons.org/licenses/by/4.0/deed.en_US</IRI>
<name>Creative Commons Attribution 4.0 International License</name>
<desc>Exclusive of rights held and licenses offered by rightsholders of the source or
sources listed below, this data file, insofar as it constitutes an independent work, is
licensed under a Creative Commons Attribution 4.0 International License.</desc>
</rights-excluding-sources>
<source>
.........
</source>
.........
</head>
Taken from ar.cat.fra.1844.saint-hilaire.sem<code><rights-source-only></code>The element rights-source-only states license and rights that are attached to the source of the data.For more discussion, see and for a list of vocabulary, main.xml# keywords-rights-excluding-sourcesFormal Definition~ed-stamp?,
(~inclusion |
(<comment>* & (@rights-holder*,
((<IRI>+, ~metadata-human) | @which))))Used by: ~source-item<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~ed-stamp?,
(~inclusion |
(@xml:id, (<comment>* &
((<IRI>+, ~metadata-human) | @which))))Used by: ~TAN-head<code><role></code> <head>
.........
<agent roles="editor" xml:id="kalvesmaki">
.........
</agent>
<role xml:id="editor">
<IRI>http://schema.org/editor</IRI>
<name xml:lang="eng">Editor</name>
</role>
<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>
Taken from ar.cat.eng.1926.edghill.obj<code><role></code> <head>
.........
<agent roles="editor" xml:id="kalvesmaki">
.........
</agent>
<role xml:id="editor">
<IRI>http://schema.org/editor</IRI>
<name xml:lang="eng">Editor</name>
</role>
<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-1-dev/examples/ar.cat.eng.1926.edghill.sem-201606220804250030400.xml.</change>
.........
</head>
Taken from ar.cat.eng.1926.edghill.sem<code><role></code> <head>
.........
<agent roles="editor" xml:id="kalvesmaki">
.........
</agent>
<role xml:id="editor">
<IRI>http://schema.org/editor</IRI>
<name xml:lang="eng">Editor</name>
</role>
<change when="2016-07-10" who="kalvesmaki">Began new file</change>
</head>
Taken from ar.cat.fra.1844.saint-hilaire.sem-native<code><role></code> <head>
.........
<agent roles="editor" xml:id="kalvesmaki">
.........
</agent>
<role xml:id="editor">
<IRI>http://schema.org/editor</IRI>
<name xml:lang="eng">Editor</name>
</role>
<change when="2016-07-10" who="kalvesmaki">Began new file</change>
.........
</head>
Taken from ar.cat.fra.1844.saint-hilaire.sem<code><see-also></code>The element see-also identifies auxiliary entities that were materially helpful in creating or editing the data, or are helpful in understanding the data.This element is especially useful for crediting third parties who provided a set of raw data that served as a starting point, or was consulted. Formal Definition~ed-stamp?,
(~inclusion |
(<comment>* &
(<relationship>, (
((<IRI>+, ~metadata-human) | @which) |
((<IRI>+, ~metadata-human, <checksum>*, <location>+) | @which) |
(@href | (<IRI>, ~metadata-human, <checksum>*, <location>+))))))Used 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 TAN-c file must point to a TAN file whose root element is <TAN-c>.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.In class 1 files, alternative editions must share the same source.In class 1 files, alternative editions must share the same work.In class 1 files, alternative editions must share the same work-version, if supplied.In class 1 files, resegmented copies must have identical transcriptions, after TAN normalization.A class 1 file and its model must have the same work.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.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 @when-accessed predates one or more dates in a target file, a warning will be returned.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.<code><see-also></code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:model-object-refs" TAN-version="1 dev">
<head>
.........
<source>
.........
</source>
<see-also>
<relationship which="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>
<see-also>
<relationship which="alternatively divided edition"/>
<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>
<declarations>
.........
</declarations>
.........
</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="1 dev">
<head>
.........
<source>
.........
</source>
<see-also>
<relationship which="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>
.........
</see-also>
<see-also>
<relationship which="different work version"/>
<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>
<see-also>
.........
</see-also>
.........
</head>
.........
</TAN-T>
Taken from ar.cat.eng.1926.edghill.sem<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-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>+))),
{[TAN-class-2 (~source-rights):] {empty}} OR
{[TAN-core (~source-rights):] <rights-source-only>}?))))Used 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 @when-accessed predates one or more dates in a target file, a warning will be returned.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.Sources are integral parts of a class 2 TAN file. Access to at least one copy is absolutely mandatory.<code><source></code> <head>
.........
<rights-excluding-sources rights-holder="kalvesmaki">
.........
</rights-excluding-sources>
<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>
.........
</see-also>
.........
</head>
Taken from ar.cat.eng.1926.edghill.obj<code><source></code> <head>
.........
<rights-excluding-sources rights-holder="kalvesmaki">
.........
</rights-excluding-sources>
<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>
.........
</see-also>
.........
</head>
Taken from ar.cat.eng.1926.edghill.sem<code><source></code> <head>
.........
<rights-excluding-sources rights-holder="kalvesmaki">
.........
</rights-excluding-sources>
<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>
.........
</see-also>
.........
</head>
Taken from ar.cat.fra.1844.saint-hilaire.sem-native<code><source></code> <head>
.........
<rights-excluding-sources rights-holder="kalvesmaki">
.........
</rights-excluding-sources>
<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>
.........
</see-also>
.........
</head>
Taken from ar.cat.fra.1844.saint-hilaire.sem<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)<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-class-2 (~source-refs):] @src} OR
{[TAN-core (~source-refs):] {empty}} OR
{[TAN-LM-core (~source-refs):] {empty}},
(@which | (@regex, @flags?))))Used by: ~declaration-items, ~decl-class-1, ~entity-tok-defNo source may be given more than one token definition.<code><token-definition></code> <declarations>
.........
<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" regex="[-\w]+"/>
<rename-div-ns src="ger" div-type-ref="Zeile">
.........
</rename-div-ns>
</declarations>
Taken from ringoroses.div.1<code><token-definition></code> <declarations>
.........
<reuse-type xml:id="adaptation">
.........
</reuse-type>
<token-definition src="ring1881 ring1987" which="letters"/>
</declarations>
Taken from ringoroses.01+02.token.1<code><token-definition></code> <declarations>
.........
<comment when="2016-02-22-05:00" who="park">The following is equivalent to @which = 'letters'</comment>
<token-definition src="eng ger" regex="\w+"/>
</declarations>
Taken from ringoroses.01+03.token.1<code><token-definition></code> <declarations>
.........
<reuse-type xml:id="correlationGeneral">
.........
</reuse-type>
<token-definition src="eng ger" which="letters and punctuation"/>
<rename-div-ns src="ger" div-type-ref="Zeile">
.........
</rename-div-ns>
</declarations>
Taken from ringoroses.01+03.token.2<code><value></code>The element value states the value of a <checksum>Formal Definitionstring Used by: <checksum><code><value></code> <checksum>
.........
<name>SHA-1</name>
<value>91D95564ABDF2B2C1B9EEF016CBA51E8179646CC</value>
</checksum>
Taken from patricius.confessio.2003.eng<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~decl-pattern-defaultUsed by: ~TAN-c-decl-core, ~decl-class-1<code><version></code> <declarations>
<work>
.........
</work>
<version>
<IRI>urn:uuid:31648039-3dbb-49b9-b66e-9bd2cd11630e</IRI>
<name>zweite Version</name>
</version>
<div-type xml:id="Zeile">
.........
</div-type>
.........
</declarations>
Taken from ring-o-roses.deu.1897<code><when></code>The element when constrains an event to a period of time.Multiple values of <when> are interpreted to mean "or" with union. No distribution takes place (e.g., x <when/> with y <when/> means "at time x or y", not "at time x" and "at time y").Formal Definition@from, @toUsed by: ~claim, ~agent-role-list<code><work></code>The element work indicates a creative work. The element identifies a conceptual entity, not a physical one.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~decl-pattern-defaultUsed by: ~TAN-c-decl-core, ~decl-class-1A work element may invoke no more than one inclusion.<code><work></code> <declarations>
<work>
<IRI>http://dbpedia.org/resource/Categories_(Aristotle)</IRI>
<name>Aristotle, Categories</name>
</work>
<div-type xml:id="p">
.........
</div-type>
.........
</declarations>
Taken from ar.cat.eng.1926.edghill.obj<code><work></code> <declarations>
<work>
<IRI>http://dbpedia.org/resource/Categories_(Aristotle)</IRI>
<name>Aristotle, Categories</name>
</work>
<div-type xml:id="ch">
.........
</div-type>
.........
</declarations>
Taken from ar.cat.eng.1926.edghill.sem<code><work></code> <declarations>
<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>
.........
</declarations>
Taken from ar.cat.fra.1844.saint-hilaire.sem-native<code><work></code> <declarations>
<work>
<IRI>http://dbpedia.org/resource/Categories_(Aristotle)</IRI>
<name>Aristotle, Categories</name>
</work>
<div-type xml:id="ch">
.........
</div-type>
.........
</declarations>
Taken from ar.cat.fra.1844.saint-hilaire.sem<code>@affects-element</code>The attribute affects-element names one or more TAN elements that the keywords apply toFormal DefinitionUsed by: ~other-body-attributes, ~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="1 dev" 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="1 dev" 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="1 dev" 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="1 dev" 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>@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-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]))Used 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]))Used by: ~cert-claim<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 )Used by: ~ed-stampDate attributes must be castable either as xs:dateTime or xs:dateFuture dates are not permitted.<code>@ed-when</code> <head>
.........
<source>
.........
</source>
<declarations ed-who="park" ed-when="2015-10-31">
<work>
.........
</work>
<div-type xml:id="l">
.........
</div-type>
<filter>
.........
</filter>
</declarations>
<agent xml:id="park" roles="creator">
.........
</agent>
.........
</head>
Taken from ring-o-roses.eng.1987<code>@ed-when</code> <declarations>
<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="test">
.........
</lexicon>
.........
</declarations>
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>
<declarations ed-when="2015-03-03" ed-who="kalvesmaki"/>
<agent xml:id="kalvesmaki" roles="editor">
.........
</agent>
.........
</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 DefinitionUsed 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>
.........
<source>
.........
</source>
<declarations ed-who="park" ed-when="2015-10-31">
<work>
.........
</work>
<div-type xml:id="l">
.........
</div-type>
<filter>
.........
</filter>
</declarations>
<agent xml:id="park" roles="creator">
.........
</agent>
.........
</head>
Taken from ring-o-roses.eng.1987<code>@ed-who</code> <declarations>
<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="test">
.........
</lexicon>
.........
</declarations>
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>
<declarations ed-when="2015-03-03" ed-who="kalvesmaki"/>
<agent xml:id="kalvesmaki" roles="editor">
.........
</agent>
.........
</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 warn(ing)?|error|info|fatal)string (pattern [smixq]+)Used by: ~func-replace, ~decl-tok-def, ~change-list<code>@from</code>The attribute from specifies the beginning of a period of timeFormal Definition(
dateTime
date )Used by: <when>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 DefinitionUsed by: ~non-class-2-opt, ~TAN-key-item, ~TAN-LM-item<code>@group</code><TAN-key TAN-version="1 dev" 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}Used 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 DefinitionUsed by: ~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 that of <master-location>No <master-location> may have an @href that points to a compressed archive.<code>@href</code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:model-object-refs" TAN-version="1 dev">
<head>
.........
<see-also>
.........
<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>
<see-also>
.........
<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>@href</code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="1 dev">
<head>
.........
<see-also>
.........
<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>
.........
<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 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 (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+)Used by: <TAN-A-div>, <TAN-A-tok>, <TAN-c>, <TAN-key>, <TAN-mor>, <TAN-T>, <TAN-LM>Every 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.<code>@id</code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:model-object-refs" TAN-version="1 dev">
<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="1 dev">
<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="1 dev">
<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="1 dev" 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 in the file Formal DefinitionUsed by: ~decl-aliasA <alias> may not mix idrefs from different elements.<alias> references must not be circular.<code>@idrefs</code> <head>
.........
<declarations>
.........
<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"/>
.........
</declarations>
.........
</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 Used 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="1 dev" id="tag:hans@beispiel.com,2014:ringel">
<head>
.........
</head>
<body xml:lang="deu" in-progress="false">
<div type="Zeile" n="a">Ringel, Ringel, Reihe!</div>
<div type="Zeile" n="b">Sind der Kinder dreie,</div>
<div type="Zeile" n="c">Sitzen auf dem Holderbuch,</div>
.........
</body>
</TAN-T>
Taken from ring-o-roses.deu.1897<code>@in-progress</code><TAN-T TAN-version="1 dev" 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="poem" n="poem" part="N" org="uniform" sample="complete">
.........
</div>
</body>
</text>
Taken from ring-o-roses.eng.1957<code>@in-progress</code><TAN-T TAN-version="1 dev" 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 DefinitionUsed 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.Inclusions may not introduce duplicate values of @xml:id.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.Every inclusion should have at least one document available.A work element may invoke no more than one inclusion.Every <feature> inclusion must support every language that has been declared.<code>@include</code> <head>
.........
<declarations>
.........
</declarations>
<agent include="rel"/>
<agent xml:id="stylesheet" roles="editor">
.........
</agent>
.........
</head>
Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-LM-sample<code>@n</code>The attribute n names a <div> or <group>. In a <div> of a class 1 file, the space-delimited concatenation of values of @n from the rootmost ancestor becomes the reference for a <div>.Special use may be made of the tilde (~), as a kind of surrogate hyphen (which is disallowed), to indicate an @n that corresponds to a range of values, e.g., n="7~8" for a <div> that has text that mixes text from 7 and 8.Formal Definitionstring (pattern (\w+|\d+-\d+)(\s+(\w+|\d+-\d+))*)Used by: ~text-div, ~group-attributesNo single set of references may mix Roman numerals, alphabetic numerals, and numerals that are ambiguously either.Leaf div references must be unique.@n's 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.To avoid ambiguous numerals, no div type should mix Roman and alphabet numerals.<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>@regex</code>The attribute regex 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 DefinitionUsed by: ~func-replace, ~decl-tok-defAttributes that take a regular expression must use escape sequences recognized by XML schema or TAN escape extensions (\k{}). See http://www.w3.org/TR/xmlschema-2/#regexs for details.<code>@regex</code> <declarations>
.........
<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" regex="[-\w]+"/>
<rename-div-ns src="ger" div-type-ref="Zeile">
.........
</rename-div-ns>
</declarations>
Taken from ringoroses.div.1<code>@regex</code> <declarations>
.........
<comment when="2016-02-22-05:00" who="park">The following is equivalent to @which = 'letters'</comment>
<token-definition src="eng ger" regex="\w+"/>
</declarations>
Taken from ringoroses.01+03.token.1<code>@regex</code> <declarations>
<token-definition regex="[\w]+"/>
<lexicon xml:id="LSJ">
.........
</lexicon>
.........
</declarations>
Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-LM-sample<code>@regex</code> <item>
<token-definition regex="[\w]+"/>
<name>letters</name>
.........
</item>
Taken from token-definitions.TAN-key<code>@rights-holder</code>The attribute rights-holder 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 @rights-holder from <rights-source-only>. Its absence does not mean that the rightsholder is unknown or nonexistent. For more, see Formal DefinitionUsed by: ~nonsource-rights, ~source-rights<code>@rights-holder</code> <head>
<name>Categories, Aristotle, English translation by E. M. Edghill</name>
<rights-excluding-sources rights-holder="kalvesmaki">
<IRI>http://creativecommons.org/licenses/by/4.0/deed.en_US</IRI>
<name>Creative Commons Attribution 4.0 International License</name>
<desc>Exclusive of rights held and licenses offered by rightsholders of the source or
sources listed below, this data file, insofar as it constitutes an independent work, is
licensed under a Creative Commons Attribution 4.0 International License.</desc>
</rights-excluding-sources>
<source>
.........
</source>
.........
</head>
Taken from ar.cat.eng.1926.edghill.obj<code>@rights-holder</code> <head>
<name>Categories, Aristotle, English translation by E. M. Edghill</name>
<rights-excluding-sources rights-holder="kalvesmaki">
<IRI>http://creativecommons.org/licenses/by/4.0/deed.en_US</IRI>
<name>Creative Commons Attribution 4.0 International License</name>
<desc>Exclusive of rights held and licenses offered by rightsholders of the source or
sources listed below, this data file, insofar as it constitutes an independent work, is
licensed under a Creative Commons Attribution 4.0 International License.</desc>
</rights-excluding-sources>
<source>
.........
</source>
.........
</head>
Taken from ar.cat.eng.1926.edghill.sem<code>@rights-holder</code> <head>
<name>Categories, Aristotle, French translation by J. Barthélemy Saint-Hilaire</name>
<rights-excluding-sources rights-holder="kalvesmaki">
<IRI>http://creativecommons.org/licenses/by/4.0/deed.en_US</IRI>
<name>Creative Commons Attribution 4.0 International License</name>
<desc>Exclusive of rights held and licenses offered by rightsholders of the source or
sources listed below, this data file, insofar as it constitutes an independent work, is
licensed under a Creative Commons Attribution 4.0 International License.</desc>
</rights-excluding-sources>
<source>
.........
</source>
.........
</head>
Taken from ar.cat.fra.1844.saint-hilaire.sem-native<code>@rights-holder</code> <head>
<name>Realignment of Categories, Aristotle, French translation by J. Barthélemy
Saint-Hilaire</name>
<rights-excluding-sources rights-holder="kalvesmaki">
<IRI>http://creativecommons.org/licenses/by/4.0/deed.en_US</IRI>
<name>Creative Commons Attribution 4.0 International License</name>
<desc>Exclusive of rights held and licenses offered by rightsholders of the source or
sources listed below, this data file, insofar as it constitutes an independent work, is
licensed under a Creative Commons Attribution 4.0 International License.</desc>
</rights-excluding-sources>
<source>
.........
</source>
.........
</head>
Taken from ar.cat.fra.1844.saint-hilaire.sem<code>@roles</code>The attribute roles refers to the ID of one or more <role>sFormal DefinitionUsed by: ~agent-list, ~agent-role-listEvery 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> <head>
.........
<declarations>
.........
</declarations>
<agent roles="editor" xml:id="kalvesmaki">
<IRI>http://viaf.org/viaf/299582703</IRI>
<IRI>tag:kalvesmaki.com,2014:self</IRI>
<name xml:lang="eng">Joel Kalvesmaki</name>
</agent>
<role xml:id="editor">
.........
</role>
.........
</head>
Taken from ar.cat.eng.1926.edghill.obj<code>@roles</code> <head>
.........
<declarations>
.........
</declarations>
<agent roles="editor" xml:id="kalvesmaki">
<IRI>http://viaf.org/viaf/299582703</IRI>
<IRI>tag:kalvesmaki.com,2014:self</IRI>
<name xml:lang="eng">Joel Kalvesmaki</name>
</agent>
<role xml:id="editor">
.........
</role>
.........
</head>
Taken from ar.cat.eng.1926.edghill.sem<code>@roles</code> <head>
.........
<declarations>
.........
</declarations>
<agent roles="editor" xml:id="kalvesmaki">
<IRI>http://viaf.org/viaf/299582703</IRI>
<IRI>tag:kalvesmaki.com,2014:self</IRI>
<name xml:lang="eng">Joel Kalvesmaki</name>
</agent>
<role xml:id="editor">
.........
</role>
.........
</head>
Taken from ar.cat.fra.1844.saint-hilaire.sem-native<code>@roles</code> <head>
.........
<declarations>
.........
</declarations>
<agent roles="editor" xml:id="kalvesmaki">
<IRI>http://viaf.org/viaf/299582703</IRI>
<IRI>tag:kalvesmaki.com,2014:self</IRI>
<name xml:lang="eng">Joel Kalvesmaki</name>
</agent>
<role xml:id="editor">
.........
</role>
.........
</head>
Taken from ar.cat.fra.1844.saint-hilaire.sem<code>@TAN-version</code>The attribute TAN-version specifies the version of TAN schemas used. Formal Definitionstring Used by: ~TAN-root<code>@TAN-version</code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:model-object-refs" TAN-version="1 dev">
<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="1 dev">
<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="1 dev">
<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="1 dev" 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 )Used by: <when>Date attributes must be castable either as xs:dateTime or xs:dateFuture dates are not permitted.@from must predate @to<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 DefinitionUsed by: ~group-attributes, ~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>@when</code>The attribute when indicates a date or date and timeFormal Definition(
dateTime
date )Used by: ~comment, ~change-listDate attributes must be castable either as xs:dateTime or xs:dateFuture dates are not permitted.<code>@when</code> <head>
.........
<role xml:id="editor">
.........
</role>
<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>
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="1 dev">
<head>
.........
<role xml:id="editor">
.........
</role>
<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-1-dev/examples/ar.cat.eng.1926.edghill.sem-201606220804250030400.xml.</change>
<change when="2016-01-26-04:00" who="kalvesmaki">Started new file.</change>
</head>
.........
</TAN-T>
Taken from ar.cat.eng.1926.edghill.sem<code>@when</code> <head>
.........
<role xml:id="editor">
.........
</role>
<change when="2016-07-10" who="kalvesmaki">Began new file</change>
</head>
Taken from ar.cat.fra.1844.saint-hilaire.sem-native<code>@when-accessed</code>The attribute when-accessed specifies when an electronic file was last examinedFormal Definition(
date
dateTime )Used by: <location>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="1 dev">
<head>
.........
<see-also>
.........
<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>
<see-also>
.........
<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>@when-accessed</code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="1 dev">
<head>
.........
<see-also>
.........
<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>
.........
<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>@which</code>The attribute which used to point to a reserved keyword, either a reserved tokenization pattern or a relationship.Formal DefinitionUsed by: ~decl-tok-def, ~entity-digital-generic-ref, ~entity-nondigital-ref, ~metadata-human, ~decl-morphAn 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="1 dev">
<head>
.........
<see-also>
<relationship which="model"/>
<IRI>tag:kalvesmaki.com,2014:tan-t:ar.cat.grc.1949.minio-paluello:object-refs</IRI>
.........
</see-also>
<see-also>
<relationship which="alternatively divided edition"/>
<IRI>tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs</IRI>
.........
</see-also>
<declarations>
.........
<filter>
<normalization which="no hyphens"/>
</filter>
</declarations>
.........
</head>
.........
</TAN-T>
Taken from ar.cat.eng.1926.edghill.obj<code>@which</code> <see-also>
<relationship which="model"/>
<IRI>tag:kalvesmaki.com,2014:tan-t:ar.cat.grc.1949.minio-paluello:semantic-refs</IRI>
.........
</see-also>
Taken from ar.cat.eng.1926.edghill.sem<code>@who</code>The attribute who names an <agent>Formal DefinitionUsed by: ~comment, ~agent-role-list, ~change-listEvery 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> <head>
.........
<role xml:id="editor">
.........
</role>
<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>
Taken from ar.cat.eng.1926.edghill.obj<code>@who</code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:semantic-refs" TAN-version="1 dev">
<head>
.........
<role xml:id="editor">
.........
</role>
<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-1-dev/examples/ar.cat.eng.1926.edghill.sem-201606220804250030400.xml.</change>
<change when="2016-01-26-04:00" who="kalvesmaki">Started new file.</change>
</head>
.........
</TAN-T>
Taken from ar.cat.eng.1926.edghill.sem<code>@who</code> <head>
.........
<role xml:id="editor">
.........
</role>
<change when="2016-07-10" who="kalvesmaki">Began new file</change>
</head>
Taken from ar.cat.fra.1844.saint-hilaire.sem-native<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 DefinitionID (pattern \w\S*)Used by: ~decl-id-ref-opt, ~source-id-opt, ~alignment-attributes-non-class-2, ~decl-div, ~id-option, ~decl-group-type, ~inclusion-item, ~agent-list, ~role-list, ~decl-alias, ~decl-morph, ~decl-lexi, ~TAN-LM-item@xml:id values may not be repeated in the same document.Any ana with an @xml:id must point to no more than one token.Codes for (@xml:id or @code) features must be case-indifferently unique within a given category.<code>@xml:id</code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:model-object-refs" TAN-version="1 dev">
<head>
.........
<declarations>
<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>
<filter>
.........
</filter>
</declarations>
<agent roles="editor" xml:id="kalvesmaki">
<IRI>http://viaf.org/viaf/299582703</IRI>
<IRI>tag:kalvesmaki.com,2014:self</IRI>
<name xml:lang="eng">Joel Kalvesmaki</name>
</agent>
<role xml:id="editor">
.........
</role>
.........
</head>
.........
</TAN-T>
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 Used by: ~other-body-attributes, ~text-div, ~nontextual-reference, ~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="1 dev">
<head>
.........
<agent roles="editor" xml:id="kalvesmaki">
.........
<IRI>tag:kalvesmaki.com,2014:self</IRI>
<name xml:lang="eng">Joel Kalvesmaki</name>
</agent>
<role xml:id="editor">
<IRI>http://schema.org/editor</IRI>
<name xml:lang="eng">Editor</name>
</role>
.........
</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.semTAN-class-1 elements and attributes summarized<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~ed-stamp?,
(~inclusion |
(@xml:id, (<comment>* &
((<IRI>+, ~metadata-human) | @which))))Used by: ~decl-class-1To avoid ambiguous numerals, no div type should mix Roman and alphabet numerals.<code><div-type></code> <head>
.........
<declarations>
<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>
<filter>
.........
</filter>
</declarations>
.........
</head>
Taken from ar.cat.eng.1926.edghill.obj<code><div-type></code> <declarations>
<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>
.........
</declarations>
Taken from ar.cat.eng.1926.edghill.sem<code><filter></code>The element filter declares alterations that have been made to the source.Formal Definition~ed-stamp?, (<comment>* &
(<normalization>* & <replace>* & <transliteration>*))Used by: ~test-pattern, ~decl-class-1<code><filter></code> <declarations>
.........
<div-type xml:id="l">
.........
</div-type>
<filter>
<normalization which="no hyphens"/>
</filter>
</declarations>
Taken from ar.cat.eng.1926.edghill.obj<code><filter></code> <declarations>
.........
<div-type xml:id="pt" which="part"/>
<filter>
<normalization which="no hyphens"/>
</filter>
</declarations>
Taken from ar.cat.eng.1926.edghill.sem<code><filter></code> <declarations>
.........
<div-type xml:id="pt" which="part"/>
<filter>
<normalization which="no hyphens"/>
</filter>
</declarations>
Taken from ar.cat.fra.1844.saint-hilaire.sem-native<code><filter></code> <declarations>
.........
<div-type xml:id="pt" which="part"/>
<filter>
<normalization which="no hyphens"/>
</filter>
</declarations>
Taken from ar.cat.fra.1844.saint-hilaire.sem<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))))Used by: ~decl-filter-content<code><normalization></code> <filter>
<normalization which="no hyphens"/>
</filter>
Taken from ar.cat.eng.1926.edghill.obj<code><normalization></code> <filter>
<normalization which="no hyphens"/>
</filter>
Taken from ar.cat.eng.1926.edghill.sem<code><normalization></code> <filter>
<normalization which="no hyphens"/>
</filter>
Taken from ar.cat.fra.1844.saint-hilaire.sem-native<code><normalization></code> <filter>
<normalization which="no hyphens"/>
</filter>
Taken from ar.cat.fra.1844.saint-hilaire.sem<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>* & (@regex, @replacement, @flags?)))Used by: ~decl-filt-repl<code><transliteration></code>The element transliteration indicates a transliteration scheme that has been applied to a source to convert it from one writing system to another. This element may be useful if it easier to work with a source in the Latin alphabet (for example) rather than a native one. The scope of this element may be specified through optional <for-lang>s.This may be useful for texts easier to handle in a Latin alphabet rather than a native one. Formal Definition~decl-pattern-languageUsed by: ~decl-filter-content<code>@replacement</code>The attribute replacement contains a string used to replace any occurrence of <pattern>Formal DefinitionUsed by: <replace>TAN-T elements and attributes summarized<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)))Used by: ~item, ~text-divAll text must be normalized (Unicode NFC).Leaf div references must be unique.@n's taking digit values should not begin with 0.Every leaf div must have at least some non-space text.No div may begin with a modifying character.No div may have a spacing character followed by a modifying character.No div 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><TAN-T></code>The element TAN-T specifies that the TAN file contains a transcription. Root element.Formal Definition~TAN-rootEvery validated TAN file will include the following message at its root. 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.<code><TAN-T></code><TAN-T id="tag:kalvesmaki.com,2014:tan-t:ar.cat.eng.1926.edghill:model-object-refs" TAN-version="1 dev">
<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="1 dev">
<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="1 dev">
<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="1 dev" 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.semTAN-class-2 elements and attributes summarized<code><rename></code>The element rename indicates the name of a <div>@n that should be changed in a given @type, and the name to which it should be changed.There is no need to use this feature to convert Roman, alphabetic, or other numerals, which are detected and converted automatically Formal Definition@old, @newUsed by: ~decl-rename-div-n@old and @new may not share the same valueNo value of @new or @old may appear more than once for a given div type in a given source.@old must be found in every div type of every source<code><rename></code> <rename-div-ns src="ger" div-type-ref="Zeile">
<rename old="e" new="4"/>
</rename-div-ns>
Taken from ringoroses.div.1<code><rename></code> <rename-div-ns src="ger" div-type-ref="Zeile">
<rename old="5" new="4"/>
</rename-div-ns>
Taken from ringoroses.01+03.token.2<code><rename-div-ns></code>The element rename-div-ns provisionally reassigns @n values for one or more sources and one or more div types. Renaming applies only to the current file. This element is especially useful for converting Roman numerals or letter numerals into Arabic numerals. See <rename> for syntax.This feature is strictly speaking a convenience, not a necessity. All TAN-compliant preprocessors are required to automatically detect Roman and alphabetic numbering systems and treat them as Arabic numerals. It is also useful for div types that use descriptive names for @n (such as books of the Bible), particularly for reconciling those names with a system that prevails or is preferred (e.g., "mt" to "Matt"). Note for TAN-A-div users: Although this element can reconcile simple differences, it should not be used for more complex inconsistencies that affect alignment, best handled in the <body> of a TAN-A-div file.For more inforrmation see Formal Definition~ed-stamp?,
(~inclusion | (
{[TAN-class-2 (~source-refs):] @src} OR
{[TAN-core (~source-refs):] {empty}} OR
{[TAN-LM-core (~source-refs):] {empty}}, @div-type-ref, <rename>+))Used by: ~declaration-itemsEvery div type reference must be valid in every source<code><rename-div-ns></code> <declarations>
.........
<token-definition src="eng-us" regex="[-\w]+"/>
<rename-div-ns src="ger" div-type-ref="Zeile">
<rename old="e" new="4"/>
</rename-div-ns>
</declarations>
Taken from ringoroses.div.1<code><rename-div-ns></code> <declarations>
.........
<token-definition src="eng ger" which="letters and punctuation"/>
<rename-div-ns src="ger" div-type-ref="Zeile">
<rename old="5" new="4"/>
</rename-div-ns>
</declarations>
Taken from ringoroses.01+03.token.2<code><suppress-div-types></code>The element suppress-div-types marks div types in a source that should be suppressed in references. Suppressions occur shallowly. That is, it does not suppress any descendants of that div type. But if the suppression applies to a leaf div, that div and its text is effectively suppressed. Any suppression of a div type must preserve the Leaf Div Uniqueness Rule (LDUR). See This element will be used seldomly, for cases where a source has a div type that is dispensable in text references. Formal Definition~ed-stamp?,
(~inclusion | (
{[TAN-class-2 (~source-refs):] @src} OR
{[TAN-core (~source-refs):] {empty}} OR
{[TAN-LM-core (~source-refs):] {empty}}, @div-type-ref))Used by: ~declaration-itemsEvery div type reference must be valid in every source<code><suppress-div-types></code> <declarations>
<suppress-div-types src="fra" div-type-ref="sec"/>
</declarations>
Taken from ar.cat.tan-a-div<code><suppress-div-types></code> <declarations>
<suppress-div-types src="eng-1790" div-type-ref="poem"/>
<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>
.........
</declarations>
Taken from ringoroses.div.1<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-LM, it normally does.<tok>s are two types: simple and complex.SIMPLE: <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.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). This syntax, then, allows multiple <tok>s to be collapsed into a single one, to save space and perhaps enhance legibility. 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"/>COMPLEX: There are cases where one wishes to treat more than one token, in whole or part, as a single entity. In this case, @cont should be used, and it must join <tok>s that have only single values for @src, @ref, and @pos.@chars may take multiple values.The behavior of <tok> differs from <div-ref>. The former is never treated as a group, whereas the latter is. For more, see <div-ref>.Formal Definition~tok-attr-core,
{[TAN-A-div (~tok-source-ref-opt):] {empty}} OR
{[TAN-class-2 (~tok-source-ref-opt):]
{{[TAN-class-2 (~source-refs):] @src}} OR
{{[TAN-core (~source-refs):] {empty}}} OR
{{[TAN-LM-core (~source-refs):] {empty}}}},
{[TAN-LM-lang (~pointer-to-div-range):] {empty}} OR
{[TAN-class-2 (~pointer-to-div-range):] @ref},
(@val |
{[TAN-LM-lang (~seq-pos-ref):] {empty}} OR
{[TAN-class-2 (~seq-pos-ref):] @pos} | (@val,
{[TAN-LM-lang (~seq-pos-ref):] {empty}} OR
{[TAN-class-2 (~seq-pos-ref):] @pos})),
{[TAN-A-div (~tok-cert-opt):] {empty}} OR
{[TAN-class-2 (~tok-cert-opt):]
(@cert | (@cert, @cert2))?}~tok-sequence-attr-core, @src,
{[TAN-A-div (~continuation-opt):] {empty}} OR
{[TAN-class-2 (~continuation-opt):] @cont},
(@cert | (@cert, @cert2))?~tok-sequence-attr-core,
{[TAN-A-div (~continuation-opt):] {empty}} OR
{[TAN-class-2 (~continuation-opt):] @cont}~tok-sequence-attr-coreUsed by: ~split, ~complex-text-ref, ~alignment-content-non-class-2, ~tok-sequence, ~TAN-LM-itemEvery token must be locatable in every cited ref in every source.<tok> must reference a leaf <div>.No source may be split more than once in the same place.Splits may not be made at the first token in a div.A <tok> may not duplicate any sibling <tok>.Any ana with an @xml:id must point to no more than one token.<code><tok></code><TAN-A-div TAN-version="1 dev" id="tag:parkj@textalign.net,2015:ar.cat.tan-a-div:claims">
.........
<body claimant="lmp">
.........
<claim subject="andronicus boethus" adverb="perhaps" verb="omits" claim-basis="dexippus porphyry">
<locus work="grc">
<tok ref="1 a 2" pos="3-4"/>
</locus>
</claim>
<claim subject="herminus comm-omnes" verb="agrees">
<locus work="grc">
<tok ref="1 a 2" pos="3-4"/>
</locus>
</claim>
.........
<claim subject="B" verb="replaces">
<locus work="grc">
<tok ref="1 a 5" pos="1-2"/>
</locus>
.........
</claim>
<claim subject="Λ" adverb="perhaps" verb="replaces">
<locus work="grc">
<tok ref="1 a 5" pos="1-2"/>
</locus>
.........
</claim>
<claim subject="π α φ ο" verb="agrees">
<locus work="grc">
<tok ref="1 a 5" pos="1-2"/>
</locus>
</claim>
</body>
</TAN-A-div>
Taken from ar.cat.tan-a-div.claims<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+)))?)*|.*\?\?\?.*)Used by: ~tok-attr-coreSequences may not include values less than 1.Sequences may not include values greater than the maximum allowed.Sequences may not include ranges that go from a larger value to a smaller, e.g., 4 - 2.<code>@cont</code>The attribute cont indicates whether the current element is continued by the next one and to be treated as a single one. Value must be 1 or true, implied by the very presence of the attribute. If you wish to decare it to be false, delete the attribute altogether.This feature is useful in <tok> for rejoining the portion of a word split across two <div>s, or for uniting into a single linguistic token multiple tokens separated by the tokenization process, e.g., "pom pom". This feature is useful in <div-ref> for creating groups of references that cannot be expressed in a single <div-ref>Formal Definitionboolean (pattern true|1)Used by: ~continuation-optAny element taking @cont must be followed by at least one sibling of the same type.<code>@div-type-ref</code>The attribute div-type-ref 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 DefinitionUsed by: ~div-type-ref-cluster, ~decl-supp-div-type, ~decl-rename-div-nEvery div type reference must be valid in every source<code>@div-type-ref</code> <declarations>
<suppress-div-types src="fra" div-type-ref="sec"/>
</declarations>
Taken from ar.cat.tan-a-div<code>@div-type-ref</code><TAN-A-div TAN-version="1 dev" id="tag:parkj@textalign.net,2015:ring01-TAN-A-ring02">
<head>
.........
<declarations>
<suppress-div-types src="eng-1790" div-type-ref="poem"/>
<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" regex="[-\w]+"/>
<rename-div-ns src="ger" div-type-ref="Zeile">
<rename old="e" new="4"/>
</rename-div-ns>
</declarations>
.........
</head>
<body>
.........
<equate-div-types>
<div-type-ref src="ger" div-type-ref="Zeile"/>
<div-type-ref src="eng-uk" div-type-ref="line"/>
</equate-div-types>
.........
</body>
</TAN-A-div>
Taken from ringoroses.div.1<code>@new</code>The attribute new provides the new name for an @n that is to be renamedFormal Definitionstring (pattern (\w+|\d+-\d+)(\s+(\w+|\d+-\d+))*)Used by: <rename>@old and @new may not share the same valueNo value of @new or @old may appear more than once for a given div type in a given source.<code>@new</code> <rename-div-ns src="ger" div-type-ref="Zeile">
<rename old="e" new="4"/>
</rename-div-ns>
Taken from ringoroses.div.1<code>@new</code> <rename-div-ns src="ger" div-type-ref="Zeile">
<rename old="5" new="4"/>
</rename-div-ns>
Taken from ringoroses.01+03.token.2<code>@old</code>The attribute old provides the name of an @n to be renamedFormal Definitionstring (pattern (\w+|\d+-\d+)(\s+(\w+|\d+-\d+))*)Used by: <rename>@old and @new may not share the same valueNo value of @new or @old may appear more than once for a given div type in a given source.@old must be found in every div type of every source<code>@old</code> <rename-div-ns src="ger" div-type-ref="Zeile">
<rename old="e" new="4"/>
</rename-div-ns>
Taken from ringoroses.div.1<code>@old</code> <rename-div-ns src="ger" div-type-ref="Zeile">
<rename old="5" new="4"/>
</rename-div-ns>
Taken from ringoroses.01+03.token.2<code>@pos</code>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|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+)))?)*|.*\?\?\?.*)string (pattern ((last|max)|((last|max)-\d+)|(\d+))|.*\?\?\?.*)Used by: ~tok-regular, ~tok-sequence-attr-coreSequences may not include values less than 1.Sequences may not include values greater than the maximum allowed.Sequences may not include ranges that go from a larger value to a smaller, e.g., 4 - 2.<code>@pos</code><TAN-A-div TAN-version="1 dev" id="tag:parkj@textalign.net,2015:ar.cat.tan-a-div:claims">
.........
<body claimant="lmp">
.........
<claim subject="andronicus boethus" adverb="perhaps" verb="omits" claim-basis="dexippus porphyry">
<locus work="grc">
<tok ref="1 a 2" pos="3-4"/>
</locus>
</claim>
<claim subject="herminus comm-omnes" verb="agrees">
<locus work="grc">
<tok ref="1 a 2" pos="3-4"/>
</locus>
</claim>
.........
<claim subject="B" verb="replaces">
<locus work="grc">
<tok ref="1 a 5" pos="1-2"/>
</locus>
.........
</claim>
<claim subject="Λ" adverb="perhaps" verb="replaces">
<locus work="grc">
<tok ref="1 a 5" pos="1-2"/>
</locus>
.........
</claim>
<claim subject="π α φ ο" verb="agrees">
<locus work="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>. It is assumed that any simple reference that has fewer @n values than preceding simple references has been truncated. The abbreviated form will be checked before the form actually stated. 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. 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+)*)|.*\?\?\?.*)Used by: ~anchor-div-ref-item, ~reanchor-div-ref-item, ~simple-textual-reference, ~claim-div-ref-item, ~tok-regular, ~tok-sequence-attr-coreNo single set of references may mix Roman numerals, alphabetic numerals, and numerals that are ambiguously either.Every atomic reference in a @ref must correspond to a <div> in every source mentioned by @src.Every range in a @ref must correspond to one or more <div>s in every source mentioned by @src.If @ref points to a leaf div, it must be unique.A defective reference is a value of @ref that corresponds to a <div> in some but not all sources in a work. If a defective reference is used, a warning will be reported, identifying the sources that lack the appropriate <div>.<code>@ref</code><TAN-A-div TAN-version="1 dev" id="tag:parkj@textalign.net,2015:ar.cat.tan-a-div:claims">
.........
<body claimant="lmp">
.........
<claim subject="andronicus boethus" adverb="perhaps" verb="omits" claim-basis="dexippus porphyry">
<locus work="grc">
<tok ref="1 a 2" pos="3-4"/>
</locus>
</claim>
<claim subject="herminus comm-omnes" verb="agrees">
<locus work="grc">
<tok ref="1 a 2" pos="3-4"/>
</locus>
</claim>
.........
<claim subject="B" verb="replaces">
<locus work="grc">
<tok ref="1 a 5" pos="1-2"/>
</locus>
.........
</claim>
<claim subject="Λ" adverb="perhaps" verb="replaces">
<locus work="grc">
<tok ref="1 a 5" pos="1-2"/>
</locus>
.........
</claim>
<claim subject="π α φ ο" verb="agrees">
<locus work="grc">
<tok ref="1 a 5" pos="1-2"/>
</locus>
</claim>
</body>
</TAN-A-div>
Taken from ar.cat.tan-a-div.claims<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 Used by: ~div-type-ref-cluster, ~split, ~anchor-div-ref-item, ~reanchor-div-ref-item, ~simple-textual-reference, ~complex-textual-reference-set, ~decl-supp-div-type, ~decl-rename-div-n, ~tok-source-ref-opt, ~tok-with-src-and-cont, ~decl-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 atomic reference in a @ref must correspond to a <div> in every source mentioned by @src.Every range in a @ref must correspond to one or more <div>s in every source mentioned by @src.<code>@src</code><TAN-A-div TAN-version="1 dev" id="tag:parkj@textalign.net,2015:ar.cat.tan-a-div">
<head>
.........
<declarations>
<suppress-div-types src="fra" div-type-ref="sec"/>
</declarations>
.........
</head>
<body>
<split-leaf-div-at>
<tok src="fra" ref="5 5" val="Ceci"/>
<tok src="fra" ref="5 5" val="Il"/>
<tok src="fra" ref="5 6" val="Si" pos="1"/>
<tok src="fra" ref="5 12" val="Ainsi" pos="1, last"/>
.........
</split-leaf-div-at>
.........
</body>
</TAN-A-div>
Taken from ar.cat.tan-a-div<code>@val</code>The attribute val specifies a particular word token by means of its string value. Permits regular expressions.For more see Formal Definitionstring (pattern .+)Used by: ~tok-regular, ~tok-sequence-attr-coreAttributes that take a regular expression must use escape sequences recognized by XML schema or TAN escape extensions (\k{}). See http://www.w3.org/TR/xmlschema-2/#regexs for details.@val must wholly match a token in the target.A @val set to '.+', a regular expression that matches any string, is equivalent to the omission of @valThe value '.+' will match any string.<code>@val</code> <body>
<split-leaf-div-at>
<tok src="fra" ref="5 5" val="Ceci"/>
<tok src="fra" ref="5 5" val="Il"/>
<tok src="fra" ref="5 6" val="Si" pos="1"/>
<tok src="fra" ref="5 12" val="Ainsi" pos="1, last"/>
<tok src="fra" ref="5 12" val="Quant"/>
.........
</split-leaf-div-at>
.........
</body>
Taken from ar.cat.tan-a-divTAN-A-div elements and attributes summarized<code><anchor-div-ref></code>The element anchor-div-ref refers to a group of one or more <div>s (or segments of <div>s) to which <div>s from other versions of the same work should be realigned (defined by the <div-ref>s that follow). The first child of a <realign>, it is constructed exactly like <div-ref>, except that only @src, not @work, is used, and @seg is excluded. <anchor-div-ref> does not permit the comma in @ref in an undistributed realignment, since realignment must always be made to a contiguous range of text. If the parent <realign>'s @distribute is false, or missing, then each <div-ref> group will be realigned as a whole to the anchor, treated as a whole.If @distribute is true, then every nth realign head will serve as the anchor for the nth realign head in each subsequent <div-ref>s (grouped by source).@seg, which applies to splits in specific sources, is not allowed because the job of an anchor is to reconcile other <div>s to a reference that is valid independent of any particular edition. @seg would defeat that purpose.For more, see <div-ref>.Formal Definition~ed-stamp?, @src, @refUsed by: ~realignmentA <div> may be referred to in a <realign> no more than once (whether <anchor-div-ref> or <div-ref>).<code><anchor-div-ref></code><TAN-A-div TAN-version="1 dev" id="tag:parkj@textalign.net,2015:ar.cat.tan-a-div">
.........
<body>
.........
<realign>
<anchor-div-ref src="grc" ref="1 1 1 - 1 1 3"/>
<div-ref src="fra" ref="1 1 - 1 3"/>
</realign>
<realign>
<anchor-div-ref src="grc" ref="3 1 1 - 3 1 3"/>
<div-ref src="fra" ref="3 1 - 3 3"/>
</realign>
<realign>
<anchor-div-ref src="grc" ref="4 1 1 - 4 1 3"/>
<div-ref src="fra" ref="4 1 - 4 3"/>
</realign>
<realign>
<anchor-div-ref src="grc" ref="5 1 1-4"/>
<div-ref src="fra" ref="5 1 - 5 4"/>
</realign>
.........
</body>
</TAN-A-div>
Taken from ar.cat.tan-a-div<code><div-ref></code>The element div-ref refers to and groups one or more <div>s (or segments of <div>s).<div-ref>s are expanded against @src/@work, @ref, and @seg. That is, a <div-ref> points to every segment of every div of every source cited.A <div-ref>, or a group of <div-ref>s joined by @cont, are treated as many groups as sources referred to. That is, <div-ref src="X Y" ... /> will be treated as shorthand for <div-ref src="X" ... /> and <div-ref src="Y" ... />. This applies to @work as well: <div-ref work="w" ... /> is equivalent to <div-ref src="w1" ... />, <div-ref src="w2" ... />, etc. After this distinction between sources is made, the entire set of <div>s pointed to will be treated as a group, and processed as a whole (see @distribute). <div-ref> is a grouping device, and is therefore unlike <tok>, which always refers to single items, never sets. As a result, the siblings <div-ref src="X" ref="a"/> and <div-ref src="X" ref="b"/> are NOT identical to <div-ref src="X" ref="a, b"/> Formal Definition~ed-stamp?,
{[TAN-class-2 (~source-refs):] @src} OR
{[TAN-core (~source-refs):] {empty}}, @ref, @seg?~ed-stamp?, @ref, @seg?Used by: ~realignment, ~complex-text-refA defective reference is a value of @ref that corresponds to a <div> in some but not all sources in a work. If a defective reference is used, a warning will be reported, identifying the sources that lack the appropriate <div>.A <div> may be referred to in a <realign> no more than once (whether <anchor-div-ref> or <div-ref>).<code><div-ref></code><TAN-A-div TAN-version="1 dev" id="tag:parkj@textalign.net,2015:ar.cat.tan-a-div">
.........
<body>
.........
<realign>
<anchor-div-ref src="grc" ref="1 1 1 - 1 1 3"/>
<div-ref src="fra" ref="1 1 - 1 3"/>
</realign>
<realign>
<anchor-div-ref src="grc" ref="3 1 1 - 3 1 3"/>
<div-ref src="fra" ref="3 1 - 3 3"/>
</realign>
<realign>
<anchor-div-ref src="grc" ref="4 1 1 - 4 1 3"/>
<div-ref src="fra" ref="4 1 - 4 3"/>
</realign>
<realign>
<anchor-div-ref src="grc" ref="5 1 1-4"/>
<div-ref src="fra" ref="5 1 - 5 4"/>
</realign>
.........
</body>
</TAN-A-div>
Taken from ar.cat.tan-a-div<code><div-type-ref></code>The element div-type-ref points to a <div-type> in one or more sources, using the @xml:id assigned by the source to that div type. Formal Definition~ed-stamp?,
{[TAN-class-2 (~source-refs):] @src} OR
{[TAN-core (~source-refs):] {empty}}, @div-type-refUsed by: ~div-type-equiv, ~div-type-ref-cluster, ~decl-supp-div-type, ~decl-rename-div-nEvery div type reference must be valid in every source<code><div-type-ref></code> <body>
.........
<equate-div-types>
<div-type-ref src="ger" div-type-ref="Zeile"/>
<div-type-ref src="eng-uk" div-type-ref="line"/>
</equate-div-types>
.........
</body>
Taken from ringoroses.div.1<code><equate-div-types></code>The element equate-div-types declares an ad hoc equivalence between div types that are not defined by the <IRI> values in their sources as being identical.<equate-div-types> are assumed to be greedy and transitive. If this element is used to equate div type X with type Y, then any div type in any source identical to X's or Y's IRI values will treated as identical. This element does not imply that the two types of division are, in reality, one and the same. It merely states that, for the purposes of this alignment, they should be treated as equivalent.Formal Definition~ed-stamp?,
(~inclusion | (<div-type-ref>, <div-type-ref>+))Used by: ~TAN-body-coreItems that share IRI values should not be equated.Every div type reference must be valid in every source<code><equate-div-types></code> <body>
<equate-works work="eng-uk ger"/>
<equate-div-types>
<div-type-ref src="ger" div-type-ref="Zeile"/>
<div-type-ref src="eng-uk" div-type-ref="line"/>
</equate-div-types>
<split-leaf-div-at src="eng-us">
.........
</split-leaf-div-at>
</body>
Taken from ringoroses.div.1<code><equate-works></code>The element equate-works declares an ad hoc equivalence between works that are not defined by the <IRI>s in their sources as being identical.This element extends the automatic equating of works, which 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.<equate-works> does not imply that the two works are, in reality, one and the same. It merely states that, for the purposes of this alignment, they should be treated as equivalent.Formal Definition~ed-stamp?, (~inclusion | @work)Used by: ~TAN-body-coreItems that share IRI values should not be equated.<code><equate-works></code> <body>
<equate-works work="eng-uk ger"/>
<equate-div-types>
.........
</equate-div-types>
.........
</body>
Taken from ringoroses.div.1<code><realign></code>The element realign corrects misaligned or unaligned divisions and segments in versions of the same work. <realign> is intended to reconcile discordant reference systems by mapping <div>s from one or more sources onto the <div>s of another, treated as an anchor. The reanchored divs are then excluded from any default alignments, but they inherit the anchor's alignments. Realignments come in four types.An UNANCHORED, ONE-SOURCE realigment consists solely of one or more <div-ref>s belonging to only one source. Any number of <div>s may be referred to by the child <div-ref>s. All <div>s referred to will be excluded from automatic alignment with every other version of the same work.An UNANCHORED, MULTIPLE-SOURCE realignment realigns <div>s from multiple sources. The number of <div>s per source must be identical, since these <div>s will not only be excluded from automatic alignment, but realigned with each other, with the nth <div> in each source constituting a realigned group.An ANCHORED, ONE-TO-ONE realignment consists of an <anchor-div-ref> that points to n <div>s, and each source invoked by the following <div-ref>s also point to n <div>s, which will be reanchored to the nth <div> in the anchor. An ANCHORED, ONE-TO-MANY realignment consists of an <anchor-div-ref> that points only to one <div>, and <div-ref>s that point to any number of sources and any number of <div>s. To that one anchor will be remapped each source's collection of <div>s to be reanchored. The sequence of <div>s referred to will be respected. If to an anchor A is remapped <div>s 2, 4, and 3, then Realignment is disruptive, displacing any default alignment that might have been inferred in the reanchored source. Assume a case where a <div> with reference B is being realigned to an anchor with reference A. In the source to be reanchored reference A, if it exists, will be excluded from automatic alignment with the anchor, unless if it is explicitly included in a <realign>. All realignment, except one-to-many anchored, is inheritable, affecting not only the specified <div>s but also their descendants. That is, if X is realigned to Y, then children in X will be automatically aligned with children in Y, based on normalized values of @n. Children of <div>s in one-to-many anchored realignments must be explicitly realigned.Because of the distributive nature of the realignment, every value of @ref that involves a hyphen must have siblings with balanced depth on the left and right side of the hyphen (i.e., ref="1 - 2.1" would be invalid).<realign> does not affect subsequent nomenclature of @ref. If in source x a <div> A is realigned with <div> B in source y, then subsequent references to the realigned <div> in source x should still use A as a value of @ref, not B. The order of <realign>s is immaterial. No <realign> overwrites any other <realign>. If two <realign>s each reanchor A and B in the same source to C in the anchor, then A and B will be realigned in parallel. If one meant to say that A followed by B is to be realigned to C, then a one-to-many anchored realignment should be used. Formal Definition~ed-stamp?,
(~inclusion |
(<comment>* & (<anchor-div-ref>*, <div-ref>+)))Used by: ~TAN-body-coreA <div> may be referred to in a <realign> no more than once (whether <anchor-div-ref> or <div-ref>).Distribution must be applied to groups of equal size.No <div> that is a member of a complex realignment may be used to align all members of a work (@src should be used instead of @work)<code><realign></code><TAN-A-div TAN-version="1 dev" id="tag:parkj@textalign.net,2015:ar.cat.tan-a-div">
.........
<body>
<split-leaf-div-at>
.........
</split-leaf-div-at>
<realign>
<anchor-div-ref src="grc" ref="1 1 1 - 1 1 3"/>
<div-ref src="fra" ref="1 1 - 1 3"/>
</realign>
<realign>
<anchor-div-ref src="grc" ref="3 1 1 - 3 1 3"/>
<div-ref src="fra" ref="3 1 - 3 3"/>
</realign>
<realign>
<anchor-div-ref src="grc" ref="4 1 1 - 4 1 3"/>
<div-ref src="fra" ref="4 1 - 4 3"/>
</realign>
<realign>
<anchor-div-ref src="grc" ref="5 1 1-4"/>
<div-ref src="fra" ref="5 1 - 5 4"/>
</realign>
<realign>
.........
</realign>
.........
</body>
</TAN-A-div>
Taken from ar.cat.tan-a-div<code><split-leaf-div-at></code>The element split-leaf-div-at creates ad hoc splits in leaf <div>s, to facilitate alignments and realignments of textual units smaller than leaf <div>s. Any leaf div may be split as many times as there are token, as defined by <tokenization>s.Each split creates a provisional segment, a textual subdivision of a leaf <div>.Formal Definition~ed-stamp?,
(~inclusion |
(
{[TAN-class-2 (~source-refs):] @src} OR
{[TAN-core (~source-refs):] {empty}}, (<comment>* & <tok>+)))Used by: ~TAN-body-coreSplits may be made only at leaf divs.No source may be split more than once in the same place.Splits may not be made at the first token in a div.<code><split-leaf-div-at></code> <body>
<split-leaf-div-at>
<tok src="fra" ref="5 5" val="Ceci"/>
<tok src="fra" ref="5 5" val="Il"/>
<tok src="fra" ref="5 6" val="Si" pos="1"/>
.........
</split-leaf-div-at>
<realign>
.........
</realign>
.........
</body>
Taken from ar.cat.tan-a-div<code><split-leaf-div-at></code> <body>
.........
<equate-div-types>
.........
</equate-div-types>
<split-leaf-div-at src="eng-us">
<tok ref="2" pos="last-3"/>
</split-leaf-div-at>
</body>
Taken from ringoroses.div.1<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-rootEvery validated TAN file will include the following message at its root. 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.<code><TAN-A-div></code><TAN-A-div TAN-version="1 dev" 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="1 dev" id="tag:parkj@textalign.net,2015:ar.cat.tan-a-div">
<head>
.........
</head>
<body>
.........
</body>
</TAN-A-div>
Taken from ar.cat.tan-a-div<code><TAN-A-div></code><TAN-A-div TAN-version="1 dev" id="tag:parkj@textalign.net,2015:ring01-TAN-A-ring02">
<head>
.........
</head>
<body>
.........
</body>
</TAN-A-div>
Taken from ringoroses.div.1<code>@seg</code>The attribute seg picks specific segments in a leaf div. There must be an appropriate number of splits declared for those leaf divs in <split-leaf-div-at>.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+)))?)*|.*\?\?\?.*)Used by: ~reanchor-div-ref-item, ~simple-textual-reference, ~claim-div-ref-item@seg may not be applied to any element that is not a leaf divSequences may not include values less than 1.Sequences may not include values greater than the maximum allowed.Sequences may not include ranges that go from a larger value to a smaller, e.g., 4 - 2.<code>@seg</code><TAN-A-div TAN-version="1 dev" id="tag:parkj@textalign.net,2015:ar.cat.tan-a-div">
.........
<body>
.........
<realign>
<anchor-div-ref src="grc" ref="5 1 5 - 5 1 7"/>
<div-ref src="fra" ref="5 5" seg="1-3"/>
</realign>
<realign>
<anchor-div-ref src="grc" ref="5 2 1 - 5 2 2"/>
<div-ref src="fra" ref="5 6" seg="1-2"/>
</realign>
.........
<realign>
<anchor-div-ref src="grc" ref="5 4 1 - 5 4 5"/>
<div-ref src="fra" ref="5 12" seg="1-5"/>
</realign>
<realign>
<anchor-div-ref src="grc" ref="5 4 6 - 5 4 7"/>
<div-ref src="fra" ref="5 13" seg="1-2"/>
</realign>
.........
</body>
</TAN-A-div>
Taken from ar.cat.tan-a-div<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.The attribute work refers to works by means of source IDs as a proxy. Formal Definitionstring (pattern \S+)Used by: ~work-equiv, ~simple-textual-reference, ~complex-textual-reference-setNo <div> that is a member of a complex realignment may be used to align all members of a work (@src should be used instead of @work)<code>@work</code><TAN-A-div TAN-version="1 dev" id="tag:parkj@textalign.net,2015:ar.cat.tan-a-div:claims">
.........
<body claimant="lmp">
.........
<claim subject="andronicus boethus" adverb="perhaps" verb="omits" claim-basis="dexippus porphyry">
<locus work="grc">
<tok ref="1 a 2" pos="3-4"/>
</locus>
</claim>
<claim subject="herminus comm-omnes" verb="agrees">
<locus work="grc">
<tok ref="1 a 2" pos="3-4"/>
</locus>
</claim>
.........
<claim subject="B" verb="replaces">
<locus work="grc">
<tok ref="1 a 5" pos="1-2"/>
</locus>
<object>τις ἀποδιδῷ</object>
</claim>
<claim subject="Λ" adverb="perhaps" verb="replaces">
<locus work="grc">
<tok ref="1 a 5" pos="1-2"/>
</locus>
<object>τις ἀποδιδῷ</object>
</claim>
<claim subject="π α φ ο" verb="agrees">
<locus work="grc">
<tok ref="1 a 5" pos="1-2"/>
</locus>
</claim>
</body>
</TAN-A-div>
Taken from ar.cat.tan-a-div.claimsTAN-A-tok elements and attributes summarized<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> | ~tok-sequence)+)))Used by: ~itemA defective reference is a value of @ref that corresponds to a <div> in some but not all sources in a work. If a defective reference is used, a warning will be reported, identifying the sources that lack the appropriate <div>.No <div> that is a member of a complex realignment may be used to align all members of a work (@src should be used instead of @work)A <tok> may not duplicate any sibling <tok>.<code><align></code><TAN-A-tok TAN-version="1 dev" 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" pos="1"/>
<tok src="ring1987" ref="1" pos="1"/>
</align>
<align>
<tok src="ring1881" ref="1" pos="2"/>
<tok src="ring1987" ref="1" pos="2"/>
</align>
<align>
<tok src="ring1881" ref="1" pos="3"/>
<tok src="ring1987" ref="1" pos="3"/>
</align>
<align>
<tok src="ring1881" ref="1" pos="4"/>
<tok src="ring1987" ref="1" pos="4"/>
</align>
<align>
.........
</align>
.........
</body>
</TAN-A-tok>
Taken from ringoroses.01+02.token.1<code><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~decl-pattern-defaultUsed by: ~declaration-items<code><bitext-relation></code> <declarations>
<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>
.........
</declarations>
Taken from ringoroses.01+02.token.1<code><bitext-relation></code> <declarations>
<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>
.........
</declarations>
Taken from ringoroses.01+03.token.1<code><bitext-relation></code> <declarations>
<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>
.........
</declarations>
Taken from ringoroses.01+03.token.2<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~decl-pattern-default<code><reuse-type></code> <declarations>
<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"/>
</declarations>
Taken from ringoroses.01+02.token.1<code><reuse-type></code> <declarations>
<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>
.........
</declarations>
Taken from ringoroses.01+03.token.1<code><reuse-type></code> <declarations>
<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"/>
.........
</declarations>
Taken from ringoroses.01+03.token.2<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-rootEvery validated TAN file will include the following message at its root. 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.<code><TAN-A-tok></code><TAN-A-tok TAN-version="1 dev" 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="1 dev" 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="1 dev" 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>@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 DefinitionUsed by: ~other-body-attributes, ~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="1 dev" 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="1 dev" 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="1 dev" 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>@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 DefinitionUsed by: ~other-body-attributes, ~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="1 dev" 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="1 dev" 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="1 dev" 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.2TAN-LM-core elements and attributes summarized<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?, @xml:id?,
(<comment>* & ((<tok> | ~tok-sequence)+, <lm>+))))Used by: ~itemA <tok> may not duplicate any sibling <tok>.<code><ana></code><TAN-LM TAN-version="1 dev" id="tag:kalvesmaki.com,2014:tan-t:ar.cat.grc.1949.minio-paluello:semantic-refs:TAN-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-LM>
Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-LM-sample<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, textUsed by: ~TAN-LM-item<code><l></code><TAN-LM TAN-version="1 dev" id="tag:kalvesmaki.com,2014:tan-t:ar.cat.grc.1949.minio-paluello:semantic-refs:TAN-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-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, <for-lang>*, (
((<IRI>+, ~metadata-human, <checksum>*, <location>+) | @which) |
((<IRI>+, ~metadata-human) | @which))))Used by: ~declaration-items<code><lexicon></code> <head>
.........
<declarations>
<token-definition regex="[\w]+"/>
<lexicon xml:id="LSJ">
<for-lang>grc</for-lang>
<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">
<for-lang>grc</for-lang>
<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">
<for-lang>grc</for-lang>
<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>
.........
</declarations>
.........
</head>
Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-LM-sample<code><lexicon></code> <declarations>
<morphology xml:id="penn" ed-when="2015-08-20-04:00" ed-who="park">
.........
</morphology>
<lexicon xml:id="test">
<IRI>tag:kalvesmaki@gmail.com,2014:lexicon:eng:test</IRI>
<name>test lexicon</name>
</lexicon>
<token-definition which="letters and punctuation"/>
</declarations>
Taken from ring-o-roses.eng.1881.lm<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>+)))Used by: <ana><code><lm></code><TAN-LM TAN-version="1 dev" id="tag:kalvesmaki.com,2014:tan-t:ar.cat.grc.1949.minio-paluello:semantic-refs:TAN-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-LM>
Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-LM-sample<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]+)*)Used by: ~TAN-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 <assert> (<report>) must be true (false) otherwise an error will be returned.Every condition of an uncertain but relevant <assert> (<report>) must be true (false) otherwise a warning will be returned.<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>+)))))Used by: ~declaration-items<code><morphology></code> <declarations>
.........
<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"/>
</declarations>
Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-LM-sample<code><morphology></code> <declarations>
<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="test">
.........
</lexicon>
.........
</declarations>
Taken from ring-o-roses.eng.1881.lm<code><TAN-LM></code>The element TAN-LM specifies that the file is a TAN file containing lexico-morphology data about a text. Root element.Formal Definition~TAN-rootEvery validated TAN file will include the following message at its root. 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.<code><TAN-LM></code><TAN-LM TAN-version="1 dev" id="tag:kalvesmaki.com,2014:tan-t:ar.cat.grc.1949.minio-paluello:semantic-refs:TAN-LM:2016-04-05T07:07:40.033-04:00">
<head>
.........
</head>
<body lexicon="LSJ Lampe new" morphology="Perseus">
.........
</body>
</TAN-LM>
Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-LM-sample<code><TAN-LM></code><TAN-LM TAN-version="1 dev" id="tag:parkj@textalign.net,2015:ring01-lm">
<head>
.........
</head>
<body lexicon="test" morphology="penn" in-progress="false">
.........
</body>
</TAN-LM>
Taken from ring-o-roses.eng.1881.lm<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 DefinitionUsed by: <l><code>@lexicon</code>The attribute lexicon points to one or more <lexicon> or <agent> IDsThis attribute is inheritable. See Formal DefinitionUsed by: ~other-body-attributes, ~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-LM TAN-version="1 dev" id="tag:kalvesmaki.com,2014:tan-t:ar.cat.grc.1949.minio-paluello:semantic-refs:TAN-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-LM>
Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-LM-sample<code>@lexicon</code><TAN-LM TAN-version="1 dev" id="tag:parkj@textalign.net,2015:ring01-lm">
<head>
.........
</head>
<body lexicon="test" morphology="penn" in-progress="false">
<ana>
.........
<lm>
<l lexicon="test">ring-a-ring-a-rose</l>
<m>NNS ;</m>
</lm>
</ana>
<ana>
.........
</ana>
<ana xml:id="anatest">
.........
</ana>
.........
</body>
</TAN-LM>
Taken from ring-o-roses.eng.1881.lm<code>@morphology</code>The attribute morphology points to one or more <morphology> IDsThis attribute is inheritable. See Formal DefinitionUsed by: ~other-body-attributes, ~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-LM TAN-version="1 dev" id="tag:kalvesmaki.com,2014:tan-t:ar.cat.grc.1949.minio-paluello:semantic-refs:TAN-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-LM>
Taken from ar.cat.grc.1949.minio-paluello-sem-TAN-LM-sample<code>@morphology</code><TAN-LM TAN-version="1 dev" id="tag:parkj@textalign.net,2015:ring01-lm">
<head>
.........
</head>
<body lexicon="test" morphology="penn" in-progress="false">
<ana>
.........
</ana>
<ana>
.........
</ana>
<ana xml:id="anatest">
.........
</ana>
.........
</body>
</TAN-LM>
Taken from ring-o-roses.eng.1881.lmTAN-LM elements and attributes summarizedNo attributes or elements are defined for TAN-LM.TAN-LM-lang elements and attributes summarizedNo attributes or elements are defined for TAN-LM-lang.TAN-class-3 elements and attributes summarizedNo attributes or elements are defined for TAN-class-3.TAN-key elements and attributes summarized<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)))Used by: ~item, ~TAN-body-core, ~body-group@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="1 dev" 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><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-rootEvery validated TAN file will include the following message at its root. 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.<code><TAN-key></code><TAN-key TAN-version="1 dev" 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="1 dev" 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="1 dev" 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="1 dev" id="tag:textalign.net,2015:tan-key:features">
<head>
.........
</head>
<body in-progress="false" affects-element="feature">
.........
</body>
</TAN-key>
Taken from features.TAN-keyTAN-mor elements and attributes summarized<code><assert></code>The element assert names a pattern that, if found to be false in any <m> in a dependent TAN-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~test-patternUsed by: ~TAN-R-mor-body@feature-test and @context must point to one or more feature @codes or @xml:ids a space or +<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 |
(<comment>* & (<feature>, <feature>+)))Used by: ~category-list<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~feature-pattern~feature-pattern-no-codeUsed by: ~feature-list, ~categoryEvery <feature> inclusion must support every language that has been declared.<code><feature></code><TAN-mor TAN-version="1 dev" id="tag:kalvesmaki.com,2014:tan-r-mor:eng:penn">
.........
<body>
<for-lang>eng</for-lang>
<feature code="''">
<IRI>tag:textalign.net,2015:morphology:option:quotation-mark-closing</IRI>
<name>closing quotation mark</name>
<desc>Examples: ' ''</desc>
</feature>
<feature code="--">
<IRI>http://dbpedia.org/resource/Dash</IRI>
<name>dash</name>
<desc>Examples: --</desc>
</feature>
<feature code="$">
<IRI>http://dbpedia.org/resource/Dollar_sign</IRI>
<name>dollar</name>
<desc>Examples: $ -$ --$ A$ C$ HK$ M$ NZ$ S$ U.S.$ US$</desc>
</feature>
<feature code="[">
<IRI>tag:textalign.net,2015:morphology:option:bracket-opening</IRI>
<name>opening bracket</name>
<desc>Examples: ( [ {</desc>
</feature>
<feature code="]">
.........
</feature>
.........
</body>
</TAN-mor>
Taken from eng.kalvesmaki.com,2014.2<code><report></code>The element report names a pattern that, if found to be true in any <m> in a dependent TAN-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~test-patternUsed by: ~TAN-R-mor-body@feature-test and @context must point to one or more feature @codes or @xml:ids a space or +<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-rootEvery validated TAN file will include the following message at its root. 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.<code><TAN-mor></code><TAN-mor TAN-version="1 dev" id="tag:kalvesmaki.com,2014:tan-r-mor:eng:penn">
<head>
.........
</head>
<body>
.........
</body>
</TAN-mor>
Taken from eng.kalvesmaki.com,2014.2<code>@code</code>The attribute code contains a string that serves as an identifier for <feature>.Formal Definitionstring (pattern [^\-\+\s]|[^\+\s]+)Used by: ~feature-patternCodes for (@xml:id or @code) features must be case-indifferently unique within a given category.<code>@code</code><TAN-mor TAN-version="1 dev" id="tag:kalvesmaki.com,2014:tan-r-mor:eng:penn">
.........
<body>
<for-lang>eng</for-lang>
<feature code="''">
<IRI>tag:textalign.net,2015:morphology:option:quotation-mark-closing</IRI>
<name>closing quotation mark</name>
<desc>Examples: ' ''</desc>
</feature>
<feature code="--">
<IRI>http://dbpedia.org/resource/Dash</IRI>
<name>dash</name>
<desc>Examples: --</desc>
</feature>
<feature code="$">
<IRI>http://dbpedia.org/resource/Dollar_sign</IRI>
<name>dollar</name>
<desc>Examples: $ -$ --$ A$ C$ HK$ M$ NZ$ S$ U.S.$ US$</desc>
</feature>
<feature code="[">
<IRI>tag:textalign.net,2015:morphology:option:bracket-opening</IRI>
<name>opening bracket</name>
<desc>Examples: ( [ {</desc>
</feature>
<feature code="]">
.........
</feature>
.........
</body>
</TAN-mor>
Taken from eng.kalvesmaki.com,2014.2<code>@context</code>The attribute context specifies under what conditions a particular <assert> or <report> should be enforced. When an <m> in a dependent TAN-LM file is validated, if it contains the codes for the features in question, the other conditions of the <assert> or <report> will be checked; otherwise, the <assert> or <report> will be ignored.Formal DefinitionUsed by: ~test-pattern@feature-test and @context must point to one or more feature @codes or @xml:ids a space or +<code>@feature-qty-test</code>The attribute feature-qty-test 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+)))?)*|.*\?\?\?.*)Used by: ~test-patternSequences may not include values less than 1.Sequences may not include values greater than the maximum allowed.Sequences may not include ranges that go from a larger value to a smaller, e.g., 4 - 2.<code>@feature-test</code>The attribute feature-test 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\+]+)*)Used by: ~test-pattern@feature-test and @context must point to one or more feature @codes or @xml:ids a space or +<code>@matches-m</code>The attribute matches-m 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 DefinitionUsed by: ~test-patternAttributes that take a regular expression must use escape sequences recognized by XML schema or TAN escape extensions (\k{}). See http://www.w3.org/TR/xmlschema-2/#regexs for details.<code>@matches-tok</code>The attribute matches-tok 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 DefinitionUsed by: ~test-patternAttributes that take a regular expression must use escape sequences recognized by XML schema or TAN escape extensions (\k{}). See http://www.w3.org/TR/xmlschema-2/#regexs for details.TAN-c elements and attributes summarized<code><TAN-c></code>The element TAN-c specifies that the TAN file makes assertions subject a conceptual work. Root element.Formal Definition~TAN-rootEvery validated TAN file will include the following message at its root. 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.TAN-c-core elements and attributes summarized<code><claim></code>The element claim contains one or more claims.Formal Definition
(~inclusion |
(~ed-stamp?,
(@cert | (@cert, @cert2))?, @claimant?, @adverb?, @verb?, @where?, (
(@subject | <subject>+)? &
(@object |
(<object> | <claim>+)+)? & <locus>+? & <when>* &
(@claim-basis | <claim-basis>+)?)))Used by: ~set-of-claims, ~TAN-c-item, ~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 subject, either @subject (self or ancestral <body>) or a child <subject><code><claim-basis></code>The element claim-basis points to a textual passage that serves as the rationale for why a claim was made.Formal Definition~ed-stamp?, {empty}Used by: ~rationale<code><locus></code>Formal Definition~ed-stamp?, {empty}Used by: ~claim<code><locus></code><TAN-A-div TAN-version="1 dev" id="tag:parkj@textalign.net,2015:ar.cat.tan-a-div:claims">
.........
<body claimant="lmp">
.........
<claim subject="andronicus boethus" adverb="perhaps" verb="omits" claim-basis="dexippus porphyry">
<locus work="grc">
<tok ref="1 a 2" pos="3-4"/>
</locus>
</claim>
<claim subject="herminus comm-omnes" verb="agrees">
<locus work="grc">
<tok ref="1 a 2" pos="3-4"/>
</locus>
</claim>
.........
<claim subject="B" verb="replaces">
<locus work="grc">
<tok ref="1 a 5" pos="1-2"/>
</locus>
<object>τις ἀποδιδῷ</object>
</claim>
<claim subject="Λ" adverb="perhaps" verb="replaces">
<locus work="grc">
<tok ref="1 a 5" pos="1-2"/>
</locus>
<object>τις ἀποδιδῷ</object>
</claim>
<claim subject="π α φ ο" verb="agrees">
<locus work="grc">
<tok ref="1 a 5" pos="1-2"/>
</locus>
</claim>
</body>
</TAN-A-div>
Taken from ar.cat.tan-a-div.claims<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~decl-pattern-defaultUsed by: ~TAN-c-decl-core<code><modal></code> <declarations>
.........
<verb xml:id="replaces" which="replaces" object-datatype="string"/>
<modal which="possibly" xml:id="perhaps"/>
</declarations>
Taken from ar.cat.tan-a-div.claims<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 | {empty})Used by: ~claim, ~complex-object<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="1 dev" id="tag:parkj@textalign.net,2015:ar.cat.tan-a-div:claims">
.........
<body claimant="lmp">
.........
<claim subject="B" verb="replaces">
<locus work="grc">
.........
</locus>
<object>τις ἀποδιδῷ</object>
</claim>
<claim subject="Λ" adverb="perhaps" verb="replaces">
<locus work="grc">
.........
</locus>
<object>τις ἀποδιδῷ</object>
</claim>
.........
</body>
</TAN-A-div>
Taken from ar.cat.tan-a-div.claims<code><person></code>The element person contains an IRI + name pattern identifying a person. This element is very similar to <agent>, but does not imply that the person had anything to do with the data in the TAN file.Although person implies a single individual, this element may be applied to corporate entities, or groups of more than one person.Formal Definition~decl-pattern-defaultUsed by: ~TAN-c-decl-core<code><person></code> <head>
.........
<declarations>
<person xml:id="andronicus">
<IRI>https://inpho.cogs.indiana.edu/thinker/2532</IRI>
<IRI>http://dbpedia.org/resource/Andronicus_of_Rhodes</IRI>
<name>Andronicus of Rhodes</name>
</person>
<person xml:id="boethus">
<IRI>http://dbpedia.org/resource/Boethus_of_Sidon</IRI>
<name>Boethus of Sidon</name>
</person>
<person xml:id="dexippus">
<IRI>http://dbpedia.org/resource/Dexippus</IRI>
<name>Dexippus</name>
</person>
<person xml:id="herminus">
<IRI>http://dbpedia.org/resource/Herminus</IRI>
<name>Herminus</name>
</person>
<person xml:id="porphyry">
.........
</person>
.........
</declarations>
.........
</head>
Taken from ar.cat.tan-a-div.claims<code><place></code>The element place contains an IRI + name pattern identifying a spatial location, usually somewhere on earthFormal Definition~decl-pattern-defaultUsed by: ~TAN-c-decl-core<code><scriptum></code>The element scriptum contains an IRI + name pattern identifying a text-bearing object.Formal Definition~decl-pattern-defaultUsed by: ~TAN-c-decl-core<code><scriptum></code> <head>
.........
<declarations>
.........
<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"/>
.........
</declarations>
.........
</head>
Taken from ar.cat.tan-a-div.claims<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?, {empty}Used by: ~set-of-claims, ~other-body-attributes, ~claim, ~subjectEvery <claim> must have at least one subject, either @subject (self or ancestral <body>) or a child <subject><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~decl-pattern-defaultUsed by: ~TAN-c-decl-core<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~decl-pattern-defaultUsed by: ~TAN-c-decl-core<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?, ~decl-pattern-defaultUsed by: ~set-of-claims, ~other-body-attributes, ~TAN-c-decl-core, ~claimClaims 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>
.........
<declarations>
.........
<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"/>
<modal which="possibly" xml:id="perhaps"/>
</declarations>
.........
</head>
Taken from ar.cat.tan-a-div.claims<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 DefinitionUsed by: ~claim<code>@adverb</code><TAN-A-div TAN-version="1 dev" id="tag:parkj@textalign.net,2015:ar.cat.tan-a-div:claims">
.........
<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 suggests 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, these
sources show that the claim is not that Andronicus and Boethus omitted the text, or
relied on sources that had omitted it, but that they observed that there were
manuscripts that had done so.</comment>
<claim subject="andronicus boethus" adverb="perhaps" verb="omits" claim-basis="dexippus porphyry">
<locus work="grc">
.........
</locus>
</claim>
<claim subject="herminus comm-omnes" verb="agrees">
.........
</claim>
.........
<claim subject="B" verb="replaces">
.........
</claim>
<claim subject="Λ" adverb="perhaps" verb="replaces">
<locus work="grc">
.........
</locus>
<object>τις ἀποδιδῷ</object>
</claim>
<claim subject="π α φ ο" verb="agrees">
.........
</claim>
</body>
</TAN-A-div>
Taken from ar.cat.tan-a-div.claims<code>@claim-basis</code>The attribute claim-basis points to an entity that serves as the rationale for why a claim was made. Formal DefinitionUsed by: ~rationale<code>@claim-basis</code> <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 suggests 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, these
sources show that the claim is not that Andronicus and Boethus omitted the text, or
relied on sources that had omitted it, but that they observed that there were
manuscripts that had done so.</comment>
<claim subject="andronicus boethus" adverb="perhaps" verb="omits" claim-basis="dexippus porphyry">
<locus work="grc">
.........
</locus>
</claim>
<claim subject="herminus comm-omnes" verb="agrees">
.........
</claim>
.........
</body>
Taken from ar.cat.tan-a-div.claims<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 DefinitionUsed by: ~set-of-claims, ~other-body-attributes, ~claim<code>@claimant</code><TAN-A-div TAN-version="1 dev" 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 suggests 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, these
sources show that the claim is not that Andronicus and Boethus omitted the text, or
relied on sources that had omitted it, but that they observed that there were
manuscripts that had done so.</comment>
<claim subject="andronicus boethus" adverb="perhaps" verb="omits" claim-basis="dexippus porphyry">
.........
</claim>
<claim subject="herminus comm-omnes" verb="agrees">
.........
</claim>
.........
</body>
</TAN-A-div>
Taken from ar.cat.tan-a-div.claims<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 DefinitionUsed by: ~claim, ~object<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 <declarations>.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)Used 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> <declarations>
.........
<verb xml:id="agrees" which="agrees"/>
<verb xml:id="replaces" which="replaces" object-datatype="string"/>
<modal which="possibly" xml:id="perhaps"/>
</declarations>
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 DefinitionUsed 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>@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 DefinitionUsed by: ~set-of-claims, ~other-body-attributes, ~claim, ~subjectEvery <claim> must have at least one subject, either @subject (self or ancestral <body>) or a child <subject><code>@units</code>The attribute units points to the ID ref of a <unit>, defining the type of units.Formal DefinitionUsed by: ~nontextual-reference<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 DefinitionUsed by: ~set-of-claims, ~other-body-attributes, ~claimAny predefined strictures on verbs must be respected.Every <claim> must have at least one subject, either @subject (self or ancestral <body>) or a child <subject><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 DefinitionUsed by: ~claimTAN patterns<code>~agent-list</code>Formal Definition<agent>Used by: ~TAN-head<code>~agent-ref</code>Formal Definition@whoUsed by: ~comment, ~agent-role-list, ~change-list<code>~agent-role-list</code>Formal Definition<agentrole>Used by: ~TAN-head<code>~alignment</code>Formal Definition<align>Used by: ~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?Used by: ~alignment<code>~alignment-content-non-class-2</code>TAN-A-tok: alignments must contain one or more toksFormal Definition(<tok> | ~tok-sequence)+Used by: ~alignment<code>~alignment-inclusion-opt</code>Formal Definition~inclusionUsed by: ~alignment<code>~anchor-div-ref-item</code>Formal Definition<anchor-div-ref>Used by: ~realignment<code>~any-attribute</code>Formal Definition@[ANY]Used by: ~any-element<code>~any-content</code>Formal Definition(<[ANY]>* & text)Used by: ~TAN-tail, ~any-element<code>~any-element</code>Formal Definition<[ANY]>Used by: ~any-content<code>~assert</code>Formal Definition<assert>Used by: ~TAN-R-mor-body<code>~attr-cert</code>Formal Definition@certUsed by: ~cert-claim<code>~attr-cert2</code>Formal Definition@cert2Used by: ~cert-claim<code>~bitext-relation-attr</code>Formal Definition@bitext-relationUsed by: ~other-body-attributes, ~alignment-attributes-non-class-2<code>~body-group</code>Formal Definition{empty}<group>Used by: ~body-group-opt, ~body-group<code>~body-group-opt</code>Formal Definition<group><group><group>*{empty}<group>Used by: ~TAN-body-core<code>~category</code>Formal Definition<category>Used by: ~category-list<code>~category-feature</code>Formal Definition<feature>Used by: ~category<code>~category-list</code>Formal Definition<category>*Used by: ~TAN-R-mor-body<code>~cert-claim</code>Formal Definition
(@cert | (@cert, @cert2))Used by: ~claim, ~tok-with-src-and-cont, ~cert-opt, ~certainty-stamp<code>~cert-content</code>Formal Definitiondouble (pattern 1|0|(0\.\d*[1-9]))Used by: ~attr-cert, ~attr-cert2<code>~cert-opt</code>Formal Definition
(@cert | (@cert, @cert2))?Used by: ~tok-cert-opt<code>~certainty-stamp</code>Formal Definition
(@cert | (@cert, @cert2))?, ~ed-stamp?Used by: ~alignment, ~test-pattern, ~TAN-LM-item, ~lexeme, ~morph<code>~change-list</code>Formal Definition<change>+Used by: ~TAN-head<code>~char-ref</code>Formal Definition@charsUsed by: ~tok-attr-core<code>~checksum</code>Formal Definition<checksum>Used by: ~entity-digital-tan-other-ref, ~entity-digital-generic-ref<code>~claim</code>Formal Definition<claim>Used by: ~set-of-claims, ~TAN-c-item, ~complex-object<code>~claim-div-ref-item</code>Formal Definition<div-ref>Used by: ~complex-text-ref<code>~claimant</code>Formal Definition@claimantUsed by: ~set-of-claims, ~other-body-attributes, ~claim<code>~code</code>Formal Definition@codeUsed by: ~feature-pattern<code>~comment</code>Formal Definition<comment>Used by: ~split, ~realignment, ~alignment, ~feature-pattern, ~feature-pattern-no-code, ~category, ~decl-div, ~decl-filt, ~decl-filt-norm, ~func-replace, ~decl-pattern-default, ~decl-pattern-no-id, ~decl-pattern-language, ~decl-group-type, ~TAN-head, ~TAN-body, ~nonsource-rights, ~inclusion-item, ~key-item, ~source-item, ~source-rights, ~see-also-item, ~decl-opt, ~agent-list, ~role-list, ~TAN-LM-item<code>~complex-object</code>Formal Definition(<object> | <claim>+)Used by: ~object<code>~complex-rationale</code>Formal Definition<claim-basis>Used by: ~rationale<code>~complex-subject</code>Formal Definition{empty}<subject>Used by: ~subject<code>~complex-text-ref</code>Formal Definition(<div-ref> | <tok>)Used by: ~complex-textual-reference-set<code>~complex-textual-reference-set</code>Formal Definition(
{[TAN-class-2 (~source-refs):] @src} OR
{[TAN-core (~source-refs):] {empty}} | @work),
(<div-ref> | <tok>)+Used by: ~textual-reference<code>~continuation</code>Formal Definition@contUsed by: ~continuation-opt<code>~continuation-opt</code>Formal Definition{empty}@contUsed by: ~tok-with-src-and-cont, ~tok-with-cont-but-no-src<code>~decl-alias</code>Formal Definition<alias>Used by: ~declaration-core<code>~decl-brel</code>Formal Definition<bitext-relation>Used by: ~declaration-items<code>~decl-class-1</code>TAN-class-1: Class 1 files must declare a single work, perhaps one version, one or more divisions, one or more recommended tokenizations, perhaps one filter, and perhaps one Formal Definition(<work> & <version>? & <div-type>+ & <token-definition>* & <filter>?)Used by: ~declaration-items<code>~decl-div</code>Formal Definition<div-type>Used by: ~decl-class-1<code>~decl-filt</code>Formal Definition<filter>Used by: ~decl-class-1<code>~decl-filt-norm</code>Formal Definition<normalization>Used by: ~decl-filter-content<code>~decl-filt-repl</code>TAN-class-1: Replacements that have been made to an XML source file. Formal Definition<replace>Used by: ~decl-filter-content<code>~decl-filt-tlit</code>Formal Definition<transliteration>Used by: ~decl-filter-content<code>~decl-filter-content</code>Formal Definition(<normalization>* & <replace>* & <transliteration>*)Used by: ~decl-filt<code>~decl-group-type</code>Formal Definition<group-type>Used by: ~declaration-items, ~TAN-key-decl<code>~decl-id-ref-opt</code>TAN-A-div: declarations by default have idsTAN-A-tok: all declarations must have idsTAN-c: declarations by default have idsTAN-key: all declarations must have idsTAN-mor: no declarations may have idsTAN-core: Option to allow an @xml:id in children of <declarations>Formal Definition@xml:id@xml:id@xml:id@xml:id{empty}{empty}Used by: ~decl-filt-norm, ~decl-pattern-default, ~decl-pattern-language<code>~decl-lexi</code>Formal Definition<lexicon>Used by: ~declaration-items<code>~decl-mode</code>Formal Definition<modal>Used by: ~TAN-c-decl-core<code>~decl-morph</code>Formal Definition<morphology>Used by: ~declaration-items<code>~decl-non-class-1</code>TAN-class-1: Reserved for declarations specific to individual types of class 1 filesFormal Definition{empty}Used by: ~declaration-items<code>~decl-opt</code>Formal Definition<declarations>Used by: ~TAN-head<code>~decl-pattern-default</code>Formal Definition~ed-stamp?,
(~inclusion |
(
{[TAN-A-div (~decl-id-ref-opt):] @xml:id} OR
{[TAN-A-tok (~decl-id-ref-opt):] @xml:id} OR
{[TAN-c (~decl-id-ref-opt):] @xml:id} OR
{[TAN-key (~decl-id-ref-opt):] @xml:id} OR
{[TAN-mor (~decl-id-ref-opt):] {empty}} OR
{[TAN-core (~decl-id-ref-opt):] {empty}}, (<comment>* &
((<IRI>+, ~metadata-human) | @which))))Used by: ~decl-brel, ~decl-reus, ~decl-place, ~decl-topic, ~decl-verb, ~decl-unit, ~decl-pers, ~decl-mode, ~decl-scri, ~decl-work, ~decl-vers<code>~decl-pattern-language</code>Formal Definition~ed-stamp?,
(~inclusion |
(
{[TAN-A-div (~decl-id-ref-opt):] @xml:id} OR
{[TAN-A-tok (~decl-id-ref-opt):] @xml:id} OR
{[TAN-c (~decl-id-ref-opt):] @xml:id} OR
{[TAN-key (~decl-id-ref-opt):] @xml:id} OR
{[TAN-mor (~decl-id-ref-opt):] {empty}} OR
{[TAN-core (~decl-id-ref-opt):] {empty}},
(<comment>* & (<for-lang>*,
((<IRI>+, ~metadata-human) | @which)))))Used by: ~decl-filt-tlit<code>~decl-pattern-no-id</code>Formal Definition~ed-stamp?,
(~inclusion | (<comment>* &
((<IRI>+, ~metadata-human) | @which)))<code>~decl-pers</code>Formal Definition<person>Used by: ~TAN-c-decl-core<code>~decl-place</code>Formal Definition<place>Used by: ~TAN-c-decl-core<code>~decl-rename-div-n</code>Formal Definition<rename-div-ns>Used by: ~declaration-items<code>~decl-reus</code>Formal Definition<reuse-type>+Used by: ~declaration-items<code>~decl-scri</code>Formal Definition<scriptum>Used by: ~TAN-c-decl-core<code>~decl-supp-div-type</code>Formal Definition<suppress-div-types>Used by: ~declaration-items<code>~decl-tok-def</code>Formal Definition<token-definition>Used by: ~declaration-items, ~decl-class-1, ~entity-tok-def<code>~decl-topic</code>Formal Definition<topic>Used by: ~TAN-c-decl-core<code>~decl-unit</code>Formal Definition<unit>Used by: ~TAN-c-decl-core<code>~decl-verb</code>Formal Definition<verb>Used by: ~TAN-c-decl-core<code>~decl-vers</code>Formal Definition<version>Used by: ~TAN-c-decl-core, ~decl-class-1<code>~decl-work</code>Formal Definition<work>Used by: ~TAN-c-decl-core, ~decl-class-1<code>~declaration-core</code>Formal Definition<alias>*Used by: ~decl-opt<code>~declaration-items</code>TAN-core: declaration-items to be filled out by each TAN-class-X.rnc fileTAN-LM-core: TAN-LM files must each have at least one lexicon and one TAN-mor declarationFormal Definition(<token-definition>* & <suppress-div-types>* & <rename-div-ns>* & )(<token-definition>* & <suppress-div-types>* & <rename-div-ns>* & <bitext-relation>+ & <reuse-type>++ & <group-type>*)<group-type>*(
(<work> & <version>? & <div-type>+ & <token-definition>* & <filter>?) & {empty}){empty}(<token-definition>* & <suppress-div-types>* & <rename-div-ns>* & <lexicon>+ & <morphology>+ & <group-type>*)Used by: ~decl-opt<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+)*)|.*\?\?\?.*)Used by: ~pointer-to-div-item<code>~div-range-ref</code>TAN-core: For more see Formal Definitionstring (pattern (\w+([^\w\-]\w+)*)(((\s*-\s*)|(\s*,\s+))(\w+([^\w\-]\w+)*))*|.*\?\?\?.*)Used by: ~pointer-to-div-range<code>~div-type-equiv</code>Formal Definition<equate-div-types>Used by: ~TAN-body-core<code>~div-type-ref</code>Formal Definition@div-type-refUsed by: ~div-type-ref-cluster, ~decl-supp-div-type, ~decl-rename-div-n<code>~div-type-ref-cluster</code>Formal Definition<div-type-ref>Used by: ~div-type-equiv<code>~ed-agent</code>Formal Definition@ed-whoUsed 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-whenUsed by: ~work-equiv, ~div-type-equiv, ~div-type-ref-cluster, ~split, ~anchor-div-ref-item, ~reanchor-div-ref-item, ~realignment, ~claim-div-ref-item, ~TAN-key-item, ~feature-pattern, ~feature-pattern-no-code, ~category, ~text-div, ~claim, ~complex-subject, ~object-element, ~locus, ~complex-rationale, ~decl-div, ~decl-filt, ~decl-filt-norm, ~func-replace, ~decl-supp-div-type, ~decl-rename-div-n, ~tok-attr-core, ~certainty-stamp, ~decl-pattern-default, ~decl-pattern-no-id, ~decl-pattern-language, ~decl-group-type, ~decl-tok-def, ~IRI-gen-ref, ~loc-self, ~loc-src, ~metadata-desc, ~TAN-root, ~TAN-head, ~TAN-body, ~body-group, ~nonsource-rights, ~inclusion-item, ~key-item, ~source-item, ~source-rights, ~see-also-item, ~relationship, ~decl-opt, ~agent-list, ~role-list, ~agent-role-list, ~change-list, ~decl-alias, ~decl-morph, ~decl-lexi, ~TAN-LM-item<code>~ed-time</code>Formal Definition@ed-whenUsed by: ~ed-stamp<code>~element-scope</code>Formal Definition@affects-elementUsed by: ~other-body-attributes, ~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)Used by: ~TAN-key-item, ~source-item, ~see-also-item, ~decl-lexi<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>+))Used by: ~TAN-key-item, ~metadata-human, ~inclusion-item, ~key-item, ~source-item, ~see-also-item, ~decl-morph<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>*Used by: ~TAN-head<code>~entity-nondigital-ref</code>TAN-core: Reference to an external non-digital entity (e.g., agents, roles, works, topics)Formal Definition
((<IRI>+, ~metadata-human) | @which)Used by: ~TAN-key-item, ~feature-pattern, ~feature-pattern-no-code, ~decl-div, ~decl-filt-norm, ~checksum, ~decl-pattern-default, ~decl-pattern-no-id, ~decl-pattern-language, ~decl-group-type, ~nonsource-rights, ~source-item, ~source-rights, ~see-also-item, ~relationship, ~agent-list, ~role-list, ~decl-lexi<code>~entity-tok-def</code>Formal Definition<token-definition>, ~metadata-humanUsed by: ~TAN-key-item<code>~error-flag</code>Formal Definition@flagsUsed by: ~change-list<code>~feature</code>TAN-mor: TAN-R-mor files declare the morphological features that are allowed for a given languageFormal Definition<feature>Used by: ~feature-list, ~category<code>~feature-list</code>Formal Definition<feature>*Used by: ~TAN-R-mor-body<code>~feature-pattern</code>Formal Definition~ed-stamp?,
(~inclusion |
(@code, (<comment>* &
((<IRI>+, ~metadata-human) | @which))))Used by: ~feature<code>~feature-pattern-no-code</code>Formal Definition~ed-stamp?,
(~inclusion | (<comment>* &
((<IRI>+, ~metadata-human) | @which)))Used by: ~category-feature<code>~feature-qty-test</code>Formal Definition@feature-qty-testUsed by: ~test-pattern<code>~feature-test</code>Formal Definition@feature-testUsed by: ~test-pattern<code>~filter</code>Formal Definition@contextUsed by: ~test-pattern<code>~func-param-flags</code>Formal Definition@flagsUsed by: ~func-replace, ~decl-tok-def<code>~func-param-pattern</code>Formal Definition@regexUsed by: ~func-replace, ~decl-tok-def<code>~func-replace</code>Formal Definition<replace>Used by: ~decl-filt-repl<code>~grammar-attr</code>Formal Definition@morphologyUsed by: ~other-body-attributes, ~morph<code>~group-attributes</code>Formal Definition@type?, @affects-element?@type, @n?@type, @n?Used by: ~body-group<code>~group-ref</code>Formal Definition@groupUsed by: ~non-class-2-opt, ~TAN-key-item, ~TAN-LM-item<code>~help-opt</code>Formal Definition@helpUsed by: ~inclusion<code>~href-opt</code>Formal Definition@hrefUsed 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-LM files.Formal Definition@xml:id{empty}<code>~inclusion</code>Formal Definition@include, @help?Used by: ~work-equiv, ~div-type-equiv, ~split, ~realignment, ~alignment-inclusion-opt, ~TAN-key-item, ~feature-pattern, ~feature-pattern-no-code, ~category, ~test-pattern, ~text-div, ~claim, ~decl-div, ~decl-filt-norm, ~func-replace, ~decl-supp-div-type, ~decl-rename-div-n, ~decl-pattern-default, ~decl-pattern-no-id, ~decl-pattern-language, ~decl-group-type, ~decl-tok-def, ~body-group, ~nonsource-rights, ~key-item, ~source-item, ~source-rights, ~see-also-item, ~relationship, ~agent-list, ~role-list, ~agent-role-list, ~decl-alias, ~decl-morph, ~decl-lexi, ~TAN-LM-item<code>~inclusion-att</code>Formal Definition@includeUsed by: ~inclusion<code>~inclusion-item</code>Formal Definition<inclusion>Used by: ~inclusion-list<code>~inclusion-list</code>Formal Definition<inclusion>*Used by: ~TAN-head<code>~internal-id</code>Formal Definition@xml:idUsed by: ~decl-id-ref-opt, ~source-id-opt, ~alignment-attributes-non-class-2, ~decl-div, ~id-option, ~decl-group-type, ~inclusion-item, ~agent-list, ~role-list, ~decl-alias, ~decl-morph, ~decl-lexi, ~TAN-LM-item<code>~internal-idrefs</code>Formal Definition@idrefsUsed by: ~decl-alias<code>~IRI-gen</code>TAN-core: Any generic IRI identifier.Formal DefinitionanyURI (pattern [a-zA-Z][\-.+a-zA-Z0-9]+:\S+)Used by: ~IRI-gen-ref<code>~IRI-gen-ref</code>Formal Definition<IRI>Used by: ~entity-digital-tan-other-ref, ~entity-digital-generic-ref, ~entity-nondigital-ref<code>~item</code>Formal Definition<align>+<item><div>{empty}<ana>Used by: ~TAN-body-core, ~body-group<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+))|.*\?\?\?.*)Used by: ~item-pos-ref<code>~item-pos-ref</code>Formal Definition@posUsed by: ~tok-sequence-attr-core<code>~key-item</code>Formal Definition<key>Used by: ~key-list<code>~key-list</code>Formal Definition<key>*Used by: ~TAN-head<code>~keyword-ref</code>Formal Definition@whichUsed by: ~decl-tok-def, ~entity-digital-generic-ref, ~entity-nondigital-ref, ~metadata-human, ~decl-morph<code>~lang-of-content</code>Formal Definition@xml:langUsed by: ~other-body-attributes, ~text-div, ~nontextual-reference, ~metadata-desc<code>~lang-outside</code>Formal Definition<for-lang>Used by: ~source-list, ~TAN-R-mor-body, ~decl-pattern-language, ~decl-morph, ~decl-lexi<code>~lexeme</code>Formal Definition<l>Used by: ~TAN-LM-item<code>~lexicon-attr</code>Formal Definition@lexiconUsed by: ~other-body-attributes, ~lexeme<code>~loc-self</code>Formal Definition<master-location>Used by: ~entity-digital-tan-self-ref<code>~loc-src</code>Formal Definition<location>Used by: ~entity-digital-tan-other-ref, ~entity-digital-generic-ref<code>~locus</code>Formal Definition{empty}<locus>+Used by: ~claim<code>~matches-m</code>Formal Definition@matches-mUsed by: ~test-pattern<code>~matches-tok</code>Formal Definition@matches-tokUsed by: ~test-pattern<code>~metadata-desc</code>Formal Definition~ed-stamp?, (@xml:lang?,
string (pattern (.|\n)+))Used by: ~metadata-human<code>~metadata-human</code>Formal Definition<name>+, <desc>*Used by: ~entity-digital-tan-other-ref, ~entity-digital-generic-ref, ~entity-digital-tan-self-ref, ~entity-nondigital-ref, ~entity-tok-def<code>~modal-claim</code>Formal Definition@adverbUsed by: ~claim<code>~morph</code>Formal Definition<m>Used by: ~TAN-LM-item<code>~n</code>Formal Definition@nUsed by: ~text-div, ~group-attributes<code>~n-val</code>TAN-core: Acceptable values of @n, used by class 1 and class 2 files; this is related to div-range-ref, in that it allows ranges of items, but ignores "last", "max", or "all" keyterms.Formal Definitionstring (pattern (\w+|\d+-\d+)(\s+(\w+|\d+-\d+))*)Used by: ~name-change, ~n<code>~name-change</code>Formal Definition<rename>Used by: ~decl-rename-div-n<code>~non-class-2-opt</code>Formal Definition@group?Used by: ~alignment<code>~nonsource-rights</code>Formal Definition<rights-excluding-sources>Used by: ~TAN-head<code>~nontextual-reference</code>Formal Definition(@xml:lang | @units)?, textUsed by: ~object-element<code>~object</code>Formal Definition(@object |
(<object> | <claim>+)+)Used by: ~claim<code>~object-constraint</code>Formal Definition@object-datatype, @object-lexical-constraint?Used by: ~decl-verb<code>~object-datatype</code>Formal Definition@object-datatypeUsed by: ~object-constraint<code>~object-element</code>Formal Definition<object>Used by: ~complex-object<code>~object-lexical-constraint</code>Formal Definition@object-lexical-constraintUsed by: ~object-constraint<code>~other-body-attributes</code>Formal Definition@bitext-relation, @reuse-type?, ?@affects-element?@xml:lang{empty}@lexicon, @morphologyUsed by: ~TAN-body-core<code>~period-filter</code>Formal Definition<when>Used by: ~claim, ~agent-role-list<code>~place-filter</code>Formal Definition@whereUsed by: ~claim<code>~pointer-to-div-item</code>Formal Definition{empty}@refUsed by: ~tok-sequence-attr-core<code>~pointer-to-div-range</code>TAN-class-2: Pointer (link) to a div in a TAN-T(EI) fileFormal Definition{empty}@refUsed by: ~anchor-div-ref-item, ~reanchor-div-ref-item, ~simple-textual-reference, ~claim-div-ref-item, ~tok-regular<code>~progress</code>TAN-core: specifies whether the creation and editing of the data is still in progress. Default value is true.Formal Definition@in-progressUsed by: ~TAN-body<code>~rationale</code>Formal Definition(@claim-basis | <claim-basis>+)Used by: ~claim<code>~realignment</code>Formal Definition<realign>Used by: ~TAN-body-core<code>~reanchor-div-ref-item</code>Formal Definition<div-ref>Used by: ~realignment<code>~relationship</code>Formal Definition<relationship>Used by: ~see-also-item<code>~report</code>Formal Definition<report>Used by: ~TAN-R-mor-body<code>~reuse-type-attr</code>Formal Definition@reuse-typeUsed by: ~other-body-attributes, ~alignment-attributes-non-class-2<code>~rights-holder</code>Formal Definition@rights-holderUsed by: ~nonsource-rights, ~source-rights<code>~role-list</code>Formal Definition<role>Used by: ~TAN-head<code>~role-ref</code>Formal Definition@rolesUsed by: ~agent-list, ~agent-role-list<code>~see-also-item</code>Formal Definition<see-also>Used by: ~see-also-list<code>~see-also-list</code>Formal Definition<see-also>*Used by: ~TAN-head<code>~seg-ref</code>Formal Definition@segUsed by: ~reanchor-div-ref-item, ~simple-textual-reference, ~claim-div-ref-item<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+)))?)*|.*\?\?\?.*)Used by: ~seg-ref, ~feature-qty-test, ~seq-pos-ref, ~char-ref<code>~seq-pos-ref</code>Formal Definition{empty}@posUsed by: ~tok-regular<code>~set-of-claims</code>Formal Definition?, ?, +Used by: ~TAN-body-core<code>~simple-object</code>Formal Definition@objectUsed by: ~object<code>~simple-rationale</code>Formal Definition@claim-basisUsed by: ~rationale<code>~simple-subject</code>Formal Definition@subjectUsed by: ~subject<code>~simple-textual-reference</code>Formal Definition(
{[TAN-class-2 (~source-refs):] @src} OR
{[TAN-core (~source-refs):] {empty}} | @work), @ref, @seg?Used 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}Used by: ~source-item<code>~source-item</code>Formal Definition<source>Used 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-c: claims made of textual objects should be done in the context of TAN-A-div filesTAN-LM-lang: TAN-LM files point only to one sourceTAN-LM: TAN-LM files point only to one sourceTAN-class-3: Class 3 files allow zero or many sourcesFormal Definition<source>+<source>, <source>{empty}{empty}<for-lang><source><source>*<source>Used by: ~TAN-head<code>~source-ref</code>Formal Definition@srcUsed by: ~anchor-div-ref-item, ~tok-with-src-and-cont<code>~source-refs</code>TAN-LM-core: Because TAN-LM files depend on only one source, no id references to sources are neededFormal Definition@src{empty}{empty}Used by: ~div-type-ref-cluster, ~split, ~reanchor-div-ref-item, ~simple-textual-reference, ~complex-textual-reference-set, ~decl-supp-div-type, ~decl-rename-div-n, ~tok-source-ref-opt, ~decl-tok-def<code>~source-rights</code>TAN-class-2: All sources are TAN files, so no source rights should be declared--they're already statedFormal Definition{empty}<rights-source-only>Used by: ~source-item<code>~split</code>Formal Definition<split-leaf-div-at>Used by: ~TAN-body-core<code>~subject</code>Formal Definition(@subject | <subject>+)Used by: ~set-of-claims, ~other-body-attributes, ~claim<code>~TAN-body</code>Formal Definition<body>Used by: ~TAN-root<code>~TAN-body-core</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<equate-works>*, <equate-div-types>*, <split-leaf-div-at>*, <realign>*, ~set-of-claims?~TAN-R-mor-body
{[TAN-A-tok (~other-body-attributes):] ~other-body-attributes} OR
{[TAN-c (~other-body-attributes):] ~other-body-attributes} OR
{[TAN-key (~other-body-attributes):] @affects-element?} OR
{[TAN-T (~other-body-attributes):] @xml:lang} OR
{[TAN-core (~other-body-attributes):] {empty}} OR
{[TAN-LM-core (~other-body-attributes):] ~other-body-attributes}, (
{[TAN-A-tok (~body-group-opt):] <group>} OR
{[TAN-key (~body-group-opt):] <group>} OR
{[TAN-class-2 (~body-group-opt):] <group>*} OR
{[TAN-core (~body-group-opt):] {empty}} OR
{[TAN-LM-core (~body-group-opt):] <group>} |
{[TAN-A-tok (~item):] <align>} OR
{[TAN-c (~item):] +} OR
{[TAN-key (~item):] <item>} OR
{[TAN-T (~item):] <div>} OR
{[TAN-core (~item):] {empty}} OR
{[TAN-LM-core (~item):] <ana>})+Used by: ~TAN-body<code>~TAN-c-decl</code>Formal DefinitionUsed by: ~declaration-items<code>~TAN-c-decl-core</code>Formal Definition(<work>* & <place>* & <unit>* & <person>* & <modal>* & <version>* & <scriptum>* & <topic>* & <verb>*)Used by: ~declaration-items, ~TAN-c-decl<code>~TAN-c-item</code>Formal Definition+Used by: ~item<code>~TAN-head</code>Formal Definition<head>Used by: ~TAN-root<code>~TAN-key-decl</code>Formal Definition<group-type>*Used by: ~declaration-items<code>~TAN-key-item</code>Formal Definition<item>Used by: ~item<code>~TAN-LM-item</code>Formal Definition<ana>Used by: ~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>+,
((<feature>* | <category>*) & <assert>* & <report>*)Used by: ~TAN-body-core<code>~TAN-root</code>Formal Definition@id, @TAN-version, ~ed-stamp?, <head>, <body>, <tail>?Used by: <TAN-A-div>, <TAN-A-tok>, <TAN-c>, <TAN-key>, <TAN-mor>, <TAN-T>, <TAN-LM><code>~TAN-tail</code>Formal Definition<tail>?Used by: ~TAN-root<code>~TAN-ver</code>Formal Definition@TAN-versionUsed by: ~TAN-root<code>~test-pattern</code>TAN-mor: Test pattern attributes for determining whether to return the message provided by text.Formal Definition~certainty-stamp?,
(~inclusion |
(@context?, (@matches-m | @matches-tok | @feature-test | @feature-qty-test), text))Used by: ~assert, ~report<code>~text-div</code>Formal Definition<div>Used by: ~item, ~text-div<code>~textual-reference</code>Formal Definition(~simple-textual-reference | ~complex-textual-reference-set){empty}Used by: ~complex-subject, ~object-element, ~locus, ~complex-rationale<code>~tok-attr-core</code>Formal Definition~ed-stamp?, @chars?Used by: ~tok-regular, ~tok-sequence-attr-core<code>~tok-cert-opt</code>Formal Definition{empty}
(@cert | (@cert, @cert2))?Used by: ~tok-regular<code>~tok-regular</code>Formal Definition<tok>Used by: ~split, ~complex-text-ref, ~alignment-content-non-class-2, ~TAN-LM-item<code>~tok-sequence</code>Formal Definition<tok>, <tok>*, <tok>Used by: ~alignment-content-non-class-2, ~TAN-LM-item<code>~tok-sequence-attr-core</code>Formal Definition~tok-attr-core,
{[TAN-LM-lang (~pointer-to-div-item):] {empty}} OR
{[TAN-class-2 (~pointer-to-div-item):] @ref},
(@val | @pos | (@val, @pos))Used by: ~tok-with-src-and-cont, ~tok-with-cont-but-no-src, ~tok-without-cont-or-src<code>~tok-source-ref-opt</code>Formal Definition{empty}
{[TAN-class-2 (~source-refs):] @src} OR
{[TAN-core (~source-refs):] {empty}} OR
{[TAN-LM-core (~source-refs):] {empty}}Used by: ~tok-regular<code>~tok-with-cont-but-no-src</code>Formal Definition<tok>Used by: ~tok-sequence<code>~tok-with-src-and-cont</code>Formal Definition<tok>Used by: ~tok-sequence<code>~tok-without-cont-or-src</code>Formal Definition<tok>Used by: ~tok-sequence<code>~token-value-ref</code>Formal Definition@valUsed by: ~tok-regular, ~tok-sequence-attr-core<code>~type</code>Formal Definition@typeUsed by: ~group-attributes, ~text-div<code>~units</code>Formal Definition@unitsUsed 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+)Used by: ~TAN-root<code>~verb</code>Formal Definition@verbUsed by: ~set-of-claims, ~other-body-attributes, ~claim<code>~when-claim</code>Formal Definition@whenUsed by: ~comment, ~change-list<code>~work-equiv</code>Formal Definition<equate-works>Used by: ~TAN-body-core<code>~work-ref</code>Formal Definition@workUsed by: ~simple-textual-reference, ~complex-textual-reference-set<code>~work-refs</code>Formal Definition@workUsed by: ~work-equiv