3 Elements Available in All TEI Documents

목차

This chapter describes elements which may appear in any kind of text and the tags used to mark them in all TEI documents. Most of these elements are freely floating phrases, which can appear at any point within the textual structure, although they should generally be contained by a higher-level element of some kind (such as a paragraph). A few of the elements described in this chapter (for example, bibliographic citations and lists) have a comparatively well-defined internal structure, but most of them have no consistent inner structure of their own. In the general case, they contain only a few words, and are often identifiable in a conventionally printed text by the use of typographic conventions such as shifts of font, use of quotation or other punctuation marks, or other changes in layout.

This chapter begins by describing the p tag used to mark paragraphs, the prototypical formal unit for running text in many TEI modules. This is followed, in section 3.2 Treatment of Punctuation, by a discussion of some specific problems associated with the interpretation of conventional punctuation, and the methods proposed by these Guidelines for resolving ambiguities therein.

The next section (section 3.3 Highlighting and Quotation) describes a number of phrase-level elements commonly marked by typographic features (and thus well-represented in conventional markup languages). These include features commonly marked by font shifts (section 3.3.2 Emphasis, Foreign Words, and Unusual Language) and features commonly marked by quotation marks (section 3.3.3 Quotation) as well as such features as terms, cited words, and glosses (section 3.4 Terms and Glosses, Ruby Annotations, and Equivalents and Descriptions).

Section 3.5 Simple Editorial Changes introduces some phrase-level elements which may be used to record simple editorial interventions, such as emendation or correction of the encoded text. The elements described here constitute a simple subset of the full mechanisms for encoding such information (described in full in chapter 11 Representation of Primary Sources), which should be adequate to most commonly encountered situations.

The next section (section 3.6 Names, Numbers, Dates, Abbreviations, and Addresses) describes several phrase-level and inter-level elements which, although often of interest for analysis or processing, are rarely explicitly identified in conventional printing. These include names (section 3.6.1 Referring Strings), numbers and measures (section 3.6.3 Numbers and Measures), dates and times (section 3.6.4 Dates and Times), abbreviations (section 3.6.5 Abbreviations and Their Expansions), and addresses (section 3.6.2 Addresses).

In the same way, the following section (section 3.7 Simple Links and Cross-References) presents only a subset of the facilities available for the encoding of cross-references or text-linkage. The full story may be found in chapter 16 Linking, Segmentation, and Alignment; the tags presented here are intended to be usable for a wide variety of simple applications.

Sections 3.8 Lists, and 3.9 Notes, Annotation, and Indexing, describe two kinds of quasi-structural elements: lists and notes. These may appear either within chunk-level elements such as paragraphs, or between them. Several kinds of lists are catered for, of an arbitrary complexity. The section on notes discusses both notes found in the source and simple mechanisms for adding annotations of an interpretive nature during the encoding; again, only a subset of the facilities described in full elsewhere (specifically, in chapter 17 Simple Analytic Mechanisms) is discussed.

Section 3.10 Graphics and Other Non-textual Components introduces some simple ways of representing graphic or other non-textual content found in a text. A fuller discussion of the multimedia facilities supported by these Guidelines may be found in chapters 14 Tables, Formulæ, Graphics and Notated Music and 16 Linking, Segmentation, and Alignment.

Next, section 3.11 Reference Systems, describes methods of encoding within a text the conventional system or systems used when making references to the text. Some reference systems have attained canonical authority and should be recorded to make the text useable in normal work; in other cases, a convenient reference system should be created by the creator or analyst of an electronic text.

Like lists and notes, the bibliographic citations discussed in section 3.12 Bibliographic Citations and References, may be regarded as structural elements in their own right. A range of possibilities is presented for the encoding of bibliographic citations or references, which may be treated as simple phrases within a running text, or as highly-structured components suitable for inclusion in a bibliographic database.

Additional elements for the encoding of passages of verse or drama (whether prose or verse) are discussed in section 3.13 Passages of Verse or Drama.

The chapter concludes with a technical overview of the structure and organization of the module described here. This should be read in conjunction with chapter 1 The TEI Infrastructure, describing the structure of the TEI document type definition.

3.1 Paragraphs

The paragraph is the fundamental organizational unit for all prose texts, being the smallest regular unit into which prose can be divided. Prose can appear in all TEI texts, even those that are primarily of another genre (e.g., verse); thus the paragraph is described here, as an element which can appear in any kind of text.

Paragraphs can contain any of the other elements described within this chapter, as well as some other elements which are specific to individual text types. We distinguish phrase-level elements, which must be entirely contained within a paragraph or similar structure and cannot appear except within one, from chunks, which can appear between, but not within, paragraphs, and from inter-level elements, which can appear either within a single paragraph or between paragraphs. The class of phrases includes emphasized or quoted phrases, names, dates, etc. The class of inter-level elements includes bibliographic citations, notes, lists, etc. The class of chunks includes the paragraph itself, and other elements which have similar structural properties, notably the ab (anonymous block) element described in 16.3 Blocks, Segments, and Anchors) which may be used as an alternative to the paragraph in some kinds of texts.

Because paragraphs may appear in different base or additional tag sets, their possible contents may differ in different kinds of documents. In particular, additional elements not listed in this chapter may appear in paragraphs in certain kinds of text. However, the elements described in this chapter are always by default available in all kinds of text.

The paragraph is marked using the p element:

  • p (문단) 산문에서 문단을 표시한다.

If a consistent internal subdivision of paragraphs is desired, the s or seg (‘segment’) elements may be used, as discussed in chapters 16 Linking, Segmentation, and Alignment and 17 Simple Analytic Mechanisms respectively. More usually, however, paragraphs have no firm internal structure, but contain prose encoded as a mix of characters, entity references, phrases marked as described in the rest of this chapter, and embedded elements like lists, figures, or tables.

Since paragraphs are usually explicitly marked in Western texts, typically by indentation, the application of the p tag usually presents few problems.

In some cases, the body of a text may comprise but a single paragraph:
<body>
 <p>I fully appreciate Gen. Pope's splendid achievements with their
   invaluable results; but you must know that Major Generalships in the
   Regular Army, are not as plenty as blackberries.</p>
</body>
This news story shows typically short journalistic paragraphs:
<head>SARAJEVO, Bosnia and Herzegovina, April 19</head>
<p>Serbs seized more territory in this struggling new country today as
the United States Air Force ended a two-day airlift of humanitarian
aid into the capital, Sarajevo.</p>
<p>International relief workers called on European Community nations
to step up their humanitarian aid to the former Yugoslav republic,
in conjunction with new American aid flights if necessary.</p>
<p>A special envoy from the European Community, Colin Doyle, harshly
condemned the decision by Serbs to shell Sarajevo on Saturday night
during a visit to the Bosnian capital by a senior American official,
Deputy Assistant Secretary of State Ralph R. Johnson.</p>
<p>...</p>
The following extract from a Russian fairy tale demonstrates how other phrase level elements (in this case q elements representing direct speech; see section 3.3.3 Quotation) may be nested within, but not across, paragraphs:
<p>A fly built a castle, a tall and mighty castle.
There came to the castle the Crawling Louse. <q>Who,
   who's in the castle? Who, who's in your house?</q>
said the Crawling Louse. <q>I, I, the Languishing Fly.
   And who art thou?</q>
 <q>I'm the Crawling Louse.</q>
</p>
<p>Then came to the castle the Leaping Flea. <q>Who,
   who's in the castle?</q> said the Leaping Flea. <q>I,
   I, the Languishing Fly, and I, the Crawling Louse. And
   who art thou?</q>
 <q>I'm the Leaping Flea.</q>
</p>
<p>Then came to the castle the Mischievous Mosquito.
<q>Who, who's in the castle?</q> said the Mischievous
Mosquito. <q>I, I, the Languishing Fly, and I, the
   Crawling Louse, and I, the Leaping Flea. And who art
   thou?</q>
 <q>I'm the Mischievous Mosquito.</q>
</p>

3.2 Treatment of Punctuation

Punctuation marks cause two distinct classes of problem for text markup: the marks may not be available in the character set used, and they may be significantly ambiguous. To some extent, the availability of the Unicode character set addresses the first of these problems, since it provides specific code points for most punctuation marks, and also the second to the extent that it distinguishes glyphs (such as stop, comma, and hyphen) which are used with different functions. Where punctuation itself is the subject of study, the element pc (punctuation character) may be used to mark it explicitly, as further discussed in 17.1.2 Below the Word Level. Where the character used for a punctuation mark is not available in Unicode, the g element and other facilities described in chapter 5 Characters, Glyphs, and Writing Modes may also be used to mark its presence.

3.2.1 Functions of Punctuation

Punctuation is itself a form of markup, historically introduced to provide the reader with an indication about how the text should be read. As such, it is unsurprising that encoders will often wish to encode directly the purpose for which punctuation was provided, as well as, or even instead of, the punctuation itself. We discuss some typical cases below.

The Full stop (period) may mark (orthographic) sentence boundaries, abbreviations, decimal points, or serve as a visual aid in printing numbers. These usages can be distinguished by tagging S-units, abbreviations, and numbers, as described in sections 16.3 Blocks, Segments, and Anchors, 3.6.5 Abbreviations and Their Expansions, and 3.6.3 Numbers and Measures respectively. However, there are independent reasons for tagging these, whether or not they are marked by full stops, and the polysemy of the full stop itself is perhaps no different from that of any other character in the writing system.

The Question mark and exclamation mark usually mark the end of orthographic sentences, but may also be used as a mid-sentence comment by the author (! to express surprise or some other strong feeling, ? to query a word or expression or mark a sentence as dubious in linguistic discussion). Such usages may be distinguished by marking S-units, in which case the mid-sentence uses of these punctuation marks may be left unmarked, or tagged using the pc element discussed in 17.1 Linguistic Segment Categories.

Dashes are used for a variety of purposes: as a mark of omission, insertion, or interruption; to show where a new speaker takes over (in dialogue); or to introduce a list item. In the latter two cases particularly, it is clearly desirable to mark the function as well as its rendition using the elements q or item, on which see section 3.3.3 Quotation, and section 3.8 Lists, respectively.

Quotation marks may be removed from text contained by q or quote elements on editorial grounds, or they may be marked in a variety of ways; see the discussion of quotation and related features in section 3.3.3 Quotation.

Apostrophes should be distinguished from single quote marks. As with hyphens, this disambiguation is best performed by selecting the appropriate Unicode character, though it may also be represented by using appropriate XML markup for quotations as suggested above. However, apostrophes have a variety of uses. In English they mark contractions, genitive forms, and (occasionally) plural forms. Full disambiguation of these uses belongs to the level of linguistic analysis and interpretation.

Parentheses and other marks of suspension such as dashes or ellipses are often used to signal information about the syntactic structure of a text fragment. Full disambiguation of their uses also belongs to the level of linguistic analysis and interpretation, and will therefore need to use the mechanisms discussed in chapter 17 Simple Analytic Mechanisms.

Where punctuation marks are disambiguated by tagging their assumed function in the text (for example, quotation), it may be debated whether they should be excluded or left as part of the text. In the case of quotation marks, it may be more convenient to distinguish opening from closing marks simply by using the appropriate Unicode character than to use the q element, with or without an indication of rendition.

Where segmentation of a text is performed automatically, the accuracy of the result may be considerably enhanced by a first pass in which the function of different punctuation characters is explicitly marked. This need not be done for all cases, but only where the structural function of the punctuation markup (for example as a word or phrase delimiter) is ambiguous. Thus, dots indicating abbreviation might be distinguished from dots indicating sentence end, and exclamation or question marks internal to a sentence distinguished from those which terminate one. Furthermore, when encoding historical materials, it may be considered essential to retain the original punctuation, whether by using an appropriate character code, if this is available (or using the g element where it is not) or by an explicit encoding using pc. The particular method adopted will vary depending upon the feature concerned and upon the purpose of the project.

3.2.2 Hyphenation

Hyphenation as a phenomenon is generally of most concern when producing formatted text for display in print or on screen: different languages and systems have developed quite sophisticated sets of rules about where hyphens may be introduced and for what reason. These generally do not concern the text encoder, since they belong to the domain of formatting and will generally be handled by the rendition software in use. In this section, we discuss issues arising from the appearance of hyphens in pre-existing formatted texts which are being re-encoded for analysis or other processing. Unicode distinguishes four characters visually similar to the hyphen, including the undifferentiated hyphen-minus (U+002D) which is retained for compatibility reasons. The hard hyphen (U+2010) is distinguished from the minus sign (U+2212) which is for use in mathematical expressions, and also from the soft hyphen (U+00AD) which may appear in ‘born digital’ documents to indicate places where it is acceptable to insert a hyphen when the document is formatted.

Historically, the hard hyphen has been used in printed or manuscript documents for two distinct purposes. In many languages, it is used between words to show that they function as a single syntactic or lexical unit. For example, in French, est-ce que; in English body-snatcher, tea-party etc. It may also have an important role in disambiguation (for example, by distinguishing say a man-eating fish from a man eating fish). Such usages, although possibly problematic when a linguistic analysis is undertaken, are not generally of concern to text encoders: the hyphen character is usually retained in the text, because it may be regarded as part of the way a compound or other lexical item is spelled. Deciding whether a compound is to be decomposed into its constituent parts, and if so how, is a different question, involving consideration of many other phenomena in addition to the simple presence of a hyphen.

When it appears at the end of a printed or written line however, the hard hyphen generally indicates that—contrary to what might be expected—a word is not yet complete, but continues on the next line (or over the next page or column or other boundary). The hyphen character is not, in this case, part of the word, but just a signal that the word continues over the break. Unfortunately, few languages distinguish these two cases visually, which necessarily poses a problem for text encoders. Suppose, for example, that we wish to investigate a diachronic English corpus for occurrences of tea-pot and teapot, to find evidence for the point at which this compound becomes lexicalized. Any case where the word is hyphenated across a linebreak, like this: 

tea-
pot⚓

is ambiguous: there is no simple way of deciding which of the two spellings was intended.

As elsewhere, therefore, encoders have a range of choices:

  • They may decide simply to remove any end-of-line hyphenation from the encoded text, on the grounds that its presence is purely a secondary matter of formatting. This will obviously apply also if line endings are themselves regarded as unimportant.
  • Alternatively, they may decide to record the presence of the hyphen, perhaps on the grounds that it provides useful morphological information; perhaps in order to retain information about the visual appearance of the original source. In either case, they need to decide whether to record it explicitly, by including an appropriate punctuation character in the text data, or implicitly by supplying an appropriate symbolic value for one or more of the attributes on the lb or other milestone element used to record the fact of the line division. If the hyphen is included in the character data of the TEI document, it might be marked up using the pc (punctuation character) tag, which allows the encoder to express information about its function as a separator, through the force attribute. For example, the example above could be encoded with a force value of "inter" to indicate that the punctuation mark may or may not be a word separator (See also 17.1.2 Below the Word Level).
    tea<pc force="inter">-</pc>pot

A similar range of possibilities applies equally to the representation of other common punctuation marks, notably quotation marks, as discussed in 3.3.3 Quotation.

The ‘text data’ of which XML documents are composed is decomposable into smaller units, here called orthographic tokens, even if those units are not explicitly indicated by the XML markup. The ambiguity of the end-of-line hyphen also causes problems in the way a processor identifies such tokens in the absence of explicit markup. If token boundaries are not explicitly marked (for example using the seg or w elements), for most languages a processor will rely on character class information to determine where they are to be found: some punctuation characters are considered to be word-breaking, while others are not. In XML, the newline character in text data is a kind of whitespace, and is therefore word breaking. However, it is generally unsafe to assume that whitespace adjacent to markup tags will always be preserved, and it is decidedly unsafe to assume that markup tags themselves are equivalent to whitespace.

The lb, pb, and cb elements are notable exceptions to this general rule, since their function is precisely to represent (or replace) line, page, or column breaks, which, as noted above, are generally considered to be equivalent to whitespace. These elements provide a more reliable way of preserving the lineation, pagination, etc of a source document, since the encoder should not assume that (untagged) line breaks etc. in an XML source file will necessarily be preserved.

To control the intended tokenization, the encoder may use the break attribute on such elements to indicate whether or not the element is to be regarded as equivalent to whitespace. This attribute can take the values yes or no to indicate whether or not the element corresponds with a token boundary. The value maybe is also available, for cases where the encoder does not wish (or is unable) to determine whether the orthographic token concerned is broken by the line ending.

As a final complication, it should be noted that in some languages, particularly German and Dutch, the spelling of a word may be altered in the presence of end of line hyphenation. For example, in Dutch, the word opaatje (granddad), occurring at the end of a line may be hyphenated as opa-tje, with a single letter a. An encoder wishing to preserve the original form of this orthographic token in a printed text while at the same time facilitating its recognition as the word opaatje will therefore need to rely on a more sophisticated process than simply removing the hyphen. This is however essentially the same as any other form of normalization accompanying the recognition of variations in spelling or morphology: as such it may be encoded using the choice element discussed in 3.5 Simple Editorial Changes, or the more sophisticated mechanisms for linguistic analysis discussed in chapter 17 Simple Analytic Mechanisms.

3.3 Highlighting and Quotation

This section deals with a variety of textual features, all of which have in common that they are frequently realized in conventional printing practice by the use of such features as underlining, italic fonts, or quotation marks, collectively referred to here as highlighting. After an initial discussion of this phenomenon and alternate approaches to encoding it, this section describes ways of encoding the following textual features, all of which are conventionally rendered using some kind of highlighting:

  • emphasis, foreign words and other linguistically distinct uses of highlighting
  • representation of speech and thought, quotation, etc.
  • technical terms, glosses, etc.

3.3.1 What Is Highlighting?

By highlighting we mean the use of any combination of typographic features (font, size, hue, etc.) in a printed or written text in order to distinguish some passage of a text from its surroundings.11 The purpose of highlighting is generally to draw the reader's attention to some feature or characteristic of the passage highlighted; this section describes the elements recommended by these Guidelines for the encoding of such textual features.

In conventionally printed modern texts, highlighting is often employed to identify words or phrases which are regarded as being one or more of the following:

  • distinct in some way—as foreign, dialectal, archaic, technical, etc.
  • emphatic, and which would for example be stressed when spoken
  • not part of the body of the text, for example cross-references, titles, headings, labels, etc.
  • identified with a distinct narrative stream, for example an internal monologue or commentary.
  • attributed by the narrator to some other agency, either within the text or outside it: for example, direct speech or quotation.
  • set apart from the text in some other way: for example, proverbial phrases, words mentioned but not used, names of persons and places in older texts, editorial corrections or additions, etc.

The textual functions indicated by highlighting may not be rendered consistently in different parts of a text or in different texts. (For example, a foreign word may appear in italics if the surrounding text is in roman, but in roman if the surrounding text is in italics.) For this reason, these Guidelines distinguish between the encoding of rendering itself and the encoding of the underlying feature expressed by it.

Highlighting as such may be encoded by using one of the global attributes rend, rendition, or style (see further 1.3.1.1 Global Attributes). This allows the encoder both to specify the function of a highlighted phrase or word, by selecting the appropriate element described here or elsewhere in these Guidelines, and to further describe the way in which it is highlighted, by means of an attribute. If the encoder wishes to offer no interpretation of the feature underlying the use of highlighting in the source text, then the hi element may be used, which indicates only that the text so tagged was highlighted in some way.

  • hi (강조체) 어떤 이유인지는 명세하지 않고, 주변 텍스트와 시각적으로 구별된 단어나 구를 표시한다.

The hi element is provided by the model.hiLike class.

The possible values carried by the rend attribute are not formally defined in this version of the Guidelines. It may be used to document any peculiarity of the way a given segment of text was rendered in the original source text, and may thus express a very large range of typographic or other features, by no means restricted to typeface, type size, etc. The style attribute, by contrast, defines the way the source text was rendered using a formally defined style language, such as the W3C standard Cascading Stylesheet Language (Lie and Bos (eds.) (1999)). The complementary rendition attribute is used to point to one or more fragments expressed using such a language which have been predefined in the TEI header using the rendition element discussed in section 2.3.4 The Tagging Declaration.

Where it is both appropriate and feasible, these Guidelines recommend that the textual feature marked by the highlighting should be encoded, rather than just the simple fact of the highlighting. This is for the following reasons:

  • the same kind of highlighting may be used for different purposes in different contexts
  • the same textual function may be highlighted in different ways in different contexts
  • for analytic purposes, it is in general more useful to know the intended function of a highlighted phrase than simply that it is distinct.

In many, if not most, cases the underlying function of a highlighted phrase will be obvious and non-controversial, since the distinctions indicated by a change of highlighting correspond with distinctions discussed elsewhere in these Guidelines. The elements available to record such distinctions are, for the most part, members of the model.emphLike class. This and the model.hiLike class mentioned above constitute the model.highlighted class, which is a phrase level class. Members of this class may appear anywhere within paragraph level elements.

The distinction between the two classes is simple, and typified by the two elements hi and emph: the former marks simply that a passage is typographically distinct in some way, while the latter asserts that a passage is linguistically emphasized for some purpose. These two properties, though often combined, are not identical. It should however be recognized, however, that cases do exist in which it is not economically feasible to mark the underlying function (e.g. in the preparation of large text corpora), as well as cases in which it is not intellectually appropriate (as in the transcription of some older materials, or in the preparation of material for the study of typographic practice). In such cases, the hi element or some other element from the model.hiLike class should be used.

Elements which are sometimes realized by typographic distinction but which are not discussed in this section include title (discussed in section 3.12 Bibliographic Citations and References) and name (discussed in section 3.6.1 Referring Strings).

3.3.2 Emphasis, Foreign Words, and Unusual Language

This subsection discusses the following elements:

  • foreign (외국어) 주변 텍스트와 다른 언어로 사용된 단어나 구를 표시한다.
  • emph (강조) 언어적 또는 수사적 효과를 위해 강세가 붙거나 강조된 단어 또는 구를 표시한다.
  • distinct 고어, 전문어, 방언, 비선호 단어 등과 같이 언어적으로 구분되거나 하위언어의 부분을 형성하는 것으로 간주되는 임의의 단어 또는 구를 표시한다.

These elements are all members of the model.emphLike class.

3.3.2.1 Foreign Words or Expressions
Words or phrases which are not in the main language of the text should be tagged as such, at least where the fact is indicated in the text. Where the word or phrase concerned is already distinguished from the rest of the text by virtue of its function (for example, because it is a name, a technical term, a quotation, a mentioned word, etc.) then the global xml:lang attribute should be used to specify additionally that its language distinguishes it from the surrounding text. Any element in the TEI scheme may take an xml:lang attribute, which specifies both the writing system and the language used by its content (see sections 1.3.1.1.2 Language Indicators and vi.1. Language Identification for discussion of this attribute and its values respectively). Where there is no other applicable element, the element foreign may be used to provide a peg onto which the xml:lang may be attached.
<q>Aren't you confusing <foreign xml:lang="la">post hoc</foreign> with <foreign xml:lang="la">propter
   hoc</foreign>?</q> said the Bee Master.
<q>Wax-moth only succeed when
weak bees let them in.</q>
The foreign element should not be used to represent foreign words which are mentioned or glossed within the text: for these use the appropriate element from section 3.4.1 Terms and Glosses below. Compare the following example sentences:
John eats a <foreign xml:lang="fr">croissant</foreign> every morning.
<mentioned xml:lang="fr">Croissant</mentioned> is difficult to
pronounce with your mouth full.
A <term xml:lang="fr">croissant</term> is a crescent-shaped
piece of light, buttery, pastry that is usually eaten for
breakfast, especially in France.

Elements which do not explicitly state the language of their content by means of an xml:lang attribute are understood to inherit a value for it from their parent element. In the general case, therefore, it is recommended practice to supply a default value for xml:lang on the root TEI or text element, as further discussed in section 1.3.1.1.2 Language Indicators

3.3.2.2 Emphatic Words and Phrases
The emph element is provided to mark words or phrases which are linguistically emphatic or stressed. Text which is only typographically ‘emphasized’ falls into the class of highlighted text, and may be tagged with the hi element. In printed works, emphasis is generally indicated by devices such as the use of an italic font, a large typeface, or extra wide letter spacing; in manuscripts and typescripts, it is usually indicated by the use of underlining. As the following examples demonstrate, an encoder may choose whether or not to make explicit the particular type of rendition associated with the emphasis. If a source text consistently renders a particular feature (e.g. emphasis or words in foreign languages) in a particular way, the rendering associated with that feature may be described in the TEI header using the rendition element. The rend, rendition, or style attributes may then be used to describe examples which deviate from the norm. For example, assuming that the TEI header has defined a default rendering for the emph element, the following encoding would use it:
<q>Sex, sir, is <emph>purely</emph> a question
of appetite!</q> Tarr exclaimed.
If on the other hand no such default has been defined for the element, the encoder may specify it informally using the rend attribute:
<q>What it all comes to is this,</q> he said.

<q>
 <emph rend="italic">What does Christopher Robin do in the morning
   nowadays?</emph>
</q>
If the encoder wishes to express information about the rendition used in the source using a formal language such as CSS, then the style attribute can be used in a similar way:
<q>What it all comes to is this,</q> he said.

<q>
 <emph style="font-style: italic">What does Christopher Robin do in
   the morning nowadays?</emph>
</q>
In cases where the rendition of a source needs to be indicated several times in a document, it may be more convenient to provide a default value using the rendition element in the header. If a small number of distinct values are required, it may also be convenient to define them all by means of a series of rendition elements which can then be referenced from the elements in question by means of the global rendition attribute:
<l>Here Thou, great <name rendition="#italic">Anna</name>!
whom three Realms obey,</l>
<l>Doth sometimes Counsel take —
and sometimes <emph rendition="#italic">Tea</emph>.</l>
<!-- in the header ... -->
<rendition xml:id="italic" scheme="css">font-style: italic</rendition>
Further information on the use of the rendition element is provided at 2.3.4 The Tagging Declaration.

The hi element is used to mark words or phrases which are highlighted in some way, but for which identification of the intended distinction is difficult, controversial, or impossible. It enables an encoder simply to record the fact of highlighting, possibly describing it by the use of a rend, style, or rendition attribute, as discussed above, without however taking a position as to the function of the highlighting. This may also be useful if the text is to be processed in two stages: representing simply typographic distinctions during a first pass, and then replacing the hi elements with more specific elements in a second pass.

Some simple examples:
<hi rend="gothic">And this Indenture further witnesseth</hi>
that the said <hi rend="italic">Walter Shandy</hi>, merchant,
in consideration of the said intended marriage ...
In this example, the first highlighted phrase uses black letter or gothic print to mimic the appearance of a legal document, and italic to mark Walter Shandy as a name. In a second pass, the elements head or label might be appropriate for the first use, and the element name for the second.
The heaviest rain, and snow, and hail, and
sleet, could boast of the advantage over him in only one respect. They
often <hi rend="quoted">came down</hi> handsomely, and Scrooge never
did.
In this example, the phrase came down uses inverted commas to indicate a play on words.12 In a second pass, the element soCalled might be preferred as a means of indicating that the narrator is distancing himself from this usage.
3.3.2.3 Other Linguistically Distinct Material

For some kinds of analysis, it may be desirable to encode the linguistic distinctiveness of words and phrases with more delicacy than is allowed by the foreign element. The distinct element is provided for this purpose. Its attributes allow for additional information characterizing the nature of the linguistic distinction to be made in two distinct ways: the type attribute simply assigns a user-defined code of some kind to the word or phrase which assigns it to some register, sub-language, etc. No recommendations as to the set of values for this attribute are provided at this time, as little consensus exists in the field.

Alternatively, the remaining three attributes may be used in combination to place a word or phrase on a three-dimensional scale sometimes used in descriptive linguistics, as for example in Mattheier et al, 1988. The time attribute places a word or phrase diachronically, for example as archaic, old-fashioned, contemporary, futuristic, etc.; the space attribute places a word or phrase diatopically, that is, with respect to a geographical classification, for example as national, regional, international, etc.; the social attribute places a word or phrase diastratically, that is, with respect to a social classification, for example as technical, polite, impolite, restricted, etc. Again, no recommendations are made for the values of these attributes at this time; the encoder should provide a description of the scheme used in the appropriate section of the header (see section 2.3 The Encoding Description).

Examples:
Next morning a boy in that dormitory confided to his
bosom friend, a <distinct type="psSlang">fag</distinct> of
Macrea's, that there was trouble in their midst which
King <distinct type="archaic">would fain</distinct> keep
secret.
Next morning a boy in that dormitory confided to his
bosom friend, a
<distinct time="1900" space="GB"
 social="publicschool">fag</distinct>
