Below is a list of 111 specifically defined TAN errors.The 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.

Token-based assertions of multiple class 2 TAN documents that share the same class 1 source may be compared or collated only if those class 2 documents adopt identical token definitions.General rule not affecting specific attibutes or elements.No variables, keys, functions, or named templates depend upon this error.

Assertions of multiple TAN-A-div documents that share the same class 1 source may be compared or collated only if they suppress, or fail to suppress, the same div types.General rule not affecting specific attibutes or elements.No variables, keys, functions, or named templates depend upon this error.

Mismatched sets of statistics may not be merged.General rule not affecting specific attibutes or elements.Used by function tan:merge-analyzed-stats()

Every @href in a catalog.tan.xml file must point to a document that is available.Affects: @hrefUsed by template ŧ catalog-expansion-terse

@root should match the target's root element nameAffects: @rootUsed by template ŧ catalog-expansion-terse

In a catalog.tan.xml, @id should match the target's root element @idAffects: @idUsed by template ŧ catalog-expansion-terse

Different TAN files should have unique @ids.Affects: @idUsed by template ŧ catalog-expansion-terse

@href values in catalog.tan.xml should be uniqueAffects: @hrefUsed by template ŧ catalog-expansion-terse

If a local catalog.tan.xml file lacks a reference to a TAN file being validated, a warning will appear.Affects: @idUsed by template ŧ core-expansion-verbose

A TAN file being validated verbosely will include errors reported in any local catalog.tan.xmlGeneral rule not affecting specific attibutes or elements.Used by template ŧ core-expansion-verbose

Every character must be locatable in every token in every ref in every source.Affects: @chars<tok>Used by template ŧ class-2-expansion-terse

Class 1 files must share the same source as any alternatively divided edition.Affects: <see-also> <relationship>Used by template ŧ core-expansion-terse

Class 1 files must share the same work as any model or alternatively divided edition.Affects: <see-also> <relationship>Used by template ŧ core-expansion-terse

Class 1 files must share the same work-version, if supplied, as any alternatively divided edition.Affects: <see-also> <relationship>Used by template ŧ core-expansion-terse

Class 1 files must have identical transcriptions, after TAN normalization, as any alternatively divided edition.Affects: <see-also> <relationship>Used by template ŧ class-1-expansion-verbose ŧ class-1-expansion-verbose ŧ class-1-expansion-verbose

A class 1 file may have no more than one model.Affects: <see-also> <relationship>Used by template ŧ core-expansion-terse

If a class 1 file diverges from the structure of its model a warning will be generated specifying where differences exist.Affects: <see-also> <relationship>Used by template ŧ class-1-expansion-verbose ŧ class-1-expansion-verbose

A work element may invoke no more than one inclusion.Affects: @include<work>Used by template ŧ core-expansion-terse

Leaf div references must be unique.Affects: @n<div>Used by template ŧ core-expansion-normal

Every leaf div must have at least some non-space text.Affects: <div>Used by template ŧ core-expansion-normal

No text may begin with a modifying character.Affects: <div>Used by template ŧ core-expansion-normal

No text may have a spacing character followed by a modifying character.Affects: <div>Used by template ŧ core-expansion-normal

No text may have Unicode characters that are disallowed, e.g., U+A0, NO BREAK SPACE.Affects: <div>Used by template ŧ core-expansion-normal

@n suffices for labeling text in a <div>; the @n's value should not appear in the text.Affects: @n<div>Used by template ŧ class-1-expansion-verbose

concatenated @n's suffice for labeling text in a <div>; the <div>'s reference should not appear in the text.Affects: @n<div>Used by template ŧ class-1-expansion-verbose

An @n taking digit values should not begin with 0.Affects: @n<div>Used by template ŧ dependency-expansion-terse

Sources are integral parts of a class 2 TAN file. Access to at least one copy is absolutely mandatory.Affects: <source>Used by template ŧ check-referred-doc

No source may be given more than one token definition.Affects: <token-definition>Used by template ŧ core-expansion-terse

@new may not take the same value as what it replaces.Affects: @new<rename>Used by template ŧ core-expansion-terse

No <tok> should duplicate any sibling <tok>.Affects: <tok> <ana> <align> <reassign> <subject> <object> <locus>Used by template ŧ core-expansion-normal

