names an <agent> Option to allow an @xml:id in children of <declarations> String that specifies a range of divs using the div-ref pattern joined by a hyphen or a comma. String that specifies a single <div> (\w+([^\w\-]\w+)*)|.*\?\?\?.* For more see main.xml#leaf_div_uniqueness_rule (\w+([^\w\-]\w+)*)(((\s*-\s*)|(\s*,\s+))(\w+([^\w\-]\w+)*))*|.*\?\?\?.* 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 main.xml#edit_stamp This attribute is inheritable. See main.xml#inheritable_attributes 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 main.xml#date_and_datetime. Along with @ed-who, this forms the Edit Stamp pattern. See main.xml#edit_stamp This attribute is inheritable. See main.xml#inheritable_attributes 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 main.xml#inheritable_attributes provides a second measure of certainty. The value is taken along with @cert as the range in which an editors certainty resides. 1|0|(0\.\d*[1-9]) 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. warn(ing)?|error|info|fatal identifies one or more <group-type>s under which the parent element, and its children, should be grouped. 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) names one or more TAN elements that the keywords apply to 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. signals that the parent element is to be replaced by all elements of the same name found in the referred <inclusion>. identifies an entity described within an element. Must be unique within a given file. Must consist only of word characters. \w\S* contains references to one or more values of xml:id in the file Any generic IRI identifier. [a-zA-Z][\-.+a-zA-Z0-9]+:\S+ 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. String that specifies a single item from a sequence: digits or "last(-digit)?" Similar to seq-picker. ((last|max)|((last|max)-\d+)|(\d+))|.*\?\?\?.* 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. (\w+|\d+-\d+)(\s+(\w+|\d+-\d+))* specifies the version of TAN schemas used. 1 dev used to point to a reserved keyword, either a reserved tokenization pattern or a relationship. 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 main.xml#language. Examples: 'eng' (English), 'grc' (classical Greek), 'lat' (Latin) 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 main.xml#language. Examples: 'eng' (English), 'grc' (classical Greek), 'lat' (Latin). For more see main.xml#language 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"). specifies the beginning of a period of time specifies the end of a period of time specifies whether the creation and editing of the data is still in progress. Default value is true. 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. 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 main.xml#license refers to the ID of one or more <role>s String that specifies a range of items in a sequence: digits or "last(-digit)?" joined by hyphens (ranges) or commas. Similar to item-picker. ((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+)))?)*|.*\?\?\?.* 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>. Tag URN, mandatory pattern for the IRI name of every TAN file 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+ indicates a date or date and time 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. states the value of a <checksum> discusses issues relevant to nearby data. Must credit an <agent>, specified by @who, and a time the comment was made, specified by @when. defines types of <group>s. See main.xml# keywords-group-type 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 main.xml#defining_tokens Editorial stamp: who created or edited the enclosed data and when. 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>) Reference to an external digital entity that is not a TAN file Reference to self as digital entity (i.e., TAN file) Reference to an external non-digital entity (e.g., agents, roles, works, topics) 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 main.xml#regular_expressions and https://www.w3.org/TR/xpath-functions-30/#regex-syntax specifies flags to be applied in an XPath function that uses regular expressions. s = dot-all mode; m = multi-line mode; i = case-insensitive mode; x = remove whitespace characters from regular expression; q = no metacharacters For more see http://www.w3.org/TR/xpath-functions-30/#flags [smixq]+ 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 main.xml#IRIs_and_linked_data. 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. 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. declares where an electronic file was found and when. The URL may be absolute or relative to the current document. specifies when an electronic file was last examined (.|\n)+ 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>) 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. contains a tag URN that permanently and uniquely names the current file, the so-called IRI Name of the current file. See main.xml#iri_name for discussion. For more on the syntax of tag URNs see main.xml#tag_urn 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>. contains the data collects items that share a common property, defined by the <group-type> to which it refers. permits any arbitrary content. This element is suitable as a placeholder for temporary data, especially to facilitate time-consuming validation routines. xml:id 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 main.xml#license and for a list of standard vocabulary, main.xml# keywords-rights-excluding-sources 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 main.xml#inclusions-and-keys 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 main.xml#tan-key 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. states license and rights that are attached to the source of the data. For more discussion, see main.xml#license and for a list of vocabulary, main.xml# keywords-rights-excluding-sources Parameter to indicate whether <source> should be allowed to take xml:id (forbidden for TAN files with only one source; mandated otherwise) 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. 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. contains assumptions or decisions made that materially affect the interpretation of the data in <body>. Every TAN format's <declarations> is unique. 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 main.xml#iri_name 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. 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. specifies a time period when one or more <agent>s held one or more <role>s. 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. assigns multiple values of xml:id to a single xml:id. declaration-items to be filled out by each TAN-class-X.rnc file 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 main.xml#conceptual_works 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 main.xml#conceptual_works