of Macrea's, that there was trouble in their midst which
King <distinct time="archaic">would fain</distinct> keep
secret.
Where more complex (or more rigorous) interpretive analyses of the associations of a word are required, the more detailed and general mechanisms described in chapter 18 Feature Structures should be preferred to these simple characterizations. It may also be preferable to record the kinds of analysis suggested here by means of the simple annotation element note described in section 3.9 Notes, Annotation, and Indexing, or the span element described in section 17.3 Spans and Interpretations.

3.3.3 Quotation

One form of presentational variation found particularly frequently in written and printed texts is the use of quotation marks. As with the typographic variations discussed in the preceding section, it is generally helpful to separate the encoding of the underlying textual feature (for example, a quotation or a piece of direct speech) from the encoding of its rendering (for example, the use of a particular style of quotation marks).

This section discusses the following elements, all of which are often rendered by the use of quotation marks:

  • q (인용 부호로 주변 텍스트와 구분됨.) 직접 대화 또는 사고, 전문 용어 또는 은어, 작가의 거리두기, 외부로부터의 인용문, 그리고 사용되지 않고 언급된 단락 등의 이유로, 그리고 그 밖의 다른 이유로, 주변 텍스트와 어떤 방식으로든 차이가 있다고 (명시적으로) 표시된 부분을 포함한다.
  • said (대화 또는 사고) 원본에 명시적으로 표시되었든지 않았든지, 직접적으로 또는 간접적으로 보고되었든지 않았든지, 그리고 실제 인물 또는 가공의 인물에 의해 생성되었는지 간에, 생각 혹은 소리 내어 말한 단락을 표시한다.
    direct인용부가 직접 대화로 또는 간접 대화로 간주할 수 있는지를 표시할 때 사용할 수 있다.
    aloud인용부가 발화된 것으로 또는 신호된 것으로 볼 수 있는지를 표시할 때 사용할 수 있다.
  • quote (인용) 해설자 또는 저자에 의해, 텍스트의 외부 주체에 의해 생성된 것이라 밝혀진 구 또는 단락을 포함한다.
  • att.global.source provides an attribute used by elements to point to an external source.
    sourcespecifies the source from which some aspect of this element is drawn.
  • cit (참조 인용) 원문 참고문헌과 함께 제시된 다른 문서로부터의 인용을 포함한다. 사전에서는 기술된 의미로 사용된 어형이 들어간 용례, 또는 표제어의 번역어 또는 예문을 포함할 수 있다.
  • mentioned marks words or phrases mentioned, not used.
  • soCalled (so called) contains a word or phrase for which the author or narrator indicates a disclaiming of responsibility, for example by the use of scare quotes or italics.

The elements mentioned and soCalled are members of the class model.emphLike while q stems from model.hiLike; the element said is a member of the class model.attributable in its own right, while cit and quote are members of model.quoteLike, a subclass of model.attributable. This class is a subclass of model.inter; hence all of these elements are permitted both within and between paragraph-level elements.

The most common and important use of quotation marks is, of course, to mark quotation, by which we mean simply any part of the text which the author or narrator wishes to attribute to some agency other than the narrative voice. The q element may be used if no further distinction beyond this is judged necessary. If it is felt necessary to distinguish such passages further, for example to indicate whether they are regarded as speech, writing, or thought, either the type attribute or one of the more specialized elements discussed in this section may be used. For example, the element quote may be used for written passages cited from other works, or the element said for words or phrases represented as being spoken or thought by people or characters within the current work. The soCalled element is used for cases where the author or narrator distances him or herself from the words in question without however attributing them to any other voice in particular. The mentioned element is appropriate for a case where a word or phrase is being discussed in the body of a text rather than forming part of the text directly.

As noted above, if the distinction among these various reasons why a passage is offset from surrounding text cannot be made reliably, or is not of interest, then any representation of speech, thought, or writing may simply be marked using the q element.

Quotation may be indicated in a printed source by changes in type face, by special punctuation marks (single or double or angled quotes, dashes, etc.) and by layout (indented paragraphs, etc.), or it may not be explicitly represented at all. If these characteristics are of interest, one or other of the global rend or rendition attributes discussed in section 1.3.1.1 Global Attributes may be used to record them.

Quotation marks themselves may, like other punctuation marks, be felt for some purposes to be worth retaining within a text, quite independently of their description by the rend attribute. This should generally be done using the appropriate Unicode character, or, if this is not possible, a numeric character reference (see Character References). If the encoder decides both to retain the quotation marks and to represent their function by means of an explicit tag such as quote, the quotation marks should be included within the element, rather than outside it, as in the first example below:
Adolphe se tourna vers lui :
<said>— Alors, Albert, quoi de neuf?</said>
<said>— Pas grand-chose.</said>
<said>— Il fait beau,</said> dit Robert.
Alternatively, since this use of the leading mdash is very common typographic practice, it may be considered unnecessary to retain it in the encoding. Its presence in the source might instead be signalled using one of the attributes rend, style, or rendition. This kind of rendering might be predefined using a rendition element, which can then be referenced using the rendition attribute as follows:
Adolphe se tourna vers lui :
<said rendition="#dashBefore">Alors,
Albert, quoi de neuf ?</said>
<said rendition="#dashBefore">Pas grand-chose.</said>
<said rendition="#dashBefore">Il fait beau,</said>
dit Robert.

<!-- ... within the header -->
<rendition xml:id="dashBefore"
 scope="before">content: '— '</rendition>
<!-- ... -->
<quotation marks="none"/>

Whatever policy is adopted, the encoder should document the decision in some way, for example by using the quotation element provided in the TEI header (see 2.3.3 The Editorial Practices Declaration) to indicate that quotation marks have not been retained in the encoding; their presence in the source is implied by the rendition attribute values supplied.

Whether or not the quotation marks are suppressed, their presence and nature may be described using some appropriate set of conventions in the rend attribute. These conventions may be entirely idiosyncratic, and hence not necessarily useful for interchange, as in the following example:
<said rend="pre(‘) post(’)">Who-e debel
you?</said> — he at last said —
<said rend="pre(‘) post(’)">you no speak-e,
damme, I kill-e.</said> And so saying,
the lighted tomahawk began flourishing
about me in the dark.
Such passages might more effectively be encoded without loss of rendering information by using the rendition attribute and its associated rendition element as described in section 2.3.4.1 Rendition. If the rendition of passages tagged as said is generally uniform throughout a text, then the rendition element may used to specify a default rendering, in which case the same section might simply be tagged:
<said>Who-e debel
you?</said> — he at last said —
<said>you no speak-e,
damme, I kill-e.</said> And so saying,
the lighted tomahawk began flourishing
about me in the dark.

<!-- in the header: -->
<tagsDecl partial="true">
 <rendition scheme="css" selector="said"
  scope="before">content:"‘";</rendition>
 <rendition scheme="css" selector="said"
  scope="after">content:"’";</rendition>
</tagsDecl>
As members of the att.ascribed.directed class, elements said and q share the following attributes:
  • att.ascribed 특정 개인의 대화 또는 행위를 표시하는 요소에 대한 속성을 제공한다.
    who요소 내용이 속하는 사람 또는 사람의 그룹을 나타낸다.
  • att.ascribed.directed provides attributes for elements representing speech or action that can be directed at a group or individual.
    toWhomindicates the person, or group of people, to whom a speech act or action is directed.
These may be used to make explicit who is speaking and who is being spoken to:
Adolphe se tourna vers lui :
<said who="#Ado" toWhom="#Alb">— Alors, Albert, quoi de neuf?</said>
<said who="#Alb" toWhom="#Ado">— Pas grand-chose.</said>
<said who="#Rob">— Il fait beau,</said> dit Robert.

<!-- ... elsewhere in the document -->
<standOff>
 <listPerson type="speakers">
  <person xml:id="Ado">
   <persName>Adolphe</persName>
  </person>
  <person xml:id="Alb">
   <persName>Albert</persName>
  </person>
  <person xml:id="Rob">
   <persName>Robert</persName>
  </person>
 </listPerson>
</standOff>
The who attribute may be supplied whether or not an indication of the speaker is given explicitly in the text. Likewise, the toWhom attribute may be supplied to indicate the encoder's interpretation of the intended recipient of the speech. They may take the form (as above) of an abbreviated or normalized form of the speaker's name, but the role of these attributes is to act as a pointer to a location elsewhere in the text, or another document, where data about each party may be supplied. While these attributes could point to any source of information about the parties involved, the most appropriate place for such information is within the participant description component of the TEI header, as further discussed in 15.2.2 The Participant Description but for simple cases like the above, a simple list of speakers located in the front or back matter of the text may suffice.
It may also be useful to distinguish representations of speech from representations of thought, in modern printed texts often indicated by a change of typeface. The aloud attribute is provided for this purpose, as in this example:
<said aloud="true">Oh yes,</said> said Henry,
<said aloud="false">I mean
Gordon Macrae, for example…</said>
<said aloud="false">Jungian
Analyst with Winebox! That's what you called him, you callous bastard,
didn't you? Eh? Eh?</said>
Quoted matter may be embedded within quoted matter, as when one speaker reports the speech of another:
<said who="#Wilson">Spaulding, he came down into the office just this day
eight weeks with this very paper in his hand, and he says:—
<said who="#WilsonSpaulding">I wish to the Lord, Mr. Wilson, that I was a
   red-headed man.</said>
</said>
<!-- ... -->
<list type="speakers">
 <item xml:id="Wilson">Wilson</item>
 <item xml:id="WilsonSpaulding">Spaulding reported by Wilson</item>
<!-- ...-->
</list>
Direct speech nested in this way is treated in the same way as elsewhere: a change of rendition may occur, but the same element should be used. An encoder may however choose to distinguish between direct speech which contains quotations from extra-textual matter and direct speech itself, as in the following example:
<p>
 <said>The Lord! The Lord! It is Sakya Muni himself,</said> the lama half
sobbed; and under his breath began the wonderful Buddhist
invocation:-<said>
  <quote>
   <l>To Him the Way — the Law — Apart —</l>
   <l>Whom Maya held beneath her heart</l>
   <l>Ananda's Lord — the Bodhisat</l>
  </quote>
   And He is here! The Most Excellent Law is here also. My
   pilgrimage is well begun. And what work! What work!</said>
</p>
Quotations from other works are often accompanied by a reference to their source. The cit element may be used to group together the quotation and its associated bibliographic reference, which should be encoded using the elements for bibliographic references discussed in section 3.12 Bibliographic Citations and References, as in the following example.
<div xml:id="mm01" type="chapter">
 <head>Chapter 1</head>
 <epigraph>
  <cit>
   <quote>
    <l>Since I can do no good because a woman</l>
    <l>Reach constantly at something that is near it.</l>
   </quote>
   <bibl>
    <title>The Maid's Tragedy</title>
    <author>Beaumont and Fletcher</author>
   </bibl>
  </cit>
 </epigraph>
 <p>Miss Brooke had that kind of beauty which seems to be thrown into
   relief by poor dress...</p>
</div>
Like other bibliographic references, the citation associated with a quotation may be represented simply by a cross-reference, as in this example:
Lexicography has shown little sign of being affected by the
work of followers of J.R. Firth, probably best summarized
in his slogan, <cit>
 <quote>You shall know a word by the company it keeps.</quote>
 <ref>(Firth, 1957)</ref>
</cit>
It is also common for quotations to be separated from their bibliographic reference by intervening text, which makes the use of cit impractical. In such circumstances, the quotation can be linked to a bibliographical reference using source:
<bibl xml:id="tlk_36">Tolkien (1936)</bibl> tells us that
<quote source="#tlk_36">
 <title>Beowulf</title> is in fact so interesting as
poetry, in places poetry so powerful, that this quite
overshadows the historical content
</quote>.
source could also be used to point to a complete external bibliographic reference in a listBibl elsewhere in the document, or external to it.

Unlike most of the other elements discussed in this chapter, direct speech and quotations may frequently contain other high-level elements such as paragraphs or verse lines, as well as being themselves contained by such elements. Three possible solutions exist for this well-known structural problem:

  • the quotation is broken into segments, each of which is entirely contained within a paragraph
  • the quotation is marked up using stand-off markup
  • the quotation boundaries are represented by empty segment boundary delimiter elements

For further discussion and several examples, see chapter 20 Non-hierarchical Structures.

Finally, in this section, the element soCalled is provided for all cases in which quotation marks are used to distance the quoted text from the narrator or speaker. Common examples include the ‘scare’ quotes often found in newspaper headlines and advertising copy, where the effect is to cast doubts on the veracity of an assertion:
<head>PM dodges <soCalled>election threat</soCalled> in interview</head>
The same element should be used to mark a variety of special ironic usages. Some further examples follow:
He hated <soCalled>good</soCalled> books.
<soCalled>Croissants</soCalled> indeed! toast not good enough for you?
Although Chomsky's decision that all NL
sentences are finite objects was never justified by arguments from
the attested properties of NLs, it did have a certain
<soCalled>social</soCalled> justification. It was commonly assumed in
works on logic until fairly recently that the notion
<mentioned>language</mentioned> is necessarily restricted to finite
strings.

3.4 Terms and Glosses, Ruby Annotations, and Equivalents and Descriptions

This section describes a set of textual elements which are used to provide a gloss, alternate identification, or description of something.

3.4.1 Terms and Glosses

Technical terms are often italicized or emboldened upon first mention in printed texts; an explanation or gloss is sometimes given in quotation marks. Linguistic analyses conventionally cite words in languages under discussion in italics, providing a gloss immediately following marked with single quotation marks. Other texts in which individual words or phrases are mentioned (for example, as examples) rather than used may mark them either with italics or with quotation marks, and will gloss them less regularly.

  • term (term) 전문용어로 간주되는 단일어, 복합어, 기호적 명칭을 포함한다.
  • gloss (gloss) 다른 단어나 구에 대한 해설 또는 정의를 제공할 때 사용되는 구나 단어를 표시한다.

These elements are also members of the class model.emphLike.

A term may appear with or without a gloss, as may a mentioned element. Where the gloss is present, it may be linked to the term it is glossing by means of its target attribute. To establish such a link, the encoder should give an xml:id value to the term or mentioned element and provide that value, prefixed by a sharp sign, as the value of the target attribute on the gloss element. For example:
We may define <term xml:id="TDPv" rend="sc">discoursal point of view</term>
as
<gloss target="#TDPv">the relationship, expressed through discourse
structure, between the implied author or some other addresser,
and the fiction.</gloss>
<gloss rend="unmarked" target="#PRSR">A computational device that infers
structure from grammatical strings of words</gloss> is known as a
<term xml:id="PRSR">parser</term>, and much of the history of NLP over the
last 20 years has been occupied with the design of parsers.
In the absence of a gloss in the source text, a term can also be associated with a gloss or definition by means of its ref attribute, as in this imaginary example:
We discuss Leech's concept of <term ref="#TDPV2" rend="sc">discoursal point of view</term> below.
Here, the value #TDPV2 references some other XML element in the same document. This might be, for example, an entry in a list of technical vocabulary given in the document header, or in an appendix. This attribute could also reference an entry in some centrally maintained terminological database, perhaps using one of the pointing mechanisms discussed in section 16.2 Pointing Mechanisms.
Note that the element term is intended for use with words or phrases identified as terminological in nature; where words or phrases are simply being cited, discussed, or glossed in a text, it will often be more appropriate to use the mentioned element, as in the following example:
There is thus a striking accentual difference between a verbal
form like <mentioned xml:id="cw234" xml:lang="grc">eluthemen</mentioned>
<gloss target="#cw234">we were released,</gloss> accented on the
second syllable of the word, and its participial derivative

<mentioned xml:id="cw235" xml:lang="grc">lutheis</mentioned>
<gloss target="#cw235">released,</gloss> accented on the last.

For technical terminology in particular, and generally in terminological studies, it may be useful to associate an instance of a term within a text with a canonical definition for it, which is stored either elsewhere in the same text (for example in a glossary of terms) or externally, for example in a database, authority file, or published standard. The attributes key and ref discussed in section 3.6.1 Referring Strings below are available on the term element for this purpose.

3.4.1.1 Some Further Examples
As a simple example of the elements discussed here and in 3.3 Highlighting and Quotation, consider the following sentence:
On the one hand the Nibelungenlied is associated with the new rise of romance of twelfth-century France, the romans d'antiquité, the romances of Chrétien de Troyes, and the German adaptations of these works by Heinrich van Veldeke, Hartmann von Aue, and Wolfram von Eschenbach.
A first approximation to the encoding of this sentence might be simply to record the fact that the phrases printed above in italics are highlighted, as follows:
On the one hand the <hi rend="italic">Nibelungenlied</hi> is
associated with the new rise of romance of twelfth-century France,
the <hi xml:lang="fr" rend="italic">romans d'antiquité</hi>,
the romances of Chrétien de Troyes, ...
This encoding would, however, lose the important distinction between an italicized title and an italicized foreign phrase. Many other phrases might also be italicized in the text, and a retrieval program seeking to identify foreign terms (for example) would not be able to produce reliable results by simply looking for italicized words. Where economic and intellectual constraints permit, therefore, it would be preferable to encode both the function of the highlighted phrases and their appearance, as follows:
On the one hand the <title rend="italic">Nibelungenlied</title>
is associated with the new rise of romance of twelfth-century France,
the <foreign rend="italic">romans d'antiquité</foreign>, the
romances of Chrétien de Troyes, ...

In this example, the decision as to which textual features are distinguished by the highlighting is relatively uncontroversial. As a less straightforward example, consider the use of italic font in the following passage:

A pretty common case, I believe; in all vehement debatings. She says I am too witty; Anglicé, too pert; I, that she is too wise; that is to say, being likewise put into English, not so young as she has been: in short, she is grown so much into a mother, that she had forgotten she ever was a daughter. ...

Clearly, the word vehement is not italicized for the same reason as the phrase not so young as she has been; the former is emphasized, while the latter is proverbial. It also provides an ironic gloss for the words too wise, in the same way as too pert glosses too witty. The glossed phrases are not, however, technical terms or cited words, but quoted phrases, as if the writer were putting words into her own and her mother's mouths. Finally, the words mother and daughter are apparently italicized simply to oppose them in the sentence; certainly they do not fit into any of the categories so far proposed as reasons for italicizing. Note also that the word Anglicé is not italicized although it is not generally considered an English word.

The following sample encoding for the above passage attempts to take into account all the above points:
A pretty common case, I believe; in all <emph>vehement</emph>
debatings. She says I am <q rend="italic">too witty</q>;
<foreign xml:lang="la" rend="roman">Anglicé</foreign>,
<gloss rend="italic">too pert</gloss>; I, that she is
<q rend="italic"> too wise</q>; that is to say, being likewise
put into English, <gloss rend="italic">not so young as she has
been</gloss>: in short, she is grown so much into a
<hi rend="italic">mother</hi>, that she had forgotten she ever
was a <hi rend="italic">daughter</hi>.

3.4.2 Ruby Annotations

The word ruby (or rubi) refers to a particular method of glossing runs of text which is common in East Asian scripts. In horizontally-oriented text, ruby annotations typically appear above the text being glossed, while in vertical runs of text they may appear to the left or right, or both, also oriented vertically. An English example of a ruby annotation might look like this:

In Japanese, furigana (振り仮名) ruby annotations are often used to provide pronunciation guidance for readers; characters from the largely phonetic hiragana or katakana syllabaries accompany Chinese characters, like this:

The first line of a news story from NHK News Web Easy intended for Japanese learners, in which every word composed of Chinese characters has a ruby gloss.
그림 3.1. The first line of a news story from NHK News Web Easy intended for Japanese learners, in which every word composed of Chinese characters has a ruby gloss.

Pinyin ruby annotations are also used in Chinese to provide pronunciation guidance, and Zhuyin (注音) phonetic symbols (commonly known as bopomofo) are used in Taiwan for the same purpose.

The TEI schema provides many different ways of encoding glosses and annotations, from the simple and flexible note element to a native implementation of the Web Annotation Data Model (16.11 Annotations). However, ruby is a particular, distinct, and widely-used form of annotation that appears in script, print, calligraphy, and web pages, and the TEI therefore provides specific elements for it:

  • ruby (ruby container) contains a passage of base text along with its associated ruby gloss(es).
  • rb (ruby base) contains the base text annotated by a ruby gloss.
  • rt (ruby text) contains a ruby text, an annotation closely associated with a passage of the main text.

The rt element is a member of att.placement, and thus the place attribute may be used to indicate where the ruby gloss is with respect to the base text:

  • att.placement 원본 페이지 또는 대상에서 텍스트 요소가 나타나는 위치를 기술하기 위한 속성을 제공한다.
    placespecifies where this item is placed. 제안값은 다음을 포함한다: 1] top; 2] bottom; 3] margin; 4] opposite; 5] overleaf; 6] above; 7] right; 8] below; 9] left; 10] end; 11] inline; 12] inspace

The most relevant suggested values of place for ruby text are above, below, left, and right.

In its simplest representation, a glossed form consists of an rb (ruby base) element containing the base form, an rt (ruby text) element containing the gloss, and a ruby element which wraps them together:
<p xml:lang="ja">
<!--...-->
 <ruby>
  <rb>大学</rb>
  <rt place="above">だいがく</rt>
 </ruby>
<!--...-->
</p>
In the example above, the word 大学 (daigaku = university) is provided with a phonation gloss in hiragana. The full gloss is applied to the complete word. However, it might instead be broken down by character:
<p xml:lang="ja">
<!--...-->
 <ruby>
  <rb>大</rb>
  <rt place="above">だい</rt>
 </ruby>
 <ruby>
  <rb>学</rb>
  <rt place="above">がく</rt>
 </ruby>
<!--...-->
</p>
Here is a similar example from Taiwan using bopomofo (pinyin píngzi = bottle)13:
<p xml:lang="zh-TW">
<!--...-->
 <ruby>
  <rb>瓶</rb>
  <rt place="right">ㄆㄧㄥˊ</rt>
 </ruby>
 <ruby>
  <rb>子</rb>
  <rt place="right">˙ㄗ</rt>
 </ruby>
<!--...-->
</p>
Where place is not provided, the default assumption is that the ruby gloss is above where the text is horizontal, and to the right of the text where it is vertical. See 5.6 Writing Modes for a detailed guide to writing modes and text directionality.
The same ruby base may be accompanied by more than one gloss. Here, the Japanese word 打球場 (dakyūba, or billiard hall) is glossed with two different pronunciations: ‘biriādo’ (its English equivalent) and ‘dakyū’, a phonation guide for the first two characters.
그림 3.2. Billiard hall with two ruby glosses. 国文学研究資料館所蔵：：英国／龍動新繁昌記.
with two ruby glosses. .
This example is intriguing in that the right-side ruby glosses apply to the first and second characters respectively, but the left-side gloss applies to the whole word as a unit. We use this instance to exemplify multiple approaches to encoding the same phenomena, which may be appropriate for different projects or editorial preferences. First, using the same segmentation approach as demonstrated for 大学 above, but with nesting:
<p style="writing-mode: vertical-rl"
 xml:lang="ja">
<!--...-->
 <ruby>
  <rb>
   <ruby>
    <rb>打</rb>
    <rt place="right">ダ</rt>
   </ruby>
   <ruby>
    <rb>球</rb>
    <rt place="right">キウ</rt>
   </ruby>
     場
  </rb>
  <rt place="left">ビリヤード</rt>
 </ruby>
<!--...-->
</p>
We could also use a standoff approach with anchor elements and pointers:
<p style="writing-mode: vertical-rl"
 xml:lang="ja">
<!--...-->
 <ruby>
  <rb>
   <anchor xml:id="da"/>打
  <anchor xml:id="kyuu"/>球
  <anchor xml:id="ba"/>場
  <anchor xml:id="owari"/>
  </rb>
  <rt place="left" from="#da" to="#owari">ビリヤード</rt>
  <rt place="right" from="#da" to="#kyuu">ダ</rt>
  <rt place="right" from="#kyuu" to="#ba">キウ</rt>
 </ruby>
<!--...-->
</p>
Alternatively, if the encoding itself already includes segmentation below the word level, we can use the existing elements instead of adding anchors:
<p style="writing-mode: vertical-rl"
 xml:lang="ja">
<!--...-->
 <ruby>
  <rb xml:id="dakyuuba">
   <c xml:id="chr1">打</c>
   <c xml:id="chr2">球</c>
   <c>場</c>
  </rb>
  <rt place="left" target="#dakyuuba">ビリヤード</rt>
  <rt place="right" target="#chr1">ダ</rt>
  <rt place="right" target="#chr2">キウ</rt>
 </ruby>
<!--...-->
</p>

The current support for ruby is rudimentary, and in future releases of the Guidelines we expect to see more development of these features and recommendations.

3.4.3 Equivalents and Descriptions

Another group of elements is used to supply different kinds of names for objects described by the TEI. Examples of this are documentation of elements, attributes, classes (and also attribute values where appropriate), and description of glyphs.

  • altIdent (교체 확인소) 어떤 언어에서 요소, 부류, 속성에 대해 권고된 XML 이름을 제시한다.
  • desc (기술) 요소, 속성, 또는 속성 값의 목적과 적용에 대한 간단한 기술을 포함한다.
  • equiv (동치) 부모 요소와 동치로 고려되는 성분을 공지시 또는 외부 연결을 통해 명시한다.
    uri(표준 자원 확인소(URL)) 부모가 외부 확인소를 통해서 표상하는 기저 개념을 지시한다.
    filter이 요소의 실례를 표준 TEI로 변환하는 방법을 포함하는 외부 스크립트를 참조한다.
    name부모가 표상하는 기저 개념에 대한 이름을 부여한다.
    predicate [att.predicate]the condition under which the element bearing this attribute applies, given as an XPath predicate expression.

Along with the gloss element mentioned above, these elements constitute the model.glossLike class. They are described in more detail in 22.4.1 Description of Components.

3.5 Simple Editorial Changes

As in editing a printed text, so in encoding a text in electronic form, it may be necessary to accommodate editorial comment on the text and to render account of any changes made to the text in preparing it. The tags described in this section may be used to record such editorial interventions, whether made by the encoder, by the editor of a printed edition used as a copy text, by earlier editors, or by the copyists of manuscripts.

The tags described here handle most common types of editorial intervention and stereotyped comment; where less structured commentary of other types is to be included, it may be marked using the note element described in section 3.9 Notes, Annotation, and Indexing. Systematic interpretive annotation is also possible using the various methods described in chapter 16 Linking, Segmentation, and Alignment. The examples given here illustrate only simple cases of editorial intervention; in particular, they permit economical encoding of a simple set of alternative readings of a short span of text. To encode multiple views of large or heterogeneous spans of text, the mechanisms described in chapter 16 Linking, Segmentation, and Alignment should be used. To encode multiple witnesses of a particular text, a similar mechanism designed specifically for critical editions is described in chapter 12 Critical Apparatus.

For most of the elements discussed here, some encoders may wish to indicate both a responsibility, that is, a code indicating the person or agency responsible for making the editorial intervention in question, and also an indication of the degree of certainty which the encoder wishes to associate with the intervention. These requirements are served by the att.global.responsibility class, along with att.global.source and att.dimensions. Any of the elements discussed here thus may potentially carry any of the following optional attributes:

  • att.global.responsibility provides attributes indicating the agent responsible for some aspect of the text, the markup or something asserted by the markup, and the degree of certainty associated with it.
    cert(확실성) 간섭 또는 해석과 연관된 확실성의 정도를 나타낸다.
    resp(책임 당사자) 편집자 또는 전사자와 같이 또는 해석에 대한 책임이 있는 대리인을 나타낸다.
  • att.global.source provides an attribute used by elements to point to an external source.
    sourcespecifies the source from which some aspect of this element is drawn.
  • att.editLike 어떤 유형의 부호화된 학문적 간섭 또는 해석의 특성을 기술하는 속성을 제공한다.
    evidence간섭 또는 해석의 신뢰성 또는 정확성을 지지하는 증거의 특성을 나타낸다. 제안값은 다음을 포함한다: 1] internal; 2] external; 3] conjecture
  • att.dimensions 물리적 대상의 크기를 기술하는 속성을 제공한다.
    unit측정 단위의 이름을 기술한다. 제안값은 다음을 포함한다: 1] cm (centimetres); 2] mm (millimetres); 3] in (inches); 4] line; 5] char (characters)
    quantity명시된 단위의 길이를 명시한다.
    extentindicates the size of the object concerned using a project-specific vocabulary combining quantity and units in a single string of words.
    precisioncharacterizes the precision of the values specified by the other attributes.
    scope측정의 적용가능성을 명시하며, 하나 이상의 대상이 측정된다. 샘플 값은 다음을 포함한다 Sample values include: 1] all; 2] most; 3] range