Only the first of multiple <rename>s that apply to a particular <div> will be applied.Affects: <rename>Used by template ŧ dependency-expansion-terse

@by may be applied only to those @n and @ref values that are calculable as integers.Affects: @by<rename>Used by template ŧ dependency-expansion-terse

If more than one <skip> applies to a <div> only the first will be applied.Affects: <skip>Used by template ŧ dependency-expansion-terse

At least one instance of an @n value should be found in each source.Affects: @n<rename>Used by template ŧ class-2-expansion-terse

In a <rename>, the number of values in @ref and @new must be identical.Affects: @new @ref<rename>Used by template ŧ core-expansion-terse

No alter action should result in the mixing of leaf <div>s and non-leaf <div>s.Affects: @new<reassign> <rename> <alter> <to>Used by template ŧ dependency-expansion-normal

Claims involving verbs whose object is constrained must use <object>, not @object.Affects: @object-datatype @object-lexical-constraint<claim> <verb>Used by template ŧ core-expansion-terse

Verbs that have object constraints must not be combined with other verbs in @verb.Affects: @object-datatype @object-lexical-constraint<claim> <verb>Used by template ŧ core-expansion-terse

<object>s taking strings must match the predefined @object-datatype for the verb.Affects: @object-datatype<object>Used by template ŧ core-expansion-terse

<object>s taking strings for verbs that have lexical constraints must match those lexical constraints.Affects: @object-lexical-constraint<object>Used by template ŧ core-expansion-terse

Every <claim> must have at least one subject, either @subject (self or ancestral <body>) or a child <subject>Affects: @subject<claim> <subject>Used by template ŧ core-expansion-terse

Any predefined strictures on verbs must be respected.Affects: @verb<claim>Used by template ŧ core-expansion-terse

Every <claim> must have at least one verb, either @verb (self or ancestral <body>)Affects: @verb<claim>Used by template ŧ core-expansion-terse

Every div type reference must be valid in every sourceAffects: @div-type<skip> <rename>Used by template ŧ class-2-expansion-terse

For any element with @include, at least one element of the same name must be found in target inclusion document.Affects: @include<inclusion>Used by template ŧ resolve-attr-include

Inclusions may not be circular.Affects: @include<inclusion>Used by variable $erroneously-looped-docUsed by template ŧ resolve-attr-include

Inclusions are integral parts of any TAN file. Access to at least one copy is absolutely mandatory.Affects: @include<inclusion>Used by template ŧ check-referred-docUsed by function tan:get-1st-doc()

Every element with a <location> should have at least one document available.Affects: <location> <inclusion> <see-also> <source> <key>Used by function tan:get-1st-doc()

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>Affects: <location> <inclusion> <see-also> <source> <key>Used by template ŧ check-referred-doc

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.Affects: <location> <inclusion> <see-also> <source> <key>Used by template ŧ check-referred-doc

In a ranged <tok> in a <reassign>, the token referred to by <from> must precede the one referred to by <to>.Affects: <reassign> <tok> <from> <to>Used by template ŧ dependencies-tokenized-selectively

Only the first of multiple <reassign>s that apply to a particular token will be applied.Affects: <reassign>Used by template ŧ dependencies-tokenized-selectively

If a <div> is renamed, and the target reference is subject to <reassign> instructions, the following message will appear.<reassign> targets a reference that has been altered by <rename>. Any reassignments will treat the newly created <div>, not the original.Affects: <reassign> <rename>Used by template ŧ dependencies-tokenized-selectively

Every part of a @ref must correspond to a <div> in every source.Affects: @ref @srcUsed by template ŧ class-2-expansion-terse

If a reference to a work is not found in some sources, a warning will be returned.Affects: @ref @workUsed by template ŧ class-2-expansion-terse

Any <see-also> whose <relationship> is defined as requiring a target TAN file must point to a file whose root element is a TAN file.Affects: <see-also> <relationship>Used by template ŧ check-referred-doc

Any <see-also> whose <relationship> is defined as requiring a target copy must point to a TAN file whose root element is identical.Affects: <see-also> <relationship>Used by template ŧ check-referred-doc

<see-also> may have the <relationship> of a different work version only if both are class 1 files and both share the same work.Affects: <see-also> <relationship>Used by template ŧ check-referred-doc

Sequences may not include values less than 1.Affects: @pos @chars @feature-qty-testUsed by template ŧ class-2-expansion-terseUsed by function tan:sequence-error()

