| Attributes | Attributes att.global.linking (@corresp, @next, @prev) att.global.analytic (@ana) att.global.facs (@facs) | xml:id xml:id¶ | (identifier) provides a unique identifier for the element bearing the attribute.| Status | Optional | | Datatype |
xsd:ID | | Note | The xml:id attribute may be used to specify a canonical reference for an element; see section 3.10. . |
| | n n¶ | (number) gives a number (or other label) for an element, which is not necessarily unique within the document.| Status | Optional | | Datatype |
data.text | | Values | the value consists of a single token which may however contain punctuation characters, whitespace or word separating characters. It need not be restricted to numbers. | | Note | The n attribute may be used to specify the numbering of chapters, sections, list items, etc.; it may also be used in the specification of a standard reference system for the text. |
| | xml:lang xml:lang¶ | (language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.| Status | Optional | | Datatype |
data.language | | Values | The value must conform to BCP 47. If the value is a private use code (i.e., starts with x- or contains -x-), a language element with a matching value for its ident attribute should be supplied in the TEI header to document this value. Such documentation may also optionally be supplied for non-private-use codes, though these must remain consistent with their (IETF)Internet Engineering Task Force definitions. | <p> … The consequences of
this rapid depopulation were the loss of the last
<foreign xml:lang="rap">ariki</foreign> or chief
(Routledge 1920:205,210) and their connections to
ancestral territorial organization.</p> | | Note | the xml:lang value will be inherited from the immediately enclosing element, or from its parent, and so on up the document hierarchy. It is generally good practice to specify xml:lang at the highest appropriate level, noticing that a different default may be needed for the teiHeader from that needed for the associated resource element or elements, and that a single TEI document may contain texts in many languages. The authoritative list of registered language subtags is maintained by IANA and is available at http://www.iana.org/assignments/language-subtag-registry. For a good general overview of the construction of language tags, see http://www.w3.org/International/articles/language-tags/, and for a practical step-by-step guide, see http://www.w3.org/International/questions/qa-choosing-language-tags. |
| | rend rend¶ | (rendition) indicates how the element in question was rendered or presented in the source text.| Status | Optional | | Datatype | 1–∞ occurrences of
data.wordseparated by whitespace | | Values | may contain any number of tokens, each of which may contain letters, punctuation marks, or symbols, but not whitespace or word-separating characters. | <head rend="align(center) case(allcaps)">
<lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle,
<lb/>On Her <lb/>
<hi rend="case(mixed)">New Blazing-World</hi>.
</head> | | Note | These Guidelines make no binding recommendations for the values of the rend attribute; the characteristics of visual presentation vary too much from text to text and the decision to record or ignore individual characteristics varies too much from project to project. Some potentially useful conventions are noted from time to time at appropriate points in the Guidelines. The values of the rend attribute are a set of sequence-indeterminate individual tokens separated by whitespace. |
|
|