Many of the elements discussed here can be used in two ways. Their primary purpose is to indicate that the text encoded as the element's content represents an editorial intervention (or non-intervention) of a specific kind, indicated by the element itself. However, pairs or other meaningful groupings of such elements can also be supplied, wrapped within a special purpose choice element:

  • choice (choice) 텍스트 동일 지점에서 대체 가능한 부호화를 모아 놓는다.

This element enables the encoder to represent for example a text in its ‘original’ uncorrected and unaltered form, alongside the same text in one or more ‘edited’ forms. This usage permits software to switch automatically between one ‘view’ of a text and another, so that (for example) a stylesheet may be set to display either the text in its original form or after the application of editorial interventions of particular kinds.

Elements which can be combined in this way constitute the model.choicePart class. The default members of this class are sic, corr, reg, orig, unclear, supplied, abbr, expan, ex, am and seg; some of their functions and usage are described further below.

Three categories of editorial intervention are discussed in this section:

  • indication or correction of apparent errors
  • indication or regularization of variant, irregular, non-standard, or eccentric forms
  • editorial additions, suppressions, and omissions

A more extended treatment of the use of these tags in transcriptional and editorial work is given in chapter 11 Representation of Primary Sources.

3.5.1 Apparent Errors

When the copy text is manifestly faulty, an encoder or transcriber may elect simply to correct it without comment, although for scholarly purposes it will often be more generally useful to record both the correction and the original state of the text. The elements described here enable all three approaches, and allows the last to be done in such a way as make it easy for software to present either the original or the correction.

  • sic (Latin for thus or so) contains text reproduced although apparently incorrect or inaccurate.
  • corr (정정) 복사된 텍스트에서 오류로 보이는 단락의 정정 형식을 포함한다.

The following examples show alternative treatment of the same material. The copy text reads:

Another property of computer-assisted historical research is that data modelling must permit any one textual feature or part of a textual feature to be a part of more than one information model and to allow the researcher to draw on several such models simultaneously, for example, to select from a machine-readable text those marginal comments which indicate that the date's mentioned in the main body of the text are incorrect.
An encoder may choose to correct the typographic error, either silently or with an indication that a correction has been made, as follows:
… marginal comments which indicate that the <corr>dates</corr>
mentioned in the main body of the text are incorrect.
Alternatively, the encoder may simply record the typographic error without correcting it, either without comment or with a sic element to indicate the error is not a transcription error in the encoding:
… marginal comments which indicate that the <sic>date's</sic>
mentioned in the main body of the text are incorrect.
If the encoder elects both to record the original source text and to provide a correction for the sake of word-search and other programs, both sic and corr are used, wrapped in a choice:
… marginal comments which indicate that the
<choice>
 <corr>dates</corr>
 <sic>date's</sic>
</choice> mentioned in the main body of the text are
incorrect.
The sic and corr elements can appear in either order.
If it is desired to indicate the person or edition responsible for the emendation, this might be done as follows:
… marginal comments which indicate that the
<choice>
 <corr resp="#msm">dates</corr>
 <sic>date's</sic>
</choice> mentioned in the main body of the text are
incorrect.

<!-- within the header for this document ... -->
<respStmt xml:id="msm">
 <resp>editor</resp>
 <name>C.M. Sperberg-McQueen</name>
</respStmt>
Here the resp attribute has been used to indicate responsibility for the correction. Its value (#msm) is an example of the pointer values discussed in section 3.7 Simple Links and Cross-References; in this case, it points to a respStmt element within the TEI header, but any element might be indicated in this way, including for example a name element, or (if the module described in 13 Names, Dates, People, and Places has been included) a person element. The resp attribute is available for all elements which are members of the att.global.responsibility class. The same class makes available a cert attribute, which may be used to indicate the degree of editorial confidence in a particular correction, as in the following example:
An <choice>
 <corr cert="high">Autumn</corr>
 <sic>Antony</sic>
</choice> it was,
That grew the more by reaping
See further the discussion in section 11.3.1.3 Correction and Conjecture.

Where, as here, the correction takes the form of adding text not otherwise present in the text being encoded, the encoder should use the corr element. Where the correction is present in the text being encoded, and consists of some combination of visible additions and deletions, the elements add or del should be used: see further section 3.5.3 Additions, Deletions, and Omissions below. Where the correction takes the form of addition of material not present in the original because of physical damage or illegibility, the supplied element may be used. Where the ‘correction’ is simply a matter of expanding an abbreviation the ex element may be used. These and other elements to support the detailed encoding of authorial or scribal interventions of this kind are all provided by the module described in chapter 11 Representation of Primary Sources.

3.5.2 Regularization and Normalization

When the source text makes extensive use of variant forms or non-standard spellings, it may be desirable for a number of reasons to regularize it: that is, to provide ‘standard’ or ‘regularized’ forms equivalent to the non-standard forms.14

As with other such changes to the copy text, the changes may be made silently (in which case the TEI header should specify the types of silent changes made) or may be explicitly marked using the following elements:

  • reg (정규화) 어떤 면에서 정규화 또는 표준화된 해석을 포함한다.
  • orig (원형식) 표준화 또는 수정된 것이 아닌 원형식을 따르는 해석을 포함한다.
  • choice (choice) 텍스트 동일 지점에서 대체 가능한 부호화를 모아 놓는다.

Typical applications for these elements include the production of editions intended for student or lay readers, linguistic research in which spelling or usage variation is not the main question at issue, production of spelling dictionaries, etc.

Consider this 16th-century text:

how godly a dede it is to overthrowe so wicked a race the world may judge: for my part I thinke there canot be a greater sacryfice to God.
An encoder may choose to preserve the original spelling of this text, but simply flag it as nonstandard by using the orig element with no attributes specified, as follows:
<p>...how godly a <orig>dede</orig> it is to
<orig>overthrowe</orig> so wicked a race the
world may judge: for my part I <orig>thinke</orig>
there <orig>canot</orig> be a greater
<orig>sacryfice</orig> to God</p>
Alternatively, the encoder may simply indicate that certain words have been modernized by using the reg element with no attributes specified, as follows:
<p>...how godly a
<reg>deed</reg> it is to <reg>overthrow</reg> so wicked a race the
world may judge: for my part I <reg>think</reg>
there <reg>cannot</reg> be a greater
<reg>sacrifice</reg> to God.</p>
Alternatively, the encoder may elect to record both old and new spellings, so that (for example) the same electronic text may serve as the basis of an old- or new-spelling edition:
<p>...how godly a <choice>
  <orig>dede</orig>
  <reg>deed</reg>
 </choice> it is to
<choice>
  <orig>overthrowe</orig>
  <reg>overthrow</reg>
 </choice> so wicked a race the
world may judge: for my part I <choice>
  <orig>thinke</orig>
  <reg>think</reg>
 </choice>
there <choice>
  <orig>canot</orig>
  <reg>cannot</reg>
 </choice> be a greater
<choice>
  <orig>sacryfice</orig>
  <reg>sacrifice</reg>
 </choice> to God.</p>

As elsewhere, the resp attribute may be used to specify the agency responsible for the regularization.

3.5.3 Additions, Deletions, and Omissions

The following elements are used to indicate when words or phrases have been omitted from, added to, or marked for deletion from, a text. Like the other editorial elements, they allow for a wide range of editorial practices:

  • gap (gap) 텍스트 선정 시 TEI 헤더에 기술된 편집 기준 때문에, 또는 읽고 듣기 어렵기 때문에 사본에서 누락된 지점을 가리킨다.
    reason(reason) 누락의 이유를 제시한다. 그 값의 예들은 다음과 같다: sampling, illegible, inaudible, irrelevant, cancelled, cancelled and illegible 제안값은 다음을 포함한다: 1] cancelled (cancelled); 2] deleted (deleted); 3] editorial (editorial); 4] illegible (illegible); 5] inaudible (inaudible); 6] irrelevant (irrelevant); 7] sampling (sampling)
  • unclear (unclear) 원본에서 읽거나 듣기 어려워서 분명하게 전사할 수 없는 단어, 구, 단락들을 포함한다.
    reason전사하기 어려운 이유를 표시한다. 제안값은 다음을 포함한다: 1] illegible (illegible); 2] inaudible (inaudible); 3] faded (faded); 4] background_noise (background_noise); 5] eccentric_ductus (eccentric_ductus)
  • add (삽입, 첨가) 저자, 전사자, 부호화 작업자 또는 수정작업자에 의해 텍스트에 삽입된 문자, 단어, 또는 구를 포함한다.
  • del (삭제) 삭제된 것으로 표시되었거나, 저자, 전사자, 부호화자 또는 수정작업자에 의해 사본 텍스트에서 불필요하거나 위조된 것으로 표시되어 삭제된 문자, 단어, 단락을 포함한다.
Encoders may choose to omit parts of the copy text for reasons ranging from illegibility of the source or impossibility of transcribing it, to editorial policy, e.g. a systematic exclusion of poetry or prose from an encoding. The full details of the policy decisions concerned should be documented in the TEI header (see section 2.3 The Encoding Description). Each place in the text at which omission has taken place should be marked with a gap element, with optionally further information about the reason for the omission, its extent, and the person or agency responsible for it, as in the following examples:
<gap reason="illegible" unit="word"
 quantity="2"/>
<gap reason="overwriting illegible"
 extent="several characters"/>
Note that the extent of the gap may be marked precisely using attributes unit and quantity, or more descriptively using the extent attribute. Other, more detailed, options are also available for representing dimensions of any kind; see further 10.3.4 Dimensions.
The desc element may be used to supply a description of the material omitted, where that is considered useful:
<gap reason="sampling" quantity="120"
 unit="lines">
 <desc>irrelevant commentary</desc>
</gap>
… Their arrangement with respect to Jupiter and to each other was as follows:
<gap reason="sampling" extent="restOfPage">
 <desc>astrological figure</desc>
</gap>
That is, there were two stars on the easterly side and one to the
west; …

The add and del elements may be used to record where words or phrases have been added or deleted in the copy text. They are not appropriate where longer passages have been added or deleted, which span several elements; for these, the elements addSpan and delSpan described in chapter 11.3.1.4 Additions and Deletions should be used.

Additions to a text may be recorded for a number of reasons. Sometimes they are marked in a distinctive way in the source text, for example by brackets or insertion above the line (supralinear insertion), as in the following example, taken from a 19th century manuscript:
The story I am going to relate is true as to its main facts,
and as to the consequences <add place="above">of
these facts</add> from which this tale takes its title.

The add element should not be used to mark editorial changes, such as supplying a word omitted by mistake from the source text or a passage present in another version. In these cases, either the corr or supplied tags should be used, as discussed above in section 3.5.1 Apparent Errors, and in section 11.3.1.3 Correction and Conjecture, respectively.

The unclear element is used to mark passages in the original which cannot be read with confidence, or about which the transcriber is uncertain for other reasons, as for example when transcribing a partially inaudible or illegible source. Its reason and resp attributes are used, as with the gap element, to indicate the cause of uncertainty and the person responsible for the conjectured reading.

For example:
<l>And where the sandy mountain Fenwick scald</l>
<l>
 <unclear reason="ink blot">The</unclear> sea between
yet hence his pray'r prevail'd
</l>
or from a spoken text:
<p>... and then <unclear reason="passingTruck">marbled queen</unclear>...</p>

Where the material affected is entirely illegible or inaudible, the gap element discussed above should be used in preference.

The del element is used to mark material which is deleted in the source but which can still be read with some degree of confidence, as opposed to material which has been omitted by the encoder or transcriber either because it is entirely illegible or for some other reason. This is of particular importance in transcribing manuscript material, though deletion is also found in printed texts, sometimes for humorous purposes:
<l>One day I will sojourn to your shores</l>
<l>I live in the middle of England</l>
<l>But!</l>
<l>Norway! My soul resides in your watery
<del rend="overstrike">fiords fyords fiiords</del>
</l>
<l>Inlets.</l>
The rend attribute may be used to distinguish different methods of deletion in manuscript or typescript material, as in this line from the typescript of Eliot's Waste Land:
<l>
 <del rend="overtyped">Mein</del> Frisch
<del type="overstrike">schwebt</del> weht der Wind
</l>
Deletion in manuscript or typescript is often associated with addition:
<l>
 <del rend="overstrike">Inviolable</del>
 <add place="below">Inexplicable</add>
splendour of Corinthian white and gold
</l>
The subst element discussed in 11.3.1.5 Substitutions provides a way of grouping additions and deletions of this kind.

The del element should not be used where the deletion is such that material cannot be read with confidence, or read at all, or where the material has been omitted by the transcriber or editor for some other reason. Where the material deleted cannot be read with confidence, the unclear tag should be used with the reason attribute indicating that the difficulty of transcription is due to deletion. Where material has been omitted by the transcriber or editor, this may be indicated by use of the gap element. A deletion in which some parts may be read but not others may thus be represented by one or more gap elements intermingled with text, all contained by a del element. Text supplied or marked as unneccessary by an editor should be marked with the supplied and surplus elements (discussed in 11.3.1.7 Text Omitted from or Supplied in the Transcription) rather than add and del. These two sets of elements allow the encoder to distinguish editorial changes from those visible in the source text.

3.6 Names, Numbers, Dates, Abbreviations, and Addresses

This section describes a number of textual features which it is often convenient to distinguish from their surrounding text. Names, dates, and numbers are likely to be of particular importance to the scholar treating a text as source for a database; distinguishing such items from the surrounding text is however equally important to the scholar primarily interested in lexis.

The treatment of these textual features proposed here is not intended to be exhaustive: fuller treatments for names, numbers, measures, and dates are provided in the names and dates module (see chapter 13 Names, Dates, People, and Places); more detailed treatment of abbreviations is provided by the transcription module (see section 11.3.1.2 Abbreviation and Expansion).

3.6.1 Referring Strings

A referring string is a phrase which refers to some person, place, object, etc. Two elements are provided to mark such strings:

  • rs (referencing string) contains a general purpose name or referring string.
  • name (이름, 고유명사) 고유명사 또는 명사구를 포함한다.

Both the name and rs elements are members of the att.typed class, from which they inherit the following attributes:

  • att.typed 요소의 분류 또는 하위분류에서 사용될 수 있는 속성을 제공한다.
    type다양한 분류 스키마 또는 유형을 사용해서 요소의 특성을 기술한다.
    subtype(subtype) 필요하다면 요소의 하위범주를 제시한다.

which may be used to further categorize the kind of object referred to.

Examples include:
<p>
 <q>My dear
 <rs type="person">Mr. Bennet</rs>
 </q>, said his lady to
him one day, <q>have you heard that <rs type="place">Netherfield Park</rs> is let at last?</q>
</p>
<p>Collectors of water-rents were appointed by the
<rs type="org">Watering Committee</rs>.
They were paid a commission not exceeding four per
cent, and gave bond.</p>
<p>It being one of the principles of the
<rs type="org">Circumlocution Office</rs> never, on any
account whatsoever, to give a straightforward answer,
<rs type="person">Mr Barnacle</rs> said, <q>Possibly.</q>
</p>
As the following example shows, the rs element may be used for any reference to a person, place, etc., not only to references in the form of a proper noun or noun phrase.
<p>
 <q>My dear <rs type="person">Mr. Bennet</rs>
 </q>, said
<rs type="person">his lady</rs> to him one day ...
</p>
The name element by contrast is provided for the special case of referencing strings which consist only of proper nouns; it may be used synonymously with the rs element, or nested within it if a referring string contains a mixture of common and proper nouns. The following example shows an alternative way of encoding the short sentence from Pride and Prejudice quoted above:
<p>
 <q>My dear <name type="person">Mr. Bennet</name>,</q> said <rs type="person">his lady</rs> to him one day,
<q>have you heard that <name type="place">Netherfield Park</name> is let at last?</q>
</p>
As the following example shows, a proper name may be nested within a referring string:
<rs>His Excellency the Life President, <name>Ngwazi Dr H. Kamuzu Banda</name>
</rs>

Simply tagging something as a name is generally not enough to enable automatic processing of personal names into the canonical forms usually required for reference purposes. The name as it appears in the text may be inconsistently spelled, partial, or vague. Moreover, name prefixes such as van or de la may or may not be included as part of the reference form of a name, depending on the language and country of origin of the bearer.

Two issues arise in this context: firstly, there may be a need to encode a regularized form of a name, distinct from the actual form in the source to hand; secondly, there may be a need to identify the particular person, place, etc. referred to by the name, irrespective of whether the name itself is normalized or not. The element reg, introduced in 3.5.2 Regularization and Normalization is provided for the former purpose; the attributes key or ref for the latter.

The key and ref attributes are common to all members of the att.canonical class and are defined as follows:

  • att.canonical provides attributes which can be used to associate a representation such as a name or title with canonical information about the object being named or referenced.
    keyprovides an externally-defined means of identifying the entity (or entities) being named, using a coded value of some kind.
    ref(reference) provides an explicit means of locating a full definition or identity for the entity being named by means of one or more URIs.
A very useful application for them is as a means of gathering together all references to the same individual or location scattered throughout a document:
<q>My dear
<rs key="BENM1" type="person">Mr. Bennet</rs>,</q> said
<rs key="BENM2" type="person">his lady</rs> to him one day,

<q>have you heard that
<rs key="NETP1" type="place">Netherfield Park</rs> is let at
last?</q>
<p>
 <name key="VOM1" type="person">Mme. de Volanges</name>
marie <rs key="VOM2">sa fille</rs>:
c'est encore un secret;
mais elle m'en a fait part hier.
</p>
The value of the key attribute may be an unexpanded code, as in the examples above, with no particular significance. More usually however, it will be an externally defined code of some kind, as provided by a standard reference source.
<p>
 <name key="LHR" type="airport">Heathrow</name>
</p>

The standard reference source should be documented, for example using a taxonomy element in the TEI header.

The ref attribute can be used to point directly to some other resource providing more information about the entity named by the element, such as an authority record in a database, an encylopaedia entry, another element in the same or a different document etc.
<p>
 <name ref="http://en.wikipedia.org/wiki/Heathrow_airport"
  type="airport">Heathrow</name>
</p>
This use should be distinguished from the use of a nested reg (regularization) element to provide the standard form of a referring string, as in this example:
<p>My personal life during
the administration of <rs key="POJA1" type="person">Col. Polk
   (<reg>Polk, James K.</reg>)</rs> has but poorly compensated me for the
suspended enjoyments and pursuits of private and professional
spheres</p>
No particular syntax is proposed for the values of the key attribute, since its form will depend entirely on practice within a given project. For the same reason, this attribute is not recommended in data interchange, since there is no way of ensuring that the values used by one project are distinct from those used by another. In such a situation, a preferable approach for magic tokens which follows standard practice on the Web is to use a ref attribute whose value is a tag URI as defined in RFC 4151. For example:
<p>
 <name ref="tag:projectname.org,2012:VOM1"
  type="person">Mme. de Volanges</name> marie <rs ref="tag:theworksoflaclos.org,2012:VOM2">sa fille</rs>: c'est encore un secret;
mais elle m'en a fait part hier.
</p>
The inclusion of the domain name of the party responsible for tagging (theworksoflaclos.org), as specified in RFC 4151, helps ensure uniqueness of magic token values across TEI encoding projects, allowing for improved interchange of TEI documents.
The choice element discussed in 3.5 Simple Editorial Changes may be used if it is desired to record both a normalized form of a name and the name used in the source being encoded:
<p>
 <name ref="tag:projectname.org,2012:WADLM1"
  type="person">
  <choice>
   <orig>Walter de la Mare</orig>
   <reg>de la Mare, Walter</reg>
  </choice>
 </name>
was born at <name ref="tag:projectname.org,2012:Ch1"
  type="place">Charlton</name>, in
<name ref="tag:projectname.org,2012:KT1"
  type="county">Kent</name>, in 1873.
</p>
The index element discussed in 3.9.2 Index Entries may be more appropriate if the function of the regularization is to provide a consistent index:
<p>
 <name type="place">Montaillou</name> is not a large parish.
At the time of the events which led to
<name type="person">Fournier<index>
   <term>Benedict XII, Pope of Avignon (Jacques Fournier)</term>
  </index>
 </name>'s
investigations, the local population consisted of between 200 and 250 inhabitants.
</p>
Although adequate for many simple applications, these methods have two inconveniences: if the name occurs many times, then its regularized form would be repeated many times; and the burden of additional XML markup in the body of the text may be inconvenient to maintain and complex to process. For applications such as onomastics, relating to persons or places named rather than the name itself, or wherever a detailed analysis of the component parts of a name is needed, the specialized elements described in chapter 13 Names, Dates, People, and Places or the analytical tools described in chapter 18 Feature Structures should be used.

3.6.2 Addresses

These Guidelines propose the following elements to distinguish postal and electronic addresses:

  • address (address) 예를 들어, 출판사, 기관, 개인의 우편 주소를 포함한다.
  • email (전자우편 주소) 전자우편 메시지가 전달되는 위치를 식별하는 전자우편 주소를 포함한다.

These two elements constitute the class of model.addressLike elements; for other kinds of address this class may be extended by adding new elements if necessary.

These Guidelines provide no particular means for encoding the substructure of an email address (for example, distinguishing the local part from the domain part), nor of distinguishing personal email addresses from generic or fictitious ones.
<email>info@tei-c.org</email>
The simplest way of encoding a postal address is to regard it as a series of distinct lines, just as they might be written on an envelope. The following element supports this view:
  • addrLine (주소 행) 우편 주소의 한 행을 포함한다.
Here is an example of a postal address encoded using this approach:
<address>
 <addrLine>110 Southmoor Road,</addrLine>
 <addrLine>Oxford OX2 6RB,</addrLine>
 <addrLine>UK</addrLine>
</address>

Alternatively, an address may be encoded as a structure of more semantically rich elements. The class model.addrPart element class identifies a number of such possible components:

  • street 거리 또는 도로 이름을 비롯하여 건물을 식별할 수 있는 이름 및 번지를 포함하는 전체 주소.
  • name (이름, 고유명사) 고유명사 또는 명사구를 포함한다.
  • postCode (우편 번호) 우편의 분류 및 배달을 용이하도록 우편 주소의 일부로 사용되는 숫자 또는 문자와 숫자가 혼용된 기호.
  • postBox (우편함 또는 사서함) 주소 이외의 우편 배달 지점을 위한 숫자 또는 다른 확인소를 포함한다.
  • model.nameLike 인물, 장소, 또는 조직의 이름 또는 지시를 나타내는 요소를 모아 놓는다.
    model.nameLike.agent개인 또는 기업체의 이름을 포함하는 요소를 모아 놓는다.
    model.offsetLike장소명의 부분으로서만 나타날 수 있는 요소를 모아 놓는다.
    model.persNamePart사람 이름의 부분을 형성하는 요소를 모아놓는다.
    model.placeStateLike장소의 변화하는 상태를 기술하는 요소를 모아 놓는다.
    idno(식별 숫자) 서지 정보 항목을 식별하기 위해 사용되는 표준 또는 비표준 숫자를 제시한다.
    lang(언어명) 어원적 또는 기타 언어적 논의에서 언급된 언어의 이름
    objectName(name of an object) contains a proper noun or noun phrase used to refer to an object.
    rs(referencing string) contains a general purpose name or referring string.
  • model.persNamePart 사람 이름의 부분을 형성하는 요소를 모아놓는다.
    addName(부가명) 별명, 통명, 가명, 또는 개인 이름 내에서 사용되는 다른 기술적 구와 같이 부가적 이름 성분을 포함한다.
    forename(forename) 이름 또는 세례명을 포함한다.
    genName(세대명 성분) 개인의 상대적 나이 또는 세대에 기반하여 유사 이름을 다른 방식으로 구분하는 이름 성분을 포함한다.
    nameLink(name link) van der 또는 of와 같이 이름의 부분으로 간주되지 않는 이름 내의 연결 구 또는 연결을 포함한다.
    persPronouns(personal pronouns) indicates the personal pronouns used, or assumed to be used, by the individual being described.
    roleName(role name) 공식적 직함 또는 서열과 같이 사회에서 특별한 역할 또는 지위를 나타내는 이름 성분을 포함한다.
    surname(surname) 이름, 세례명, 또는 별명에 반대되는 것으로 (물려받은) 성을 포함한다.
  • model.placeNamePart 장소명의 부분을 형성하는 요소를 모아 놓는다.
    bloc(bloc) 둘 이상의 민족국가 또는 국가로 구성된 지리-정치적 단위의 이름을 포함한다.
    country(country) 하나의 블록보다 큰 국가, 지역, 식민지, 또는 공화국, 또는 하나의 블록보다 작은 지역의 상급 행정기관과 같은, 지리-정치 단위명을 포함한다.
    district(district) 교구, 구 또는 다른 행정 지리적 단위와 같이 거주지의 하위 구분명을 포함한다.
    geogName(지리명) 윈드러시 계곡 또는 시나이 산과 같이 지리적 특성과 관련된 이름
    placeName(place name) 절대적 또는 상대적 위치명을 포함한다.
    region(region) 도보다는 작고 정착지보다는 큰 주, 성, 도와 같은 행정단위명을 포함한다.
    settlement(settlement) 하나의 지리-정치 또는 행정 단위로 식별되는 시, 읍, 마을과 같이 거주지명을 포함한다.

Any number of elements from the model.addrPart class may appear within an address and in any order. None of them is required.

Where code letters are commonly used in addresses (for example, to identify regions or countries) a useful practice is to supply the full name of the region or country as the content of the element, but to supply the abbreviatory code as the value of the global n attribute, so that (for example) an application preparing formatted labels can readily find the required information. Other components of addresses may be represented using the general-purpose name element or (when the additional module for names and dates is included) the more specialized elements provided for that purpose.

Using just the elements defined by the core module, the above address could thus be represented as follows:
<address>
 <street>110 Southmoor Road</street>
 <name type="city">Oxford</name>
 <postCode>OX2 6RB</postCode>
 <name type="country">United Kingdom</name>
</address>
The order of elements within an address is highly culture-specific, and is therefore unconstrained:
<address>
 <name type="org">Università di Bologna</name>
 <name type="country">Italy</name>
 <postCode>40126</postCode>
 <name type="city">Bologna</name>
 <street>via Marsala 24</street>
</address>
A telephone number (normally outside of the address element) might be tagged with an addrLine and ref, with the number itself appearing in the tel: namespace:
<addrLine>
 <ref target="tel:+1-201-555-0123">(201) 555 0123</ref>
</addrLine>

For further discussion of ways of regularizing the names of places, see section 3.6 Names, Numbers, Dates, Abbreviations, and Addresses. A full postal address may also include the name of the addressee, tagged as above using the general purpose name element.

When a schema includes the names and dates module discussed in chapter 13 Names, Dates, People, and Places, a large number of more specific elements such as country or settlement will be available from the class model.addrPart. The above example might then be encoded as follows:
<address>
 <street>110 Southmoor Road</street>
 <settlement>Oxford</settlement>
 <postCode>OX2 6RB</postCode>
 <country>United Kingdom</country>
</address>

3.6.3 Numbers and Measures

This section describes elements provided for the simple encoding of numbers and measurements and gives some indication of circumstances in which this may usefully be done. The following phrase level elements are provided for this purpose:

  • num (숫자) 다양한 형식의 숫자를 포함한다.
    type수치의 유형을 나타낸다. 제안값은 다음을 포함한다: 1] cardinal; 2] ordinal; 3] fraction; 4] percentage
    value표준형의 숫자 값을 제시한다.
  • measure (measure) 개체 또는 물체의 수량을 지시하는 단어 또는 구를 포함한다. 이들은 숫자, 단위, 물체명으로 구성되어 있다.
    type편리한 방식으로 측정 유형을 명시한다.
  • measureGrp (측정 그룹) 예를 들어, 원고지 페이지의 가로 세로 크기와 같이 동일 개체에 관련된 여러 종류의 측량값의 그룹을 포함한다.

Like names or abbreviations, numbers can occur virtually anywhere in a text. Numbers are special in that they can be written with either letters or digits (twenty-one, xxi, and 21) and their presentation is language-dependent (e.g. English 5th becomes Greek 5.; English 123,456.78 equals French 123.456,78).

For many kinds of application, e.g. natural-language processing or machine translation, numbers are not regarded as ‘lexical’ in the same way as other parts of a text. For these and other applications, the num element provides a convenient method of distinguishing numbers from the surrounding text. For other kinds of application, numbers are only useful if normalized: here the num element is useful precisely because it provides a standardized way of representing a numerical value.

For example:
<num value="33">xxxiii</num>
<num type="cardinal" value="21">twenty-one</num>
<num type="percentage" value="10">ten percent</num>
<num type="percentage" value="10">10%</num>
<num type="ordinal" value="5">5th</num>
<num type="fraction" value="0.5">one half</num>
<num type="fraction" value="0.5">1/2</num>