Sequences may not include values greater than the maximum allowed.Affects: @pos @chars @feature-qty-testUsed by function tan:sequence-error()

Ranges in sequences must go from a lesser value to a greater.Affects: @pos @chars @feature-qty-testUsed by template ŧ class-2-expansion-terseUsed by function tan:sequence-error()

Ranges consist of exactly two values separated by a hyphen.Affects: @ref @pos @charsUsed by function tan:analyze-sequence()

When renaming references, ranges must be predictably calculated.Affects: @ref<rename>Used by function tan:analyze-sequence()

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.Affects: @id<agent>Used by template ŧ core-expansion-terse

Any TAN file marked as being no longer in progress should have at least one master-location.Affects: @in-progress<master-location>Used by template ŧ core-expansion-terse-attributes

@xml:id values may not be repeated in the same document.Affects: @xml:id @idUsed by template ŧ core-expansion-terse-attributesUsed by function tan:definition()

All text must be normalized (Unicode NFC).Affects: <desc> <div> <name> <IRI>Used by template ŧ core-expansion-normal

Every idref in an attribute must point to the @xml:id value of the appropriate corresponding element.Affects: @who @ed-who @roles @src @lexicon @morphology @reuse-type @bitext-relation @feature @includeUsed by template ŧ core-expansion-terse-alias dependency-expansion-terse ŧ core-expansion-terse-attributes ŧ resolve-attr-includeUsed by function tan:definition() tan:resolve-doc()

All idrefs in an attribute must be unique.Affects: @who @ed-who @roles @src @lexicon @morphology @reuse-type @bitext-relation @feature @includeUsed by template ŧ core-expansion-terse-attributes

Attributes that take a regular expression must use escape sequences recognized by XML schema or TAN escape extensions (\u{}). See http://www.w3.org/TR/xmlschema-2/#regexsAffects: @regex @matches-m @matches-tok @valUsed by template ŧ core-expansion-terse-attributes

@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.Affects: @hrefUsed by template ŧ core-expansion-terse-attributes

An IRI may appear no more than once in a TAN document.Affects: <IRI>Used by template ŧ core-expansion-terse ŧ check-referred-doc ŧ core-expansion-terse

An IRI that names a TAN file must match that file's @id exactly.Affects: <IRI>Used by template ŧ check-referred-doc

No file may import keys that have duplicate IRIs.Affects: <key> <IRI>Used by template ŧ check-referred-doc

An <alias> may not mix idrefs from different elements.Affects: @idrefs<alias>Used by template ŧ core-expansion-terse-alias dependency-expansion-terse

<alias> references must not be circular.Affects: @idrefs<alias>Used by function tan:resolve-alias-loop()

No <master-location> may have an @href that points to a compressed archive.Affects: @href<master-location>Used by template ŧ core-expansion-terse-attributes

The only @href in a TAN document that may point to the same document id is that of <master-location>Affects: @hrefUsed by function tan:get-1st-doc()

No @href should point to the URI of the document itself.Affects: @hrefUsed by template ŧ core-expansion-terse-attributes

Files should match the version kept at <master-location>.Affects: <master-location>Used by template ŧ class-2-expansion-verbose ŧ core-expansion-normal

Any IRI beginning urn: must continue with a name that is part of the official IANA Registry of URN Namespaces. See RFC 2414, https://tools.ietf.org/html/rfc8141, and https://www.iana.org/assignments/urn-namespaces/urn-namespaces.xhtmlAffects: <IRI>Used by template ŧ core-expansion-terse

Files that point to older versions of TAN rules will be pointed to conversion stylesheets.Affects: @TAN-versionUsed by template ŧ core-expansion-terse

<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.Affects: <div>Used by template ŧ core-expansion-terse dependency-expansion-terse-no-alter ŧ dependency-expansion-terse

A <div> must not mix @include with any other attributes.Affects: <div>Used by template ŧ core-expansion-terse dependency-expansion-terse-no-alter ŧ dependency-expansion-terse

A <div> must have either @type + @n or @include but not both.Affects: <div>Used by template ŧ core-expansion-terse dependency-expansion-terse-no-alter ŧ dependency-expansion-terse

Text that represents a line, column, or page break should be moved into a @rend within a <lb>, <pb>, or <cb>.Affects: @rend<tei:lb> <tei:pb> <tei:cb>Used by template ŧ core-expansion-terse dependency-expansion-terse normalize-tei-space

