The element div
marks a textual unit. Contains other <div>
s or text, but not both (no mixed content).
TAN's <div>
differs from the TEI's, in that the latter is intended for the first level or levels of subdivision in the front, body, or back of a text, but not for paragraphs or anonymous blocks. The TAN <div>
better resembles the one defined by HTML, and can be applied to any kind of division whatsoever., even down to the letter or character level.
Formal Definition
~ed-stamp
?, (~inclusion
| (@type
,@n
,@xml:lang
?, (<div>
+ | text)))
Caution | |
---|---|
All text must be normalized (Unicode NFC). |
Caution | |
---|---|
Leaf div references must be unique. |
Caution | |
---|---|
|
Caution | |
---|---|
Every leaf div must have at least some non-space text. |
Caution | |
---|---|
No div may begin with a modifying character. |
Caution | |
---|---|
No div may have a spacing character followed by a modifying character. |
Caution | |
---|---|
No div may have Unicode characters that are disallowed, e.g., U+A0, NO BREAK SPACE. |
Caution | |
---|---|
|
Important | |
---|---|
concatenated |
Example 8.135. <div>
<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 element TAN-T
specifies that the TAN file contains a transcription. 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.136. <TAN-T>
<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.137. <TAN-T>
<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.138. <TAN-T>
<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.139. <TAN-T>
<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 |