Sometimes it may be desired to mark something as numerical which cannot be accurately normalized, for example an expression such as dozens; less frequently the number may be recognisable linguistically as such but may use a notation with which the encoder is unfamiliar. To help in these situations, the num element may also bear either or both of the following attributes from the att.ranging class:

  • att.ranging provides attributes for describing numerical ranges.
    atLeastgives a minimum estimated value for the approximate measurement.
    atMostgives a maximum estimated value for the approximate measurement.

In its fullest form, a measure consists of a number, a phrase expressing units of measure and a phrase expressing the commodity being measured, though not all of these components need be present in every case. It may be helpful to distinguish measures from surrounding text for two reasons. Firstly, a measure may be expressed using a particular notation or system of abbreviations which the encoder does not wish to regard as lexical. Secondly, a quantitative application may wish to distinguish and normalize the internal components of a measure, in order to perform calculations on them.

Consider, as an example of the first case, the following list of Celia's charms, in which the encoder has chosen to make explicit the measurements:
<div n="2">
 <list type="gloss">
  <label>Age</label>
  <item>Unimportant</item>
  <label>Head</label>
  <item>Small and round</item>
  <label>Eyes</label>
  <item>Green</item>
  <label>Complexion</label>
  <item>White</item>
  <label>Hair</label>
  <item>yellow</item>
  <label>Features</label>
  <item>Mobile</item>
  <label>Neck</label>
  <item>
   <measure>13¾"</measure>
  </item>
  <label>Upper arm</label>
  <item>
   <measure>11"</measure>
  </item>
<!--...-->
 </list>
<!-- ... -->
</div>
In the same way, it may be convenient to mark representations of currency which might otherwise be misinterpreted as lexical:
<p>...the sum of
<measure type="currency">12s 6d</measure>...</p>
In general, normalization of a measure will require specification of one or more of its three parts: the quantity, the units, and possibly also the commodity being measured. This is accomplished by supplying values for the three attributes quantity, unit, and commodity, which are supplied by the att.measurement class:
  • att.measurement 정상화 또는 규격화된 측정 방식을 표상하는 속성을 제시한다.
    quantity(quantity) 측정을 구성하는 명시적 단위의 수를 명시한다.
    unit(unit) 측정에 사용된 단위를 나타내며, 일반적으로 요구 단위에 대한 표준 기호를 사용한다. 제안값은 다음을 포함한다: 1] m (metre); 2] kg (kilogram); 3] s (second); 4] Hz (hertz); 5] Pa (pascal); 6] Ω (ohm); 7] L (litre); 8] t (tonne); 9] ha (hectare); 10] Å (ångström); 11] mL (millilitre); 12] cm (centimetre); 13] dB (decibel); 14] kbit (kilobit); 15] Kibit (kibibit); 16] kB (kilobyte); 17] KiB (kibibyte); 18] MB (megabyte); 19] MiB (mebibyte)
    commodity(commodity) 측정되고 있는 물질을 나타낸다.
With these attributes, the measurement of Celia's neck may be specified in a normalized form:
<measure quantity="13.75" unit="in">13¾"</measure>
Such techniques are particularly useful when representing historical data such as inventories:
<list>
 <item>
  <measure type="volume" quantity="2"
   unit="bag" commodity="hops">ii bags hops</measure>
 </item>
 <item>
  <measure type="volume" quantity="6"
   unit="truss" commodity="cloth">six trusses Woolen and linen goods</measure>
 </item>
 <item>
  <measure type="weight" quantity="5"
   unit="ton" commodity="coal">5 tonnes coale</measure>
 </item>
</list>
The measureGrp element is provided as a means of grouping several related measurements together, either because the measurement involves several dimensions (for example height and width) or to avoid the need to repeat all the normalizing attributes:
<measureGrp type="volume" unit="in">
 <measure type="height" quantity="14">xiv</measure>
 <measure type="width" quantity="5">v</measure>
 <measure type="depth" quantity="10">x</measure>
</measureGrp>
The unit element may be applied when units of measurement require more detailed encoding about the system they belong to or the what kind of phenomenon they designate. The unit element may carry the unit attribute to indicate a standard value, as well as other optional attributes for indicating type, language, and other distinguishing characteristics.
  • unit contains a symbol, a word or a phrase referring to a unit of measurement in any kind of formal or informal system.
  • att.measurement 정상화 또는 규격화된 측정 방식을 표상하는 속성을 제시한다.
    unit(unit) 측정에 사용된 단위를 나타내며, 일반적으로 요구 단위에 대한 표준 기호를 사용한다. 제안값은 다음을 포함한다: 1] m (metre); 2] kg (kilogram); 3] s (second); 4] Hz (hertz); 5] Pa (pascal); 6] Ω (ohm); 7] L (litre); 8] t (tonne); 9] ha (hectare); 10] Å (ångström); 11] mL (millilitre); 12] cm (centimetre); 13] dB (decibel); 14] kbit (kilobit); 15] Kibit (kibibit); 16] kB (kilobyte); 17] KiB (kibibyte); 18] MB (megabyte); 19] MiB (mebibyte)
  • att.typed 요소의 분류 또는 하위분류에서 사용될 수 있는 속성을 제공한다.
  • att.global TEI 부호화 스키마의 모든 요소에 공통 속성을 제공한다.
A measure element may contain a combination of num and unit elements:
<measure type="list">
 <num>1</num>, <num>2</num>, <num>5</num>, <num>7</num>
 <unit type="length" unit="mm">millimètres</unit>
</measure>
The unit element may also be nested to indicate a complex unit and its component parts, for example, to indicate that rate combines space and time:
<p>Light travels at <num value="3E10">3×10^10</num>
 <unit type="rate" unit="cm/s">
  <unit type="space">cm</unit> per <unit type="time">second</unit>
 </unit>.</p>

3.6.4 Dates and Times

Dates and times, like numbers, can appear in widely varying culture- and language-dependent forms, and can pose similar problems in automatic language processing. Such elements constitute the model.dateLike class, of which the default members are:

  • date (date) 다양한 형식의 날짜를 포함한다.
  • time (time) 어떤 형식의, 하루의 시간을 정의하는 구를 포함한다.

These elements have some additional attributes by virtue of being members of the att.datable and att.duration classes which, in turn, are members of the att.datable.w3c and att.duration.w3c classes. In particular, the when and calendar attributes will be discussed here:

  • att.datable.w3c W3C 데이터 유형을 사용하여 날짜가 명기된 사건을 포함하는 요소의 규격화를 위한 속성을 제공한다.
    when표준형식으로 날짜 또는 시간의 값을 제공한다.
  • att.datable 날짜, 시간 또는 날짜 명기 사건을 포함하는 요소의 규격화에 대한 속성을 제공한다.
    calendar날짜 표현 시스템 또는 달력 표시 형식을 표시한다.

Dates can occur virtually anywhere in a text, but in some contexts (e.g. bibliographic citations) their encoding is recommended or required rather than optional. Times can also appear anywhere but encoding these is more generally optional.

Partial dates or times (e.g. 1990, September 1990, twelvish) can be expressed in the when attribute by simply omitting a part of the value supplied. Imprecise dates or times (for example early August, some time after ten and before twelve) may be expressed as date or time ranges.

These mechanisms are useful primarily for fully specified dates or times known with certainty. If component parts of dates or times are to be marked up, or if a more complex analysis of the meaning of a temporal expression is required, the techniques described in chapter 13 Names, Dates, People, and Places should be used in preference to the simple method outlined here.

Where the certainty (i.e. reliability) of the date or time is in question, the encoder should record this fact using the mechanisms discussed in chapter 21 Certainty, Precision, and Responsibility. The same chapter also discusses various methods of recording the precision of numerical or temporal assertions.

The when attribute is a useful way of normalizing or disambiguating dates and times which can appear in many formats, as the following examples show:
<date when="1980-02-12">12/2/1980</date>
Given on the <date when="1977-06-12">Twelfth Day of June
in the Year of Our Lord One Thousand Nine Hundred and
Seventy-seven of the Republic the Two Hundredth and first
and of the University the Eighty-Sixth.</date>
The when attribute always supplies a normalized representation of the date given as content of the date element. The format used should be a valid W3C schema datatype.15 Some typical examples follow:
<date when="2001">The year 2001</date>
<date when="2001-09">September 2001</date>
<date when="2001-09-11">11 Sep 01</date>
<date when="--09-11">9/11</date>
<date when="--09">September</date>
<date when="---11">Eleventh of the month</date>
<time when="08:48:00">8:48</time>
<date when="2001-09-11T12:48:00">Sept 11th, 12 minutes before 9 am</date>
Note in the last example the use of a normalized representation for the date string which includes a time: this example could thus equally well be tagged using the time element.
The following examples demonstrate the use of the date element to mark a period of time:
<p>Those five years —
<date from="1918" to="1923">1918 to 1923</date>
— had been, he suspected,
somehow very important.</p>
<p>The Eddic poems are preserved in a unique
manuscript (Codex Regius 2365) from
<date notBefore="1250" notAfter="1300">the second half of the
   thirteenth century</date>, and <title>Hervarar
   saga</title> dates from <date when="1300">around 1300</date>.</p>

The calendar attribute may be used to specify a date in any calendar system; if the when attribute is also supplied, it should specify the equivalent date in the Gregorian calendar.

3.6.5 Abbreviations and Their Expansions

It is sometimes desirable to mark abbreviations in the copy text, whether to trigger special processing for them, to provide the full form of the word or phrase abbreviated, or to allow for different possible expansions of the abbreviation. Abbreviations may be transcribed as they stand, or expanded; they may be left unmarked, or marked using these tags:

  • abbr (약어) 어떤 종류의 약어를 포함한다.
  • expan (확장 표기) 약어의 확장(비약어) 표기
The abbr element is useful as a means of distinguishing semi-lexical items such as acronyms or jargon:
We can sum up the above discussion as follows:
the identity of a <abbr>CC</abbr> is defined by that calibration of values which
motivates the elements of its <abbr>GSP</abbr>; ...
Every manufacturer of <abbr>3GL</abbr> or <abbr>4GL</abbr>
languages is currently nailing on <abbr>OOP</abbr> extensions.
The type attribute may be used to distinguish types of abbreviation by their function:
<abbr type="title">Dr.</abbr>
<abbr type="initial">M.</abbr> Deegan is
the Director of the <abbr type="acronym">CTI</abbr> Centre for Textual Studies.
Abbreviations such as Dr. M. above may be treated as two abbreviations, as above, or as one:
<abbr>Dr. M.</abbr> Deegan is
the Director of the <abbr>CTI</abbr> Centre for Textual Studies.
The expan element may be used simply to record that an abbreviation has been silently expanded by the encoder, perhaps for reasons of house style or editorial policy. It should always include the whole of an abbreviated phrase or word. More usually however this will be combined with the abbr element inside a choice element to record both the abbreviation and its expansion:
the
<choice>
 <expan>World Wide Web Consortium</expan>
 <abbr>W3C</abbr>
</choice>
Nested abbreviations may also be handled in this way:
<choice>
 <abbr>RELAX NG</abbr>
 <expan>regular
   language for <choice>
   <abbr>XML</abbr>
   <expan>extensible markup
       language</expan>
  </choice>, next
   generation</expan>
</choice>

Abbreviation is a particularly important feature of manuscript and other source materials, the transcription of which needs more detailed treatment than is possible using these simple elements. A more detailed set of recommendations is discussed in 11.3.1 Altered, Corrected, and Erroneous Texts, which includes additional elements made available for the purpose by the transcr module.

3.7 Simple Links and Cross-References

Cross-references or links between one location in a document and one or more other locations, either in the same or different XML documents, may be encoded using the elements ptr and ref, as discussed in this section. These elements both ‘point’ from one location in a document, the place that the element itself appears, to another (or to several), specified by means of a target attribute, supplied by the att.pointing class:

  • att.pointing 하나 이상의 URI 참조를 통해서 다른 요소를 가리키는 모든 요소에 의해 사용된 속성 집합을 정의한다.
    target하나 혹은 다수의 URI 참조를 제시하여 참조의 목적지를 명시한다.

Linkages of several other kinds are also provided for in these guidelines; see further chapter 16 Linking, Segmentation, and Alignment.