A breaking element without @break="no" should have at least one space on either side; one with @break="no" should have no nearby spacesAffects: <tei:lb> <tei:pb> <tei:cb>Used by template ŧ core-expansion-terse dependency-expansion-terse normalize-tei-space

Names may not duplicate reserved TAN keyword names for the affected element.Affects: <name>Used by template ŧ expand-tan-key-dependencies core-expansion-terse

Names may not be duplicates of, case-variants of, or hyphen variants of other names for the same element.Affects: <name>Used by template ŧ core-expansion-normal

@affects-element must include only names of TAN elements that accept @whichAffects: @affects-element<item> <group>Used by template ŧ core-expansion-terse

Every item in a reserved TAN-key must have at least one IRI with a tag URN in the TAN namespaceAffects: <IRI> <item>Used by template ŧ core-expansion-terse

<for-lang> and <source> are mutually exclusive in a TAN-A-lm file.Affects: <for-lang> <source>Used by template ŧ core-expansion-terse

When using a category-based morphology, the number of feature codes in an <m> may not exceed the number of categories.Affects: <m>Used by template ŧ class-2-expansion-terse-pass-2

Every feature code in an <m> must be found in the target morphology file.Affects: <m>Used by template ŧ class-2-expansion-terse-pass-2

Every condition of a relevant dependency morphology <assert> (<report>) must be true (false) otherwise an error will be returned.Affects: <m>No variables, keys, functions, or named templates depend upon this error.

Id values for features must be case-indifferently unique within a given category.Affects: @code @xml:id<option>Used by template ŧ dependency-expansion-terse core-expansion-terse

Every token must be locatable in every cited ref in every source.Affects: @pos @val<tok>Used by template ŧ dependencies-tokenized-selectively ŧ class-2-expansion-terse ŧ class-2-expansion-normal

<tok> must reference a leaf <div>.Affects: @pos @val<tok>Used by template ŧ class-2-expansion-terse

Date attributes must be castable either as xs:dateTime or xs:dateAffects: @when @ed-when @when-accessed @from @toUsed by template ŧ core-expansion-terse-attributes

Future dates are not permitted.Affects: @when @ed-when @when-accessed @from @toUsed by template ŧ core-expansion-terse-attributes

@from must predate @toAffects: @from @toUsed by template ŧ core-expansion-terse-attributes

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.Affects: @which<key>Used by template ŧ resolve-keyword

Keywords (values of @which) must be unique for a given element name.Affects: @which<key>Used by template ŧ check-referred-doc ŧ resolve-keyword

Any element that takes @which must have keywords defined for that element.Affects: @which<key>Used by template ŧ resolve-keyword

Keys are integral parts of a document. Access to at least one version is absolutely mandatory.Affects: @which<key>Used by template ŧ check-referred-docUsed by function tan:get-1st-doc()

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.Affects: @hrefUsed by template ŧ core-expansion-terse-attributesUsed by function tan:get-1st-doc()

If @when-accessed predates one or more dates in a target file, a warning will be returned.Affects: @when-accessed<location> <inclusion> <see-also> <source> <key>Used by template ŧ check-referred-doc

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.Affects: <location> <inclusion> <see-also> <source> <key>Used by template ŧ check-referred-doc

Users should be warned about versions of TAN that are under development.This version of TAN is under development, and is subject to change. Participants in developing the TAN schemas, functions, and guidelines are welcome. See http://textalign.net for details.Affects: <TAN-T> <TEI> <TAN-A-div> <TAN-A-tok> <TAN-A-lm> <TAN-key> <TAN-mor>No variables, keys, functions, or named templates depend upon this warning.

If a target file has a <see-also> marked as a new version (update) a warning will be returned.Affects: <location> <inclusion> <see-also> <source> <key>Used by template ŧ check-referred-doc

Users should be warned about versions of TAN that are semi-stable.This version of TAN is semi-stable. RELAX-NG schemas will be changed only to correct egregious errors. Other files might be edited, but most efforts on improvement will be spent on future versions.Affects: <TAN-T> <TEI> <TAN-A-div> <TAN-A-tok> <TAN-A-lm> <TAN-key> <TAN-mor>Used by template ŧ core-expansion-normal dependency-expansion-normal