The element align
declares one or more groups of words that should be aligned with each other. <align>
specifies that all the tokens invoked for one source collectively align with the tokens in the other.
Formal Definition
(~inclusion
| (~alignment-attributes-non-class-2
,~certainty-stamp
,@group
?, (<comment>
* & (<tok>
|~tok-sequence
)+)))
Used by: ~item
Important | |
---|---|
A defective reference is a value of |
Caution | |
---|---|
No |
Example 8.170. <align>
<TAN-A-tok TAN-version="1 dev" id="tag:parkj@textalign.net,2015:TAN-A-tok,ring01+ring02"> ......... <body bitext-relation="B-descends-from-A" reuse-type="adaptation" in-progress="false"> <align> <tok src="ring1881" ref="1" pos="1"/> <tok src="ring1987" ref="1" pos="1"/> </align> <align> <tok src="ring1881" ref="1" pos="2"/> <tok src="ring1987" ref="1" pos="2"/> </align> <align> <tok src="ring1881" ref="1" pos="3"/> <tok src="ring1987" ref="1" pos="3"/> </align> <align> <tok src="ring1881" ref="1" pos="4"/> <tok src="ring1987" ref="1" pos="4"/> </align> <align> ......... </align> ......... </body> </TAN-A-tok>
Note | |
---|---|
Taken from ringoroses.01+02.token.1 |
The element bitext-relation
identifies how the text on one text-bearing object relates to that on another by specifying a relationship, e.g., B is a direct copy of A, B and A descent from a commont parent, etc. See the section called “Token-Based Alignments (<TAN-A-tok>)” for theoretical background.
In most cases, there will be need for only one of these elements. But multiple values may be helpful for cases where a bitext has a complex history, for example, a textual object that was created over time, and in different phases.
This element should not be used to describe any activities (e.g., translation, copying), reserved for <reuse-type>
.
For examples see main.xml# keywords-bitext-relation
Formal Definition
~decl-pattern-default
Used by: ~declaration-items
Example 8.171. <bitext-relation>
<declarations> <bitext-relation xml:id="B-descends-from-A"> <IRI>tag:textalign.net,2015:bitext-relation:a/x+/b</IRI> <name>B descends directly from A, unknown number of intermediaries</name> <desc>The 1987 versions is hypothesized to descend somehow from the 1881 version, mainly for the sake of illustration.</desc> </bitext-relation> <reuse-type xml:id="adaptation"> ......... </reuse-type> ......... </declarations>
Note | |
---|---|
Taken from ringoroses.01+02.token.1 |
Example 8.172. <bitext-relation>
<declarations> <bitext-relation xml:id="unclear"> <IRI>tag:kalvesmaki@gmail.com,2014:bitext-relation:unclear</IRI> <name>The German and English versions bear some relationship, but what exactly is unclear.</name> </bitext-relation> <reuse-type xml:id="correlationGeneral"> ......... </reuse-type> ......... </declarations>
Note | |
---|---|
Taken from ringoroses.01+03.token.1 |
Example 8.173. <bitext-relation>
<declarations> <bitext-relation xml:id="unclear"> <IRI>tag:kalvesmaki@gmail.com,2014:bitext-relation:unclear</IRI> <name>The German and English versions bear some relationship, but what exactly is unclear.</name> </bitext-relation> <reuse-type xml:id="correlationGeneral"> ......... </reuse-type> ......... </declarations>
Note | |
---|---|
Taken from ringoroses.01+03.token.2 |
The element reuse-type
identifies a category of text reuse (e.g., translation, mistranslation, paraphrase, ridicule). See the section called “Token-Based Alignments (<TAN-A-tok>)” for theoretical background.
For examples see main.xml# keywords-reuse-type
Formal Definition
~decl-pattern-default
Example 8.174. <reuse-type>
<declarations> <bitext-relation xml:id="B-descends-from-A"> ......... </bitext-relation> <reuse-type xml:id="adaptation"> <IRI>tag:textalign.net,2015:reuse-type:adaptation:general</IRI> <name>general adaptation</name> </reuse-type> <token-definition src="ring1881 ring1987" which="letters"/> </declarations>
Note | |
---|---|
Taken from ringoroses.01+02.token.1 |
Example 8.175. <reuse-type>
<declarations> <bitext-relation xml:id="unclear"> ......... </bitext-relation> <reuse-type xml:id="correlationGeneral"> <IRI>tag:kalvesmaki@gmail.com,2014:reuse-type:correlation-general</IRI> <name>Texts are generally correlated, but without specifying the relation</name> </reuse-type> <comment when="2016-02-22-05:00" who="park">The following is equivalent to @which = 'letters'</comment> ......... </declarations>
Note | |
---|---|
Taken from ringoroses.01+03.token.1 |
Example 8.176. <reuse-type>
<declarations> <bitext-relation xml:id="unclear"> ......... </bitext-relation> <reuse-type xml:id="correlationGeneral"> <IRI>tag:kalvesmaki@gmail.com,2014:reuse-type:correlation-general</IRI> <name>Texts are generally correlated, but without specifying the relation</name> </reuse-type> <token-definition src="eng ger" which="letters and punctuation"/> ......... </declarations>
Note | |
---|---|
Taken from ringoroses.01+03.token.2 |
The element TAN-A-tok
specifies that the file is a token-based TAN alignment file. Root element.
Formal Definition
~TAN-root
Important | |
---|---|
Every validated TAN file will include the following message at its root. “This version of TAN is under development, and is subject to change. Participants in developing the TAN schemas, functions, and guidelines are welcome. See http://textalign.net for details.” |
Example 8.177. <TAN-A-tok>
<TAN-A-tok TAN-version="1 dev" id="tag:parkj@textalign.net,2015:TAN-A-tok,ring01+ring02"> <head> ......... </head> <body bitext-relation="B-descends-from-A" reuse-type="adaptation" in-progress="false"> ......... </body> </TAN-A-tok>
Note | |
---|---|
Taken from ringoroses.01+02.token.1 |
Example 8.178. <TAN-A-tok>
<TAN-A-tok TAN-version="1 dev" id="tag:parkj@textalign.net,2015:TAN-A-tok,ring01+ring03"> <head> ......... </head> <body reuse-type="correlationGeneral" bitext-relation="unclear"> ......... </body> </TAN-A-tok>
Note | |
---|---|
Taken from ringoroses.01+03.token.1 |
Example 8.179. <TAN-A-tok>
<TAN-A-tok TAN-version="1 dev" id="tag:parkj@textalign.net,2015:TAN-A-tok,ring01+ring03:alt"> <head> ......... </head> <body reuse-type="correlationGeneral" bitext-relation="unclear"> ......... </body> </TAN-A-tok>
Note | |
---|---|
Taken from ringoroses.01+03.token.2 |
The attribute bitext-relation
points to one or more <bitext-relation>
@xml:id
values that qualify the type of relation that holds. Multiple values assume inclusive or (A or B or A and B)
This attribute is inheritable. See the section called “Interpretation of inheritable attributes”
Formal Definition
Used by: ~other-body-attributes
, ~alignment-attributes-non-class-2
Caution | |
---|---|
Every idref in an attribute must point to the |
Caution | |
---|---|
All idrefs in an attribute must be unique. |
Example 8.180. @bitext-relation
<TAN-A-tok TAN-version="1 dev" id="tag:parkj@textalign.net,2015:TAN-A-tok,ring01+ring02"> <head> ......... </head> <body bitext-relation="B-descends-from-A" reuse-type="adaptation" in-progress="false"> <align> ......... </align> <align> ......... </align> <align> ......... </align> ......... </body> </TAN-A-tok>
Note | |
---|---|
Taken from ringoroses.01+02.token.1 |
Example 8.181. @bitext-relation
<TAN-A-tok TAN-version="1 dev" id="tag:parkj@textalign.net,2015:TAN-A-tok,ring01+ring03"> <head> ......... </head> <body reuse-type="correlationGeneral" bitext-relation="unclear"> <align> ......... </align> <align> ......... </align> <align> ......... </align> ......... </body> </TAN-A-tok>
Note | |
---|---|
Taken from ringoroses.01+03.token.1 |
Example 8.182. @bitext-relation
<TAN-A-tok TAN-version="1 dev" id="tag:parkj@textalign.net,2015:TAN-A-tok,ring01+ring03:alt"> <head> ......... </head> <body reuse-type="correlationGeneral" bitext-relation="unclear"> <align> ......... </align> <align> ......... </align> <align> ......... </align> ......... </body> </TAN-A-tok>
Note | |
---|---|
Taken from ringoroses.01+03.token.2 |
The attribute reuse-type
points to one or more <reuse-type>
@xml:id
values that qualify the type of textual reuse that holds. Multiple values assume inclusive or (A or B or A and B)
This attribute is inheritable. See the section called “Interpretation of inheritable attributes”
Formal Definition
Used by: ~other-body-attributes
, ~alignment-attributes-non-class-2
Caution | |
---|---|
Every idref in an attribute must point to the |
Caution | |
---|---|
All idrefs in an attribute must be unique. |
Example 8.183. @reuse-type
<TAN-A-tok TAN-version="1 dev" id="tag:parkj@textalign.net,2015:TAN-A-tok,ring01+ring02"> <head> ......... </head> <body bitext-relation="B-descends-from-A" reuse-type="adaptation" in-progress="false"> <align> ......... </align> <align> ......... </align> <align> ......... </align> ......... </body> </TAN-A-tok>
Note | |
---|---|
Taken from ringoroses.01+02.token.1 |
Example 8.184. @reuse-type
<TAN-A-tok TAN-version="1 dev" id="tag:parkj@textalign.net,2015:TAN-A-tok,ring01+ring03"> <head> ......... </head> <body reuse-type="correlationGeneral" bitext-relation="unclear"> <align> ......... </align> <align> ......... </align> <align> ......... </align> ......... </body> </TAN-A-tok>
Note | |
---|---|
Taken from ringoroses.01+03.token.1 |
Example 8.185. @reuse-type
<TAN-A-tok TAN-version="1 dev" id="tag:parkj@textalign.net,2015:TAN-A-tok,ring01+ring03:alt"> <head> ......... </head> <body reuse-type="correlationGeneral" bitext-relation="unclear"> <align> ......... </align> <align> ......... </align> <align> ......... </align> ......... </body> </TAN-A-tok>
Note | |
---|---|
Taken from ringoroses.01+03.token.2 |