The value of the target attribute, wherever it appears, provides a way of pointing to some other element using a method standardized by the W3C consortium, and known as the XPointer mechanism. This permits a range of complexity, from the very simple (a reference to the value of the target element's xml:id attribute) to the more complex usage of a full URI with embedded XPointers. For example, the source of the following paragraph looks something like this:
<p>...
The complete XPointer specification is managed by the W3C<note place="foot">
  <ptr target="http://www.w3.org/TR/xptr-framework/"/>,
 <ptr target="http://www.w3.org/TR/xptr-element/"/>,
 <ptr target="http://www.w3.org/TR/xptr-xmlns/"/>, and
 <ptr target="http://www.w3.org/TR/xptr-xpointer/"/>
 </note>;
for a discussion of TEI schemes for XPointer, see
<ptr target="#eSATS"/>.</p>
<!--... -->
<div xml:id="eSATS">
<!--... -->
</div>
Alternatively, if no explicit link is to be encoded, but it is simply required to mark the phrase as a cross-reference, the ref element may be used without a target attribute.

For an introduction to the use of links in general, see 16 Linking, Segmentation, and Alignment. The complete XPointer specification is managed by the W3C16; for a discussion of TEI schemes for XPointer, see 16.2.4 TEI XPointer Schemes.

  • ptr (포인터) 다른 위치로의 포인터를 정의한다.
  • ref (참조) 부가적인 텍스트 또는 해설로 수정될 수 있는, 다른 위치로 참조를 정의한다.

The elements ptr and ref are the default members of the phrase-level model class model.ptrLike. As members of the classes att.pointing, att.typed, att.cReferencing, and att.internetMedia they also carry the following attributes:

  • att.pointing 하나 이상의 URI 참조를 통해서 다른 요소를 가리키는 모든 요소에 의해 사용된 속성 집합을 정의한다.
    target하나 혹은 다수의 URI 참조를 제시하여 참조의 목적지를 명시한다.
    evaluate(evaluate) 포인터의 대상이 포인터일 때 의도된 의미를 명시한다.
  • att.cReferencing provides an attribute which may be used to supply a canonical reference as a means of identifying the target of a pointer.
    cRef(표준 참조) TEI 헤더의 refsDecl 요소에서 정의된 체계의 표준 참조를 이용하여 포인터의 목적지를 명시한다.
  • att.typed 요소의 분류 또는 하위분류에서 사용될 수 있는 속성을 제공한다.
    type다양한 분류 스키마 또는 유형을 사용해서 요소의 특성을 기술한다.
    subtype(subtype) 필요하다면 요소의 하위범주를 제시한다.
  • att.internetMedia 표준 분류법을 사용하는 컴퓨터 자원의 유형을 명시하는 속성을 제시한다.
    mimeType(MIME 매체 유형) 적용 가능한 다중매체 인터넷 메일 확장자(MIME) 매체 유형을 명시한다.
The two elements may be used in the same way; the difference between them is simply that while the ptr element is empty, the ref element may contain phrases specifying, or describing more exactly, the target of a cross-reference, which form the content of the element. Since its content thus serves as a human-readable pointer, in the simplest case a ref element need not identify its target in any other way. For example:
See <ref>section 12 on page 34</ref>.
More usually, it will be desirable to identify the target of the cross-reference using either the target or the cRef attribute, so that processing software can access it directly, for example to implement a linkage, to generate an appropriate reference, or to give an error message if it cannot be found. Assuming that section 12 in the previous example has been tagged
<div1 xml:id="SEC12">
<!-- ... -->
</div1>
then the same cross-reference might more exactly be encoded as
See especially <ref target="#SEC12">section 12 on page 34</ref>.
If the cross-reference itself is to be generated according to a fixed pattern, or if no text is to appear in the body of the cross-reference, the ptr element would be used as follows:
See in particular <ptr target="#SEC12"/>.

The cRef attribute may be used to express the target of a cross reference using some canonical referencing scheme, such as those typically used for ancient texts. In this case, the referencing scheme must be defined using the cRefPattern or citeStructure elements discussed below (3.11.4 Declaring Reference Systems); the definition these provide may be used to translate the value of the cRef attribute into a conventional pointer value, such as one that might be supplied by the target attribute. It is an error to supply both cRef and target values.

When the target attribute is used, a cross reference may point to any number of locations simultaneously, simply by giving more than one identifier as the value of its target attribute. This may be particularly useful where an analytic index is to be encoded, as in the following example:
<list>
 <item>Saints aid rejected in mel. <ptr target="#p299"/>
 </item>
 <item>Sallets censured <ptr target="#p143 #p144"/>
 </item>
 <item>Sanguine mel. signs <ptr target="#p263"/>
 </item>
 <item>Scilla or sea onyon, a purger of mel. <ptr target="#p442"/>
 </item>
</list>
Here the targets of the cross-references are simply page numbers; it is assumed that corresponding elements with identifiers p299, p143, etc. have been provided in the body of the text, for example as page breaks
<pb xml:id="p143"/>
...
<pb xml:id="p144"/>
...
<pb xml:id="p263"/>
...
<pb xml:id="p299"/>
...
<pb xml:id="p442"/>
...
A similar method may be used to link annotations on a text with the sigla used to encode their points of attachment in a text. For example:
annotated text <ref target="#a51" type="noteAnchor">⁵¹</ref>
<!-- ... -->
<note xml:id="a51" type="footnote">text of annotation</note>
The type attribute may be used, as elsewhere, to categorize the cross-reference according to any system of importance to the encoder. If bibliographic references require special processing (e.g. in order to provide a consistent short-form reference), they might be tagged thus:
Similar forms, often called
<term rend="ldquo rdquo">rewriting systems</term>, have a long history
among mathematicians, but the specific form of <ptr target="#fig22"/>
was first studied extensively by Chomsky <ptr type="bibliog" target="#chom59"/>.

<!-- ... -->
<figure xml:id="fig22">
 <graphic url="fig22.jpg"/>
</figure>
<!-- elsewhere, in the bibliography -->
<bibl xml:id="chom59">
<!-- citation for the book referenced above -->
</bibl>
The value bibliog for the type attribute on the second ptr element here might be used to indicate that the object being referenced here is a bibliographic entry rather than a simple cross-reference to an illustration, as is the first ptr. In either case, the value of the target attribute is a pointer to some other element.

The ptr and ref elements have many applications in addition to the simple cross-referencing facilities illustrated in this section. In conjunction with the analytic tools discussed in chapters 16 Linking, Segmentation, and Alignment, 17 Simple Analytic Mechanisms, and 18 Feature Structures, they may be used to link analyses of a text to their object, to combine corresponding segments of a text, or to align segments of a text with a temporal or other axis or with each other.

Where the target attribute of ptr or ref points to an external resource available on the network, the mimeType attribute may be used to specify the mime type of that resource; this may be important for to enable appropriate processing. For example:
<p>The current version of the TEI Guidelines source code
is available in the TEI GitHub Repository; <ref target="https://github.com/TEIC/TEI/blob/dev/P5/Source/guidelines-en.xml"
  mimeType="application/tei+xml">guidelines-en.xml</ref>
is the root document used to create the English version
of these Guidelines.</p>

3.8 Lists

The following elements are provided for the encoding of lists, their constituent items, and the labels or headings associated with them:

  • list (list) 목록의 형태로 정리된 항목을 포함한다.
  • item (item) 목록에서 하나의 성분을 포함한다.
  • label (label) 목록의 항목과 관련된 표지를 포함한다; 용어집에서는 정의되고 있는 용어를 표지한다.
  • head (표제부) 예를 들어 절의 제목 또는 용어집, 원고 기술의 제목 등과 같이 표제부 유형을 포함한다.
  • headLabel (heading for list labels) contains the heading for the label or term column in a glossary list or similar structured list.
  • headItem (목록의 항목에 대한 표제부) 용어집 목록 또는 유사 구조의 목록에서 항목 또는 해설에 대한 표제부를 포함한다.

The list element may be used to mark any kind of list: numbered, lettered, bulleted, or unmarked. Lists formatted as such in the copy text should in general be encoded using this element, with an appropriate value for the rend attribute. Suggested values for rend include:

  • bulleted (items preceded by bullets or similar markings)
  • inline (items rendered within continuous prose, with no linebreaks)
  • numbered (items preceded by numbers or letters)
  • simple (items rendered as blocks, but with no bullet or number)

Some of these values may of course be combined; a list may be inline, but also be rendered with numbers. An example appears below. For more sophisticated and detailed description of list rendering, consider using the style attribute with Cascading Stylesheet properties and values, as described in the W3C's CSS Lists and Counters Module Level 3.

Each distinct item in the list should be encoded as a distinct item element. If the numbering or other identification for the items in a list is unremarkable and may be reconstructed by any processing program, no enumerator need be specified. If however an enumerator is retained in the encoded text, it may be supplied either by using the n attribute on the item element, or by using a label element. The following examples are thus equivalent:
I will add two facts, which have seldom occurred in
the composition of six, or even five quartos.
<list rend="inline numbered">
 <label>(1)</label>
 <item>My first rough manuscript, without any
   intermediate copy, has been sent to the press.</item>
 <label>(2)</label>
 <item>Not a sheet has been seen by any human
   eyes, excepting those of the author and the printer:
   the faults and the merits are exclusively my own.</item>
</list>
I will add two facts, which have seldom occurred in
the composition of six, or even five quartos.
<list rend="inline numbered">
 <item n="1">My first rough manuscript, without any
   intermediate copy, has been sent to the press.</item>
 <item n="2">Not a sheet has been seen by any human
   eyes, excepting those of the author and the printer:
   the faults and the merits are exclusively my own.</item>
</list>
The two styles may not be mixed in the same list: if one item is preceded by a label, all must be.
A list need not necessarily be displayed in list format. For example, the following is a reasonable encoding of a list which (in the original) is simply printed as a single paragraph:
On those remote pages it is written that animals are
divided into <list rend="inline">
 <item n="a">those that belong to the Emperor, </item>
 <item n="b">embalmed ones, </item>
 <item n="c">those that are trained, </item>
 <item n="d">suckling pigs, </item>
 <item n="e">mermaids, </item>
 <item n="f">fabulous ones, </item>
 <item n="g">stray dogs, </item>
 <item n="h">those that are included in this classification, </item>
 <item n="i">those that tremble as if they were mad, </item>
 <item n="j">innumerable ones, </item>
 <item n="k">those drawn with a very fine camel's-hair brush, </item>
 <item n="l">others, </item>
 <item n="m">those that have just broken a flower vase, </item>
 <item n="n">those that resemble flies from a distance. </item>
</list>
A list may be given a heading or title, for which the head element should be used, as in the next example, which also demonstrates simple use of the label element to mark a tabular or glossary list in which each item is associated with a word or phrase rather than a numeric or alphabetic enumerator:
<list type="gloss">
 <head>Report of the conduct and progress of Ernest Pontifex.
   Upper Vth form — half term ending Midsummer 1851</head>
 <label>Classics</label>
 <item>Idle listless and unimproving</item>
 <label>Mathematics</label>
 <item>ditto</item>
 <label>Divinity</label>
 <item>ditto</item>
 <label>Conduct in house</label>
 <item>Orderly</item>
 <label>General conduct</label>
 <item>Not satisfactory, on account of his great
   unpunctuality and inattention to duties</item>
</list>
In such a list, the individual items have internal structure. In complex cases, where list items contain many components, the list is better treated as a table, on which see chapter 14 Tables, Formulæ, Graphics and Notated Music. A particularly important instance of the simple two-column table is the ‘glossary list’, which should be marked by the tag <list type="gloss">. In such lists, each label element contains a term and each item its gloss; it is a semantic error for a list tagged with type="gloss" not to have labels. For example:
<list type="gloss">
 <head>Unit Three — Vocabulary</head>
 <label xml:lang="la">acerbus, -a, -um </label>
 <item>bitter, harsh</item>
 <label xml:lang="la">ager, agrī, M. </label>
 <item>field</item>
 <label xml:lang="la">audiō, īre,
   īvī, ītus </label>
 <item>hear, listen (to)</item>
 <label xml:lang="la">bellum, -ī, N. </label>
 <item>war</item>
 <label xml:lang="la">bonus, -a, -um </label>
 <item>good</item>
</list>
Additionally, the term and gloss elements discussed in section 3.4.1 Terms and Glosses might be used to make explicit the role that each column in the glossary list has, as follows:
<list type="gloss">
 <head>Unit Three — Vocabulary</head>
 <label>
  <term xml:lang="la">acerbus, -a, -um</term>
 </label>
 <item>
  <gloss>bitter, harsh</gloss>
 </item>
 <label>
  <term xml:lang="la">ager, agrī, M. </term>
 </label>
 <item>
  <gloss>field</gloss>
 </item>
 <label>
  <term xml:lang="la">audiō, -īre, -īvī, -ītus</term>
 </label>
 <item>
  <gloss>hear, listen (to)</gloss>
 </item>
 <label>
  <term xml:lang="la">bellum, -ī, N. </term>
 </label>
 <item>
  <gloss>war</gloss>
 </item>
 <label>
  <term xml:lang="la">bonus, -a, -um</term>
 </label>
 <item>
  <gloss>good</gloss>
 </item>
</list>
Note in the above examples the use of the global xml:lang attribute to specify on the label (or term) element what language the term is from. For further discussion of the xml:lang attribute see section 1.3.1.1 Global Attributes, and section vi.1. Language Identification. A more elaborate markup for this glossary would distinguish the headword forms from the grammatical information (principal parts and gender), perhaps using elements taken from 9 Dictionaries.
In addition to the head element used to supply a title or heading for the whole list, headings for the two columns of a glossary-style list may be specified using the two special elements headLabel and headItem:
The simple, straightforward statement of an idea is
preferable to the use of a worn-out expression.
<list type="gloss">
 <headLabel>TRITE</headLabel>
 <headItem>SIMPLE, STRAIGHTFORWARD</headItem>
 <label>bury the hatchet </label>
 <item>stop fighting, make peace</item>
 <label>at loose ends </label>
 <item>disorganized</item>
 <label>on speaking terms </label>
 <item>friendly</item>
 <label>fair and square </label>
 <item>completely honest</item>
 <label>at death's door </label>
 <item>near death</item>
</list>
The elements label, head, headLabel, and headItem may contain only phrase-level elements. The item element however may contain paragraphs or other ‘chunks’, including other lists. In this example, a glossary list contains two items, each of which is itself a simple list:
<list type="gloss">
 <label>EVIL</label>
 <item>
  <list rend="bulleted">
   <item>I am cast upon a horrible desolate island, void
       of all hope of recovery.</item>
   <item>I am singled out and separated as it were from
       all the world to be miserable.</item>
   <item>I am divided from mankind — a solitaire; one
       banished from human society.</item>
  </list>
 </item>
 <label>GOOD</label>
 <item>
  <list rend="bulleted">
   <item>But I am alive; and not drowned, as all my
       ship's company were.</item>
   <item>But I am singled out, too, from all the ship's
       crew, to be spared from death...</item>
   <item>But I am not starved, and perishing on a barren place,
       affording no sustenances....</item>
  </list>
 </item>
</list>

Lists of different types may be nested to arbitrary depths in this way.

3.9 Notes, Annotation, and Indexing

3.9.1 Notes and Simple Annotation

The following element is provided for the encoding of discursive notes, whether already present in the copy text or supplied by the encoder:

  • note (note) contains a note or annotation.

A note is any additional comment found in a text, marked in some way as being out of the main textual stream. All notes should be marked using the same tag, note, whether they appear as block notes in the main text area, at the foot of the page, at the end of the chapter or volume, in the margin, or in some other place.

Notes may be in a different hand or typeface, may be authorial or editorial, and may have been added later. Attributes may be used to specify these and other characteristics of notes, as detailed below.

A note is usually attached to a specific point or span within a text, which we term here its point of attachment. In conventional printed text, the point of attachment is represented by some siglum such as a star or cross, or a superscript digit.

When encoding such a text, it is conventional to replace this siglum by the content of the annotation, duly marked up with a note element. This may not always be possible for example with marginal notes, which may not be anchored to an exact location. For ease of processing, it may be adequate to position marginal notes before the relevant paragraph or other element. In printed texts, it is sometimes conventional to group notes together at the foot of the page on which their points of attachment appear. This practice is not generally recommended for TEI-encoded texts, since the pagination of a particular printed text is unlikely to be of structural significance. In some cases, however, it may be desirable to transcribe notes not at their point of attachment to the text but at their point of appearance, typically at the end of the volume, or the end of the chapter. In such cases, the target attribute of the note may be used to indicate the point of attachment. It is also possible to encode the point of attachment itself, using the ptr or ref element, pointing from that to the body of the note placed elsewhere.

In cases where the note is applied not to a point but to a span of text, not itself represented as a TEI element, the target attribute may use an appropriate pointer expression, for example using the range() function to specify the span of attachment.

For further discussion of pointing to points and spans in the text, see section 3.7 Simple Links and Cross-References.

In the following example, the type attribute is used to categorise the note as a gloss:
<l>The self-same moment I could pray</l>
<l>And from my neck so free</l>
<l>The albatross fell off, and sank</l>
<l>Like lead into the sea.
<note type="gloss" place="margin">The spell begins to break</note>
</l>
As the note appears within an l element, we may infer that its point of attachment is in the margin adjacent to the line in question. In the following version of the same text, however, it may be inferred that the note applies to the whole of the stanza:
<lg>
 <l>The self-same moment I could pray</l>
 <l>And from my neck so free</l>
 <l>The albatross fell off, and sank</l>
 <l>Like lead into the sea.</l>
 <note type="gloss" place="margin">The spell begins to break</note>
</lg>
This type of annotation, very common in the early printed texts which Coleridge may be presumed to be imitating in this case, may also be regarded as providing a heading or descriptive label for the passage concerned. The encoder may therefore prefer to use the label element to represent it, as in the following case:
<lg>
 <l>The self-same moment I could pray</l>
 <l>And from my neck so free</l>
 <l>The albatross fell off, and sank</l>
 <l>Like lead into the sea.</l>
 <label place="margin">The spell begins to break</label>
</lg>
In the following example, a note which appears at the foot of the page in the printed source is given at its point of attachment within the text. The global n attribute is used to indicate the note number:
Collections are ensembles of
distinct entities or objects of any sort.<note n="1" place="bottom">We
explain below why we use the uncommon term
<mentioned>collection</mentioned> instead of the expected
<mentioned>set</mentioned>. Our usage corresponds to the
<mentioned>aggregate</mentioned> of many mathematical writings and to
the sense of <mentioned>class</mentioned> found in older logical
writings.</note> The elements ...

In addition to transcribing notes already present in the copy text, researchers may wish to add their own notes or comments to it. The note element may be used for either purpose, but it will usually be advisable to distinguish the two categories. One way might be to use the type attribute shown above, categorizing notes as authorial, editorial, etc. Where notes derive from many sources, or where a more precise attribution is required, the resp attribute may be used to point to a definition of the person or other agency responsible for the content of the note.

As a simple example, an edition of the Ancient Mariner might include both Coleridge's original glosses and those of a modern commentator:
<lg>
<!-- ... -->
 <l>The self-same moment I could pray;
 <note place="margin" resp="#STC"
   type="gloss">The spell begins to break</note>
  <note place="bottom" resp="#JLL">The turning point of the poem...</note>
 </l>
</lg>
For this to be valid, the codes #JLL and #STC must point to some more information identifying the agency concerned. The syntax used is identical to that used for other cross-references, as discussed in 3.7 Simple Links and Cross-References; thus in this case, the TEI header for this text might contain a title statement like the following:
<titleStmt>
 <title>The Rime of the Ancient Mariner: an annotated edition</title>
 <author xml:id="STC">Samuel Taylor Coleridge</author>
 <editor xml:id="JLL">John Livingston Lowes</editor>
</titleStmt>

When annotating the electronic text by means of analytic notes in some structured vocabulary, e.g. to specify the topics or themes of a text, the span and interp elements may be more effective than the free form note element; these elements are available when the module for simple analysis is selected (see section 17.3 Spans and Interpretations).

3.9.1.1 Encoding Grouped Notes

The following element is provided for the grouping of notes:

A text may have multiple alternative versions of the same note, such as the same annotation expressed in multiple languages, or both an extensive note and a short form for different audiences. In such cases multiple note elements may be grouped within a noteGrp element.

Typically, the note elements within a noteGrp would be differentiated by use of attributes such as xml:lang or type, while sharing the same point of attachment. This differentiation can be made either implicitly in case of inline notes, or explicitly via a target attribute, which may be specified on the noteGrp itself.

The simple example below demonstrates the grouping of a short and a full version of the same note, where the short version might be intended for use in contexts with space constraints.
<p>... reuerendos dominos archiepiscopum et canonicos Leopolienses
in duplicibus Quatuortemporibus
<noteGrp>
  <note type="short">Quatuor Tempora, so called dry fast days.</note>
  <note type="full">Quatuor Tempora, so called dry fast days (Wednesday, Friday, and Saturday)
     falling on each of the quarters of the year. In the first quarter they were called Cinerum
     (following Ash Wednesday), second Spiritus (following Pentecost), third Crucis
     (after the Exaltation of the Holy Cross, September 14th), and Luciae
     in the fourth (after the feast of St. Lucia, December 13th).
  </note>
 </noteGrp>
totaliter expediui.
</p>

3.9.2 Index Entries

The indexing of scholarly texts is a skilled activity, involving substantial amounts of human judgment and analysis. It should not therefore be assumed that simple searching and information retrieval software will be able to meet all the needs addressed by a well-crafted manual index, although it may complement them for example by providing free text search. The role of an index is to provide access via keywords and phrases which are not necessarily present in the text itself, but must be added by the skill of the indexer.

3.9.2.1 Pre-existing Indexes
When encoding a pre-existing text, therefore, if such an index is present it may be advisable to retain it along with the text, rather than attempt to regenerate it automatically. Elements discussed elsewhere in these Guidelines may be used for this purpose. For example, the div1 element or div element may be used to mark the section of the text containing the index and the list element might be used to mark the index itself, each entry being represented by an item element, possibly containing within it a series of ptr or ref elements, as follows:
<div type="index">
<!--...-->
 <list type="index">
  <item>Women, how cause of mel. <ref>193</ref>; their vanity in
     apparell taxed, <ref>527</ref>; their counterfeit tears
  <ref>547</ref>; their vices <ref>601</ref>, commended,
  <ref>624</ref>.</item>
  <item>Wormwood, good against mel. <ref>443</ref>
  </item>
  <item>World taxed, <ref>181</ref>
  </item>
  <item>Writers of the cure of mel. 295</item>
<!--...-->
 </list>
</div>
Note that this simple representation does not capture the nested structure of the first of these index entries. A more accurate representation might entail the use of nested lists like the following:
<item>Women,
<list>
  <item>how cause of mel. <ref>193</ref>;</item>
  <item>their vanity in apparell taxed, <ref>527</ref>;</item>
  <item>their counterfeit tears <ref>547</ref>;</item>
  <item>their vices
  <list>
    <item>
     <ref>601</ref>,</item>
    <item> commended, <ref>624</ref>.</item>
   </list>
  </item>
 </list>
</item>
The page references, encoded simply as ref elements above, might also include direct links to the appropriate location in the encoded text, using (for example) a target attribute to supply the identifier of an associated page break element:

<!-- in the text --><pb xml:id="P624"/>
<!-- start of page 624 -->
<!-- in the index -->
<ref target="#P624">624</ref>
For further discussion of this and alternative ways of encoding such links see the discussion in section 16 Linking, Segmentation, and Alignment. Note that similar methods may also be used to encode a table of contents, as further exemplified in section 4.5 Front Matter.
3.9.2.2 Auto-generated Indexes

It can also be useful, however, to generate a new index from a machine-readable text, whether the text is being written for the first time with the tags here defined, or as an addition to a text transcribed from some other source. Depending on the complexity of the text and its subject matter, such an automatically-generated index may not in itself satisfy all the needs of scholarly users. However it can assist a professional indexer to construct a fully adequate index, which might then be post-edited into the digital text, marked-up along the lines already suggested for preserving pre-existing index material.

Indexes generally contain both references to specific pages or sections and references to page ranges or sequences. The same element is used in either case:

  • index (색인 표제 항목) 어떤 목적으로 사용할 수 있도록, 색인된 위치를 표지한다.

Like the interp element described in 17.3 Spans and Interpretations this element may be used simply to provide descriptive or interpretive label of some kind for any location within a text, to be processed in any way by analytic software, but its main purpose is to facilitate the generation of an index for a printed version of the text. An index element may be placed anywhere within a text, between or within other elements. The headwords to be used when making up this index are given by the term elements within the index element. The location of the generated index might be specified by means of a processing instruction within the text, such as the following (the exact form of the PI is of course dependent on the application software in use): 

<?tei indexplacement ?>⚓

Alternatively, the special purpose divGen element might be used.

In the simplest case, a single headword is supplied by a term element contained by an index element:
<p>The students understand procedures for Arabic lemmatisation
<index>
  <term>Lemmatization, Arabic</term>
 </index>and are beginning to build parsers.</p>

The effect of this is to document an index entry for the term ‘Lemmatization, Arabic’, which when processed could reference the location of the original index element.

If the subject of Arabic lemmatization is treated at length in a text, then the index entry generated may need to reference a sequence of locations (e.g. page numbers). In such a case it will be necessary to identify the end of the relevant span of text as well as its starting point. This is most conveniently done by supplying an empty anchor element (as discussed in chapter 16 Linking, Segmentation, and Alignment) at the appropriate point and pointing to it from the index element by means of its spanTo attribute, as in this example:
<p>We now turn to the
topic of Arabic lemmatisation
<index spanTo="#ALAMEND">
  <term>Lemmatization, Arabic</term>
 </index> concerning which it is important to note [...]

<!-- much learned material omitted here -->
and now we can build our parser.<anchor xml:id="ALAMEND"/>
</p>

This would generate the same index entries as the previous example, but the reference would be to the whole span of text between the location of the index element and the location of the element identified by the code ALAMEND, rather than a single point, and thus might (for example) include a sequence of page numbers.

Although the position of the index element in the text provides the target location that will be specified in the generated index entry, no part of the text itself is used to construct that entry. Index terms appearing in the entry come solely from the content of term elements, which consequently may have to repeat words or phrases from the text proper. This need not be done verbatim, thus giving scope for normalization of spelling (as in the example above) or other modifications which may assist generation of an index in a desired form or sequence.

Sometimes, for example when index terms are taken from a different language or consist of mathematical formulae or other expressions, even a normalized form of an index term may be insufficient for an application to order it exactly as desired. The sortKey attribute may be used to address this problem, as in the following example:
<p>The @ operator
<index>
  <term sortKey="0000">@</term>
 </index> precedes an
attribute name</p>
Here, an entry for the symbol @ will appear in the index, but will be sorted alphabetically as if it were the string 0000. This technique is also useful when an index entry is to contain some non-Unicode character or glyph represented by the g element discussed in chapter 5 Characters, Glyphs, and Writing Modes. In the following example, we assume that somewhere a definition for this glyph has been provided using the elements described in chapter 5 Characters, Glyphs, and Writing Modes, and given the code PrinceGlyph:
<char xml:id="PrinceGlyph">
<!-- definition of the glyph here -->
</char>
<p>The Artist formerly known as Prince <index>
  <term sortKey="Prince">
   <g ref="#PrinceGlyph"/>
  </term>
 </index>...</p>
Note that if no value is supplied for the sortKey attribute, a sorting application should always use the content of the term element as a sort key.
It is common practice to compile more than one index for a given text. A biography of a poet, for example, may offer an index of references to poems by the subject of the study, another index of works by other writers, an index of places or historical personages etc. The indexName attribute is used to assigning index terms and locations to one or more specific indexes:
<p>Sir John Ashford
<index indexName="INDEX-PERSONS">
  <term>Ashford, John</term>
 </index> was,
coincidentally, born in
<index indexName="INDEX-PLACES">
  <term>Ashford
     (Kent)</term>
 </index>Ashford...</p>
Multi-level indexing is particularly common in scholarly documents. For example, as well as entries such as TEI, or markup, an index may contain structured entries like TEI, markup practices, index terms, where a top level entry TEI is followed by a number of second-level subcategories, any or all of which may have a third-level list attached to them and so on. In order to reflect such a hierarchical index listing, index elements may be nested to the required depth. For example, suppose that we wish to make a structured index entry for ‘lemmatisation’ with subentries for ‘Arabic’, ‘Sanskrit’, etc. The example at the start of this section might then be encoded with nested index elements:
<p>The students understand procedures for Arabic lemmatisation
<index>
  <term>lemmatization</term>
  <index>
   <term>arabic</term>
  </index>
 </index>
...</p>
The index entry from Burton's Anatomy of Melancholy quoted above might be generated in a similar way. To generate such an entry, the body of the text might include, at page 193, an index element such as
<index>
 <term>Women</term>
 <index>
  <term>how cause of mel.</term>
 </index>
</index>
. Similarly, page 601 of the body text would include an index element like the following:
<index>
 <term>Women</term>
 <index>
  <term>their vices</term>
 </index>
</index>
while the index element at page 624 would have a structure like the following:
<index>
 <term>Women</term>
 <index>
  <term>their vices</term>
  <index>
   <term>commended</term>
  </index>
 </index>
</index>

When processing such index elements, the duplication required to make the structure explicit will normally be removed, so as to produce entries like those quoted above. However, this is not required by the encoding recommended here.

As noted above, either a processing instruction or a divGen element may be used to mark the place at which an index generated from index elements should be inserted into the output of a processing program; typically but not necessarily this will be at some point within the back matter of the document. If the divGen element is used, then the type attribute should be used to specify which kind of index is to be generated, and its value should correspond with that of the indexName attribute on the relevant index elements.
<back>
 <div type="appendix">
  <head>Bibliography</head>
  <listBibl>
   <bibl> ... </bibl>
  </listBibl>
 </div>
 <divGen n="Index Nominum"
  type="INDEX-NAMES"/>
 <divGen n="Index Loci" type="INDEX-PLACES"/>
</back>
As this example shows, the global n attribute may also be used to specify a name or identifier for the generated index itself in the usual way. Any additional headings etc. required for the generated index must be specified as content of the divGen element.
<back>
 <divGen n="A1" type="INDEX-NAMES">
  <head>An Index of Names</head>
 </divGen>
</back>

If a processing instruction is used, then these parameters for the generated index may be supplied in some other way.

One final feature frequently found in manually-created indexes to printed works cannot readily be encoded by the means provided here, namely cross-references internal to the index term listing. For example, if all references to the TEI in a text have been indexed using the index term Text Encoding Initiative, it may also be helpful to include an entry under the term TEI containing some text such as ‘see Text Encoding Initiative’. Such internal cross-references must be added as part of the post-editing phase for an auto-generated index.

3.10 Graphics and Other Non-textual Components

Graphics, such as illustrations or diagrams, appear in many different kinds of text, and often with different purposes. Audio or video clips may also appear. In some cases, such media form an integral part of a text (indeed, some texts—comic books for example—may be almost entirely graphic); in others the graphic or video may be a kind of optional extra. In some cases, the text may be incomprehensible unless the media is included; in others, the presence of the media adds little to the sense of the work. It will therefore be a matter of encoding policy as to whether or how media found in a source text are transferred to a new encoded version of the same. In documents which are ‘born digital’, media such as graphics and other non-textual components may be particularly salient, but their inclusion in an archival form of the document concerned remains an editorial decision.

Considered as structural components, media may be anchored to a particular point in the text, or they may float either completely freely, or within some defined scope, such as a chapter or section. Time-based media such as audio or video may need to be synchronized with particular parts of a written text. Media of all kinds often contain associated text such as a heading or label. These Guidelines provide the following different elements to indicate their appearance within a text:

  • figure (figure) 삽화 또는 그림과 같은 시각 정보를 표시하거나 포함하는 요소를 모아 놓는다.
  • media indicates the location of any form of external media such as an audio or video clip etc.
  • graphic (graphic) 인라인 그래픽, 삽화, 또는 도형의 위치를 표시한다.
  • binaryObject 인라인 그래픽 또는 다른 개체를 표상하는 부호화된 이진 데이터를 제시한다.

Media files may be encoded in a number of different ways:

  • in some non-XML or binary format such as PNG, JPEG, MP3, MP4 etc.
  • in an XML format such as SVG
  • in a TEI XML format such as the notation for graphs and trees described in 19 Graphs, Networks, and Trees

In the last two cases, the presence of the graphic will be indicated by an appropriate XML element, drawn from the SVG namespace in the second case, and its content will fully define the graphic to be produced. In the first case, however, one of the elements graphic or media is used to mark the presence of the graphic only and the visual content itself is stored outside the XML document at a location referenced by means of a url attribute. This attribute is provided by membership of these elements in the att.resourced class. Alternatively, if it is small, the media information may be embedded directly within the document using some suitable binary format such as Base64; in this case the binaryObject element may be used to contain it.

The elements graphic, media, and binaryObject are made available as members of the class model.graphicLike when this module is included in a schema. These elements are also members of the class att.media, from which they inherit the following attributes:

  • att.internetMedia 표준 분류법을 사용하는 컴퓨터 자원의 유형을 명시하는 속성을 제시한다.
    mimeType(MIME 매체 유형) 적용 가능한 다중매체 인터넷 메일 확장자(MIME) 매체 유형을 명시한다.
  • att.media provides attributes for specifying display and related properties of external media.
    widthWhere the media are displayed, indicates the display width
    heightWhere the media are displayed, indicates the display height
    scaleWhere the media are displayed, indicates a scale factor to be applied when generating the desired display size
For example, the following passage indicates that a copy of the image found in the source text may be recovered from the URL zigzag2.png and that this image is in PNG format:
<p>These were the four lines I moved in
through my first, second, third, and
fourth volumes. -- In the fifth volume
I have been very good, -- the precise
line I have described in it being this:
<graphic url="zigzag2.png"
  mimeType="image/png"/>
By which it appears, that except at the
curve, marked A. where I took a trip
to Navarre, -- and the indented curve B.
which is the short airing when I was
there with the Lady Baussiere and her
page, -- I have not taken the least frisk
...</p>
The media elements are phrase level elements which may be used anywhere that textual content is permitted, within but not between paragraphs or headings. In the following example, the encoder has decided to treat a specific printer's ornament as a heading:
<head>
 <graphic url="http://www.iath.virginia.edu/gants/Ornaments/Heads/hp-ral02.gif"/>
</head>
.

The figure element discussed in 14.4 Specific Elements for Graphic Images provides additional capabilities, for example the ability to combine a number of images into a hierarchically organized structure or a block of images. The figure element carries a type attribute, which can be used to distinguish different kinds of graphic component within a single work, for example, maps as opposed to illustrations. It also provides the ability to associate an image with additional information such as a heading or a description.

3.11 Reference Systems

By reference system we mean the system by which names or references are associated with particular passages of a text (e.g. Ps. 23:3 for the third verse of Psalm 23 or Amores 2.10.7 for Ovid's Amores, book 2, poem 10, line 7). Such names make it possible to mark a place within a text and enable other readers to find it again. A reference system may be based on structural units (chapters, paragraphs, sentences; stanza and verse), typographic units (page and line numbers), or divisions created specifically for reference purposes (chapter and verse in Biblical texts). Where one exists, the traditional reference system for a text should be preserved in an electronic transcript of it, if only to make it easier to compare electronic and non-electronic versions of the text.

Reference systems may be recorded in TEI-encoded texts in any of the following ways:

  • where a reference system exists, and is based on the same logical structure as that of the text's markup, the reference for a passage may be recorded as the value of the global xml:id or n attribute on an appropriate tag, or may be constructed by combining attribute values from several levels of tags, as described below in section 3.11.1 Using the xml:id and n Attributes.
  • where there is no pre-existing reference system, the global xml:id or n attributes may be used to construct one (e.g. collections and corpora created in electronic form), as described below in section 3.11.2 Creating New Reference Systems.
  • where a reference system exists which is not based on the same logical structure as that of the text's markup (for example, one based on the page and line numbers of particular editions of the text rather than on the structural divisions of it), any of a variety of methods for encoding the logical structure representing the reference system may be employed, as described in chapter 20 Non-hierarchical Structures.
  • where a reference system exists which does not correspond to any particular logical structure, or where the logical structure concerned is of no interest to the encoder except as a means of supporting the referencing system, then references may be encoded by means of milestone elements, which simply mark points in the text at which values in the reference system change, as described below in section 3.11.3 Milestone Elements.

The specific method used to record traditional or new reference systems for a text should be declared in the TEI header, as further described in section 3.11.4 Declaring Reference Systems and in section 16.2.5 Canonical References.

When a text has no pre-existing associated reference system of any kind, these Guidelines recommend as a minimum that at least the page boundaries of the source text be marked using one of the methods outlined in this section. Retaining page breaks in the markup is also recommended for texts which have a detailed reference system of their own. Line breaks in prose texts may be, but need not be, tagged.17

3.11.1 Using the xml:id and n Attributes

When traditional reference schemes represent a hierarchical structuring of the text which mirrors that of the marked-up document, the n attribute defined for all elements may be used to indicate the traditional identifier of the relevant structural units. The n attribute may also be used to record the numbering of sections or list items in the copy text if the copy-text numbering is important for some reason, for example because the numbers are out of sequence.

For example, a traditional reference to Ovid's Amores might be Amores 2.10.7—book 2, poem 10, line 7. Book, poem, and line are structural units of the work and will therefore be tagged in any case. (See chapter 6 Verse for a discussion of structural units in verse collections.) In such cases, it is convenient to record traditional reference numbers of the structural units using the n attribute. The relevant tags for our example would be:
<div1 n="Amores" type="volume">
 <div2 n="1" type="book">
<!-- ... -->
 </div2>
 <div2 n="2" type="book">
  <div3 n="1" type="poem">
<!-- ... -->
  </div3>
  <div3 n="2" type="poem">
<!-- ... -->
  </div3>
<!-- ... -->
  <div3 n="10" type="poem">
   <l n="1"> ... </l>
   <l n="2"> ... </l>
<!-- ... -->
   <l n="7"> ... </l>
  </div3>
<!-- ... -->
 </div2>
<!-- ... -->
</div1>
One may also place the entire standard reference for each portion of the text into the appropriate value for the n attribute, though for obvious reasons this takes more space in the file:
<div1 n="Amores" type="volume">
 <div2 n="Amores 1" type="book">
<!-- ... -->
 </div2>
 <div2 n="Amores 2" type="book">
  <div3 n="Amores 2.1" type="poem">
<!-- ... -->
  </div3>
<!-- ... -->
  <div3 n="Amores 2.10" type="poem">
<!-- ... -->
   <l n="Amores 2.10.7"> ... </l>
<!-- ... -->
  </div3>
<!-- ... -->
 </div2>
<!-- ... -->
</div1>
If the names used by the traditional reference system can be formulated as identifiers, then the references can be given as values for the xml:id attribute; this requires that the reference be given without internal spaces, begin with a letter or underscore, and contain no characters other than letters, digits, hyphens, underscores, full stops, and the various combining and extender characters, as defined by the XML specification. Unlike values for the n attribute, values for the xml:id attribute must be unique throughout the document. Our example then looks like this:
<div1 n="Amores" type="volume">
 <div2 xml:id="am.1" type="book">
<!-- ... -->
 </div2>
 <div2 xml:id="am.2" type="book">
  <div3 xml:id="am.2.1" type="poem">
<!-- ... -->
  </div3>
<!-- ... -->
  <div3 xml:id="am.2.10" type="poem">
<!-- ... -->
   <l xml:id="am.2.10.7"> ... </l>
<!-- ... -->
  </div3>
<!-- ... -->
 </div2>
<!-- ... -->
</div1>

To document the usage and to allow automatic processing of these standard references, it is recommended that the TEI header be used to declare whether standard references are recorded in the n or xml:id attributes and which elements may carry standard references or portions of them. For examples of declarations for the reference systems just shown, see section 3.11.4 Declaring Reference Systems.

Using the n attribute one can specify only a single standard referencing system, a limitation not without problems, since some editions may define structural units differently and thus create alternative reference systems. For example, another edition of the Amores considers poem 10 a continuation of poem 9, and therefore would specify the same line as Amores 2.9.31. In order to record both of these reference systems one could employ any of a variety of methods discussed in chapter 20 Non-hierarchical Structures.

3.11.2 Creating New Reference Systems

If a text has no canonical reference system of its own, a new custom reference system may be used.

The global attributes n and xml:id may be used to assign reference identifiers to segments of the text. Identifiers specified by either attribute apply to the entire element for which they are given. xml:id attributes must be unique within a single document, and xml:id values must begin with a letter. No such restrictions are made on the values of n attributes.

Determining a referencing system for a TEI encoding depends on many factors that may either be derived from textual structure, or influenced by extra-textual contingencies such as project and file management concerns. It is important, therefore, that the attribute used, the elements which can bear standard reference identifiers, and the method for constructing standard reference identifiers, should all be declared in the header as described in section 2.3.6 The Reference System Declaration.

The Guidelines do not recommend one specific method for creating new referencing systems; however, the rest of this section lists some possibly useful strategies.

3.11.2.1 Referencing system derived from markup

A new referencing system may be derived from the structure of the electronic text, specifically from the markup of the text. As with any reference system intended for long-term use, it is important to see the reference as an established, unchanging point in the text. Should the text be revised or rearranged, the reference-system identifiers associated with any section of text must stay with that section of text, even if it means the reference numbers fall out of sequence. (A new reference system may always be created beside the old one if out-of-sequence numbers must be avoided.)

A convenient method of mechanically generating unique values for xml:id or n attributes based on the structure of the document is to construct, for each element, a domain-style address comprising a series of components separated by full stops, with one component for each level of the document hierarchy. Two methods may be used. In the typed path form of identifier, each component in the identifier takes the form of an element identifier, a hyphen, and a number, for example p-2. The element name specifies what type of element is to be sought, and the number specifies which occurrence of that element type is to be selected. (The hyphen and number may be omitted if there is only one element of the given type.) In the untyped path form of identifier, each component consists of a number, indicating which element in the sequence of nodes at each level is to be selected. To make the resulting identifier a valid XML identifier, it may need to be prefixed with an unchanging alphabetic letter.

Identifiers generated with these methods should use the text element as their starting point, rather than the TEI or body elements. The TEI element may be taken as a starting point only if identifiers need to be generated for the teiHeader, which is not usually the case; using the body element as a root would prevent assignment of identifiers for the front and back matter. The component corresponding to the root element can be omitted from identifiers, if no confusion will result. In collections and corpora, the component corresponding to the root may be replaced by the unique identifier assigned to the text or sample.

In the following example, each element within the text element has been given a typed-path identifier as its xml:id value, and an untyped-path identifier as its n value; the latter are prefixed with the string AB, which may be imagined to be the general identifier for this text.
<text xml:id="Text-1" n="AB">
 <front xml:id="Front" n="AB.1">
  <div xml:id="Front.div-1" n="AB.1.1">
   <p> ... </p>
  </div>
  <titlePage xml:id="Front.titlePage"
   n="AB.1.2">
   <titlePart> ... </titlePart>
  </titlePage>
  <div xml:id="Front.div-2" n="AB.1.3">
   <p> ... </p>
  </div>
 </front>
 <body xml:id="Body" n="AB.2">
  <p xml:id="Body.p-1" n="AB.2.1"> ... </p>
  <p xml:id="Body.p-2" n="AB.2.2"> ... </p>
  <div xml:id="Body.div-1" n="AB.2.3">
   <head xml:id="Body.div-1.head"
    n="AB.2.3.1"> ... </head>
   <p xml:id="Body.div-1.p-1" n="AB.2.3.2"> ... </p>
   <p xml:id="Body.div-1.p-2" n="AB.2.3.3"> ... </p>
  </div>
  <div xml:id="Body.div-2" n="AB.2.4">
   <head xml:id="Body.div-2.head"
    n="AB.2.4.1"> ... </head>
   <p xml:id="Body.div-2.p-1" n="AB.2.4.2"> ... </p>
   <p xml:id="Body.div-2.p-2" n="AB.2.4.3"> ... </p>
  </div>
 </body>
</text>
The typed and untyped path methods are convenient, but are in no way required for anyone creating a reference system.

If the xml:id attribute is used to record the reference identifiers generated, each value should record the entire path. If the n attribute is used, each value may record either the entire path or only the subpath from the parent element. The attribute used, the elements which can bear standard reference identifiers, and the method for constructing standard reference identifiers, should all be declared in the header as described in section 2.3.6 The Reference System Declaration.

3.11.2.2 Referencing systems based on project conventions

A reference system may be based on an agreed project-specific convention for xml:id attributes. Every convention will have strengths and weaknesses and it is left to encoders to make a decision that enables them to locate information in their TEI document.

Here are some examples of referencing systems that have been used in TEI project:

  • Title-based identifiers: identifiers constructed with a number of characters from the main document title, followed by an incremental number. E.g. HOL001, HOL002, etc. using a fixed number of digits; or without fixed digits: HOL1, HOL2, etc.
  • Based on markup, with prefix: identifiers constructed on the markup itself, as described in the previous section. To facilitate uniqueness in a corpus, each identifier may be prefixed with the identifier of the root TEI element. E.g. RootID-Body-p-1.
  • Opaque identifiers: computed identifiers using either a randomized algorithm or a universally unique identifier (UUID) algorithm. Note that XSLT's function generate-id() only guarantees identifier unique to the document being processed.

XML well-formedness requires only that xml:id attributes be unique within a single document. However, it is also worth keeping in mind that for operating with referencing systems across a corpus of TEI files it is helpful (or even necessary in some circumstances) to have unique identifiers across the whole corpus.

Values of xml:id may be either populated computationally or manually. In the latter case, it is advisable to put measures in place to avoid human error. Custom data types and Schematron rules may be defined in a customization ODD, and a check digit may be added to prevent unwanted changes. 18

3.11.3 Milestone Elements

Where the desired reference system does not correspond to any particular structural hierarchy, or the document combines multiple structural hierarchies (as further discussed in 20 Non-hierarchical Structures), simpler though less expressive methods may be necessary. In such cases the simplest solution may be just to mark up changes in the reference system where they occur, by using one or more of the following milestone elements:

  • milestone (milestone) 텍스트의 절을 분할하는 경계점을 표지한다. 이는 표준 참조 시스템에서의 변화로 표시되며, 구조적 요소에 의해서는 표시되지 않는다.
  • gb (gathering beginning) marks the beginning of a new gathering or quire in a transcribed codex.
  • pb (페이지 바꿈) 표준 참조 시스템에서 텍스트 페이지와 다음 페이지 사이의 경계를 표지한다.
  • lb (행 바꿈) 텍스트의 편집 또는 버전에서 새로운 (인쇄상의) 행 시작을 표지한다.
  • cb (열 바꿈) 표준 참조 시스템에서 텍스트의 한 열과 다음 열 사이의 경계를 표지한다.

These elements simply mark the points in a text at which some category in a reference system changes. They have no content but subdivide the text into regions, rather in the same way as milestones mark points along a road, thus implicitly dividing it into segments. The elements gb, pb, cb, and lb are specialized types of milestone, marking gathering, page, column, and line boundaries respectively. The global n attribute is used in each case to provide a value for the particular unit associated with this milestone (for example, the page or line number). Since it is not structural, validation of a reference system based on milestones cannot readily be checked by an XML parser, so it will be the responsibility of the encoder or the application software to ensure that they are given in the correct order.

Milestone elements are often used as a simple means of capturing the original appearance of an early printed text, which will rarely coincide exactly with structural units, but they are generally useful wherever a text has two or more competing structures. For example, many English novels were first published as serial works, individual parts of which do not always contain a whole number of chapters. An encoder might decide to represent the chapter-based structure using div1 elements, with milestone elements to mark the points at which individual parts end; or the reverse. Thus, an encoding in which chapters are regarded as more important than parts might encode some work in which chapter three begins in part one and is concluded in part two as follows:
<text>
 <body>
  <milestone unit="part" n="1"/>
  <div1 n="1" type="chapter">
   <p>
<!-- ... -->
   </p>
  </div1>
  <div1 n="2" type="chapter">
   <p>
<!-- ... -->
   </p>
  </div1>
  <div1 n="3" type="chapter">
   <p>
<!-- ... -->
   </p>
   <milestone unit="part" n="2"/>
   <p>
<!-- ... -->
   </p>
  </div1>
 </body>
</text>
An encoding of the same work in which parts are regarded as more important than chapters might begin as follows:
<text>
 <body>
  <div1 n="1" type="part">
   <milestone unit="chapter" n="1"/>
   <p>
<!-- ... -->
   </p>
   <milestone unit="chapter" n="2"/>
   <p>
<!-- ... -->
   </p>
   <milestone unit="chapter" n="3"/>
   <p>
<!-- ... -->
   </p>
  </div1>
  <div1 n="2" type="part">
   <p>
<!-- ... -->
   </p>
   <milestone unit="chapter" n="4"/>
   <p>
<!-- ... -->
   </p>
  </div1>
 </body>
</text>
Similarly, when tagging dramatic verse one may wish to privilege stanzas and lines over speeches and speakers, particularly where speeches cross line and line group boundaries. One might also wish to mark changes in narrative voice in a prose text. In either case, a milestone tag may be used to indicate change of speaker:
<lg>
 <milestone unit="speaker" n="Man"/>
 <l>Oh what is this I cannot see</l>
 <l>With icy hands gets a hold on me</l>
 <milestone unit="speaker" n="Death"/>
 <l>Oh I am Death, none can excel</l>
 <l>I open the doors of heaven and hell</l>
</lg>

Milestone tags also make it possible to record the reference systems used in a number of different editions of the same work. The reference system of any one edition can be recreated from a text in which all are marked by simply ignoring all elements that do not specify that edition on their ed attribute.

As a simple example, assuming that edition E1 of some collection of poems regards the first two poems as constituting the first book, while edition E2 regards the first poem as prefatory, a markup scheme like the following might be adopted:
<milestone ed="E1" unit="work"/>
<milestone ed="E2" unit="work"/>
<milestone ed="E1" unit="book"/>
<milestone ed="E1" unit="poem"/>
<milestone ed="E2" unit="poem"/>
<milestone ed="E2" unit="book"/>
<milestone ed="E1" unit="poem"/>
<milestone ed="E2" unit="poem"/>

In this case no n value is specified, since the numbers rise predictably and the application can keep a count from the start of the document, if desired.

The value of the n attribute may but need not include the identifiers used for any larger sections. That is, either of the following styles is legitimate:
<milestone ed="E1" unit="work" n="Amores"/>
<milestone ed="E1" unit="book" n="1"/>
<milestone ed="E1" unit="poem" n="1"/>
<milestone ed="E1" unit="poem" n="2"/>
<milestone ed="E1" unit="book" n="2"/>
or
<milestone ed="E1" unit="work" n="Amores"/>
<milestone ed="E1" unit="book" n="1"/>
<milestone ed="E1" unit="poem" n="1.1"/>
<milestone ed="E1" unit="poem" n="1.2"/>
<milestone ed="E1" unit="book" n="2"/>

When using milestone tags, line numbers may be supplied for every line or only periodically (every fifth, every tenth line). The latter may be simpler; the former is more reliable.

The style of numbering used in the values of n is unrestricted: for the example above, I.i, I.ii, and I.iii could have been used equally well if preferred. The special value unnumbered should be reserved for marking sections of text which fall outside the normal numbering system (e.g. chapter heads, poem numbers, titles, or speaker attributions in a verse drama).

By default, there are no constraints on the values supplied for the ed attribute. If it is felt appropriate to enforce such a restriction, the techniques described in 23.3 Customization may be used, for example to specify that the attribute must specify one of a predefined set of values.

See below, section 3.11.4 Declaring Reference Systems, for examples of declarations for the reference systems just shown.

Milestone elements may be used to mark any kind of shift in the properties associated with a piece of text, whether or not would normally be considered a reference system. For example, they may be used to mark changes in narrative voice in a prose text, or changes of speaker in a dramatic text, where these are not marked using structural elements such as sp, perhaps in order to avoid a clash of hierarchies.

As noted in 3.2.2 Hyphenation above, milestone elements such as lb or pb represent whitespace and are therefore by default assumed to occur between orthographic tokens in the text, where these are not otherwise indicated. By default it is reasonable to assume that words are not broken across page or line boundaries, and that therefore a sequence such as
...sed imp<lb/>erator dixit...
should be tokenized as four words (sed, imp, erator, and dixit). The break attribute is provided to change the default assumption. To make explicit that imperator in the above example should be treated as a single word, a tagging such as the following is recommended:
...sed imp<lb break="no"/>erator dixit...
Where hyphenation appears before a line or page break, the encoder may or may not choose to record the fact, either explicitly using an appropriate Unicode character, or descriptively for example by means of the rend attribute; see further 3.2.2 Hyphenation.

3.11.4 Declaring Reference Systems

Whatever kind of reference system is used in an electronic text, it is recommended that the TEI header contain a description of its construction in the refsDecl element described in section 2.3.6 The Reference System Declaration. As described there, the declaration may consist either of a formal declaration using the cRefPattern or citeStructure elements, or an informal description in prose. One of the former is recommended because unlike prose they can be processed by software.

The three examples given in section 3.11.1 Using the xml:id and n Attributes would be declared as follows. The first example encodes the standard references for Ovid's Amores one level at a time, using the n attribute on the div1, div2, div3, and l tags. The header section for such an encoding should look something like this:
<encodingDesc>
 <refsDecl>
  <cRefPattern matchPattern="([^ ]+) ([0-9]+)\.([0-9]+)\.([0-9]+)"
   replacementPattern="#xpath(//div1[@n='$1']/div2[@n='$2']/div3[@n='$3']/l[@n='$4']">
   <p>A canonical reference is assembled with
   <list>
     <item>the name of the <label>work</label>: the
     <att>n</att> of a <gi>div1</gi>,</item>
     <item>a space,</item>
     <item>the number of the <label>book</label>: the
     <att>n</att> of a child <gi>div2</gi>,</item>
     <item>a full stop</item>
     <item>the number of the <label>poem</label>: the
     <att>n</att> of a child <gi>div3</gi>,</item>
     <item>the line number: the <att>n</att> value of a
           child <gi>l</gi>
     </item>
    </list>
   </p>
  </cRefPattern>
  <cRefPattern matchPattern="([^ ]+) ([0-9]+)\.([0-9]+)"
   replacementPattern="#xpath(//div1[@n='$1']/div2[@n='$2']/div3[@n='$3']">
   <p>Same as above, but without the last component (full
       stop followed by the <gi>l</gi>'s <att>n</att>.</p>
  </cRefPattern>
  <cRefPattern matchPattern="([^ ]+) ([0-9]+)"
   replacementPattern="#xpath(//div1[@n='$1']/div2[@n='$2']">
   <p>Same as above, but without the poem component (full
       stop followed by the <gi>div3</gi>'s <att>n</att>.</p>
  </cRefPattern>
 </refsDecl>
</encodingDesc>
The second example encodes the same reference system, again using the n attribute on the div1, div2, div3, and l tags, but giving the reference string in full on each tag. If canonical references are made only to lines, the reference system could be declared as follows:
<refsDecl>
 <cRefPattern matchPattern="([^ ]+ [0-9]+\.[0-9]+\.[0-9]+)"
  replacementPattern="#xpath(//l[@n='$1')"/>
</refsDecl>
Since the entire regular expression is enclosed as a parenthetical subgroup, the entire canonical reference string is sought as the value of the n attribute on an l element.
In order to handle references to poems as well as to individual lines, the declaration for the reference system must be more complicated:
<refsDecl>
 <cRefPattern matchPattern="([^ ]+ [0-9]+\.[0-9]+\.[0-9]+)"
  replacementPattern="#xpath(//l[@n='$1')"/>
 <cRefPattern matchPattern="([^ ]+ [0-9]+\.[0-9]+)"
  replacementPattern="#xpath(//div2[@n='$1')"/>
</refsDecl>
This declaration indicates that the entire reference string must be sought as the value of the n attribute on a div1, div2, div3, or l element.
The third example encodes the same reference system, this time giving the entire reference string as the value of the xml:id attribute on the relevant tags. The reference system declaration for such an encoding could be:
<refsDecl>
 <cRefPattern matchPattern="(.*)"
  replacementPattern="#$1"/>
</refsDecl>
although in general there seems to be little advantage in this case: it is no more difficult to use a standard relative URI reference as the value of target.
In cases where a more complete formal declaration of text structure is desirable, for example in systems that will present the contents of a large TEI file in smaller chunks, the citeStructure element may be used. This method permits canonical references to be resolved and also allows them to be extracted, so that, for example, a list of resolvable citations may be generated from the document. The example from the Amores above could be implemented using citeStructure thus:
<refsDecl>
 <citeStructure unit="work" match="//div1"
  use="@n">
  <citeStructure unit="book" match="div2"
   use="@n" delim=" ">
   <citeStructure unit="poem" match="div3"
    use="@n" delim=".">
    <citeStructure unit="line" match="l"
     use="@n" delim="."/>
   </citeStructure>
  </citeStructure>
 </citeStructure>
</refsDecl>
citeStructure also provides a method for attaching informational properties to units of structure, by means of the citeData element. The work, book, and poem divisions above might all have head elements which provide a title for the section. If we wish that information to be extractable, we can use citeData to specify where it is to be found:
<refsDecl>
 <citeStructure unit="work" match="//div1"
  use="@n">
  <citeData property="http://purl.org/dc/terms/title"
   use="head"/>
  <citeStructure unit="book" match="div2"
   use="@n" delim=" ">
   <citeData property="http://purl.org/dc/terms/title"
    use="head"/>
   <citeStructure unit="poem" match="div3"
    use="@n" delim=".">
    <citeData property="http://purl.org/dc/terms/title"
     use="head"/>
    <citeStructure unit="line" match="l"
     use="@n" delim="."/>
   </citeStructure>
  </citeStructure>
 </citeStructure>
</refsDecl>
The example above maps the head element to the Dublin Core property title. For convenience, property URIs may be abbreviated using prefixDef.
Reference systems recorded by means of milestone tags can also be declared; the following prose description could be used to declare the example given in section 3.11.3 Milestone Elements.
<refsDecl>
 <p>Standard references to work, book, poem, and line may be
   constructed from the milestone tags in the text.</p>
</refsDecl>
Or in this way, using a formal declaration for this reference scheme derived from edition E1.
<refsDecl>
 <refState ed="E1" unit="work" delim=" "/>
 <refState ed="E1" unit="book" delim="."/>
 <refState ed="E1" unit="poem" delim=":"/>
 <refState ed="E1" unit="line"/>
</refsDecl>

3.12 Bibliographic Citations and References

Bibliographic references (that is, full descriptions of bibliographic items such as books, articles, films, broadcasts, songs, etc.) or pointers to them may appear at various places in a TEI text. They are required at several points within the TEI header's source description, as discussed in section 2.2.7 The Source Description; they may also appear within the body of a text, either singly (for example within a footnote), or collected together in a list as a distinct part of a text; detailed bibliographic descriptions of manuscript or other source materials may also be required. These Guidelines propose a number of specialized elements to encode such descriptions, which together constitute the model.biblLike class.

  • model.biblLike 서지 기술을 포함하는 요소를 모아 놓는다.
    bibl(서지 인용) 하위 성분이 명시적으로 구분된 또는 그렇지 않은 덜 구조화된 서지 인용을 포함한다.
    biblFull(완전히 구조화된 서지 인용 정보) 완전히 구조화된 서지 정보를 포함하며, 그 안에 TEI 파일 기술의 모든 성분이 제시된다.
    biblStruct(구조화된 서지 인용) 서지의 하위 요소만이 나타나는, 명시적 순서로 구성되는 구조화된 서지 인용을 포함한다.
    listBibl(인용 목록) 여러 종류의 서지 인용 목록을 포함한다.
    msDesc(원고 기술) 하나의 식별가능한 원고에 대한 기술을 포함한다.

Lists of such elements may also be encoded using the following element:

  • listBibl (인용 목록) 여러 종류의 서지 인용 목록을 포함한다.

In printed texts, the individual constituents of a bibliographic reference are conventionally marked off from each other and from the flow of text by such features as bracketing, italics, special punctuation conventions, underlining, etc. In electronic texts, such distinctions are also important, whether in order to produce acceptably formatted output or to facilitate intelligent retrieval processing,19 quite apart from the need to distinguish the reference itself as a textual object with particular linguistic properties.

It should be emphasized that for references as for other textual features, the primary or sole consideration is not how the text should be formatted when it is printed or displayed. The distinctions permitted by the scheme outlined here may not necessarily be all that particular formatters or bibliographic styles require, although they should prove adequate to the needs of many such commonly used software systems.20 The features distinguished and described below (in section 3.12.2 Components of Bibliographic References) constitute a set which has been useful for a wide range of bibliographic purposes and in many applications, and which moreover corresponds to a great extent with existing bibliographic and library cataloguing practice. For a fuller account of that practice as applied to electronic texts see section 2.2.7 The Source Description; for a brief mention of related library standards see section 2.8 Note for Library Cataloguers.

The most commonly used elements in the model.biblLike class are biblStruct and bibl. biblStruct will usually be easier to process mechanically than bibl because its structure is more constrained and predictable. It is suited to situations in which the objective is to represent bibliographic information for machine processing directly by other systems or after conversion to some other bibliographic markup formats such as BibTeXML or MODS. Punctuation delimiting the components of a print citation is not permitted directly within a biblStruct element; instead, the presence and order of child elements must be used to reconstruct the punctuation required by a particular style.

By contrast, bibl allows for considerable flexibility in that it can include both delimiting punctuation and unmarked-up text; and its constituents can also be ordered in any way. This makes it suitable for marking up bibliographies in existing documents, where it is considered important to preserve the form of references in the original document, while also distinguishing important pieces of information such as authors, dates, publishers, and so on. bibl may also be useful when encoding ‘born digital’ documents which require use of a specific style guide when rendering the content; its flexibility makes it easier to provide all the information for a reference in the exact sequence required by the target rendering, including any necessary punctuation and linking words, rather than using an XSLT stylesheet or similar to reorder and punctuate the data.

The third element in the model.biblLike class, biblFull, has a content model based on the fileDesc element of the TEI header. Both are based on the International Standard for Bibliographic Description (ISBD), which forms the basis of several national standards for bibliographic citations. The order of child elements in both biblFull and fileDesc corresponds to the order of bibliographic description ‘areas’ in ISBD with two minor exceptions. First, the extent element, corresponding to the physical description area in ISBD, appears just after the publication, production, distribution, etc. area in ISBD, not before it as in TEI. Second, biblFull and fileDesc use the child element publicationStmt to cover not only the publication, production, distribution, etc. area but also the resource identifier and terms of availability area associated with that publication. Despite these inconsistencies, users encoding citations and attempting to format them according to a standard that closely adheres to ISBD may find that biblFull, used with its child elements and without delimiting punctuation, provides an appropriate granularity of encoding with elements that can easily be rendered for the reader. However, it is important to note that some ISBD-derived citation formats (such as ANSI/NISO Z39.29 and ГОСТ 7.1) are not entirely conformant to ISBD either, since they may begin with a statement of authorship that does not map to the ISBD statement of responsibility.

3.12.1 Methods of Encoding Bibliographic References and Lists of References

The members of the model.biblLike class all share a number of possible component sub-elements. For the bibl and biblStruct elements, exactly the same sub-elements are concerned, and they are described together in section 3.12.2 Components of Bibliographic References; for the biblFull element, the sub-elements concerned are fully described in section 2.2 The File Description.

Different levels of specific tagging may be appropriate in different situations. In some cases, it may be felt necessary to mark just the extent of the reference itself, with perhaps a few distinctions being made within it (for example, between the part of the reference which identifies a title or author and the rest). Such references, containing a mixture of text with specialized bibliographic elements, are regarded as bibl elements, and tagged accordingly. For example:
<p>A book which had a great influence on him
was <bibl>Tufte's <title>Envisioning
     Information</title>
 </bibl>, although he may
never have actually read it.</p>
Indeed, some encoders may find it unnecessary to mark the bibliographic reference at all:
<p>A book which had a great influence on him
was Tufte's <title>Envisioning Information</title>,
although he may never have actually read it.</p>
Some bibliographic references are extremely elliptical, often only a string of the form Baxter, 1983. If no further details of Baxter's book are given in the source text and none is supplied by the encoder, then the reference thus given should be tagged as a bibl:
All of this is of course much more fully treated
in <bibl>Baxter, 1983</bibl>.
In general, however, normal modern bibliographic practice, and these Guidelines, distinguish between a bibliographic reference, which is a self-sufficient description of a bibliographic item, and a bibliographic pointer, which is a short-form citation (e.g. Baxter, 1983) which serves usually as a place-holder or pointer to a full long-form reference found elsewhere in the text. The usual encoding of short-form references such as Baxter, 1983 is not as bibl elements but as cross-references to such elements; see section 3.12.3 Bibliographic Pointers below.
In cases where the encoder wishes to impose more structure on the bibliographic information, for example to make sure it conforms to a particular stylesheet or retrieval processor, the biblStruct element should be used. Note that several of the features in this and later examples are explained later in the current section.
<biblStruct>
 <monogr>
  <author>
   <persName>
    <forename>Edward</forename>
    <forename full="init">R.</forename>
    <surname>Tufte</surname>
   </persName>
   <idno type="scopus">6506403994</idno>
   <idno type="lcaf">http://id.loc.gov/authorites/names/n50012763.html</idno>
  </author>
  <title level="m">Envisioning Information</title>
  <imprint>
   <pubPlace>Cheshire, Conn.</pubPlace>
   <publisher>Graphics Press</publisher>
   <date when="1990"/>
  </imprint>
 </monogr>
</biblStruct>
A more complex and detailed bibliographic structure is provided by the biblFull element defined in the TEI header module. This element is provided as a means of embedding the file description of one existing digital text within that of another (see further section 2.2 The File Description); however, its use is not confined to digital texts, and it may be used in the same way as any other bibliographic element, as in this example:
<biblFull>
 <titleStmt>
  <title>Envisioning Information</title>
  <author>Tufte, Edward R[olf]</author>
 </titleStmt>
 <extent>126 pp.</extent>
 <publicationStmt>
  <publisher>Graphics Press</publisher>
  <pubPlace>Cheshire, Conn. USA</pubPlace>
  <date>1990</date>
 </publicationStmt>
</biblFull>
A list of bibliographic items, of whatever kind, may be treated in the same way as any other list (see section 3.8 Lists). Alternatively, the specialized listBibl element may be used. The difference between the two is that a list contains item elements, within which bibliographic elements (bibl, biblStruct, or biblFull) may appear, as well as other phrase- and paragraph-level elements, whereas the listBibl may contain only bibliographic elements, optionally preceded by a heading and a series of introductory paragraphs. For most purposes, good practice would usually require that a listBibl contain only one kind of bibliographic element, though the following example combines both fully structured biblStruct and informal bibl elements:
<listBibl>    <head>Bibliography</head>    <biblStruct xml:id="NELSON80">       <analytic>         <author>           <persName>             <surname>Nelson</surname>             <forename>Theodore</forename>             <forename>Holm</forename>           </persName>         </author>         <title level="a">Replacing the printed word:              a complete literary system</title>       </analytic>       <monogr>          <title level="m">Information Processing '80:  Proceedings of the IFIPS              Congress, October 1980</title>          <editor>            <persName>              <forename>Simon</forename>              <forename>H.</forename>              <surname>Lavington</surname>            </persName>          </editor>          <imprint>             <publisher>North-Holland</publisher>             <pubPlace>Amsterdam</pubPlace>             <date when="1980"/>          </imprint>          <biblScope unit="page" from="1013"
 to="1023">1013–23</biblScope>       </monogr>       <note>Apparently a draft of section 4 of            <title level="m">Literary Machines</title>.</note>    </biblStruct>      <bibl xml:id="NELSON88"><author><persName><forename>Ted</forename> <surname>Nelson</surname></persName></author>:  <title level="u">Literary Machines</title> (privately published,  <date when="1987">1987</date>).</bibl>      <bibl xml:id="BAXTER88"><author><persName><surname>Baxter</surname>,  <forename>Glen</forename></persName></author>: <title level="m">Glen Baxter His Life: the years of struggle</title>  <pubPlace>London</pubPlace>: <publisher>Thames and Hudson</publisher>,  <date when="1988">1988</date>.</bibl> </listBibl>
This example also demonstrates the way that bibliographical markup of authors, titles, dates etc. can be handled differently in biblStructs and bibls. In the two bibl items, the key information is marked up, but it is presented in an order which makes it suitable for direct rendering, with the punctuation included.
The listBibl element is most appropriate for a more formal bibliography. The same bibl or biblStruct elements may however be embedded within an ordinary list, thus allowing them to be mixed with running prose or presented informally, as in the following version of the same example:
<list>
 <head>Bibliography</head>
 <item>
  <bibl xml:id="NEL80">
   <author>Nelson, T. H.</author>
   <title level="a">Replacing the printed word:
       a complete literary system</title>.
  <title level="m">Information Processing '80:
       Proceedings of the IFIPS Congress, October 1980</title>.
  <editor>Simon H. Lavington</editor>
   <publisher>North-Holland</publisher>:
  <pubPlace>Amsterdam</pubPlace>,
  <date>1980</date>.
  <biblScope>pp 1013–23
   </biblScope>
   <note>Apparently a draft of section 4 of
   <title>Literary Machines</title>.</note>
  </bibl>
 </item>
 <item>
  <bibl xml:id="NEL88">Ted Nelson: <title>Literary Machines</title>
     (privately published, 1987)</bibl>
 </item>
 <item>
  <bibl xml:id="BAX88">
   <author>Baxter, Glen</author>
   <title>Glen Baxter His Life: the years of struggle</title>
     London: Thames and Hudson, 1988.
  </bibl>
 </item>
</list>

3.12.2 Components of Bibliographic References

This section discusses commonly occurring components of bibliographic references and elements used for encoding them. They fall into four groups:

  • elements for grouping components of the analytic, monographic, and series levels in a structured bibliographic reference
  • titles of various kinds, and statements of intellectual responsibility (authorship, etc.)
  • information relating to the publication, pagination, etc. of an item (most of these constitute the default members of the model.biblPart class)
  • annotation, commentary, and further detail

The following sections describe the elements which may be used to represent such information within a bibl or biblStruct element. Within the former, elements from the model.biblPart class, other phrase-level elements, and plain text may be combined without other constraint; within the latter, such of these elements as exist for a given reference must be distinguished, and must also be presented in a specific order, discussed further below (section 3.12.2.9 Order of Components within References).

3.12.2.1 Analytic, Monographic, and Series Levels

In common library practice a clear distinction is made between an individual item within a larger collection and a free-standing book, journal, or collection. Similarly a book in a series is distinguished sharply from the series within which it appears. An article forming part of a collection which itself appears in a series thus has a bibliographic description with three quite distinct levels of information:

  1. the analytic level, giving the title, author, etc., of the article;
  2. the monographic level, giving the title, editor, etc., of the collection;
  3. the series level, giving the title of the series, possibly the names of its editors, etc., and the number of the volume within that series.

In the same way, an article in a journal requires at least two levels of information: the analytic level describing the article itself, and the monographic level describing the journal.

A different identifying number may be supplied for any of these three items, that is, for the analytic item, the monographic item, or the series.

Within bibl, these three levels may be distinguished simply by the use of the level attribute on title. They may also be distinguished through the practice of employing nested bibl elements. In this example, for instance, the monograph-level component of the reference is encapsulated in its own bibl within the main bibl for the article:
<bibl type="article"
 subtype="magazine_article" xml:id="beaupaire_1911">
 <author>
  <name>
   <surname>Beaupaire</surname>
     (<forename>Edmond</forename>)</name>
 </author>,
<title level="a">A propos de la rue de la Femme-sans-Tête</title>,
<bibl type="monogr">
  <title level="j">La Cité</title>,
 <date when="1911-01">janvier 1911</date>, pp. <biblScope unit="page" from="5" to="17">5-17</biblScope>.
 </bibl>
</bibl>

Within biblStruct, the levels are distinguished by the use of the following distinct elements:

  • analytic (분석적 층위) 독립 출판이 아닌, 단행본 또는 학술지 내에 포함되어 출판된 항목(예를 들어, 논문 또는 시)을 기술하는 참고문헌 요소를 포함한다.
  • monogr (단행본 층위) 독립 항목(즉, 독립된 물리적 개체)으로 출판된 항목(예를 들어 단행본 또는 학술지)을 기술하는 참고문헌 요소를 포함한다.
  • series (연간물 정보) 책 또는 다른 참고문헌 항목이 나타나는 연간물 정보를 포함한다.

For purposes of TEI encoding, journals and anthologies are both treated as monographs; a journal title should thus be tagged as a <title level="j"> element within a monogr element. Individual articles in the journal or collected texts should be treated at the ‘analytic’ level. When an article has been printed in more than one journal or collection, the bibliographic reference may have more than one monogr element, each possibly followed by one or more series elements. A series element always relates to the most recently preceding monogr element. (Whether reprints of an article are treated in the same bibliographic reference or a separate one varies among different styles. Library lists typically use a different entry for each publication, while academic footnoting practice typically treats all publications of the same article in a single entry.)

The biblScope element is used to supply further information about the location of some part of a bibliographic reference. It specifies where to find the component in which it appears within the immediately preceding component of a different level.

In the following example, Schacter's article Iolaos appeared on pages 64 to 70 of a volume entitled Herakles to Poseidon, which was itself the second of a four volumes published together under the title Cults of Boitia; this last title constituted the 38th volume in the series of Bulletin of the Institute of Classical Studies Supplements:
<biblStruct>
 <analytic>
  <author>Albert Schachter</author>
  <title level="a">Iolaos</title>
 </analytic>
 <monogr>
  <title level="m">Herakles to Poseidon</title>
  <imprint>
   <date>1986</date>
  </imprint>
  <biblScope unit="page">64-70</biblScope>
 </monogr>
 <monogr>
  <title level="m">Cults of Boiotia</title>
  <imprint>
   <pubPlace>London</pubPlace>
  </imprint>
  <extent>4 vols.</extent>
  <biblScope unit="part">2</biblScope>
 </monogr>
 <series>
  <title level="s">Bulletin of the Institute of Classical Studies
     Supplements</title>
  <biblScope unit="volume">38</biblScope>
 </series>
</biblStruct>
In the following example, the article cited has been published twice, once in a journal (where it appeared in volume 40, on pages 3 -46 of the issue of October 1986) and once as a free-standing item, which appeared as number 11 of a German language series.
<biblStruct>
 <analytic>
  <author>
   <persName>
    <surname>Thaller</surname>
    <forename>Manfred</forename>
   </persName>
  </author>
  <title level="a">A Draft Proposal for a Standard for the
     Coding of Machine Readable Sources</title>
 </analytic>
 <monogr>
  <title level="j">Historical Social Research</title>
  <imprint>
   <date when="1986-10">October 1986</date>
  </imprint>
  <biblScope unit="volume">40</biblScope>
  <biblScope unit="page" from="3" to="46">3-46</biblScope>
 </monogr>
 <monogr>
  <title level="m">Modelling Historical Data:
     Towards a Standard for Encoding and
     Exchanging Machine-Readable Texts</title>
  <editor>
   <persName>
    <forename>Daniel</forename>
    <forename full="init">I.</forename>
    <surname>Greenstein</surname>
   </persName>
  </editor>
  <imprint xml:lang="de">
   <pubPlace>St. Katharinen</pubPlace>
   <publisher>Max-Planck-Institut für Geschichte
       In Kommission bei
       Scripta Mercaturae Verlag</publisher>
   <date when="1991"/>
  </imprint>
 </monogr>
 <series xml:lang="de">
  <title level="s">Halbgraue Reihe
     zur Historischen Fachinformatik</title>
  <respStmt>
   <resp>Herausgegeben von</resp>
   <name type="person">Manfred Thaller</name>
   <name type="org">Max-Planck-Institut für Geschichte</name>
  </respStmt>
  <title level="s">Serie A: Historische Quellenkunden</title>
  <biblScope unit="volume">11</biblScope>
 </series>
</biblStruct>

The practice of analytic vs. monographic citation, as described here, should be distinguished from the practice of including within one citation a reference to another work, which the encoder considers to be related to in some way: see further 3.12.2.7 Related Items below.

If an identifier is available for the analytic item, it should be represented by means of an idno element placed within the analytic element, as in the following example where a DOI (Digital Object identifier) is supplied for the article in question.

<biblStruct>
 <analytic>
  <author>
   <forename>James</forename>
   <forename>H.</forename>
   <surname>Coombs</surname>
  </author>
  <author>
   <forename>Allen</forename>
   <surname>Renear</surname>
  </author>
  <author>
   <forename>Steven</forename>
   <forename>J.</forename>
   <surname>DeRose</surname>
  </author>
  <title level="a">Markup Systems and The Future of Scholarly Text
     Processing</title>
  <idno type="DOI">10.1145/32206.32209</idno>
  <ref type="url">http://xml.coverpages.org/coombs.html</ref>
 </analytic>
 <monogr>
  <title level="j">Communications of the ACM</title>
  <imprint>
   <date>1987</date>
  </imprint>
  <biblScope unit="volume">30</biblScope>
  <biblScope unit="issue">11</biblScope>
  <biblScope unit="page">933–947</biblScope>
 </monogr>
</biblStruct>

Punctuation must not appear between the elements within a structured bibliographic entry encoded with biblStruct or biblFull, unless it is contained within the elements it delimits. When (as in most of the examples in this chapter) entries are encoded without any inter-element punctuation, they can be usually be processed more easily by rendering systems able to output bibliographic references in any of several styles.

Within a bibl however, it is possible and often convenient to include punctuation.
<bibl xml:id="NELSON_80">
 <author>
  <persName>
   <surname>Nelson</surname>,
  <forename>T.</forename>
   <forename>H.</forename>
  </persName>
 </author>
 <date when="1980">1980</date>.
<title level="a">Replacing the printed word: a complete literary
   system</title>. In <title level="m">Information Processing '80: Proceedings of the
   IFIPS Congress, October 1980</title>,
ed.
<editor>
  <persName>
   <forename>Simon</forename>
   <forename>H.</forename>
   <surname>Lavington</surname>
  </persName>
 </editor>,
<biblScope unit="page">1013-23</biblScope>.
<pubPlace>Amsterdam</pubPlace>: <publisher>North-
   Holland</publisher>. (<note>Apparently a draft of section 4 of
 <ref target="#NELSON_88">
   <title level="m">Literary
       Machines</title>
  </ref>.</note>)

</bibl>
This example shows the components sequenced and punctuated according to the Chicago style, with all the relevant data items marked up appropriately. This markup approach can provide easy rendering, if only one styleguide is targeted, or an original source document uses a specific styleguide, while still allowing for automated recovery of key data items such as names of authors, titles etc.
3.12.2.2 Titles, Authors, and Editors

Bibliographic references typically include the title of the work being cited and the names of those intellectually responsible for it. For articles in journals or collections, such statements should appear both for the analytic and for the monographic level. The following elements are provided for tagging such elements:

  • title (title) 다양한 종류의 작업에 대한 전체 제목을 제공한다.
  • author (author) 참고문헌에 작가, 단독 저자, 공동 저자의 이름을 포함한다; 서지 항목의 책임에 관한 1차적 진술.
  • editor 서지 항목의 책임에 관한 2차적 진술, 예를 들어, 편집, 번역 등의 작업을 한 편집, 개인, 기관, 또는 기구의 이름
  • respStmt (책임성 진술) 텍스트, 편집, 녹음 또는 총서의 지적 내용에 대한 책임성 진술을 제시한다. 여기에서 작가, 편집자 등에 대한 특별한 요소는 충분치 않거나 적용되지 않는다.
  • resp (책임성) 개인의 지적 책임성에 관한 특성을 기술하는 구를 포함한다.
  • name (이름, 고유명사) 고유명사 또는 명사구를 포함한다.
  • meeting 회의에서 배포된 항목 또는 회의에서 산출된 출판물의 표제 및 서문에 대한 서지적 설명으로 사용된 경우 회의 또는 학술회의의 공식적 설명을 포함한다.
  • sponsor (sponsor) 후원 조직 또는 기관의 이름을 명시한다.
  • funder (재정 지원 조직체) 프로젝트 또는 텍스트의 재정 지원 책임을 지는 개인, 기관, 조직의 이름을 명시한다.
  • distributor (distributor) 텍스트 배포 권한을 갖는 개인 또는 기관의 이름을 제시한다.
  • principal (책임 연구자) 전자 텍스트 생성에 대한 책임을 지는 책임 연구자의 이름을 제시한다.

The elements author, editor, respStmt, meeting, sponsor, funder, and principal are the default members of the model.respLike class, a subclass of the model.biblPart class to which the constituents of the bibl element belong.

In bibliographic references, all titles should be tagged as such, whether analytic, monographic, or series titles. The single element title is used for all these cases. When it appears directly within an analytic, monogr, or series element, title is interpreted as belonging to the appropriate level. However, it is recommended that the level attribute be used to signal this explicitly.

It is a semantic error to give a value for the level attribute which is inconsistent with the context. The level value a implies the analytic level; the values m, j, and u imply the monographic level; the value s implies the series level. Note, however, that the semantic error occurs only if the nested title is directly enclosed by the analytic, monogr, or series element; if it is enclosed only indirectly (i.e., nested more deeply), no semantic error need be present. For example, the analytic title may contain a monographic title, as in the following example:
<biblStruct>
 <analytic>
  <author ref="http://id.loc.gov/authorities/names/no2001067434">
   <persName>
    <forename>Lucy</forename>
    <forename>Allen</forename>
    <surname>Paton</surname>
   </persName>
  </author>
  <title>Notes on Manuscripts of the
  <title level="m" xml:lang="fr">Prophécies de Merlin</title>
  </title>
 </analytic>
 <monogr>
  <title level="j">PMLA</title>
  <imprint>
   <date>1913</date>
  </imprint>
  <biblScope unit="volume">8</biblScope>
  <biblScope unit="page">122</biblScope>
 </monogr>
</biblStruct>
In this case, the analytic title ‘Notes on Manuscripts of the Prophécies de Merlin’ needs no level attribute because it is directly contained by an analytic element; the monographic title contained within it, ‘Prophécies de Merlin’, is not semantically erroneous because it is not directly contained by the analytic element.

In some bibliographic applications, it may prove useful to distinguish main titles from subordinate titles, parallel titles, etc. The type attribute is provided to allow this distinction to be recorded.

The following reference, from a national standard for bibliographic references, illustrates this type of analysis with its distinction between main and subordinate titles. Note that this uses the more flexible bibl, rather than the structured biblStruct element: consequently, there is no requirement to tag all the components of the reference (notably the authors).
<bibl>Saarikoski, Pirkko-Liisa, and Paavo Suomalainen,
<title level="a" type="main">Studies on the physiology of
   the hibernating hedgehog, 15</title>
 <title level="a" type="sub">Effects of seasonal
   and temperature changes on the in vitro glycerol release from
   brown adipose tissue</title>
 <title level="j">Ann. Acad. Sci. Fenn., Ser. A4</title>
 <date>1972</date>
 <biblScope unit="volume">187</biblScope>
 <biblScope unit="page" to="4">1-4</biblScope>
</bibl>
Slightly more complex is the distinction made below among main, subordinate, and parallel titles, in an example from the same source (p. 63). The punctuation and the bibliographic analysis are those given in ANSI Z39.29-1977; the punctuation is in the style prescribed by the International Standard Bibliographic Description (ISBD).21 Again, it is only because this example uses bibl rather than biblStruct, that specific punctuation may be included between the component elements of the reference.
<bibl>Tchaikovsky, Peter Ilich.
<title level="m" type="main">The swan lake ballet</title>
= <title level="m" type="parallel"
  xml:lang="fr">Le lac des cygnes</title>
: <title level="m" type="sub" xml:lang="fr">grand ballet en 4 actes</title>
: <title level="m" type="sub">op. 20</title>
[Score].
New York: Broude Brothers; [1951] (B.B. 59). vi, 685 p.</bibl>

The elements author and editor have fairly obvious significance for printed books and articles; for other kinds of bibliographic items their proper usage may be less obvious. The author element should be used for the person or agency with primary responsibility for a work's intellectual content, and the element editor for other people or agencies with some responsibility for that content, whether or not they are called ‘editor’. An organization such as a radio or television station is usually accounted ‘author’ of a broadcast, for example, while the author of a government report will usually be the agency which produced it. A translator, illustrator, or compiler, may however be marked by means of the editor element, optionally using the role attribute to specify the nature of their responsibility more exactly.

Many bibliographic and Linked Data applications require disambiguation of author names using unique identifiers. Both the author and editor elements may contain one or more idno elements, to supply such identifiers. Alternatively, if only a single identifier is to be recorded, the key or ref attribute may be used, as further discussed in 3.6.1 Referring Strings.

<bibl>
 <author ref="http://viaf.org/viaf/95301405">John Warrack</author>. „Es waren seine letzten Töne!“
In <editor ref="http://viaf.org/viaf/263865979">Joachim Veit</editor>
and <editor ref="http://viaf.org/viaf/268371810">Frank Ziegler</editor> eds. Weber-Studien Bd. 3, Mainz (1996), pp.300–317

</bibl>

For anyone else with responsibility for the work, the respStmt element should be used. The nature of the responsibility is indicated by means of a resp element, and the person, organization, etc. responsible by a name, persName, or orgName element. Strings such as ‘unknown’ may be encoded using the rs element. A respStmt should comprise either at least one of the four naming elements (name, persName, orgName, or rs) followed by one or more resp elements, or at least one resp element followed by one or more of the four naming elements.

Examples of secondary responsibility of this kind include the roles of illustrator, translator, encoder, and annotator. The respStmt element may also be used for editors, if it is desired to record the specific terms in which their role is described.

Examples of author and editor may be found in sections 3.12.1 Methods of Encoding Bibliographic References and Lists of References, and 3.12.2.1 Analytic, Monographic, and Series Levels; wherever author and editor may occur, the respStmt element may also occur. When one of these elements precedes or immediately follows a title, it applies to that title; when it follows an edition element or occurs within an edition statement, it applies to the edition in question.

In this example, the respStmt elements apply to the work as a whole, not merely to the first edition:
<bibl>
 <author>Lominandze, DG</author>.
<title level="m">Cyclotron waves in plasma</title>.
<respStmt>
  <resp>Translated by</resp>
  <name>AN. Dellis</name>
 </respStmt>;
<respStmt>
  <resp>edited by</resp>
  <name>SM. Hamberger</name>
 </respStmt>.
<edition>1st ed.</edition>
 <pubPlace>Oxford</pubPlace>:
<publisher>Pergamon Press</publisher>,
<date>1981</date>.
<extent>206 p.</extent>
 <title level="s">International series in natural philosophy</title>.
<note place="inline">Translation of:
 <title xml:lang="ru-Latn" level="m">Ciklotronnye volny v
     plazme</title>.
 <idno type="ISBN">0-08-021680-3</idno>.
 </note>
</bibl>

This example retains the original punctuation and editorial conventions of the source (ISO 690: 1987) and is therefore encoded using the bibl element.

In the following example, by contrast, the respStmt element applies to the edition, and not to the collection per se (Moser and Tervooren were not responsible for the first thirty-five printings). As is permissible within a biblStruct element, the component elements have been reordered from their appearance on the title page of the volume in order to ensure the correct relationship of the collection title, the edition statement, and the statement of responsibility.
<biblStruct>
 <monogr xml:lang="de">
  <title level="m">Des Minnesangs Frühling</title>
  <note place="inline">Mit 1 Faksimile</note>
  <edition>36., neugestaltete und erweiterte Auflage</edition>
  <respStmt>
   <resp>Unter Benutzung der Ausgaben von <name>Karl
         Lachmann</name> und <name>Moriz Haupt</name>, <name>Friedrich
         Vogt</name> und <name>Carl von Kraus</name> bearbeitet von</resp>
   <name>Hugo Moser</name>
   <name>Helmut Tervooren</name>
  </respStmt>
  <imprint>
   <pubPlace>Stuttgart</pubPlace>
   <publisher>S. Hirzel Verlag</publisher>
   <date>1977</date>
  </imprint>
  <biblScope unit="volume">I Texte</biblScope>
 </monogr>
</biblStruct>
The party with a particular responsibility for the intellectual content may vary over time. Likewise, a given individal's responsibility or role may change over time. These situations may be recorded with the respStmt element. For example, the following could be used when one proofreader took over for another.
<respStmt>
 <resp>proofreading</resp>
 <persName from="1994-02" to="1994-05">Ashley Cross</persName>
 <persName from="1994-06" to="1994-10">Loren Noveck</persName>
</respStmt>
The following example records the fact that one individual had two distinctly different intellectual responsibilities at different times.
<respStmt>
 <persName>Erica Dillon</persName>
 <resp when="2000-08">annotated uncredited citations</resp>
 <resp when="2001-03">encoded named entities</resp>
</respStmt>
Another form of ‘responsibility’ arises when a work is published as the outcome of a conference, workshop or similar meeting. The meeting element may be used to supply this information, as in the following example:
<biblStruct>
 <monogr>
  <title level="m">Proceedings of a workshop on corpus resources</title>
  <respStmt>
   <resp>Programme Organizer</resp>
   <name>Geoffrey Leech</name>
  </respStmt>
  <meeting>DTI Speech and Language Technology Club meeting, 3-4
     January 1990, Wadham College, Oxford</meeting>
  <imprint>
   <pubPlace>Oxford</pubPlace>
  </imprint>
 </monogr>
</biblStruct>
3.12.2.3 Document Identifiers
Many bibliographic references include identifiers for a work to help with precise identification of an appropriate document. For example, a book in the Short Title Catalogue could be referenced with its STC number:
<biblStruct>
 <monogr>
  <author>
   <forename>John</forename>
   <surname>Downame</surname>
  </author>
  <title type="short">Foure treatises tending to disswade all Christians from foure no lesse hainous then common sinnes</title>
  <idno type="stc2ndEd">7141</idno>
  <imprint>
   <pubPlace>At London</pubPlace>
   <publisher>Imprinted by Felix Kyngston, for William Welby, and are to be sold at his shop in Pauls Church-yard at the signe of the Greyhound</publisher>
   <date when="1609">1609</date>
  </imprint>
 </monogr>
</biblStruct>

However, some bibliographic references actually require identifiers of various types because they do not include a statement of the title and the names of those intellectually responsible for it. The following elements may be used for such purposes:

  • orgName (조직명) 조직명을 포함한다.
  • idno (식별 숫자) 서지 정보 항목을 식별하기 위해 사용되는 표준 또는 비표준 숫자를 제시한다.
  • classCode (분류 부호) 표준 분류 체계에서 이 텍스트에 대하여 사용된 분류 부호를 포함한다.
  • date (date) 다양한 형식의 날짜를 포함한다.

For example, a citation to a patent typically includes a country or organization code (a two-character code identifying a patent authority) and a serial number for the patent (whose structure varies by patent authority). The citation might also contain a kind code (which characterizes a particular publication for the patent and which corresponds to a specific stage in the patent procedure) and the date when the patent was filed with or published by the issuing authority. For bibliographic references to patents, the above elements may be used as follows:

  • orgName, within authority, may be used to contain the code of the patent authority. The type attribute may be used to specify the type of patent authority (such as a national patent office or a supra-national patent organization).
  • idno may be used to contain the serial number assigned by the corresponding patent authority.
  • classCode may be used to contain the kind code of the patent document.
  • date may be used to contain the date of the patent document. The type attribute may be used to specify whether this corresponds to the filing date of a patent application or the publication date of a patent publication.
The following reference illustrates an encoding for a patent publication which might be cited in print as ‘United States patent US 6,885,550 B1, issued April 26, 2005’:
<biblStruct type="patent"
 status="publication">
 <monogr>
  <authority>
   <orgName type="national">US</orgName>
  </authority>
  <idno type="docNumber">6885550</idno>
  <imprint>
   <classCode scheme="http://www.uspto.gov/">B1</classCode>
   <date type="publicationDate"
    when="2005-04-26">April 26, 2005</date>
  </imprint>
 </monogr>
</biblStruct>
3.12.2.4 Imprint, Size of a Document, and Reprint Information

By imprint is meant all the information relating to the publication of a work: the person or organization by whose authority and in whose name a bibliographic entity such as a book is made public or distributed (whether a commercial publisher or some other organization), the place and the date of publication. It may also include a full address for the publisher or organization. A full bibliographic references will usually also specify the number of pages in a print publication (or equivalent information for non-print materials), and possibly also the specific location of the material being cited within its containing publication. The following elements are provided to hold this information:

  • imprint groups information relating to the publication or distribution of a bibliographic item.
  • address (address) 예를 들어, 출판사, 기관, 개인의 우편 주소를 포함한다.
  • pubPlace (출판지) 서지 대상이 출판된 장소명을 포함한다.
  • publisher (publisher) 서지 항목의 출판이나 배포에 책임이 있는 기구명을 제시한다.
  • date (date) 다양한 형식의 날짜를 포함한다.
  • extent (extent) 전달 매체, 즉, 디지털 또는 비디지털로 저장된 텍스트의, 다양한 단위로 명시되는, 대략적 규모를 기술한다.
  • idno (식별 숫자) 서지 정보 항목을 식별하기 위해 사용되는 표준 또는 비표준 숫자를 제시한다.

Members of the model classes model.imprintPart and model.dateLike may appear inside an imprint element in a specific location within a biblStruct, or alternatively, they may appear alongside any other bibliographic component inside a bibl.

  • model.imprintPart 간기 내에 나타날 수 있는 서지 요소를 모아 놓는다.
    biblScope(인용 범위) 예를 들어 페이지수의 목록 또는 작품의 이름 붙은 하위 성분으로, 문헌 참조의 범위를 정의한다.
    distributor(distributor) 텍스트 배포 권한을 갖는 개인 또는 기관의 이름을 제시한다.
    publisher(publisher) 서지 항목의 출판이나 배포에 책임이 있는 기구명을 제시한다.
    pubPlace(출판지) 서지 대상이 출판된 장소명을 포함한다.
  • model.dateLike 시간 표현을 포함하는 요소를 모아 놓는다.
    date(date) 다양한 형식의 날짜를 포함한다.
    time(time) 어떤 형식의, 하루의 시간을 정의하는 구를 포함한다.

For bibliographic purposes, usually only the place (or places) of publication are required, possibly including the name of the country, rather than a full address; the element pubPlace is provided for this purpose. Where however the full postal address is likely to be of importance in identifying or locating the bibliographic item concerned, it may be supplied and tagged using the address element described in section 3.6.2 Addresses. Alternatively, if desired, the rs or name elements described in section 3.6.1 Referring Strings may be used; this involves no claim that the information given is either a full address or the name of a city.

The name of the publisher of an item should be marked using the publisher element even if the item is made public (‘published’) by an organization other than a conventional publisher, as is frequently the case with technical reports:
<biblStruct>
 <monogr>
  <author>Nicholas, Charles K.</author>
  <author>Welsch, Lawrence A.</author>
  <title level="m">On the interchangeability of SGML and ODA</title>
  <idno type="NIST">NISTIR 4681</idno>
  <imprint>
   <pubPlace>Gaithersburg, MD</pubPlace>
   <publisher>National Institute of Standards and Technology
   </publisher>
   <date when="1992-01">January 1992</date>
  </imprint>
  <extent>19 pp.</extent>
 </monogr>
</biblStruct>
and with dissertations:
<biblStruct>
 <monogr>
  <author>Hansen, W.</author>
  <title level="u">Creation of hierarchic text
     with a computer display</title>
  <idno type="ANL">ANL-7818</idno>
  <note place="inline">Ph.D. dissertation</note>
  <imprint>
   <publisher>Dept. of Computer Science, Stanford Univ.</publisher>
   <pubPlace>Stanford, CA</pubPlace>
   <date when="1971-06">June 1971</date>
  </imprint>
 </monogr>
</biblStruct>

In this second example, the idno element is used to provide the identifier allocated to the thesis by the Argonne National Laboratory. Since it applies to the monographic element, the idno should be provided as a direct child of the monogr element, rather than elsewhere in the biblStruct element.

The specialist elements publisher and distributor are provided to cover the most common roles related to the production and distribution of a bibliographical item, but other roles such as printer and bookseller may also need to be encoded, and respStmt is available inside imprint for this purpose.

When an item has been reprinted, especially reprinted without change from a specific earlier edition, the reprint may appear in a monogr element with only the imprint and other details of the reprint. In the following example, a microform reprint has been issued without any change in the title or authorship. The series statement here applies only to the second monogr element.
<biblStruct>
 <monogr>
  <author>Shirley, James</author>
  <title type="main">The gentlemen of Venice</title>
  <title type="sub">a tragi-comedie presented at the private
     house in Salisbury Court by Her Majesties servants</title>
  <note place="inline">[Microform]</note>
  <imprint>
   <pubPlace>London</pubPlace>
   <publisher>H. Moseley</publisher>
   <date>1655</date>
  </imprint>
  <extent>78 p.</extent>
 </monogr>
 <monogr>
  <imprint>
   <pubPlace>New York</pubPlace>
   <publisher>Readex Microprint</publisher>
   <date>1953</date>
  </imprint>
  <extent>1 microprint card, 23 x 15 cm.</extent>
 </monogr>
 <series>
  <title level="s">Three centuries of drama: English, 1642–1700</title>
 </series>
</biblStruct>
This encoding can be extended to the case of patent documents, where the same patent application is published, with or without changes, at different stages of the patenting procedure. In this case, the kind code and, optionally, the publication date characterize different publications of the same patent application during the procedure. For example:
<biblStruct type="patent"
 status="publication">
 <monogr>
  <authority>
   <orgName type="national">EP</orgName>
  </authority>
  <idno type="docNumber">1558513</idno>
  <imprint>
   <classCode scheme="http://www.epo.org/">A1</classCode>
   <date type="publicationDate"
    when="2005-08-03"/>
  </imprint>
 </monogr>
 <monogr>
  <imprint>
   <classCode scheme="http://www.epo.org/">B1</classCode>
   <date type="publicationDate"
    when="2009-09-09"/>
  </imprint>
 </monogr>
</biblStruct>

The above bibliographic reference discloses different publications of the patent EP1558513 during the patenting procedure. The first publication from 3 August 2005 has the kind code "A1" indicating that it is a published patent application comprising the European search report issued after carrying out the search at the European Patent Office, whereas the second publication from 9 September 2009 has the kind code "B1" indicating that it was published after the patent application has been granted.

An alternative way of handling the above situations would be to use the relatedItem element described in section 3.12.2.7 Related Items below.

3.12.2.5 Scopes and Ranges in Bibliographic Citations

Many bibliographic citations contain data limiting the citation to one or more volumes, issues, or pages, or to a name or number of a subdivison of the host work. These come in two varieties:

  • the scope of a bibliographic reference (encoded using biblScope)
  • the range of a work cited (encoded using citedRange)

Where it is desired to distinguish different classes of such information (volume number, page number, chapter number, etc.), the unit attribute may be used with any convenient typology (see the element definitions for biblScope and citedRange for some suggested values).

A scope of a bibliographic reference defines that the entire work cited may be found in particular volumes, issues, pages, etc. For example:
<biblStruct>
 <analytic>
  <author>
   <persName>
    <surname>Wrigley</surname>
    <forename full="init">E.</forename>
    <forename full="init">A.</forename>
   </persName>
  </author>
  <title level="a">Parish registers and the historian</title>
 </analytic>
 <monogr>
  <author>
   <persName>
    <surname>Steel</surname>
    <forename full="init">D.</forename>
    <forename full="init">J.</forename>
   </persName>
  </author>
  <author>
   <persName>
    <surname>Steel</surname>
    <forename full="init">A.</forename>
    <forename full="init">E.</forename>
    <forename full="init">F.</forename>
   </persName>
  </author>
  <title level="m">General sources of births, marriages and deaths before 1837</title>
  <imprint>
   <pubPlace>London</pubPlace>
   <publisher>Society of Genealogists</publisher>
   <date when="1968"/>
  </imprint>
  <biblScope unit="page" from="155" to="167">155–167</biblScope>
 </monogr>
 <series>
  <title level="s">National index of parish registers</title>
  <biblScope unit="volume">1</biblScope>
 </series>
</biblStruct>
The unit attribute on biblScope is optional: both the following are legal examples:
<biblStruct>
 <analytic>
  <author>Boguraev, Branimir</author>
  <author>Neff, Mary</author>
  <title level="a">Text Representation, Dictionary Structure,
     and Lexical Knowledge</title>
 </analytic>
 <monogr>
  <title level="j">Literary &amp; Linguistic Computing</title>
  <imprint>
   <date>1992</date>
  </imprint>
  <biblScope unit="volume">7</biblScope>
  <biblScope unit="issue">2</biblScope>
  <biblScope unit="page">110-112</biblScope>
 </monogr>
</biblStruct>
<biblStruct>
 <analytic>
  <author>Chesnutt, David</author>
  <title level="a">Historical Editions in the States</title>
 </analytic>
 <monogr>
  <title level="j">Computers and the Humanities</title>
  <imprint>
   <date when="1991-12">(December, 1991):</date>
  </imprint>
  <biblScope>25.6</biblScope>
  <biblScope from="377" to="380">377–380</biblScope>
 </monogr>
</biblStruct>
On the other hand, a cited range encodes that the author cited only the portion defined by this range. For example, a footnote following a quotation from page 378 of Historical Editions in the States that includes a full bibliographic reference would be encoded using biblStruct as follows:
<biblStruct>
 <analytic>
  <author>Chesnutt, David</author>
  <title level="a">Historical Editions in the States</title>
 </analytic>
 <monogr>
  <title level="j">Computers and the Humanities</title>
  <imprint>
   <date when="1991-12">(December, 1991):</date>
  </imprint>
  <biblScope>25.6</biblScope>
  <biblScope unit="page" from="377" to="380">377–380</biblScope>
 </monogr>
 <citedRange>378</citedRange>
</biblStruct>
3.12.2.6 Series Information

Series information may (in bibl elements) or must (in biblStruct elements) be enclosed in a series element or (in a biblFull element) a seriesStmt element. The title of the series may be tagged <title level="s">, the volume number <biblScope unit="volume">, and responsibility statements for the series (e.g. the name and affiliation of the editor, as in the example in section 3.12.2.1 Analytic, Monographic, and Series Levels) may be tagged editor or respStmt. Any identifier associated with the series itself should be marked using the idno element.

3.12.2.7 Related Items

In bibliographic parlance, a related item is any bibliographic item which, though related to that being defined, is distinct from it. The distinction between analytic and monographic items made above may be thought of as a special case of this kind of ‘related’ item. More usually however, the term is applied to such items as translations, continuations, different versions, parts, etc.

The element relatedItem is provided as a means of documenting such associated items:

  • relatedItem 구성물이나 대체 버전과 같이 현 항목과 특정 방식으로 관련된 다른 서지 항목을 명시적 방식에 따라 포함하거나 지시한다.
In the following example, the first biblStruct describes a facsimile edition, and the second describes the work of which it is a facsimile. The relation between the facsimile and its source is represented by means of a relatedItem within the first description, which points to the description of the source.
<biblStruct xml:id="bibl03">
 <monogr>
  <author>Swinburne, Algernon Charles</author>
  <title level="m">Swinburne's <title level="m">Atalanta in Calydon</title>: A Facsimile of the
     First Edition</title>
  <editor>Georges Lafourcade</editor>
  <imprint>
   <pubPlace>London</pubPlace>
   <publisher>Oxford UP</publisher>
   <date>1930</date>
  </imprint>
 </monogr>
 <relatedItem type="otherEdition">
  <ref target="#bibl04"/>
 </relatedItem>
</biblStruct>
<biblStruct xml:id="bibl04">
 <monogr>
  <author> Swinburne, Algernon Charles</author>
  <title level="m">Atalanta in Calydon</title>
  <imprint>
   <pubPlace>London</pubPlace>
   <publisher>Edward Moxon</publisher>
   <date>1865</date>
  </imprint>
 </monogr>
</biblStruct>
The ref element in the above example could be replaced by the referenced biblStruct itself since a relatedItem may contain any form of bibliographic reference. For example, one of the examples quoted above might also be encoded as follows:
<biblStruct>
 <monogr>
  <author>Shirley, James</author>
  <title type="main">The gentlemen of Venice</title>
  <imprint>
   <pubPlace>New York</pubPlace>
   <publisher>Readex Microprint</publisher>
   <date>1953</date>
  </imprint>
  <extent>1 microprint card, 23 x 15 cm.</extent>
 </monogr>
 <series>
  <title level="s">Three centuries of drama: English, 1642–1700</title>
 </series>
 <relatedItem type="otherEdition">
  <biblStruct>
   <monogr>
    <author>Shirley, James</author>
    <title type="main" level="m">The gentlemen of Venice</title>
    <title type="sub" level="m">a tragi-comedie presented at the private
         house in Salisbury Court by Her Majesties servants</title>
    <imprint>
     <pubPlace>London</pubPlace>
     <publisher>H. Moseley</publisher>
     <date when="1655">1655</date>
    </imprint>
    <extent>78 p.</extent>
   </monogr>
  </biblStruct>
 </relatedItem>
</biblStruct>
The type attribute should be used to indicate the relationship between the bibliographic item and any relatedItem it contains or points to. The relationships may be transitive (for example translatedAs or reprintedFrom) or non-transitive (for example otherEdition). The subtype attribute may be used to provide a more detailed classification, where this is appropriate. Some further examples follow:
<biblStruct>
 <monogr>
  <author>Tolkien, J.R.R.</author>
  <title level="m">Den hobbit</title>
  <title type="sub">aus dem Engleschen iwwersat</title>
  <editor role="translator">Henry Wickens</editor>
  <imprint>
   <pubPlace>Esch-sur-Sûre</pubPlace>
   <publisher>Op der Lay S. àr. L</publisher>
   <date>2002</date>
  </imprint>
 </monogr>
 <relatedItem type="translatedFrom">
  <bibl>
   <author>Tolkien, J.R.R.</author>
   <title level="m">The Hobbit</title>.
  <publisher>Collins</publisher>
   <date>1997</date>
  </bibl>
 </relatedItem>
</biblStruct>
In this example, a full bibliographic description of the edition used as source for the translation is provided within the content of the relatedItem. Alternatively this might be provided by means of a link, in which case the relatedItem would be empty:
<relatedItem type="translatedFrom"
 target="http://www.example.com/bibliography.xml#TOLK97"/>
3.12.2.8 Notes and Statement of Language

Explanatory notes about the publication of unusual items, the form of an item (e.g. [Score] or [Microform]), or its provenance (e.g. translation of ...) may be tagged using the note element. The same element may be used for any descriptive annotation of a bibliographic entry in a database.

  • note (note) contains a note or annotation.
For example:
<bibl>
 <author>Coombs, James H., Allen H. Renear,
   and Steven J. DeRose.</author>
 <title level="a">Markup Systems and the Future of Scholarly
   Text Processing.</title>
 <title level="j">Communications of the ACM</title>
 <biblScope>30.11 (November 1987): 933–947.</biblScope>
 <note>Classic polemic supporting descriptive over procedural
   markup in scholarly work.</note>
</bibl>
The textLang element may be used to record information about the languages used within a bibliographic item.
  • textLang (텍스트 언어) (langUsage에 기술된 기술과 반대로) 원고에서 사용된 언어와 글 체계를 기술한다.
    mainLang(주요 언어) 원고에 사용된 주요 언어를 식별하는 부호를 제공한다.
    otherLangs(다른 언어) 원고에 사용된 다른 언어를 식별하는 하나 이상의 부호
This element can take the form of a simple note such as:
<textLang>Latin, with some glosses in Anglo-Saxon and French</textLang>
However, it is generally recommended where feasible to use the mainLang attribute to record the chief language of the bibliographic item, and optionally the otherLangs to identify other languages used in the work. For example:
<textLang mainLang="la" otherLangs="ang fr">Latin, with some glosses in Anglo-Saxon and French</textLang>

The mainLang and otherLangs attributes should both provide language identifiers in the same form as used for xml:lang as described at vi.1. Language Identification. Where additional detail is needed correctly to describe a language, or to discuss its deployment in a given text, this should be done using the langUsage element in the TEI header, within which individual language elements document the languages used: see 2.4.2 Language Usage.

A description, in French, of a work predominantly in German, but also with some Latin might have a textLang like the following:
<textLang xml:lang="fr" mainLang="de"
 otherLangs="la">allemand et latin</textLang>
For more information about the use of textLang in manuscript descriptions see: 10.6.6 Languages and Writing Systems.
3.12.2.9 Order of Components within References

The order of elements in bibl elements is not constrained.

In biblStruct elements, the analytic element, if it occurs, must come first, followed by one or more monogr and series elements, which may appear intermingled (as long as a monogr element comes first), and then zero or more of the following in any order: note, witDetail, idno, ptr, ref, relatedItem, and citedRange. Within analytic, the title(s), author(s), editor(s), and other statements of responsibility may appear in any order; it is recommended that all forms of the title be given together. Within monogr, the author, editor, and statements of responsibility may either come first or else follow the monographic title(s). Following these, the elements listed below, if present, must appear in the following order:

Within imprint, the elements allowed may appear in any order.

Finally, within the series information in a biblStruct, the sequence of elements is not constrained.

If more detailed structuring of a bibliographic description is required, the biblFull element should be used. This is not further described here, as its contents are essentially equivalent to those of the fileDesc element in the teiHeader, which is fully described in section 2.2 The File Description.

3.12.3 Bibliographic Pointers

References which are pointers to bibliographic items, of whatever kind, should be treated in the same way as other cross-references (see section 3.7 Simple Links and Cross-References). As discussed in that section, cross-referencing within TEI texts is in general represented by means of ptr or ref elements. A target attribute on these elements is used to supply an identifying value for the target of the cross-reference, which should be, in the case of bibliographic elements, a bibliographic reference of some kind. Where the form of the reference itself is unimportant, or may be reconstructed mechanically, or is not to be encoded, the ptr element is used, as in the following example:
As shown above (<ptr target="#NEL80"/>) ...
Where the form of the reference is important, or contains additional qualifying information which is to be kept but distinguished from the surrounding text, the ref element should be used, as in the following example:
Nelson claims <ref target="#NEL80">(ibid, passim)</ref> ...
It may be important to distinguish between the short form of a bibliographic reference and some qualifying or additional information. The latter should not appear within the scope of the ref element when this is the case, as for example in an application concerned to normalize bibliographic references:
Nelson claims (<ref target="#NEL80">Nelson [1980]</ref> pages 13–37)
...
If it is desired to capture additional information like this in a short-form reference, then bibl may be used with the corresp attribute pointing to the full bibliographic reference:
Nelson claims (<bibl corresp="#NEL80">Nelson [1980] pages <biblScope unit="page" from="13" to="37">13–37</biblScope>
</bibl>) ...
The ref element may also be used to provide a reference to a copy of the bibliographic item itself, particularly if this is available online, as in the following example:
<biblStruct>
 <analytic>
  <author>
   <forename>Suzana</forename>
   <surname>Sukovic</surname>
  </author>
  <title level="a">Beyond the Scriptorium: The Role of the Library in Text
     Encoding</title>
  <ref type="url">http://www.dlib.org/dlib/january02/sukovic/01sukovic.html</ref>
 </analytic>
 <monogr>
  <title level="j">D-Lib</title>
  <imprint>
   <biblScope unit="volume">8</biblScope>
   <biblScope unit="issue">1</biblScope>
   <date>2002</date>
  </imprint>
 </monogr>
</biblStruct>
The ptr element may be used as a child element of biblStruct to refer to the online catalog record of this bibliographic item:
<biblStruct type="manifestation">
 <monogr>
  <author>
   <persName>
    <forename>Germain</forename>
    <surname>Brice</surname>
   </persName>
  </author>
  <title level="m">Description de la ville de Paris et de tout ce qu’elle contient de plus remarquable, par Germain Brice ; enrichie d’un nouveau plan et de figures dessinées et gravées correctement. 7e édition, revue et augmentée par l’auteur</title>
  <imprint>
   <date when="1717">1717</date>
   <pubPlace>Paris</pubPlace>
   <publisher>F. Fournier</publisher>
  </imprint>
  <extent>In-12</extent>
 </monogr>
 <ptr type="catBnf"
  target="http://catalogue.bnf.fr/ark:/12148/cb30160624f/"/>
</biblStruct>

3.12.4 Relationship to Other Bibliographic Schemes

The bibliographic tagging defined here can capture the distinctions required by most bibliographic encoding systems; for the benefit of users of some commonly used systems, the following lists of equivalences are offered, showing the relationship of the markup defined here to the fields defined for bibliographic records in the Scribe, BibTeX, and ProCite systems.

Listed below are the equivalences between the various bibliographic fields defined for use in the Scribe and BibTeX systems of bibliographic databases and the elements defined in this module.22 Elements and structures available in the module defined here which have no analogues in Scribe and BibTeX are not noted.

address
tag as placeName or address
annote
tag as note
author
tag as author
booktitle
tag as <title level="m"> or title within monogr
chapter
tag as <biblScope unit="chap">
date
used only to record date entry was made in the bibliographic database; not supported
edition
tag as edition
editor
tag as editor or respStmt
editors
tag as multiple editor or respStmt elements
fullauthor
use the reg element, possibly inside a choice element, inside either an author or name
fullorganization
use the reg element, possibly inside a choice element, inside a <name type="org">
howpublished
tag as note, possibly using the form <note place="inline">
institution
used only for issuer of technical reports; tag as publisher
journal
tag as <title level="j"> or title within monogr
key
used to specify an alternate sort key for the bibliographic item, for use instead of author's or editor's name; not supported
meeting
tag as meeting or as note
month
use date; if the date is not in a trivially parseable form, use the when attribute to provide a normalized equivalent in one of the format from XML Schema Part 2: Datatypes Second Edition
note
tag as note
number
tag as <biblScope unit="issue"> or <biblScope unit="number">; for technical report numbers, use <idno type="docno">
organization
used only for sponsor of conference; use <name type="org"> within respStmt within meeting element
pages
tag as <biblScope unit="pp">
publisher
tag as publisher
school
used only for institutions at which thesis work is done; tag as publisher
series
tag as <title level="s"> or title within series
title
tag as title in appropriate context or with appropriate level value
volume
tag as <biblScope unit="volume">
year
tag as date; if the date is not in a trivially parseable form, use the when attribute to provide an ISO-format equivalent

3.13 Passages of Verse or Drama

The following elements are included in the core module for the convenience of those encoding texts which include mixtures of prose, verse and drama.

  • l (운문 시행) 미완성일 수도 있지만 운문의 하나의 시행을 포함한다.
  • lg (시행군) 예를 들어, 연, 후렴구, 운문 단락과 같이 형식적 단위로 기능하는 운문 행군을 포함한다.
  • sp (대화) 공연 텍스트에서 개별 대화 또는 산문이나 운문 텍스트에서 공연적 텍스트로 제시된 단락
  • speaker contains a specialized form of heading or label, giving the name of one or more speakers in a dramatic text or fragment.
  • stage (무대지시) 극적 텍스트나 부분 내에 무대지시를 포함한다.

Full details of other, more specialized, elements for the encoding of texts which are predominantly verse or drama are described in the appropriate chapter of part three (for verse, see the verse base described in chapter 6 Verse; for performance texts, see the drama base described in chapter 7 Performance Texts). In this section, we describe only the elements listed above, all of which can appear in any text, whichever of the three modes prose, verse, or drama may predominate in it.

3.13.1 Core Tags for Verse

Like other written texts, verse texts or poems may be hierarchically subdivided, for example into books or cantos. These structural subdivisions should be encoded using the general purpose div or div1 (etc.) elements described below in chapters 4 Default Text Structure and 6 Verse. The fundamental unit of a verse text is the verse line rather than the paragraph, however.

The l element is used to mark up verse lines, that is metrical rather than typographic lines. In some modern or free verse, it may be hard to decide whether the typographic line is to be regarded as a verse line or not, but the distinction is quite clear for verse following regular metrical patterns. Where a metrical line is interrupted by a typographic line break, the encoder may choose to ignore the fact entirely or to use the empty lb (line break) element discussed in 3.11 Reference Systems. By convention, the start of a metrical line implies the start of a typographic line; hence there is no need to introduce an lb tag at the start of every l element, but only at places where a new typographic line starts within a metrical line, as in the following example:
<l>Of Mans First Disobedience, and<lb/> the Fruit</l>
<l>Of that Forbidden Tree, whose<lb/> mortal tast</l>
<l>Brought Death into the World,<lb/> and all our woe,</l>
<l>With loss of Eden, till one greater Man</l>
<l>Restore us, and regain the blissful Seat...</l>
In the original copy text, the presence of an ornamental capital at the start of the poem means that the measure is not wide enough to print the first four lines on four lines; instead each metrical line occupies two typographic lines, with a break at the point indicated. Note that this encoding makes no attempt to preserve information about the whitespace or indentation associated with either kind of line; if regarded as essential, this information would be recorded using the rend or rendition attributes discussed in 1.3.1.1 Global Attributes.

The l element should not be used to represent typographic lines in non-verse materials: if the line-breaking points in a prose text are considered important for analysis, they should be marked with the lb element. Alternatively, a neutral segmentation element such as seg or ab may be used; see further discussion of these elements in chapter 16 Linking, Segmentation, and Alignment. The l element is a member of the model.lLike class, which is a subclass of the model.divPart class, along with elements from the model.pLike (paragraph-like) class.

In some verse forms, regular groupings of lines are regarded as units of some kind, often identified by a regular verse scheme. In stichic verse and couplets, groups of lines analogous to paragraphs are often indicated by indentation. In other verse forms, lines are grouped into irregular sequences indicated simply by whitespace. The lg or line group element may be used to mark any such grouping of elements from the model.lLike class. As a member of the att.typed class, the lg element bears the following attributes:
  • att.typed 요소의 분류 또는 하위분류에서 사용될 수 있는 속성을 제공한다.
    type다양한 분류 스키마 또는 유형을 사용해서 요소의 특성을 기술한다.
    subtype(subtype) 필요하다면 요소의 하위범주를 제시한다.
which may be used to further categorize the line group where this is felt desirable, as in the following example. This example also demonstrates the rend attribute to indicate whether or not a line is indented.
<lg>
 <l>Come fill up the Glass,</l>
 <l rend="indent">Round, round let it pass,</l>
 <l>'Till our Reason be lost in our Wine:</l>
 <l rend="indent">Leave Conscience's Rules</l>
 <l rend="indent">To Women and Fools,</l>
 <l>This only can make us divine.</l>
</lg>
<lg n="Chorus" type="refrain">
 <l>Then a Mohock, a Mohock I'll be,</l>
 <l>No Laws shall restrain</l>
 <l>Our Libertine Reign,</l>
 <l>We'll riot, drink on, and be free.</l>
</lg>
For some kinds of analysis, it may be useful to identify different kinds of line group within the same piece of verse. Such line groups may self-nest, in much the same way as the un-numbered div element described in chapter 4 Default Text Structure. For example:
<lg type="sonnet">
 <lg type="octet">
  <l>Thus speaks the Muse, and bends her brow severe:—</l>
  <l>“Did I, <name>Lætitia</name>, lend my choicest lays,</l>
  <l>And crown thy youthful head with freshest bays,</l>
  <l>That all the' expectance of thy full-grown year</l>
  <l>Should lie inert and fruitless? O revere</l>
  <l>Those sacred gifts whose meed is deathless praise,</l>
  <l>Whose potent charms the' enraptured soul can raise</l>
  <l>Far from the vapours of this earthly sphere!</l>
 </lg>
 <lg type="sestet">
  <l>Seize, seize the lyre! resume the lofty strain!</l>
  <l>'T is time, 't is time! hark how the nations round</l>
  <l>With jocund notes of liberty resound,—</l>
  <l>And thy own <name>Corsica</name> has burst her chain!</l>
  <l>O let the song to <name>Britain's</name> shores rebound,</l>
  <l rend="indent(-1)">Where Freedom's once-loved voice is heard,
     alas! in vain.”</l>
 </lg>
</lg>
It is often the case that verse line boundaries conflict with the boundaries of other structural elements. In the following example, the single verse line ‘A Workeman in't... welcome’ is interrupted by a stage direction:
<l>Thou fumblest <name>Eros</name>, and my Queenes a Squire</l>
<l>More tight at this, then thou: Dispatch. O Loue,</l>
<l>That thou couldst see my Warres to day, and knew'st</l>
<l>The Royall Occupation, thou should'st see</l>
<l part="I">A Workeman in't.</l>
<stage>Enter an Armed Soldier.</stage>
<l part="F">Good morrow to thee, welcome.</l>
In this encoding, the part attribute is used, as with div, to indicate that the last two l elements should be regarded as the initial and final parts of a single line, rather than as two lines.
The same technique may be used where verse lines are collected together into units such as verse paragraphs:
<lg n="6" type="para">
<!-- ... -->
 <l>Unprofitably travelling toward the grave,</l>
 <l>Like a false steward who hath much received</l>
 <l part="I">And renders nothing back.</l>
</lg>
<lg type="para" n="7">
 <l part="F">Was it for this</l>
 <l>That one, the fairest of all rivers, loved</l>
 <l>To blend his murmurs with my nurse's song,</l>
<!-- ... -->
</lg>
The part attribute may also be attached to an lg element to indicate that it is incomplete, for example because it forms part of a group that is divided between two speakers, as in the following example:
<sp>
 <speaker>First Voice</speaker>
 <lg type="stanza" part="I">
  <l>But why drives on that ship so fast</l>
  <l>Withouten wave or wind?</l>
 </lg>
</sp>
<sp>
 <speaker>Second Voice</speaker>
 <lg type="stanza" part="F">
  <l>The air is cut away before,</l>
  <l>And closes from behind.</l>
 </lg>
</sp>

For alternative methods of aligning groups of lines which do not form simple hierarchic groups, or which are discontinuous, see the more detailed discussion in chapter 16 Linking, Segmentation, and Alignment. For discussion of other elements and attributes specific to the encoding of verse, see chapter 6 Verse.

3.13.2 Core Tags for Drama

Like other written texts, dramatic and other performance texts such as cinema or TV scripts are often hierarchically organized, for example into acts and scenes. These structural subdivisions should be encoded using the general purpose div or div1 (etc.) elements described below in chapters 4 Default Text Structure and 7 Performance Texts. Within these divisions, the body of a performance text typically consists of speeches, often prefixed by a phrase indicating who is speaking, and occasionally interspersed with stage directions of various kinds.

In the following simple example, each speech consists of a single paragraph:
<div2 n="I.2" type="scene">
 <head>Scene 2.</head>
 <stage type="setting">Peachum, Filch.</stage>
 <sp>
  <speaker>FILCH.</speaker>
  <p>Sir, Black Moll hath sent word her Trial comes on in
     the Afternoon, and she hopes you will order Matters
     so as to bring her off.</p>
 </sp>
 <sp>
  <speaker>PEACHUM.</speaker>
  <p>Why, she may plead her Belly at worst; to my
     Knowledge she hath taken care of that Security.
     But, as the Wench is very active and industrious,
     you may satisfy her that I'll soften the Evidence.</p>
 </sp>
 <sp>
  <speaker>FILCH.</speaker>
  <p>Tom Gagg, sir, is found guilty.</p>
 </sp>
</div2>
In the following example, each speech consists of a sequence of verse lines, some of them being marked as metrically incomplete:
<div1 n="I" type="Act">
 <head>ACT I</head>
 <div2 n="1" type="Scene">
  <head>SCENE I</head>
  <stage rend="italic">Enter Barnardo and Francisco,
     two Sentinels, at several doors</stage>
  <sp>
   <speaker>Barn</speaker>
   <l part="Y">Who's there?</l>
  </sp>
  <sp>
   <speaker>Fran</speaker>
   <l>Nay, answer me. Stand and unfold yourself.</l>
  </sp>
  <sp>
   <speaker>Barn</speaker>
   <l part="I">Long live the King!</l>
  </sp>
  <sp>
   <speaker>Fran</speaker>
   <l part="M">Barnardo?</l>
  </sp>
  <sp>
   <speaker>Barn</speaker>
   <l part="F">He.</l>
  </sp>
  <sp>
   <speaker>Fran</speaker>
   <l>You come most carefully upon your hour.</l>
  </sp>
  <sp>
   <speaker>Barn</speaker>
   <l>'Tis now struck twelve. Get thee to bed, Francisco.</l>
  </sp>
  <sp>
   <speaker>Fran</speaker>
   <l>For this relief much thanks. 'Tis bitter cold,</l>
   <l part="I">And I am sick at heart.</l>
  </sp>
 </div2>
</div1>
In some cases, as here in the First Quarto of Hamlet, the printed speaker attributions need to be supplemented by use of the who attribute; again, the lines are marked as complete or incomplete:
<stage>Enter two Centinels.
<add place="margin">Now call'd <name xml:id="barnardo">Bernardo</name> &amp;
 <name xml:id="francisco">Francesco</name>.</add>
</stage>
<sp who="#francisco">
 <speaker>1.</speaker>
 <l part="Y">Stand: who is that?</l>
</sp>
<sp who="#barnardo">
 <speaker>2.</speaker>
 <l part="Y">Tis I.</l>
</sp>
<sp who="#francisco">
 <speaker>1.</speaker>
 <l>O you come most carefully vpon your watch,</l>
</sp>
<sp who="#barnardo">
 <speaker>2.</speaker>
 <l>And if you meete Marcellus and Horatio,</l>
 <l>The partners of my watch, bid them make haste.</l>
</sp>
<sp who="#francisco">
 <speaker>1.</speaker>
 <l part="Y">I will: See who goes there.</l>
</sp>
<stage>Enter Horatio and Marcellus.</stage>
By contrast with the preceding examples, the following encodes an early printed edition without making any assumption about which parts are prose or verse:
<div1 n="I" type="act">
 <div2 n="1" type="scene">
  <head rend="italic">Actus primus, Scena prima.</head>
  <stage rend="italic" type="setting">A tempestuous
     noise of Thunder and Lightning heard: Enter
     a Ship-master, and a Boteswaine.</stage>
  <sp>
   <speaker>Master.</speaker>
   <p>Bote-swaine.</p>
  </sp>
  <sp>
   <speaker>Botes.</speaker>
   <p>Heere Master: What cheere?</p>
  </sp>
  <sp>
   <speaker>Mast.</speaker>
   <p>Good: Speake to th' Mariners: fall
       too't, yarely, or we run our selues a ground,
       bestirre, bestirre. <stage type="move">Exit.</stage>
   </p>
  </sp>
  <stage type="move">Enter Mariners.</stage>
  <sp>
   <speaker>Botes.</speaker>
   <p>Heigh my hearts, cheerely, cheerely my harts: yare,
       yare: Take in the toppe-sale: Tend to th' Masters whistle:
       Blow till thou burst thy winde, if roome e-nough.</p>
  </sp>
 </div2>
</div1>
The sp and stage elements should also be used to mark parts of a text otherwise in prose which are presented as if they were dialogue in a play. The following example is taken from a 19th century novel in which passages of narrative and passages of dialogue are mixed within the same chapter:
<sp>
 <speaker>The reverend Doctor Opimian</speaker>
 <p>I do not think I have named a single unpresentable fish.</p>
</sp>
<sp>
 <speaker>Mr Gryll</speaker>
 <p>Bream, Doctor: there is not much to be said for bream.</p>
</sp>
<sp>
 <speaker>The Reverend Doctor Opimian</speaker>
 <p>On the contrary, sir, I think there is much to be said for him.
   In the first place ...</p>
 <p>Fish, Miss Gryll — I could discourse to you on fish by the
   hour: but for the present I will forbear ...</p>
</sp>
<sp>
 <speaker>Lord Curryfin</speaker>
 <stage>(after a pause).</stage>
 <p>
  <q>Mass</q> as the second grave-digger says
   in <title>Hamlet</title>, <q>I cannot tell.</q>
 </p>
</sp>
<p>A chorus of laughter dissolved the sitting.</p>
주석
11
Although the way in which a spoken text is performed, (for example, the voice quality, loudness, etc.) might be regarded as analogous to ‘highlighting’ in this sense, these Guidelines recommend distinct elements for the encoding of such ‘highlighting’ in spoken texts. See further section 8.3.6 Shifts.
↵
12
The Oxford English Dictionary documents the phrase to come down in the sense ‘to bring or put down; esp. to lay down money; to make a disbursement’ as being in use, mostly in colloquial or humorous contexts, from at least 1700 to the latter half of the 19th century.
↵
13
Taken from Wikipedia.
↵
14
In some contexts, the term regularization has a narrower and more specific significance than that proposed here: the reg element may be used for any kind of regularization, including normalization, standardization, and modernization.
↵
15
The datatypes are taken from the W3C Recommendation XML Schema Part 2: Datatypes Second Edition. The permitted datatypes are: There is one exception: these Guidelines permit a time to be expressed as only a number of hours, or as a number of hours and minutes, as per ISO 8601:2004 section 4.2.2.3 and 4.3.3. The W3C time and dateTime datatypes require that the minutes and seconds be included in the normalized value if they are to be correctly processed for example when sorting.
↵
17
Many encoders find it convenient to retain the line breaks of the original during data entry, to simplify proofreading, but this may be done without inserting a tag for each line break of the original.
↵
18
A check digit is computed from the value of an identifier and appended to the value itself. If the identifier is changed, the check digit would therefore invalidate it.
↵
19
For example, to distinguish London as an author's name from London as a place of publication or as a component of a title.
↵
20
Among the bibliographic software systems and subsystems consulted in the design of the biblStruct structure were BibTeX, Scribe, and ProCite. The distinctions made by all three may be preserved in biblStruct structures, though the nature of their design prevents a simple one-to-one mapping from their data elements to TEI elements. For further information, see section 3.12.4 Relationship to Other Bibliographic Schemes.
↵
21
The analysis is not wholly unproblematic: as the text of the standard points out, the first subordinate title is subordinate only to the parallel title in French, while the second is subordinate to both the English main title and the French parallel title, without this relationship being made clear, either in the markup given in the example or in the reference structure offered by the standard.
↵
22
The BibTeX scheme is intentionally compatible with that of Scribe, although it omits some fields used by Scribe. Hence only one list of fields is given here.
↵

[English] [Deutsch] [Español] [Italiano] [Français] [日本語] [한국어] [中文]

TEI Consortium | 피드백

TEI Guidelines Version 4.2.2. Last updated on 9th April 2021, revision 609a109b1. This page generated on 2021-04-09T18:44:29Z.