Table of Contents
<agent>
<agentrole>
<alias>
<body>
<change>
<checksum>
<comment>
<declarations>
<desc>
<for-lang>
<group>
<group-type>
<head>
<inclusion>
<IRI>
<key>
<location>
<master-location>
<name>
<relationship>
<rights-excluding-sources>
<rights-source-only>
<role>
<see-also>
<source>
<tail>
<token-definition>
<value>
<version>
<when>
<work>
@affects-element
@cert
@cert2
@ed-when
@ed-who
@flags
@from
@group
@help
@href
@id
@idrefs
@in-progress
@include
@n
@regex
@rights-holder
@roles
@TAN-version
@to
@type
@when
@when-accessed
@which
@who
@xml:id
@xml:lang
~agent-list
~agent-ref
~agent-role-list
~alignment
~alignment-attributes-non-class-2
~alignment-content-non-class-2
~alignment-inclusion-opt
~anchor-div-ref-item
~any-attribute
~any-content
~any-element
~assert
~attr-cert
~attr-cert2
~bitext-relation-attr
~body-group
~body-group-opt
~category
~category-feature
~category-list
~cert-claim
~cert-content
~cert-opt
~certainty-stamp
~change-list
~char-ref
~checksum
~claim
~claim-div-ref-item
~claimant
~code
~comment
~complex-object
~complex-rationale
~complex-subject
~complex-text-ref
~complex-textual-reference-set
~continuation
~continuation-opt
~decl-alias
~decl-brel
~decl-class-1
~decl-div
~decl-filt
~decl-filt-norm
~decl-filt-repl
~decl-filt-tlit
~decl-filter-content
~decl-group-type
~decl-id-ref-opt
~decl-lexi
~decl-mode
~decl-morph
~decl-non-class-1
~decl-opt
~decl-pattern-default
~decl-pattern-language
~decl-pattern-no-id
~decl-pers
~decl-place
~decl-rename-div-n
~decl-reus
~decl-scri
~decl-supp-div-type
~decl-tok-def
~decl-topic
~decl-unit
~decl-verb
~decl-vers
~decl-work
~declaration-core
~declaration-items
~div-item-ref
~div-range-ref
~div-type-equiv
~div-type-ref
~div-type-ref-cluster
~ed-agent
~ed-stamp
~ed-time
~element-scope
~entity-digital-generic-ref
~entity-digital-tan-other-ref
~entity-digital-tan-self-ref
~entity-nondigital-ref
~entity-tok-def
~error-flag
~feature
~feature-list
~feature-pattern
~feature-pattern-no-code
~feature-qty-test
~feature-test
~filter
~func-param-flags
~func-param-pattern
~func-replace
~grammar-attr
~group-attributes
~group-ref
~help-opt
~href-opt
~id-option
~inclusion
~inclusion-att
~inclusion-item
~inclusion-list
~internal-id
~internal-idrefs
~IRI-gen
~IRI-gen-ref
~item
~item-picker
~item-pos-ref
~key-item
~key-list
~keyword-ref
~lang-of-content
~lang-outside
~lexeme
~lexicon-attr
~loc-self
~loc-src
~locus
~matches-m
~matches-tok
~metadata-desc
~metadata-human
~modal-claim
~morph
~n
~n-val
~name-change
~non-class-2-opt
~nonsource-rights
~nontextual-reference
~object
~object-constraint
~object-datatype
~object-element
~object-lexical-constraint
~other-body-attributes
~period-filter
~place-filter
~pointer-to-div-item
~pointer-to-div-range
~progress
~rationale
~realignment
~reanchor-div-ref-item
~relationship
~report
~reuse-type-attr
~rights-holder
~role-list
~role-ref
~see-also-item
~see-also-list
~seg-ref
~seq-picker
~seq-pos-ref
~set-of-claims
~simple-object
~simple-rationale
~simple-subject
~simple-textual-reference
~source-id-opt
~source-item
~source-list
~source-ref
~source-refs
~source-rights
~split
~subject
~TAN-body
~TAN-body-core
~TAN-c-decl
~TAN-c-decl-core
~TAN-c-item
~TAN-head
~TAN-key-decl
~TAN-key-item
~TAN-LM-item
~TAN-R-mor-body
~TAN-root
~TAN-tail
~TAN-ver
~test-pattern
~text-div
~textual-reference
~tok-attr-core
~tok-cert-opt
~tok-regular
~tok-sequence
~tok-sequence-attr-core
~tok-source-ref-opt
~tok-with-cont-but-no-src
~tok-with-src-and-cont
~tok-without-cont-or-src
~token-value-ref
~type
~units
~URI-tag
~verb
~when-claim
~work-equiv
~work-ref
~work-refs
The 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:lang
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.
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 the section called “@id and a TAN file's 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.
Formal Definition
~ed-stamp
?, (~inclusion
| (@roles
?,@xml:id
, (<comment>
* & ((<IRI>
+,~metadata-human
) |@which
))))
Used by: ~TAN-head
Caution | |
---|---|
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 |
Example 8.1. <agent>
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.obj |
Example 8.2. <agent>
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.sem |
Example 8.3. <agent>
<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>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.sem-native |
Example 8.4. <agent>
<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>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.sem |
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
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-core
Caution | |
---|---|
A |
Caution | |
---|---|
|
Example 8.5. <alias>
<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>
Note | |
---|---|
Taken from ar.cat.tan-a-div.claims |
The element body
contains the data
Formal 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
Example 8.6. <body>
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.obj |
Example 8.7. <body>
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.sem |
Example 8.8. <body>
<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>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.sem-native |
Example 8.9. <body>
<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>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.sem |
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
Example 8.10. <change>
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.obj |
Example 8.11. <change>
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.sem |
Example 8.12. <change>
<head> ......... <role xml:id="editor"> ......... </role> <change when="2016-07-10" who="kalvesmaki">Began new file</change> </head>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.sem-native |
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
Example 8.13. <checksum>
<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>
Note | |
---|---|
Taken from patricius.confessio.2003.eng |
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
, text
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
Example 8.14. <comment>
<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>
Note | |
---|---|
Taken from gomme.1989.ring-o-roses |
Example 8.15. <comment>
<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>
Note | |
---|---|
Taken from patricius.confessio.2003.eng |
Example 8.16. <comment>
<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>
Note | |
---|---|
Taken from ring-o-roses.deu.1897 |
Example 8.17. <comment>
<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>
Note | |
---|---|
Taken from ring-o-roses.eng.1987 |
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
Example 8.18. <declarations>
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.obj |
Example 8.19. <declarations>
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.sem |
Example 8.20. <declarations>
<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>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.sem-native |
Example 8.21. <declarations>
<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>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.sem |
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>
+))))
Caution | |
---|---|
All text must be normalized (Unicode NFC). |
Example 8.22. <desc>
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.obj |
Example 8.23. <desc>
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.sem |
Example 8.24. <desc>
<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>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.sem-native |
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 the section called “Languages”.
Examples: 'eng' (English), 'grc' (classical Greek), 'lat' (Latin). For more see the section called “Languages”
Formal Definition
language
Used by: ~source-list
, ~TAN-R-mor-body
, ~decl-pattern-language
, ~decl-morph
, ~decl-lexi
Example 8.25. <for-lang>
<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>
Note | |
---|---|
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
Caution | |
---|---|
|
Example 8.26. <group>
<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>
Note | |
---|---|
Taken from ar.cat.TAN-key |
The element group-type
defines types of <group>
s. See main.xml# keywords-group-type
Formal Definition
~ed-stamp
?, (~inclusion
| (@xml:id
, (<comment>
* & ((<IRI>
+,~metadata-human
) |@which
))))
Used by: ~declaration-items
, ~TAN-key-decl
Example 8.27. <group-type>
<declarations> ......... <morphology xml:id="Perseus"> ......... </morphology> <group-type xml:id="status" which="status"/> </declarations>
Note | |
---|---|
Example 8.28. <group-type>
<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>
Note | |
---|---|
Taken from div-types.TAN-key |
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
Example 8.29. <head>
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.obj |
Example 8.30. <head>
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.sem |
Example 8.31. <head>
<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>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.sem-native |
Example 8.32. <head>
<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>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.sem |
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 the section called “Inclusions and Keys”
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-item
Caution | |
---|---|
Inclusions may not introduce duplicate values of |
Caution | |
---|---|
For any element with |
Caution | |
---|---|
Inclusions may not be circular. |
Caution | |
---|---|
Inclusions are integral parts of any TAN file. Access to at least one copy is absolutely mandatory. |
Caution | |
---|---|
Every inclusion should have at least one document available. |
Caution | |
---|---|
Every element with a |
Caution | |
---|---|
Every TAN file referred to by way of an element containing |
Caution | |
---|---|
No element may point to a TAN file that has an identical |
Important | |
---|---|
If |
Important | |
---|---|
If a target file does not explicitly give the |
Important | |
---|---|
If a target file has a |
Example 8.33. <inclusion>
<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>
Note | |
---|---|
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 the section called “Identifiers and Their Use”.
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-ref
Caution | |
---|---|
An IRI may appear no more than once in a TAN document. |
Caution | |
---|---|
An IRI that names a TAN file must match that file's |
Caution | |
---|---|
No file may import keys that have duplicate IRIs. |
Caution | |
---|---|
All text must be normalized (Unicode NFC). |
Caution | |
---|---|
Every item in a reserved TAN-key must have at least one IRI with a tag URN in the TAN namespace |
Example 8.34. <IRI>
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.obj |
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 the section called “Keyword Vocabulary (TAN-key
)”
Formal Definition
~ed-stamp
?, (~inclusion
| (<comment>
* & (@href
| (<IRI>
,~metadata-human
,<checksum>
*,<location>
+))))
Used by: ~key-list
Caution | |
---|---|
No file may import keys that have duplicate IRIs. |
Caution | |
---|---|
Every element with a |
Caution | |
---|---|
Every TAN file referred to by way of an element containing |
Caution | |
---|---|
No element may point to a TAN file that has an identical |
Important | |
---|---|
If |
Important | |
---|---|
If a target file does not explicitly give the |
Important | |
---|---|
If a target file has a |
Caution | |
---|---|
An element's |
Caution | |
---|---|
Keywords (values of |
Caution | |
---|---|
Any element that takes |
Caution | |
---|---|
Keys are integral parts of a document. Access to at least one version is absolutely mandatory. |
Example 8.35. <key>
<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>
Note | |
---|---|
Taken from ar.cat.tan-a-div.claims |
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
,@href
Used by: ~entity-digital-tan-other-ref
, ~entity-digital-generic-ref
Caution | |
---|---|
Every element with a |
Caution | |
---|---|
Every TAN file referred to by way of an element containing |
Caution | |
---|---|
No element may point to a TAN file that has an identical |
Important | |
---|---|
If |
Important | |
---|---|
If a target file does not explicitly give the |
Important | |
---|---|
If a target file has a |
Example 8.36. <location>
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.obj |
Example 8.37. <location>
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.sem |
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
?,@href
Used by: ~entity-digital-tan-self-ref
Important | |
---|---|
Any TAN file marked as being no longer in progress should have at least one master-location. |
Caution | |
---|---|
No |
Example 8.38. <master-location>
<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>
Note | |
---|---|
Taken from gomme.1989.ring-o-roses |
Example 8.39. <master-location>
<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>
Note | |
---|---|
Taken from ring-o-roses.deu.1897 |
Example 8.40. <master-location>
<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>
Note | |
---|---|
Taken from ring-o-roses.eng.1881 |
Example 8.41. <master-location>
<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>
Note | |
---|---|
Taken from ring-o-roses.eng.1957 |
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-desc
Caution | |
---|---|
All text must be normalized (Unicode NFC). |
Caution | |
---|---|
Names may not duplicate reserved TAN keywords for the affected element. |
Caution | |
---|---|
Names may not be duplicates of, case-variants of, or hyphen variants of other names for the same element. |
Example 8.42. <name>
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.obj |
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-item
Caution | |
---|---|
Any |
Caution | |
---|---|
Any |
Caution | |
---|---|
Any |
Caution | |
---|---|
|
Caution | |
---|---|
In class 1 files, alternative editions must share the same source. |
Caution | |
---|---|
In class 1 files, alternative editions must share the same work. |
Caution | |
---|---|
In class 1 files, alternative editions must share the same work-version, if supplied. |
Caution | |
---|---|
In class 1 files, resegmented copies must have identical transcriptions, after TAN normalization. |
Caution | |
---|---|
A class 1 file and its model must have the same work. |
Caution | |
---|---|
A class 1 file may have no more than one model. |
Important | |
---|---|
If a class 1 file diverges from the structure of its model a warning will be generated specifying where differences exist. |
Example 8.43. <relationship>
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.obj |
Example 8.44. <relationship>
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.sem |
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 the section called “Rights and Licenses” and for a list of standard vocabulary, main.xml# keywords-rights-excluding-sources
Formal Definition
~ed-stamp
?, (~inclusion
| (@rights-holder
, (<comment>
* & ((<IRI>
+,~metadata-human
) |@which
))))
Used by: ~TAN-head
Example 8.45. <rights-excluding-sources>
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.obj |
Example 8.46. <rights-excluding-sources>
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.sem |
Example 8.47. <rights-excluding-sources>
<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>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.sem-native |
Example 8.48. <rights-excluding-sources>
<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>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.sem |
The element rights-source-only
states license and rights that are attached to the source of the data.
For more discussion, see the section called “Rights and Licenses” and for a list of vocabulary, main.xml# keywords-rights-excluding-sources
Formal Definition
~ed-stamp
?, (~inclusion
| (<comment>
* & (@rights-holder
*, ((<IRI>
+,~metadata-human
) |@which
))))
Used by: ~source-item
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
Example 8.49. <role>
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.obj |
Example 8.50. <role>
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.sem |
Example 8.51. <role>
<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>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.sem-native |
Example 8.52. <role>
<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>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.sem |
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-list
Caution | |
---|---|
Any |
Caution | |
---|---|
Any |
Caution | |
---|---|
Any |
Caution | |
---|---|
|
Caution | |
---|---|
In class 1 files, alternative editions must share the same source. |
Caution | |
---|---|
In class 1 files, alternative editions must share the same work. |
Caution | |
---|---|
In class 1 files, alternative editions must share the same work-version, if supplied. |
Caution | |
---|---|
In class 1 files, resegmented copies must have identical transcriptions, after TAN normalization. |
Caution | |
---|---|
A class 1 file and its model must have the same work. |
Caution | |
---|---|
A class 1 file may have no more than one model. |
Important | |
---|---|
If a class 1 file diverges from the structure of its model a warning will be generated specifying where differences exist. |
Caution | |
---|---|
Every element with a |
Caution | |
---|---|
Every TAN file referred to by way of an element containing |
Caution | |
---|---|
No element may point to a TAN file that has an identical |
Important | |
---|---|
If |
Important | |
---|---|
If a target file does not explicitly give the |
Important | |
---|---|
If a target file has a |
Example 8.53. <see-also>
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.obj |
Example 8.54. <see-also>
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.sem |
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-list
Caution | |
---|---|
Every element with a |
Caution | |
---|---|
Every TAN file referred to by way of an element containing |
Caution | |
---|---|
No element may point to a TAN file that has an identical |
Important | |
---|---|
If |
Important | |
---|---|
If a target file does not explicitly give the |
Important | |
---|---|
If a target file has a |
Caution | |
---|---|
Sources are integral parts of a class 2 TAN file. Access to at least one copy is absolutely mandatory. |
Example 8.55. <source>
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.obj |
Example 8.56. <source>
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.sem |
Example 8.57. <source>
<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>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.sem-native |
Example 8.58. <source>
<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>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.sem |
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)
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 the section called “Defining Words and Tokens”
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-def
Caution | |
---|---|
No source may be given more than one token definition. |
Example 8.59. <token-definition>
<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>
Note | |
---|---|
Taken from ringoroses.div.1 |
Example 8.60. <token-definition>
<declarations> ......... <reuse-type xml:id="adaptation"> ......... </reuse-type> <token-definition src="ring1881 ring1987" which="letters"/> </declarations>
Note | |
---|---|
Taken from ringoroses.01+02.token.1 |
Example 8.61. <token-definition>
<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>
Note | |
---|---|
Taken from ringoroses.01+03.token.1 |
Example 8.62. <token-definition>
<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>
Note | |
---|---|
Taken from ringoroses.01+03.token.2 |
The element value
states the value of a <checksum>
Formal Definition
string
Used by: <checksum>
Example 8.63. <value>
<checksum> ......... <name>SHA-1</name> <value>91D95564ABDF2B2C1B9EEF016CBA51E8179646CC</value> </checksum>
Note | |
---|---|
Taken from patricius.confessio.2003.eng |
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 the section called “One work”
Formal Definition
~decl-pattern-default
Used by: ~TAN-c-decl-core
, ~decl-class-1
Example 8.64. <version>
<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>
Note | |
---|---|
Taken from ring-o-roses.deu.1897 |
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
,@to
Used by: ~claim
, ~agent-role-list
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 the section called “One work”
Formal Definition
~decl-pattern-default
Used by: ~TAN-c-decl-core
, ~decl-class-1
Caution | |
---|---|
A work element may invoke no more than one inclusion. |
Example 8.65. <work>
<declarations> <work> <IRI>http://dbpedia.org/resource/Categories_(Aristotle)</IRI> <name>Aristotle, Categories</name> </work> <div-type xml:id="p"> ......... </div-type> ......... </declarations>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.obj |
Example 8.66. <work>
<declarations> <work> <IRI>http://dbpedia.org/resource/Categories_(Aristotle)</IRI> <name>Aristotle, Categories</name> </work> <div-type xml:id="ch"> ......... </div-type> ......... </declarations>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.sem |
Example 8.67. <work>
<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>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.sem-native |
Example 8.68. <work>
<declarations> <work> <IRI>http://dbpedia.org/resource/Categories_(Aristotle)</IRI> <name>Aristotle, Categories</name> </work> <div-type xml:id="ch"> ......... </div-type> ......... </declarations>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.sem |
The attribute affects-element
names one or more TAN elements that the keywords apply to
Formal Definition
Used by: ~other-body-attributes
, ~group-attributes
, ~TAN-key-item
Caution | |
---|---|
|
Example 8.69. @affects-element
<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>
Note | |
---|---|
Taken from ar.cat.TAN-key |
Example 8.70. @affects-element
<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>
Note | |
---|---|
Taken from bitext-relations.TAN-key |
Example 8.71. @affects-element
<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>
Note | |
---|---|
Taken from div-types.TAN-key |
Example 8.72. @affects-element
<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>
Note | |
---|---|
Taken from features.TAN-key |
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 the section called “Interpretation of inheritable attributes”
Formal Definition
double (pattern 1|0|(0\.\d*[1-9]))
Used by: ~cert-claim
Example 8.73. @cert
<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>
Note | |
---|---|
Taken from ringoroses.01+03.token.1 |
Example 8.74. @cert
<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>
Note | |
---|---|
Taken from ringoroses.01+03.token.2 |
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 Definition
double (pattern 1|0|(0\.\d*[1-9]))
Used by: ~cert-claim
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 the section called “Dates and times”.
Along with @ed-who
, this forms the Edit Stamp pattern. See the section called “Edit Stamp”
This attribute is inheritable. See the section called “Interpretation of inheritable attributes”
Formal Definition
( dateTime date )
Used by: ~ed-stamp
Caution | |
---|---|
Date attributes must be castable either as xs:dateTime or xs:date |
Caution | |
---|---|
Future dates are not permitted. |
Example 8.75. @ed-when
<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>
Note | |
---|---|
Taken from ring-o-roses.eng.1987 |
Example 8.76. @ed-when
<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>
Note | |
---|---|
Taken from ring-o-roses.eng.1881.lm |
Example 8.77. @ed-when
<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>
Note | |
---|---|
Taken from eng.kalvesmaki.com,2014.2 |
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 the section called “Edit Stamp”
This attribute is inheritable. See the section called “Interpretation of inheritable attributes”
Formal Definition
Used by: ~ed-stamp
Caution | |
---|---|
Every idref in an attribute must point to the |
Caution | |
---|---|
All idrefs in an attribute must be unique. |
Example 8.78. @ed-who
<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>
Note | |
---|---|
Taken from ring-o-roses.eng.1987 |
Example 8.79. @ed-who
<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>
Note | |
---|---|
Taken from ring-o-roses.eng.1881.lm |
Example 8.80. @ed-who
<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>
Note | |
---|---|
Taken from eng.kalvesmaki.com,2014.2 |
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/#flags
Formal Definition
string (pattern warn(ing)?|error|info|fatal)string (pattern [smixq]+)
Used by: ~func-replace
, ~decl-tok-def
, ~change-list
The attribute from
specifies the beginning of a period of time
Formal Definition
( dateTime date )
Used by: <when>
Caution | |
---|---|
Date attributes must be castable either as xs:dateTime or xs:date |
Caution | |
---|---|
Future dates are not permitted. |
The attribute group
identifies one or more <group-type>
s under which the parent element, and its children, should be grouped.
Formal Definition
Used by: ~non-class-2-opt
, ~TAN-key-item
, ~TAN-LM-item
Example 8.81. @group
<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>
Note | |
---|---|
Taken from div-types.TAN-key |
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
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 Definition
Used by: ~entity-digital-tan-other-ref
, ~loc-self
, ~loc-src
Caution | |
---|---|
|
Important | |
---|---|
If |
Caution | |
---|---|
The only |
Caution | |
---|---|
No |
Example 8.82. @href
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.obj |
Example 8.83. @href
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.sem |
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 the section called “@id and a TAN file's IRI
Name” for discussion.
For more on the syntax of tag URNs see the section called “Tag URNs”
Formal Definition
anyURI (pattern tag:([\-a-zA-Z0-9._%+]+@)?[\-a-zA-Z0-9.]+\.[A-Za-z]{2,4},\d{4}(-(0\d|1[0-2]))?(-([0-2]\d|3[01]))?:\S+)
Used by: <TAN-A-div>
, <TAN-A-tok>
, <TAN-c>
, <TAN-key>
, <TAN-mor>
, <TAN-T>
, <TAN-LM>
Caution | |
---|---|
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 |
Example 8.84. @id
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.obj |
Example 8.85. @id
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.sem |
Example 8.86. @id
<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>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.sem-native |
Example 8.87. @id
<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>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.sem |
The attribute idrefs
contains references to one or more values of xml:id in the file
Formal Definition
Used by: ~decl-alias
Caution | |
---|---|
A |
Caution | |
---|---|
|
Example 8.88. @idrefs
<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>
Note | |
---|---|
Taken from ar.cat.tan-a-div.claims |
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 Definition
boolean
Used by: ~TAN-body
Important | |
---|---|
Any TAN file marked as being no longer in progress should have at least one master-location. |
Example 8.89. @in-progress
<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>
Note | |
---|---|
Taken from ring-o-roses.deu.1897 |
Example 8.90. @in-progress
<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>
Note | |
---|---|
Taken from ring-o-roses.eng.1881 |
Example 8.91. @in-progress
<text> <body xml:lang="eng" in-progress="false"> <div type="poem" n="poem" part="N" org="uniform" sample="complete"> ......... </div> </body> </text>
Note | |
---|---|
Taken from ring-o-roses.eng.1957 |
Example 8.92. @in-progress
<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>
Note | |
---|---|
Taken from ring-o-roses.eng.1987 |
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 Definition
Used by: ~inclusion
Caution | |
---|---|
Every idref in an attribute must point to the |
Caution | |
---|---|
All idrefs in an attribute must be unique. |
Caution | |
---|---|
Inclusions may not introduce duplicate values of |
Caution | |
---|---|
For any element with |
Caution | |
---|---|
Inclusions may not be circular. |
Caution | |
---|---|
Inclusions are integral parts of any TAN file. Access to at least one copy is absolutely mandatory. |
Caution | |
---|---|
Every inclusion should have at least one document available. |
Caution | |
---|---|
A work element may invoke no more than one inclusion. |
Caution | |
---|---|
Every |
Example 8.93. @include
<head> ......... <declarations> ......... </declarations> <agent include="rel"/> <agent xml:id="stylesheet" roles="editor"> ......... </agent> ......... </head>
Note | |
---|---|
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 Definition
string (pattern (\w+|\d+-\d+)(\s+(\w+|\d+-\d+))*)
Used by: ~text-div
, ~group-attributes
Caution | |
---|---|
No single set of references may mix Roman numerals, alphabetic numerals, and numerals that are ambiguously either. |
Caution | |
---|---|
Leaf div references must be unique. |
Caution | |
---|---|
|
Important | |
---|---|
concatenated |
Caution | |
---|---|
To avoid ambiguous numerals, no div type should mix Roman and alphabet numerals. |
Example 8.94. @n
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.obj |
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 the section called “Regular Expressions” and https://www.w3.org/TR/xpath-functions-30/#regex-syntax
Formal Definition
Used by: ~func-replace
, ~decl-tok-def
Caution | |
---|---|
Attributes 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. |
Example 8.95. @regex
<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>
Note | |
---|---|
Taken from ringoroses.div.1 |
Example 8.96. @regex
<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>
Note | |
---|---|
Taken from ringoroses.01+03.token.1 |
Example 8.97. @regex
<declarations> <token-definition regex="[\w]+"/> <lexicon xml:id="LSJ"> ......... </lexicon> ......... </declarations>
Note | |
---|---|
Example 8.98. @regex
<item> <token-definition regex="[\w]+"/> <name>letters</name> ......... </item>
Note | |
---|---|
Taken from token-definitions.TAN-key |
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 the section called “Rights and Licenses”
Formal Definition
Used by: ~nonsource-rights
, ~source-rights
Example 8.99. @rights-holder
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.obj |
Example 8.100. @rights-holder
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.sem |
Example 8.101. @rights-holder
<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>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.sem-native |
Example 8.102. @rights-holder
<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>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.sem |
The attribute roles
refers to the ID of one or more <role>
s
Formal Definition
Used by: ~agent-list
, ~agent-role-list
Caution | |
---|---|
Every idref in an attribute must point to the |
Caution | |
---|---|
All idrefs in an attribute must be unique. |
Example 8.103. @roles
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.obj |
Example 8.104. @roles
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.sem |
Example 8.105. @roles
<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>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.sem-native |
Example 8.106. @roles
<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>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.sem |
The attribute TAN-version
specifies the version of TAN schemas used.
Formal Definition
string
Used by: ~TAN-root
Example 8.107. @TAN-version
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.obj |
Example 8.108. @TAN-version
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.sem |
Example 8.109. @TAN-version
<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>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.sem-native |
Example 8.110. @TAN-version
<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>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.sem |
The attribute to
specifies the end of a period of time
Formal Definition
( dateTime date )
Used by: <when>
Caution | |
---|---|
Date attributes must be castable either as xs:dateTime or xs:date |
Caution | |
---|---|
Future dates are not permitted. |
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 Definition
Used by: ~group-attributes
, ~text-div
Example 8.111. @type
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.obj |
The attribute when
indicates a date or date and time
Formal Definition
( dateTime date )
Used by: ~comment
, ~change-list
Caution | |
---|---|
Date attributes must be castable either as xs:dateTime or xs:date |
Caution | |
---|---|
Future dates are not permitted. |
Example 8.112. @when
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.obj |
Example 8.113. @when
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.sem |
Example 8.114. @when
<head> ......... <role xml:id="editor"> ......... </role> <change when="2016-07-10" who="kalvesmaki">Began new file</change> </head>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.sem-native |
The attribute when-accessed
specifies when an electronic file was last examined
Formal Definition
( date dateTime )
Used by: <location>
Caution | |
---|---|
Date attributes must be castable either as xs:dateTime or xs:date |
Caution | |
---|---|
Future dates are not permitted. |
Example 8.115. @when-accessed
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.obj |
Example 8.116. @when-accessed
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.sem |
The attribute which
used to point to a reserved keyword, either a reserved tokenization pattern or a relationship.
Formal Definition
Used by: ~decl-tok-def
, ~entity-digital-generic-ref
, ~entity-nondigital-ref
, ~metadata-human
, ~decl-morph
Caution | |
---|---|
An element's |
Caution | |
---|---|
Keywords (values of |
Caution | |
---|---|
Any element that takes |
Caution | |
---|---|
Keys are integral parts of a document. Access to at least one version is absolutely mandatory. |
Example 8.117. @which
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.obj |
Example 8.118. @which
<see-also> <relationship which="model"/> <IRI>tag:kalvesmaki.com,2014:tan-t:ar.cat.grc.1949.minio-paluello:semantic-refs</IRI> ......... </see-also>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.sem |
The attribute who
names an <agent>
Formal Definition
Used by: ~comment
, ~agent-role-list
, ~change-list
Caution | |
---|---|
Every idref in an attribute must point to the |
Caution | |
---|---|
All idrefs in an attribute must be unique. |
Example 8.119. @who
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.obj |
Example 8.120. @who
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.sem |
Example 8.121. @who
<head> ......... <role xml:id="editor"> ......... </role> <change when="2016-07-10" who="kalvesmaki">Began new file</change> </head>
Note | |
---|---|
Taken from ar.cat.fra.1844.saint-hilaire.sem-native |
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 Definition
ID (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
Caution | |
---|---|
|
Caution | |
---|---|
Any ana with an |
Caution | |
---|---|
Codes for ( |
Example 8.122. @xml:id
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.obj |
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 the section called “Languages”.
Examples: 'eng' (English), 'grc' (classical Greek), 'lat' (Latin)
Formal Definition
language
Used by: ~other-body-attributes
, ~text-div
, ~nontextual-reference
, ~metadata-desc
Example 8.123. @xml:lang
<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>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.obj |
Example 8.124. @xml:lang
<div-type xml:id="par"> <IRI>http://dbpedia.org/resource/Paragraph</IRI> <name xml:lang="eng">paragraph</name> </div-type>
Note | |
---|---|
Taken from ar.cat.eng.1926.edghill.sem |